public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "William L. Thomson Jr." <wlt-ml@o-sinc.com>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] ComRel / disciplinary action reform proposal
Date: Wed, 18 Jan 2017 12:31:14 -0500	[thread overview]
Message-ID: <assp.0191beb8c4.1995388.cyKyTYy5Q1@wlt> (raw)
In-Reply-To: <20170117190530.23541e6d.mgorny@gentoo.org>

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

On Tuesday, January 17, 2017 7:05:30 PM EST Michał Górny wrote:
> On Tue, 17 Jan 2017 06:38:10 -0800
> 
> Daniel Campbell <zlg@gentoo.org> wrote:
> > 
> > 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.

Making everything public ensures no secrets. Privacy and secrecy should not 
exist or be needed for a public open source project. With the only exception 
being security vulnerabilities for obvious reason.

Any event being handled likely started in public to begin with, thus should 
remain that way for 100% transparency. Also to ensure no problems with leaking 
or making private/secret information public. Solves many problems.

-- 
William L. Thomson Jr.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  parent reply	other threads:[~2017-01-18 17:31 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
2017-01-17 18:13     ` Kristian Fiskerstrand
2017-01-18 17:31     ` William L. Thomson Jr. [this message]
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=assp.0191beb8c4.1995388.cyKyTYy5Q1@wlt \
    --to=wlt-ml@o-sinc.com \
    --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