public inbox for gentoo-council@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tobias Scherbaum <dertobi123@gentoo.org>
To: gentoo-council@lists.gentoo.org
Subject: Re: [gentoo-council] Re: [gentoo-dev] Council size & terms [WAS] One-Day Gentoo Council Reminder for January 22
Date: Thu, 22 Jan 2009 18:57:21 +0100	[thread overview]
Message-ID: <1232647041.4164.33.camel@homer.ob.libexec.de> (raw)
In-Reply-To: <20090122173755.GC20446@comet>

[-- Attachment #1: Type: text/plain, Size: 2490 bytes --]

Donnie Berkholz wrote:
> > I'm in favor of a fixed size of council members, I'd like to see at
> > least 5 council members *if* developers want to change the size.
> 
> What is your reasoning for this?

To make sure different views are represented in council's decisions and
to make sure the decisions are well-balanced. This can be partially
accomplished with having, say, 3 council members, of course - but well,
it's 5 to make sure. 

> > I dislike the idea of stretched 2-year terms, instead I prefer having 
> > 1-year staggered terms (voting every 6 months and replace 3 or 4 
> > council members). This would allow to put open council slots into the 
> > next election, we wouldn't need to hold extra elections for open slots 
> > then.
> 
> As I mentioned on the -council voting thread, I am concerned about a 
> constant influx of new members every 6 months making it very difficult 
> to make any progress. Do you think that won't be a problem? If so, what 
> makes you think that?

In fact we had a constant influx of new council members constantly in
the past - which did also work somehow (I'd say it wasn't a problem in
the past). With having elections every 6 months we *could* start to
re-fill open slots with the next election (except there are more than ~2
open slots) and therefore won't have to deal with new council members
constantly but only every 6 months.

> > Anyways, this is something we can discuss - but as a change to the
> > voting procedure most likely does change or extend what's written down
> > in GLEP 39 I'd like to see a election on those changes.
> 
> I'm assuming you mean a vote by all Gentoo devs, since an election 
> generally involves voting for a person rather than a policy.

Yup, "election by all devs"

> Just as a point of reference, the council has voted to change GLEP 39 in 
> the past. I definitely feel that we need to hold this discussion 
> publicly and get input from everyone. I think the council should then 
> take all this input into consideration and vote upon it.

In the past the council iirc didn't vote upon changes to the process of
voting for, size and lengths of terms of the council. (Adding the
_reopen_nominations candidate was something people took part in the
discussion did agree with, but there was no council or developer vote on
that.) It doesn't hurt to cast a vote by all developers on that, but
this vote does legitimate the changes voted upon.

  Tobias

[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-01-22 17:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090121233526.GA15870@comet>
     [not found] ` <20090122000229.GF15870@comet>
     [not found]   ` <1232644991.4164.19.camel@homer.ob.libexec.de>
2009-01-22 17:37     ` [gentoo-council] Re: [gentoo-dev] Council size & terms [WAS] One-Day Gentoo Council Reminder for January 22 Donnie Berkholz
2009-01-22 17:57       ` Tobias Scherbaum [this message]
2009-02-12  7:01         ` Donnie Berkholz
2009-01-22 19:31       ` Petteri Räty
2009-01-23 12:42       ` Jorge Manuel B. S. Vicetto

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=1232647041.4164.33.camel@homer.ob.libexec.de \
    --to=dertobi123@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