public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] ComRel / disciplinary action reform proposal
Date: Tue, 17 Jan 2017 10:26:58 -0500	[thread overview]
Message-ID: <CAGfcS_nzFL2Em7kYNnzkNT7tbTVUaqP59iW2pdnrkpDyrsYxNA@mail.gmail.com> (raw)
In-Reply-To: <07794881-ff2b-f269-7b0c-ec3b9ef9133f@gentoo.org>

On Tue, Jan 17, 2017 at 9:38 AM, 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.

++, in general (and anybody else doing the actual moderation/etc).

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

I tend to agree, but perhaps it would still make sense to restrict the
use of Gentoo media for such things (anything bearing our trademark).
My thinking is that we really don't want the community to be full of
petty personal bickering.

It isn't something I feel strongly about.  I'm more concerned about
people entrusted with personal information keeping it private.

-- 
Rich


  reply	other threads:[~2017-01-17 15:27 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 [this message]
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=CAGfcS_nzFL2Em7kYNnzkNT7tbTVUaqP59iW2pdnrkpDyrsYxNA@mail.gmail.com \
    --to=rich0@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