public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "M. J. Everitt" <m.j.everitt@iee.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] pre-GLEP: Gentoo Developer status
Date: Fri, 13 Apr 2018 23:29:25 +0100	[thread overview]
Message-ID: <4da302dd-3e4f-42c0-b602-57e32272ce8a@iee.org> (raw)
In-Reply-To: <CAGfcS_mCgiQvjXMm=Wjm7OmA4+UP1uU=9KuQT448U_L8Aa7Www@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 3436 bytes --]

On 13/04/18 23:25, Rich Freeman wrote:
> On Fri, Apr 13, 2018 at 6:07 PM, M. J. Everitt <m.j.everitt@iee.org> wrote:
>> On 13/04/18 22:57, Rich Freeman wrote [excerpted]:
>>> I find it ironic that you're suggesting that the folks who disagree
>>> with you leave, considering that this whole debate was started by a
>>> bunch of people who basically felt that nobody should really be kicked
>>> out for anything.
>>>
>> The problem stems from the fact that there is (perceived to be) a
>> problem with the wrong kinds of people *being* ejected or disciplined,
>> whereas some people who *should* be ejected or disciplined, are not. And
>> obviously so. There is no even-handed or transparent application of
>> whatever "rules" are being applied, and this is seen to be unjust and
>> unacceptable ...
>>
> Obviously I don't want to rehash this whole debate, but applying the
> rules in a transparent way seems to be impossible without creating
> legal risks.  I've yet to hear anything to the contrary from the
> Trustees/etc.  So, it comes down to either trusting people to do this
> well, or not doing it at all.  I'm certainly supportive of calls to
> try to improve transparency where this is possible, such as with
> anonymized stats published by comrel.
>
> FWIW I've actually heard complaints at all levels within Gentoo about
> double standards (coming from the top on down).  It is probably fair
> to say that bad deeds can be offset by good deeds to a significant
> degree around here, even if those deeds are of a different nature.
> So, somebody with a strong negative technical/non-technical/social
> contribution could be tolerated if they have a correspondingly strong
> positive social/non-technical/technical contribution.  I've seen lots
> of debate on both sides as to whether that is good or bad, but there
> are certainly consequences for being too liberal with booting people
> out, or keeping them around.
>
> I haven't heard many appeals during my time on the Council, but from
> the ones I have seen there were usually very good reasons for those
> who were asked to leave, and those same people were generally not very
> honest with the community about the reasons they were given for being
> booted.  One form of transparency I have suggested is that when
> disciplinary actions are given the person being disciplined should be
> given an explanation for why the action is being taken, and that at
> their option that explanation would be made public verbatim.  I've
> seen Debian do this and I thought it was a good way to balance
> privacy/transparency/risk.  The person being disciplined can at their
> option keep the whole matter quiet, or they can have it publicized in
> an official way.  However, if they decide to publish their own account
> of events while denying Gentoo permission to publish its side, then
> those listening will probably be skeptical that they're getting the
> full story.  Since Gentoo would not make any public statements without
> permission from the person impacted there would be little risk of
> legal repercussions.
>
I think that if this is the process, people are more likely to buy into
it, and accept that if that's the way it works, they can take it or
leave it - and the risk is more theirs than that of the organisation. I
think that in itself will garner more respect than the current situation
at least ..


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2018-04-13 22:29 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-13 17:31 [gentoo-project] pre-GLEP: Gentoo Developer status Michał Górny
2018-04-13 21:28 ` Francisco Blas Izquierdo Riera (klondike)
2018-04-13 21:57   ` Rich Freeman
2018-04-13 22:07     ` M. J. Everitt
2018-04-13 22:25       ` Rich Freeman
2018-04-13 22:29         ` M. J. Everitt [this message]
2018-04-13 22:41           ` Rich Freeman
2018-04-14  1:10             ` Alec Warner
2018-04-14  1:05         ` Raymond Jennings
2018-04-14  1:23           ` Rich Freeman
2018-04-14  1:33   ` Alec Warner
2018-04-14  5:59   ` Ulrich Mueller
2018-04-15 12:01     ` Francisco Blas Izquierdo Riera (klondike)
2018-04-15 12:25       ` Ulrich Mueller
2018-04-14  7:24   ` Michał Górny
2018-04-15 11:44     ` Francisco Blas Izquierdo Riera (klondike)
2018-04-15 12:03       ` Rich Freeman
2018-04-15 12:22       ` Michał Górny
2018-04-15 16:55         ` Francisco Blas Izquierdo Riera (klondike)
2018-04-15 17:22           ` M. J. Everitt
2018-04-22 17:24             ` Kent Fredric
2018-04-23 20:01               ` Robin H. Johnson
2018-04-23 21:30                 ` M. J. Everitt
2018-04-24  2:58                   ` Kent Fredric
2018-04-15 17:58           ` Michał Górny
2018-04-21 17:21             ` Francisco Blas Izquierdo Riera (klondike)
2018-04-14  6:57 ` Matthew Thode
2018-04-14  7:19   ` Michał Górny
2018-04-14  7:32     ` Matthew Thode
2018-04-14 20:58 ` Daniel Robbins
2018-04-14 21:16   ` Raymond Jennings

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=4da302dd-3e4f-42c0-b602-57e32272ce8a@iee.org \
    --to=m.j.everitt@iee.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