From: Ben de Groot <yngwin@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proposing fundamental changes to DevRel
Date: Thu, 17 Jun 2010 03:05:45 +0200 [thread overview]
Message-ID: <AANLkTinc41QQ_miomkvZUb3WbNKs3mu_wSIe537ZldmR@mail.gmail.com> (raw)
In-Reply-To: <4C196D69.6070808@gentoo.org>
On 17 June 2010 02:33, Jorge Manuel B. S. Vicetto
<jmbsvicetto@gentoo.org> wrote:
> On 17-06-2010 00:00, Sebastian Pipping wrote:
>> yngwin's devaway message still reads
>>
>> "inactive, pending resolution of devrel issue".
>>
>> yngwin retired. I woudn't go as far as saying that his case made him
>> retire but I definitely say that _DevRel failed on his case_.
>> I believe I had enough insight to be able to say.
>
> Sebastian,
>
> not being in the Developer Relations team means you don't have a
> complete picture about what happened.
I've been in contact with Sebastian since the beginning of my conflict
with Calchan, and kept him in the loop. Apart from anything that might
have taken place behind the closed doors of DevRel that I myself don't
know about either, he has a good picture of what happened.
>> 4) Disallow membership with both the conflict resolution group
>> and the council at the same time (as the council is where issues
>> with devrel are taken to).
>
> The reason the elections page clearly identifies members of devrel is to
> alert developers to possible conflicts.
> To clarify your above statement, I read it as being about the fact that
> disciplinary actions of DevRel can be appealed to the Council. If it
> were meant globally, I'd have to note that whenever you cannot reach an
> agreement with any project or their lead, you'll have to "appeal" to the
> council.
I indicated to Sebastian that if DevRel's verdict in my case would
turn out to be negative, that I am not inclined to appeal to Council.
As two of the most influential DevRel members happen to also be two of
the most influential Council members, I would not expect a different
outcome.
I think there is a conflict of interest here, and I agree with
Sebastian that it would be better if that were avoided.
Cheers,
Ben
next prev parent reply other threads:[~2010-06-17 1:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 0:00 [gentoo-dev] Proposing fundamental changes to DevRel Sebastian Pipping
2010-06-17 0:33 ` Jorge Manuel B. S. Vicetto
2010-06-17 1:05 ` Ben de Groot [this message]
2010-06-17 14:37 ` Sebastian Pipping
2010-06-17 22:46 ` Sebastian Pipping
2010-06-17 23:36 ` Alec Warner
2010-06-17 23:36 ` Richard Freeman
2010-06-17 0:41 ` Mike Frysinger
2010-06-17 7:56 ` [gentoo-dev] " Duncan
2010-06-17 15:10 ` Sebastian Pipping
2010-06-17 15:52 ` Petteri Räty
2010-06-18 2:38 ` Duncan
2010-06-17 0:41 ` [gentoo-dev] " Jeremy Olexa
2010-06-17 7:52 ` Petteri Räty
2010-06-17 15:00 ` Sebastian Pipping
2010-06-17 15:45 ` Petteri Räty
2010-06-17 16:20 ` Ben de Groot
2010-06-17 16:33 ` Petteri Räty
2010-06-17 16:21 ` Patrick Lauer
2010-06-17 20:09 ` Sebastian Pipping
2010-06-17 20:39 ` Patrick Lauer
2010-06-17 20:29 ` Sebastian Pipping
2010-06-21 15:44 ` Petteri Räty
2010-06-17 11:16 ` Markos Chandras
2010-06-17 18:28 ` Roy Bamford
2010-06-17 18:47 ` Roy Bamford
2010-06-18 4:06 ` Jeroen Roovers
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=AANLkTinc41QQ_miomkvZUb3WbNKs3mu_wSIe537ZldmR@mail.gmail.com \
--to=yngwin@gentoo.org \
--cc=gentoo-dev@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