From: Tobias Scherbaum <dertobi123@gentoo.org>
To: Donnie Berkholz <dberkholz@gentoo.org>
Cc: Ferris McCormick <fmccor@gentoo.org>, gentoo-council@lists.gentoo.org
Subject: Re: [gentoo-council] Re: Stepping back from council duties
Date: Mon, 17 Nov 2008 19:31:53 +0100 [thread overview]
Message-ID: <1226946713.3939.47.camel@homer.ob.libexec.de> (raw)
In-Reply-To: <20081117175525.GA23297@comet>
[-- Attachment #1: Type: text/plain, Size: 1596 bytes --]
Donnie Berkholz wrote:
> On 18:49 Mon 17 Nov , Tobias Scherbaum wrote:
> > So we could end up with only 1 council member in the worst case? ;)
>
> Yes, although worst is a matter of definition. If the developer
> community wants what is effectively a benevolent dictator, then let's
> give it to them. This is, after all, a community distribution so we
> should do what the community wants.
That would lead us to completely new (or old) leadership model. If I was
to vote on a council I'd like to get a council, not a benevolent
dictator.
> > I don't think that's something we really want.
>
> The majority of developers should choose what kind of leadership they
> want, instead of us deciding for them.
I'm speaking for myself here - I personally don't want a dictatorship.
> > In my opinion we need to have at minimum 5 council members to make
> > sure there's some kind of redundancy plus to get different views and
> > ideas on issues brought up to the council.
>
> Anyone can contribute views and ideas ... why do you need to be on the
> council to do that? Most of the issues are discussed on -dev, and I've
> pushed to make that a requirement and meetings as primarily just votes.
Discussions on a proposal are only one part, but it needs to be voted
upon that proposal. Having a larger council makes sure a broader part of
the developer community and there views are represented in that decision
making. Again, that's my personal opinion - I'm clearly in favor of the
democratic approach instead of a dictatorship model.
Tobias
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-11-17 18:31 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-15 16:05 [gentoo-council] Stepping back from council duties Markus Ullmann
2008-11-16 6:00 ` Donnie Berkholz
2008-11-16 12:04 ` [gentoo-council] " Torsten Veller
2008-11-16 13:36 ` Ferris McCormick
2008-11-16 13:45 ` Jorge Manuel B. S. Vicetto
2008-11-16 15:51 ` Torsten Veller
2008-11-17 2:55 ` Jorge Manuel B. S. Vicetto
2008-11-16 17:55 ` Donnie Berkholz
2008-11-16 18:21 ` Ferris McCormick
2008-11-16 18:40 ` Tobias Scherbaum
2008-11-16 18:44 ` Ciaran McCreesh
2008-11-17 17:38 ` Tobias Scherbaum
2008-11-17 18:03 ` Ciaran McCreesh
2008-11-17 18:18 ` Tobias Scherbaum
2008-11-17 16:15 ` Donnie Berkholz
2008-11-17 17:49 ` Tobias Scherbaum
2008-11-17 17:55 ` Donnie Berkholz
2008-11-17 18:31 ` Tobias Scherbaum [this message]
2008-11-17 19:13 ` Donnie Berkholz
2008-11-17 18:31 ` Roy Bamford
2008-11-17 19:16 ` Donnie Berkholz
2008-11-17 21:36 ` Roy Bamford
2008-11-17 21:45 ` Donnie Berkholz
2008-11-16 20:36 ` Alec Warner
2008-11-16 20:52 ` Ferris McCormick
2008-11-20 14:19 ` Torsten Veller
2008-11-20 17:29 ` Donnie Berkholz
2008-11-16 16:48 ` [gentoo-council] " Tobias Scherbaum
2008-11-16 17:43 ` 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=1226946713.3939.47.camel@homer.ob.libexec.de \
--to=dertobi123@gentoo.org \
--cc=dberkholz@gentoo.org \
--cc=fmccor@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