From: Matti Bickel <mabi@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Policy regarding the inactive members
Date: Sun, 11 Apr 2010 18:12:53 +0200 [thread overview]
Message-ID: <4BC1F505.1000209@gentoo.org> (raw)
In-Reply-To: <20100411151705.GB2298@Caemlyn.Fullrate>
[-- Attachment #1: Type: text/plain, Size: 2469 bytes --]
Zeerak Mustafa Waseem wrote:
> But isn't it the councils purpose to lead gentoo?
It's my understanding that council gets elected to lead gentoo as a
whole. But in the end the one doing the work gets to decide what's going
on (as long as it's intra-project; the only thing i remember where
council got to vote on a "project" outcome is PMS/EAPI)
Don't get me wrong: several times i hoped for somebody with authority to
magically end discussions on an issue, handing out the right direction
and be done with it (you already mentioned python-3).
But in a "consensus" community like gentoo we will instantly have
discussions about "our" definition of "right direction". Only a select
few still have that authority required to end a sub-thread with their
"right direction". And this is mostly because they post hard facts you
are buying because they've done so for years and otherwise kept their
mouth shut.
But i disgress..
> By leading they have to either delegate to someone to supervise
> Gentoo projects or do it themselves.
No. It just doesn't work that way. GLEP39 says projects may have a
leader, who will hopefully be responsible to the projects members.
That's the person you want to turn to. Older projects may still have a
"operation" lead and a "strategic" lead. In that case, you want the
"strategic" lead :)
The whole wording and history of the GLEP gives projects most of the
power. They can't be blocked by the community, they can conflict, they
can go defunct at any time. All these are explicitly spelled out in the
GLEP.
> I do agree
> that doing something yourself will always be the first step, but
> there is no way every developer can keep track of everything that's
> going on.
They are not required to. I'm not required to know of the wiki project
or the huge issue that python3 going stable seems to be. My
responsibility as a dev is to keep up with things I work on, like EAPI
changes. If I *want* others to notice, I'll contact council (if I need a
decision) or PR (if I have an announcement).
You are proposing a centralized solution. This hasn't worked since
Daniel left and I personally think gentoo's too large to successfully
try it again.
> I utterly fail to see why there should be any rock throwing.
Me too. But it happens. Despite a dozen folks calling for calm again and
again. I don't want to offer explanations for it, this mail has gotten
long enough as it is ;)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2010-04-11 16:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-11 13:16 [gentoo-dev] Policy regarding the inactive members Markos Chandras
2010-04-11 13:50 ` [gentoo-dev] Re: [gentoo-council] " Markos Chandras
2010-04-11 13:59 ` [gentoo-dev] " Tony "Chainsaw" Vroon
2010-04-11 14:04 ` Matti Bickel
2010-04-11 15:17 ` Zeerak Mustafa Waseem
2010-04-11 16:12 ` Matti Bickel [this message]
2010-04-11 15:27 ` [gentoo-dev] " Duncan
2010-04-11 15:01 ` [gentoo-dev] Re: [gentoo-council] " Denis Dupeyron
2010-04-11 15:02 ` [gentoo-dev] " Roy Bamford
2010-04-11 19:17 ` Jorge Manuel B. S. Vicetto
2010-04-11 20:09 ` Rémi Cardona
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=4BC1F505.1000209@gentoo.org \
--to=mabi@gentoo.org \
--cc=gentoo-dev@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