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 00:51:45 -0500	[thread overview]
Message-ID: <CAAr7Pr9X7KG_2-kzb3tjnBVPPXhZ4zmP5o2p33KqHmhP8amFXg@mail.gmail.com> (raw)
In-Reply-To: <b8e0efee-9a92-a249-6d66-29424b363111@iee.org>

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

On Tue, Feb 13, 2018 at 12:02 AM, M. J. Everitt <m.j.everitt@iee.org> wrote:

> On 13/02/18 04:58, Dean Stephens wrote:
> > On 02/12/18 11:55, William Hubbs wrote:
> >> Hi Daniel,
> >>
> >> On Mon, Feb 12, 2018 at 08:53:24AM -0700, Daniel Robbins wrote:
> >>> How about if they just abstain from any votes where there may be a
> conflict
> >>> of interest? I would hate to limit the ability of people to contribute
> >>> technically just because they were elected to council.
> >> The confusing thing about this is, how would we define "conflict of
> >> interest"?
> >>
> >> Suppose that the council decides to accept an appeal from comrel. Is it
> >> a conflict of interest for a member of the council who is also a member
> >> of comrel to vote in the appeal? If it isn't, it is at least a pretty
> >> strong perception that it is.
> >>
> > Why? How? Exactly what sort of conflicting interest is supposed to be
> > present?
> >
> There seems to be two divergent schools of thinking here:
> 1) Those that think that there is, or could be, (potential for) a
> conflict of interest,
> and 2) Those that cannot conceive there even could be a conflict of
> interest.
>

I'm not aware of anyone advocating for case two (not even Rich! :))


>
> I think it would be useful for both sides to state their cases, and
> perhaps this particular issue could have its bike-shed painted once, and
> for good.....
>
>
Ultimately this comes down to a discussion about whether potential
conflicts are allowed or not.

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? In other fields,
potential conflicts are allowed. There tend to be policies about disclosing
conflicts (disclosure is typically encouraged here.) Organizations can use
the disclosures to put in appropriate controls. To use an example:

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).

If you believe the above premise, even if we take William's patch, its
clear we cannot eliminate conflicts of interest among Gentoo Leadership
(e.g. the above example is a conflict; but it isn't resolved by William's
patch.)

I'm also not clear on the problem statement. William's opener was: "I have
felt this way for a long time, because I think it compromises the full
council's
ability to vote fairly on appeals." So it seems that the problem statement
is about appeals being fair (or appearing fair, or feeling fair?) Maybe we
could discuss Appeals specifically; and how they appear or make people
feel. I'm not sure I have a better idea of 'fairness' than just soliciting
feedback.

-A

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

  reply	other threads:[~2018-02-13  5:51 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 [this message]
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
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=CAAr7Pr9X7KG_2-kzb3tjnBVPPXhZ4zmP5o2p33KqHmhP8amFXg@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