public inbox for gentoo-council@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ned Ludd <solar@gentoo.org>
To: Roy Bamford <neddyseagoon@gentoo.org>
Cc: gentoo-council@lists.gentoo.org
Subject: Re: [gentoo-council] Voting procedure
Date: Tue, 13 Jan 2009 13:45:13 -0800	[thread overview]
Message-ID: <1231883113.14355.44.camel@hangover> (raw)
In-Reply-To: <1231592642.3886.0@spike>

On Sat, 2009-01-10 at 13:03 +0000, Roy Bamford wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 2009.01.08 13:01, Tiziano Müller wrote:
> > Hi everyone
> > 
> > Since Cardoe didn't present the paper up to now, I'd like to get the
> > discussion started how the voting procedure should look like in the
> > future.
> > 
> > So far we've introduced the _reopen_nominations person in the last
> > vote
> > and it didn't change a lot. But there are more questions:
> > 
> > Does there always have to be 7 council members? If yes, what should
> > happen when we i) don't have enough nominations and/or ii)
> > _reopen_nominations is ranked somewhere between rank 1-7 ?
> > If not, should there be a minimum? If yes, same questions as above.
> > 
> > I know it's boring stuff but it's better to discuss it now instead of
> > during the next election period.
> > 
> > Cheers,
> > Tiziano
> > 
> > ps The results from the 2008b vote are still not on the council page,
> > who's going to do that?
> > 
> > -- 
> > -------------------------------------------------------
> > Tiziano Müller
> > Gentoo Linux Developer
> > Areas of responsibility:
> >   Samba, PostgreSQL, CPP, Python, sysadmin
> > E-Mail     : dev-zero@gentoo.org
> > GnuPG FP   : F327 283A E769 2E36 18D5  4DE2 1B05 6A63 AE9C 1E30
> > 
> Tiziano,
> 
> I would like to widen the discussion a little.
> I propose that council members serve for two years, not the current 
> year and that half the seats are contested every year. 

You raised some good points here. But I don't think two years helps
anybody at all. Here are some of the reasons why.

In the last council we lost almost half of the people. Extending that
for 2 years.. What's it solve? 1/3rd of the orig ppl will be on the
council by the time the terms are over?  People change as well as what
they want to do. Don't tie them up in the politics for so long that they
lose whatever good it was that made them a dev in the first place.
If they are good at being a councilmen then the chances of them being
reelected is good. 2 years terms means we can also be stuck with a
**ckhead for a long time. Big no thanks there. Plus it's nice to cycle
some new blood in.

I'm in favor of 1 year terms for council. Trustees on the other hand.. 2
years would be nice as the first few months seems to be spent sorting
out stuff from the previous set (paper work etc..)

-- 
Ned Ludd <solar@gentoo.org>
Gentoo Linux




  reply	other threads:[~2009-01-13 21:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08 13:01 [gentoo-council] Voting procedure Tiziano Müller
2009-01-10 13:03 ` Roy Bamford
2009-01-13 21:45   ` Ned Ludd [this message]
2009-01-13 22:29     ` Roy Bamford
2009-01-13 23:19       ` Paul Varner
2009-01-21 23:43   ` Donnie Berkholz
2009-01-13 17:40 ` Tobias Scherbaum
2009-01-13 18:05   ` [gentoo-council] " Torsten Veller
2009-01-22 17:07     ` Tobias Scherbaum
2009-01-21 23:45 ` [gentoo-council] " Donnie Berkholz
2009-01-22  0:42   ` Ferris McCormick
2009-01-22  0:58     ` Donnie Berkholz

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=1231883113.14355.44.camel@hangover \
    --to=solar@gentoo.org \
    --cc=gentoo-council@lists.gentoo.org \
    --cc=neddyseagoon@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