From: Rich Freeman <rich@thefreemanclan.net>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] On the way Devrel is constituted
Date: Wed, 19 Jun 2013 22:00:48 -0400 [thread overview]
Message-ID: <CAGfcS_kvj0ZEkpgY2yNZw9fuFbmOJQetQbUg5HkwmmwDN_B=rQ@mail.gmail.com> (raw)
In-Reply-To: <20130619205029.44e1a3a3@gentoo.org>
On Wed, Jun 19, 2013 at 8:50 PM, Alexis Ballier <aballier@gentoo.org> wrote:
>
> So that the council controls everything: they nominate the judges
> (devrel) and are the appeal court. I consider this even worse.
The council is elected. No sane organization (democratic or corporate
or whatever) just has a self-appointing judiciary. I'm not convinced
we even need an independent judiciary, but nations that have
independent judiciaries still have elected representatives appoint
them. They also often have a means for elected officials to overturn
their decisions (at least in the direction of pardons).
Corporations have elected boards appoint executives who appoint the
members of HR/Security. Democracies elect representatives who appoint
members of the judiciary.
My feeling is that QA and Devrel should be council appointed. They
can of course recommend their own members, and Council can give
whatever deference they feel is appropriate to the recommendation.
If you wouldn't trust somebody to appoint QA/Devrel members, then you
shouldn't be electing them to the Council. Likewise, if you wouldn't
trust somebody to not just seize control of the entire distribution
(infra, DNS, bank accounts, the Gentoo name, firing the Council, etc)
you shouldn't be electing them to the Trustees (a few years ago our
sole remaining Trustee was contemplating basically just turning the
entire distro over to a benevolent dictator (our founder), who legally
wouldn't be accountable to anybody including the Council (or even the
devs in general depending on whether the bylaws were modified)).
These are real governing bodies that essentially have all the powers
you don't want to give to anybody (well, save unelected QA/Devrel team
members) whether you like it or not (at least within the boundaries of
the Foundation charter/bylaws).
I agree with hasufell's recommendation, although I would extend it to
QA as well. QA and Devrel are "special" projects and should probably
be accountable to the Council. I think they should be largely
self-governing much as infra is (even though infra is fairly dependent
on the trustees for funding/etc). It isn't about control so much as
accountability and mandate. I'd of course recommend that the Council
should be hands-off as long as things are going well, and there really
isn't anything that suggests they wouldn't be (certainly this has been
the trend with both the Council and Trustees).
Part of me is thinking that we should just write up this proposal as a
GLEP and go from there. By all means devs should register their
opinions on it as it firms up, and we can leave it to the new Council
to decide how to handle it.
Rich
next prev parent reply other threads:[~2013-06-20 2:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 20:18 [gentoo-project] On the way Devrel is constituted hasufell
2013-06-19 20:43 ` Petteri Räty
2013-06-19 21:41 ` hasufell
2013-06-19 22:19 ` William Hubbs
2013-06-20 0:50 ` Alexis Ballier
2013-06-20 2:00 ` Rich Freeman [this message]
2013-06-20 3:17 ` Alexis Ballier
2013-06-20 10:44 ` Sean Amoss
2013-06-20 10:50 ` Markos Chandras
2013-06-20 11:25 ` Douglas Dunn
2013-06-20 11:30 ` Douglas Dunn
2013-06-20 19:03 ` William Hubbs
2013-06-20 19:32 ` Alexis Ballier
2013-06-20 19:33 ` Rich Freeman
2013-06-20 20:07 ` Chí-Thanh Christopher Nguyễn
2013-06-20 20:20 ` William Hubbs
2013-06-20 11:03 ` hasufell
2013-06-20 2:03 ` Rich Freeman
2013-06-20 5:19 ` Samuli Suominen
2013-06-20 7:33 ` Thomas Raschbacher (Gentoo)
2013-06-20 10:41 ` Anthony G. Basile
2013-06-20 8:52 ` Roy Bamford
2013-06-20 11:59 ` Michał Górny
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='CAGfcS_kvj0ZEkpgY2yNZw9fuFbmOJQetQbUg5HkwmmwDN_B=rQ@mail.gmail.com' \
--to=rich@thefreemanclan.net \
--cc=gentoo-project@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