public inbox for gentoo-council@lists.gentoo.org
 help / color / mirror / Atom feed
From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-council@lists.gentoo.org
Subject: [gentoo-council] Re: [gentoo-dev] Council size & terms [WAS] One-Day Gentoo Council Reminder for January 22
Date: Thu, 22 Jan 2009 09:37:55 -0800	[thread overview]
Message-ID: <20090122173755.GC20446@comet> (raw)
In-Reply-To: <1232644991.4164.19.camel@homer.ob.libexec.de>

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

On 18:23 Thu 22 Jan     , Tobias Scherbaum wrote:
> Donnie Berkholz wrote:
> > Discuss on-list before meeting
> > ---------------------------------------
> > - Council meta stuff (-council)
> >   - Can the size change? Minimum? Maximum?
> >   - Should we have 2-year staggered terms?
> 
> 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?

> 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?

> 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.

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.

-- 
Thanks,
Donnie

Donnie Berkholz
Developer, Gentoo Linux
Blog: http://dberkholz.wordpress.com

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

       reply	other threads:[~2009-01-22 17:37 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     ` Donnie Berkholz [this message]
2009-01-22 17:57       ` [gentoo-council] Re: [gentoo-dev] Council size & terms [WAS] One-Day Gentoo Council Reminder for January 22 Tobias Scherbaum
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=20090122173755.GC20446@comet \
    --to=dberkholz@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