public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Roy Bamford <neddyseagoon@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proposing fundamental changes to DevRel
Date: Thu, 17 Jun 2010 19:28:26 +0100	[thread overview]
Message-ID: <1276799306.2335.0@NeddySeagoon> (raw)
In-Reply-To: <4C196595.20600@gentoo.org> (from sping@gentoo.org on Thu Jun 17 01:00:21 2010)

On 2010.06.17 01:00, Sebastian Pipping wrote:
> Hello!
[snip]
> 
>       Problem: Both betelgeuse and jmbsvicetto are DevRel members
>                nominated for the upcoming council election.
>                As I am also nominated proposing such rule could be
>                understood aiming at decreasing their chances on the
>                council and increasing mine as a result.  However, as 
> I
>                propose to start over with a developer voted conflict
>                resolution team this is not the case.  The only
>                implication is that if they make it to the council
>                they cannot be elected for the conflict resolution
> team.
> 
> 
> DevRel is one of the most important things in Gentoo - we dependend 
> on
> that working well.  If you care about this please make yourself 
> heard.
> 
> Thanks,
> 
> 
> 
> Sebastian
> 
> 
> 
> 

Sebastian,

You are suggesting that devrel/council members don't know of the 
conflict of interests beforehand and/or that they fail to disqualify 
themselves from an active part in either the devrel or council part of 
the proceedings. I admit that the possibility exists under present 
rules.

Enforced division of responsibility can be a good thing in places but 
I'm not convinced that this is one of those places. That said, I would 
not want devrel to become a subset of council, nor council to become a 
subset of devrel.  Its just for that reason that the Foundation bylaws 
forbid any individual serving as a trustee and on council at the same 
time.  Maybe I am coming round to supporting your view after all.

-- 
Regards,

Roy Bamford
(Neddyseagoon) a member of
gentoo-ops
forum-mods
trustees




  parent reply	other threads:[~2010-06-17 18:28 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
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 [this message]
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=1276799306.2335.0@NeddySeagoon \
    --to=neddyseagoon@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