From: "Michał Górny" <mgorny@gentoo.org>
To: Daniel Campbell <zlg@gentoo.org>
Cc: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] ComRel / disciplinary action reform proposal
Date: Tue, 17 Jan 2017 19:05:30 +0100 [thread overview]
Message-ID: <20170117190530.23541e6d.mgorny@gentoo.org> (raw)
In-Reply-To: <07794881-ff2b-f269-7b0c-ec3b9ef9133f@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2910 bytes --]
On Tue, 17 Jan 2017 06:38:10 -0800
Daniel Campbell <zlg@gentoo.org> wrote:
> On 01/15/2017 11:23 AM, Michał Górny wrote:
> > It should be noted that an unauthorized disclosure of sensitive
> > information by any party involved would be a base for a strong
> > disciplinary action.
>
> Overall fair procedures and points, but this particular part punishes
> whistleblowing, from inside *or* outside Gentoo. If a given
> target/subject decides to share all related communications to make their
> points publicly, the above suggestion recommends the subject is silenced
> and/or ejected for revealing something directly involving them.
>
> If the intent is to make whistleblowing risky or otherwise (socially)
> dangerous, then it'll get the job done, but at a cost to community
> morale over the long term. I don't support a procedure that punishes
> people for pointing out when it (the procedure) is not working correctly.
>
> I think a more fair restriction would be to place it on Comrel and
> Council, as they are being trusted to not share private information.
> What the two (or more?) sides do in a dispute isn't something we can
> reasonably control, except on our own infrastructure. I find it
> unnecessary and meaningless to place sanctions on users or other
> participants of a conflict if they choose to make their communications
> public. It's /their/ dirty laundry, after all.
This particular point, aside to ensuring that teams keep the necessary
secrecy, serves the goals:
1. to discourage users from taking 'revenge' on others by disclosing
their secrets,
2. to discourage users from bickering and turning Gentoo into a public
stoning place whenever they are unhappy with a disciplinary decision.
The first point is more important. Consider the following case. Alice
tells Bob her secret. Some time later Bob starts bullying Alice.
Eventually, Alice files a complaint at ComRel and Bob gets banned. Now,
Bob wants to reveal Alice's secret to take revenge on her.
Do you really think he should be allowed do that, just because he
disagrees with the decision? Because I certainly don't think we should
support behavior like that, and as far as I'm concerned a person that
does that should be isolated from the Gentoo community.
The second point has already been covered by Rich. If you believe
the decision was unjust, appeal. If your appeal was overthrown, get on
with it. We don't really need people turning themselves into martyrs,
demanding public judgment and ComRel stoning three times a day.
I know this rule won't prohibit this completely but I believe we're
really better off without public prosecutions. I should also point out
that some people jump straight to this without even filing an appeal --
and I think that's the best proof we need.
--
Best regards,
Michał Górny
<http://dev.gentoo.org/~mgorny/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
next prev parent reply other threads:[~2017-01-17 18:06 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
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 [this message]
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=20170117190530.23541e6d.mgorny@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
--cc=zlg@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