From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Should DevRel members be in Council?
Date: Sun, 14 Aug 2011 17:42:15 +0300 [thread overview]
Message-ID: <4E47DEC7.9030605@gentoo.org> (raw)
In-Reply-To: <4E47D790.5050302@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1544 bytes --]
On 14.08.2011 17:11, Markos Chandras wrote:
> On 08/14/2011 03:05 PM, Petteri Räty wrote:
>> On 14.08.2011 16:42, Markos Chandras wrote:
>>>
>>>> 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.
>>>
>
>> The precedent is that Council can rule whatever it wants besides
>> changing GLEP 39. Of course in a volunteer project some might never
>> get executed. Changing eligibility rules for the council requires a
>> change to GLEP 39 so it's not something we can vote on in the next
>> meeting.
>
>> Regards, Petteri
>
>
> Fair enough. I was pretty sure that the Council was not supposed to
> instruct projects how to operate. But anyway, this is irrelevant to the
> initial discussion.
>
I think Tommy presented a valid question but you are just missing the
point. DevRel is just a body that is more likely to do decisions that
are doing to be appealed to the council.
Regards,
Petteri
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]
next prev parent reply other threads:[~2011-08-14 14: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
2011-08-14 14:05 ` Petteri Räty
2011-08-14 14:11 ` Markos Chandras
2011-08-14 14:42 ` Petteri Räty [this message]
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=4E47DEC7.9030605@gentoo.org \
--to=betelgeuse@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