From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Should DevRel members be in Council?
Date: Tue, 16 Aug 2011 15:46:32 -0500 [thread overview]
Message-ID: <20110816204632.GJ3818@comet.mayo.edu> (raw)
In-Reply-To: <CAGfcS_mAE+SRA4hj4HvMT-STkX-YtNkMaDcB0pVVca9YPz01sQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1403 bytes --]
On 15:17 Tue 16 Aug , Rich Freeman wrote:
> What kind of conflict are we actually talking about? It isn't a
> conflict of interest to hold an opinion. It is only a conflict if the
> personal interests of a council member aren't aligned with the
> interests of the developer community as a whole.
>
> If a Council member has been investigating a situation closely, then
> my feeling is that they're in a BETTER position to evaluate the
> situation and not a worse one. The DevRel process is not an
> adversarial one.
>
> If we as a community can't trust somebody's ability to be
> professional, then the last thing we should do is elect them to the
> Council. Keep in mind that Developers only can lose their status if
> they really tick a lot of people off. Council members lose their
> status by default every 12 months.
>
> Is there a problem here that actually needs to be solved? Can
> somebody point to a recent situation where a conflict of interest
> between a Council member and a developer led to a decision that a
> majority of the community would consider inappropriate?
I don't normally post +1, but to get my opinion out as a council member
I will do so. I agree with Rich 1000% on everything he's said in this
thread.
--
Thanks,
Donnie
Donnie Berkholz
Council Member / Sr. Developer
Gentoo Linux
Blog: http://dberkholz.com
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-08-16 20:46 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
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 [this message]
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=20110816204632.GJ3818@comet.mayo.edu \
--to=dberkholz@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