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] ComRel / disciplinary action reform proposal
Date: Sun, 15 Jan 2017 23:05:43 +0000	[thread overview]
Message-ID: <587C0047.9000002@iee.org> (raw)
In-Reply-To: <CAGfcS_mcN6fnHvE3LqUYuOgjdcgvTU_hzKGV5bOZTafWs2et9A@mail.gmail.com>


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

On 15/01/17 20:02, Rich Freeman wrote:
> On Sun, Jan 15, 2017 at 2:23 PM, Michał Górny <mgorny@gentoo.org> wrote:
>> 2. Transparency
>> ---------------
>> Any disciplinary action should be announced by the team in a manner
>> specific to the appropriate media where the measure applies.
>> The announcement should be visible to all users of that media,
>> and contains:
>>
>> - the name of the user to whom the measure applies,
>>
>> - the description and length of the measure applied.
> I think most of your proposal is reasonable, except for this point.
>
> I'd prefer that transparency be done in an anonymous way.  I'm fine
> with the individuals being affected by a disciplinary action
> voluntarily choosing to allow this information to be divulged.
> However, if somebody is the subject of discipline they shouldn't be
> turned into public examples for a few reasons:
>
> 1.  It makes them hard to rejoin the community after their
> ban/whatever is over, because now they have a public reputation.
> 2.  It can damage somebody's public reputation, which could affect
> their ability to work on non-Gentoo projects or even for them to find
> employment.
> 3.  Because of #2, it tends to force the subject of an action to
> defend their reputation in public, which then leads to arguments/etc.
> 4.  Also because of #2, it may lead the subject of an action to defend
> their reputation using the courts, which can become an expensive
> proposition for all involved.
> 5.  #3-4 will tend to render moot your suggestion to keep the details
> of infractions private, since it will probably tend to come out in all
> the arguing.  Or, if it doesn't then all that argument doesn't
> actually serve any productive purpose since there are no facts
> involved.
>
> If the concern is abuse then let those who feel they were the victims
> of abuse be the ones to choose whether they make it a public issue.
> And by all means publish anonymous information about the volume of
> actions so that we can collectively judge whether it is happening too
> often/little/etc.
>
I respectfully disagree.

If a persons actions have escalated to an extent where disciplinary
action becomes necessary, it should have become patently obvious by this
point that something has gone badly wrong, and that the consequences of
this are that you may be publicly named and shamed. Where there may be
some legal angle, I feel there may be cause to anonymise until legal
advice has been sought, but in that event, you may not wish to publish
anything until you know where you stand anyway. In the rare event that
an error occurs, a public apology may be the correct course of action to
rectify any public disclosure that may have previously occurred. This
too, should function as a check-and-balance that you're doing The Right
Thing(tm).

If it is deemed immediate and escalated action is necessary as the First
step, I think you're going to be seeking advice anyway, and it should be
apparent that such action is only desirable in very rare and severe
cases. Again, the knowledge that you may have to quickly backtrack and
perform a public apology should function as a check-and-balance.

Increased transparency and the fear of real consequences to your actions
should be an adequate deterrent to anyone thinking of stirring the pot.
It works elsewhere, why should Gentoo be such a special case?!


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

  parent reply	other threads:[~2017-01-15 23:05 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-15 19:23 [gentoo-project] ComRel / disciplinary action reform proposal Michał Górny
2017-01-15 19:38 ` Raymond Jennings
2017-01-15 20:06   ` Rich Freeman
2017-01-15 20:02 ` Rich Freeman
2017-01-15 20:13   ` Kent Fredric
2017-01-15 23:05   ` M. J. Everitt [this message]
2017-01-16 17:54     ` Alec Warner
2017-01-15 21:59 ` Dale
2017-01-16  5:00   ` Dean Stephens
2017-01-15 22:55 ` M. J. Everitt
2017-01-16  0:25 ` Jorge Manuel B. S. Vicetto
2017-01-16  0:44   ` Raymond Jennings
2017-01-16  0:55     ` Rich Freeman
2017-01-16 11:16   ` Jeroen Roovers
2017-01-16 19:35     ` Jorge Manuel B. S. Vicetto
2017-01-17 17:38   ` Michał Górny
2017-01-16  4:56 ` Dean Stephens
2017-01-16 13:22   ` Paweł Hajdan, Jr.
2017-01-16 13:40     ` Kristian Fiskerstrand
2017-01-17  4:30       ` Dean Stephens
2017-01-17  4:29     ` Dean Stephens
2017-01-17 17:41   ` Michał Górny
2017-01-20  5:02     ` Dean Stephens
2017-01-16 20:57 ` William L. Thomson Jr.
2017-01-17 17:49   ` Michał Górny
2017-01-17 18:54     ` William L. Thomson Jr.
2017-01-17 19:03       ` Rich Freeman
2017-01-17 19:40         ` William L. Thomson Jr.
2017-01-17 20:20           ` Rich Freeman
2017-01-18  5:33             ` Raymond Jennings
2017-01-18 17:07             ` William L. Thomson Jr.
2017-01-17 14:38 ` Daniel Campbell
2017-01-17 15:26   ` Rich Freeman
2017-01-17 18:05   ` Michał Górny
2017-01-17 18:13     ` Kristian Fiskerstrand
2017-01-18 17:31     ` William L. Thomson Jr.
2017-01-18 18:25       ` Michał Górny
2017-01-18 18:31         ` William L. Thomson Jr.
2017-01-18 19:05           ` Rich Freeman
2017-01-18 19:13             ` William L. Thomson Jr.

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=587C0047.9000002@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