public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thomas Sachau <tommy@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Should DevRel members be in Council?
Date: Sun, 14 Aug 2011 15:14:37 +0200	[thread overview]
Message-ID: <4E47CA3D.3070700@gentoo.org> (raw)
In-Reply-To: <4E47BF0C.9090703@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1908 bytes --]

Markos Chandras schrieb:
> On 08/14/2011 01:19 PM, Thomas Sachau wrote:
>> Markos Chandras schrieb:
>>> Hi,
>>>
>>> This is the second item I would like to discuss for the next
>>> Council agenda ( or a later one )
>>>
>>> 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. A developer who wants to
>>> appeal to Council, seeks a review of his case and a fresh voting
>>> from new people. However, having devrel members, which are already
>>> biased based on the previous decision, makes the "Council's court
>>> role" a moot role :)
> 
>> I have to ask the same here as for the other proposal:
> 
>> Why do you restrict your proposal to a specific project? The issue
>> you are pointing at is the same for any other project, where someone
>> does open an appeal to council to vote on a team decision he does not
>> want to accept.
> 
> I don't follow. I thought disputes were handled this way
> 
> 1) Contact the guy and resolve the issue with him without bothering the
> rest of team members
> 2) Ask team lead
> 3) Ask devrel
> 4) Ask Council
> 
> There is no way to go from 2->4 without devrel's involvement.

So lets try with an example:

A dev wants to join the Sunrise project and i as the lead say no to him.

This means, both 1 and 2 are already done, 3 does not seem reasonable to me, since it looks unlikely
to me, that DevRel could/should force a team to accept a new member, which would end with the last
point. And if both sides keep their point, council could either force his addition, which will
usually mean, that the team lead leaves or accept the decision of the team lead.




[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 380 bytes --]

  reply	other threads:[~2011-08-14 13:15 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
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 [this message]
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=4E47CA3D.3070700@gentoo.org \
    --to=tommy@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