From: Alexis Ballier <aballier@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] On the way Devrel is constituted
Date: Wed, 19 Jun 2013 20:50:29 -0400 [thread overview]
Message-ID: <20130619205029.44e1a3a3@gentoo.org> (raw)
In-Reply-To: <51C21229.9070105@gentoo.org>
On Wed, 19 Jun 2013 22:18:49 +0200
hasufell <hasufell@gentoo.org> wrote:
[...]
> Who controls devrel?
> Simple answer: no one.
And this is good IMHO. Judiciary should be an independent power.
> The only thing that can stop devrel is the council, which has some
> kind of veto right. But that is not enough to guarantee that an entity
> with that kind of power/authority/responsibility consists of people
> who are capable of that task.
It might be good to have a way to demote someone from devrel if he is
abusing his powers. It can probably already be done by talking to other
devrel members. So far, I've never seen any need for it.
> It's a self-maintaining project without any logical connection between
> the legitimation of the project and the legitimation of the members.
> There is no rotation of members which is absolutely crucial for a
> position like that.
I don't see why there should be a rotation: Such a rotation might just
make people try to get as much as they can from their new powers until
they are "rotated". If people are seriously involved with devrel,
handle impartially conflicts and are able to resolve them, why
replacing them?
> What is a possible solution?
> Let the council elect all members. That way the power still comes from
> the dev community, although they do not vote devrel directly. The
> council should vote anonymously, so that no connection between council
> member and elected devrel member can be drawn which could otherwise
> affect the election of the council.
> This system should prevent people from thinking two steps ahead when
> voting the council.
So that the council controls everything: they nominate the judges
(devrel) and are the appeal court. I consider this even worse.
Alexis.
next prev parent reply other threads:[~2013-06-20 0:50 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 [this message]
2013-06-20 2:00 ` Rich Freeman
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=20130619205029.44e1a3a3@gentoo.org \
--to=aballier@gentoo.org \
--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