public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Markos Chandras <hwoarang@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Should DevRel members be in Council?
Date: Sun, 14 Aug 2011 14:42:26 +0100	[thread overview]
Message-ID: <4E47D0C2.1020007@gentoo.org> (raw)
In-Reply-To: <4E47CA3D.3070700@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 08/14/2011 02:14 PM, Thomas Sachau wrote:
> 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.
> 
> 
I don't think Council is eligible to force this. The council is not
supposed to interfere with how teams operate.

- -- 
Regards,
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)

iQIcBAEBCgAGBQJOR9DCAAoJEPqDWhW0r/LC2dwQAJkEpCiOzd1TfwoeT1bGMs8j
AHgBrR/pnn5UmvcshPI0AiCj/7wBwSpNWcTCjP2Zrw+RFI6diClIevCKn2kOiqYM
S84/ajIbeQa6VgEfxsnwLJ7nFIHIym71PMzyJWzDO36A6I+YsOA8HPmoBpQ2ChgU
By8zTDMI2dxYaPGb59Ul3wsXbOpK1Pb1XAWxFvejLzKJQ0Zazm9JiyNjZfEutx/e
3W7gI6o7vVHI6a+/oCYnBFx8MmEk+mxjqK0VVhnGuYDJhYOj53T2C1Capxi22jY+
JGui99yzh1gpufFYl7gMuKa+3kOtGYYFl5CHA+NI3N0OtB2KeOVtukWOJJKPlyj7
S4ScuQdYrmMENRMkeGuib9XGYj1GKK12FriZle+WNXvADzcM0rle17Hu/8PWQzvt
LLonJWYQDKQZOoj+WX8zXEEBIHumhHM+qQYpmHYYhzQl8Y6REYXIUKgHg0lw65iw
XyMs2fUknlaSWZAalve3aSfv+uzO3+bYyMff1TvU04uIye59ha0SeI/GlDqDhufx
CJ6WeJDTpTg9LQwds1RNKnnh63P5wRJ1WYEIAWGYOKYm2blStMVuSd9X6dybwp8G
xC5R/wcAliV88NpphlpAOlsBErJbixE5MUNgRhMLYbyhFTHZgOXrdL3GsRiaTnHY
V6b8hANLDEBlUvEIljH+
=QSxN
-----END PGP SIGNATURE-----



  reply	other threads:[~2011-08-14 13:43 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
2011-08-14 13:42       ` Markos Chandras [this message]
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=4E47D0C2.1020007@gentoo.org \
    --to=hwoarang@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