public inbox for gentoo-council@lists.gentoo.org
 help / color / mirror / Atom feed
From: Roy Bamford <neddyseagoon@gentoo.org>
To: gentoo-council@lists.gentoo.org
Subject: Re: [gentoo-council] Vote: What next?
Date: Tue, 20 May 2008 22:01:46 +0100	[thread overview]
Message-ID: <1211317312.11979.1@spike> (raw)
In-Reply-To: <20080520203151.GC9736@comet> (from dberkholz@gentoo.org on Tue May 20 21:31:51 2008)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2008.05.20 21:31, Donnie Berkholz wrote:

[snip]

> To get some movement here, I'd like to get a concrete response from
> the council in this thread for how we should proceed. Here's some 
> options that have been mentioned:
> 
>   1) Have an election now;

After a week, I don't see how the council can do anything else.

> 
>   2) Hold a 1-week vote asking all devs whether we should have
> elections;

A vote about a vote seems like wasting time if you don't get the answer 
you want.
 
>   3) Say that last week's nonmeeting didn't count for any of these 
>      reasons: it was (a) poorly announced, (b) not voted on by a
> council 
>      majority or (c) not a regularly scheduled meeting; or

Too late.

> 
>   4) Something else. (What?)
> 
> Which one do you prefer?

Whatever you do you will upset someone. Its only 6 weeks until the 
normal election process kicks off anyway, so may as well go for it 
early and add 'fix GLEP 39' to your manifestos.

> 
> Thanks,
> Donnie
> -- 
> gentoo-council@lists.gentoo.org mailing list
> 
 
I hope you all stand again. Its the GLEP that's broken, not the council 
but to gain a clear mandate to fix it, it looks like you have to go to 
the electorate.

- -- 
Regards,

Roy Bamford
(NeddySeagoon) a member of
gentoo-ops
forum-mods
treecleaners
trustees
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkgzPEAACgkQTE4/y7nJvauhYwCePNPvZZuTbho17H7lE68FLsaj
c0oAmwafhhiOGItXWa5p/aNLgq7LCHCL
=19r9
-----END PGP SIGNATURE-----

--
gentoo-council@lists.gentoo.org mailing list



  parent reply	other threads:[~2008-05-20 21:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-20 20:31 [gentoo-council] Vote: What next? Donnie Berkholz
2008-05-20 21:01 ` Wernfried Haas
2008-05-20 21:01 ` Roy Bamford [this message]
2008-05-20 21:14   ` Donnie Berkholz
2008-05-20 21:58     ` Roy Bamford
2008-05-20 21:13 ` Luca Barbato
2008-05-20 21:50 ` Ferris McCormick
2008-05-20 22:29 ` Ned Ludd
2008-05-21 19:33 ` Petteri Räty
2008-05-22  3:13 ` Chrissy Fullam
2008-05-22  7:07   ` Alec Warner
2008-05-27  6:48 ` [gentoo-council] " Torsten Veller
2008-05-28  1:32   ` Alec Warner
2008-05-28  3:09     ` Jorge Manuel B. S. Vicetto
2008-05-28 18:46       ` Petteri Räty
2008-05-28 19:37         ` Alec Warner
2008-05-29  7:30         ` Wernfried Haas
2008-05-29  9:08           ` Markus Ullmann
2008-05-30 22:00 ` [gentoo-council] " Donnie Berkholz
2008-06-02  6:16   ` Wernfried Haas
  -- strict thread matches above, loose matches on Subject: below --
2008-06-02  8:40 Markus Ullmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1211317312.11979.1@spike \
    --to=neddyseagoon@gentoo.org \
    --cc=gentoo-council@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox