From: Rich Freeman <rich@thefreemanclan.net>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Should DevRel members be in Council?
Date: Sun, 14 Aug 2011 07:25:08 -0400 [thread overview]
Message-ID: <CAGfcS_nGVBTzT2-Dmwv2C5jT5gVeqaP6gXUQvc=BNtt53iNLcw@mail.gmail.com> (raw)
In-Reply-To: <4E47ADA0.2060906@gentoo.org>
On Sun, Aug 14, 2011 at 7:12 AM, Markos Chandras <hwoarang@gentoo.org> wrote:
> Quite a few of you know that Council acts as a court in case a developer
> has unresolved disputes with Devrel or when he is not happy with a
> Devrel's decision. The problem is that having the same people in the
> Council and in Devrel makes no sense since the same people will vote
> twice on that matter.
So, the way I view it is the Council is the elected body elected by
the Devs to govern the Devs. If they feel the best way to resolve
disputes is to have Devrel first hear them then that is fine. If they
want to personally hear all disputes and have no avenue of appeal
whatsoever that is fine too. If they want to take turns hearing
disputes and then only hear appeals if there is a majority vote to
even hear the appeal in the first place, that is fine too.
If Devs don't like the way it is being done, they can always elect
somebody else. If a Dev doesn't like how they were treated they can
ask all the other devs to elect somebody else to reinstate them, fork
the project, or whatever.
All that said, I think the current system works fine and see no need
to change it. I'd view the Council as being the body that ultimately
makes all DevRel decisions - they just have delegated this
responsibility and only step in if needed.
For these reasons, I see no reason with having overlapping membership
- we're a community and we govern ourselves. The Council is elected
by the community to speak for the community, and they're allowed to
speak even if they've done so already.
For the same sorts of reasons I also see no issue with having
overlapping Council and Trustee membership (obviously allowing that
the Bylaws would need to be amended if a majority of foundation
members agreed with me). I do see the value in having more
participation, but not the requirement.
Rich
next prev parent reply other threads:[~2011-08-14 11:25 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-14 11:12 [gentoo-project] Should DevRel members be in Council? Markos Chandras
2011-08-14 11:25 ` Rich Freeman [this message]
2011-08-14 14:42 ` Roy Bamford
2011-08-14 14:52 ` Rich Freeman
2011-08-14 16:24 ` Roy Bamford
2011-08-18 0:46 ` Jorge Manuel B. S. Vicetto
2011-08-14 19:01 ` Mike Frysinger
2011-08-14 11:27 ` Fabian Groffen
2011-08-14 11:31 ` Markos Chandras
2011-08-14 11:50 ` Rich Freeman
2011-08-14 11:38 ` Rich Freeman
2011-08-14 12:19 ` Thomas Sachau
2011-08-14 12:26 ` Markos Chandras
2011-08-14 13:14 ` Thomas Sachau
2011-08-14 13:42 ` Markos Chandras
2011-08-14 14:05 ` Petteri Räty
2011-08-14 14:11 ` Markos Chandras
2011-08-14 14:42 ` Petteri Räty
2011-08-14 19:01 ` Mike Frysinger
2011-08-15 2:19 ` Samuli Suominen
2011-08-15 2:46 ` Rich Freeman
2011-08-18 1:25 ` Jorge Manuel B. S. Vicetto
2011-08-16 18:28 ` William Hubbs
2011-08-16 19:17 ` Rich Freeman
2011-08-16 20:46 ` Donnie Berkholz
2011-08-17 2:46 ` Mike Frysinger
2011-08-16 19:32 ` Roy Bamford
2011-08-18 1:09 ` 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='CAGfcS_nGVBTzT2-Dmwv2C5jT5gVeqaP6gXUQvc=BNtt53iNLcw@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