public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Warner <antarus@gentoo.org>
To: gentoo-project <gentoo-project@lists.gentoo.org>
Subject: Re: [gentoo-project] rfc: council members and appeals
Date: Tue, 13 Feb 2018 10:21:06 -0500	[thread overview]
Message-ID: <CAAr7Pr8kFrZfeE4XGWHafLfPuvjtztKNsefYCwY75wmJrNLZRQ@mail.gmail.com> (raw)
In-Reply-To: <CAGfcS_kJc8Pc8zsFJd1=Nfs2VcJaVC8DKwZDVrneTHJaATJ4=A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3084 bytes --]

On Tue, Feb 13, 2018 at 5:23 AM, Rich Freeman <rich0@gentoo.org> wrote:

> On Tue, Feb 13, 2018 at 12:51 AM, Alec Warner <antarus@gentoo.org> wrote:
> >
> > In some fields (law, or finance for example) there are rules against
> having
> > even potential conflicts. Should Gentoo emulate those rules and produce
> an
> > organization that avoids even the appearance of conflict?
>
> Absolutely!
>

> > A council member is on a team (not even necessarily QA / Comrel). That
> > team's lead makes a decision. The council member doesn't agree with the
> > decision and appeals to council.
> > I would argue the member raising the issue has a conflict and they should
> > not vote (recuse / abstain).
>
> Merely disagreeing with a decision is not a conflict of interest on its
> own.
>

> A conflict exists when somebody stands to personally benefit from a
> decision.  What personal benefit does a member of a team get from
> appealing a disagreement?




> Now, if the decision concerned them personally in some way I could see
> a conflict, such as if it were about a reimbursement of an expense
> they incurred, or if it were about sponsoring them to go on a trip.
>
I wouldn't even consider it a conflict of interest if it were a QA
> decision on a commit they made, unless this commit furthered some kind
> of work they were doing outside of Gentoo (the commit benefited their
> employer or their consulting business).
>
> Conflict of interest isn't the same as disagreement.  It is completely
> normal and healthy for people to disagree with things.  This does not
> in any way make them prejudiced or likely to make a decision that is
> bad for the distro.
>

> Again, I'm completely in favor of avoiding conflicts of interest.  It
> just seems that there is a popular notion around here of what a
> conflict of interest is which certainly wouldn't stand up in a court
> of law, or really in any organization.  Perhaps this is why so many
> seem to be paranoid that there is some kind of cabal running the show.
> (One which is elected, so presumably this cabal is upwards of 30+
> people.)
>

Ok I don't want to have a discussion about what is a conflict or not;
because I don't think the conversation solves the problems (which are
ill-specified, hoping William will use more words.) The original post
discussed appeals to the council. My understanding is that there is a
potential trust issue and William thinks removing 'conflicts' (and I use
the loosest definition of conflict here) will help improve trust. Assuming
developers have concerns about 'conflicts', having a conversation where you
say their concerns are invalid based on 'an interpretation of the phrase
conflict of interest' doesn't really address these developer concerns (and
in fact does the opposite.)

So I'd like to see the developer concerns expressed in a clearer way so we
can have a frank discussion. If there are no explicit concerns and we are
just discussing potential problems;  then I'm less likely to advocate for
policy changes based on things that have not happened yet.

-A


>
> --
> Rich
>
>

[-- Attachment #2: Type: text/html, Size: 4621 bytes --]

  parent reply	other threads:[~2018-02-13 15:21 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-11 22:42 [gentoo-project] rfc: council members and appeals William Hubbs
2018-02-11 23:20 ` Rich Freeman
2018-02-12  0:12   ` William Hubbs
2018-02-12  0:29     ` Rich Freeman
2018-02-12  2:16       ` William Hubbs
2018-02-12  2:29         ` Rich Freeman
2018-02-13  2:52           ` Andreas K. Huettel
2018-02-12  8:19 ` Fabian Groffen
2018-02-12  8:58 ` Ulrich Mueller
2018-02-12 19:14   ` Michał Górny
2018-02-12 19:36   ` Thomas Deutschmann
2018-02-12 23:02     ` Ulrich Mueller
2018-02-12 23:40       ` M. J. Everitt
2018-02-13  0:13         ` Rich Freeman
2018-02-13  0:16           ` M. J. Everitt
2018-02-13  0:18             ` M. J. Everitt
2018-02-13  0:25           ` Roy Bamford
2018-02-13  1:21             ` Rich Freeman
2018-02-13  0:39   ` Chí-Thanh Christopher Nguyễn
2018-02-13  0:57     ` Ulrich Mueller
2018-02-13  4:59     ` Dean Stephens
2018-02-13  5:06       ` M. J. Everitt
     [not found]       ` <f4781100-3fa2-170f-c388-d53f353bf914@gentoo.org>
2018-02-13 20:56         ` [gentoo-dev] " Chí-Thanh Christopher Nguyễn
     [not found]         ` <23171.27241.311990.19309@a1i15.kph.uni-mainz.de>
2018-02-14  0:33           ` Chí-Thanh Christopher Nguyễn
2018-02-12 15:53 ` Daniel Robbins
2018-02-12 16:10   ` Matthew Thode
2018-02-12 16:55   ` William Hubbs
2018-02-12 17:03     ` Daniel Robbins
2018-02-12 17:46       ` Rich Freeman
2018-02-12 17:58         ` Daniel Robbins
2018-02-12 18:34           ` Rich Freeman
2018-02-12 18:40             ` Daniel Robbins
2018-02-12 18:52               ` Rich Freeman
2018-02-12 19:05                 ` Daniel Robbins
2018-02-12 19:17                   ` Rich Freeman
2018-02-13 13:43                     ` Aaron Bauman
2018-02-13 13:51                       ` Kristian Fiskerstrand
2018-02-13 14:41                         ` Aaron Bauman
2018-02-13 14:49                           ` Kristian Fiskerstrand
2018-02-13  4:58     ` Dean Stephens
2018-02-13  5:02       ` M. J. Everitt
2018-02-13  5:51         ` Alec Warner
2018-02-13  6:36           ` Robin H. Johnson
2018-02-13 10:23           ` Rich Freeman
2018-02-13 13:59             ` Aaron Bauman
2018-02-13 20:56               ` Rich Freeman
2018-02-13 15:21             ` Alec Warner [this message]
2018-02-14  5:15           ` Dean Stephens
     [not found]       ` <a1ec3099-11d7-a779-c9c8-a17bbe1d753e@gentoo.org>
     [not found]         ` <CAGfcS_mZSNTgsRbeGJqmmEkodhK7K73EAx6D4EHMkq1FRw9pRQ@mail.gmail.com>
2018-02-13 21:12           ` [gentoo-dev] " Chí-Thanh Christopher Nguyễn
2018-02-14  5:16             ` Dean Stephens
2018-02-12 18:54 ` Thomas Deutschmann
2018-02-13  2:43 ` Andreas K. Huettel
2018-02-13  4:09   ` Matthew Thode
2018-02-13 23:21 ` Alexis Ballier
2018-02-14  5:53   ` Michał Górny
2018-02-14  6:01     ` Daniel Robbins
2018-02-14  6:44     ` R0b0t1
2018-02-14  7:22     ` Ulrich Mueller
2018-02-14  7:29       ` Michał Górny
2018-02-14  6:19 ` Mike Gilbert
2018-02-15 20:15 ` 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=CAAr7Pr8kFrZfeE4XGWHafLfPuvjtztKNsefYCwY75wmJrNLZRQ@mail.gmail.com \
    --to=antarus@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