public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kent Fredric <kentnl@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] ComRel / disciplinary action reform proposal
Date: Mon, 16 Jan 2017 09:13:54 +1300	[thread overview]
Message-ID: <20170116091354.0e36f20a@katipo2.lan> (raw)
In-Reply-To: <CAGfcS_mcN6fnHvE3LqUYuOgjdcgvTU_hzKGV5bOZTafWs2et9A@mail.gmail.com>

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

On Sun, 15 Jan 2017 15:02:53 -0500
Rich Freeman <rich0@gentoo.org> wrote:

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

Would a way for allowing such excluded members to set "away" flags,
and have the status of those "away" flags being visible in the relevant
channels be a suitable approach?

That way its up to the individual to set it, but the visibility can be
only binary, "away" or "present" ( much narrower than the dev-away system )

That way the interpretation and definition of that state is up to individuals,
and people who are given "you're banned" notices can be simply reminded that they
can change this flag if they want to.

That would at least solve the "user is unaware that person can't/wont action on bugzilla"
side of the problem.

You could allow it to be freeform, but I see that as too much a temptation as
a further venue to be abusive.

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

  reply	other threads:[~2017-01-15 20:14 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 [this message]
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.
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=20170116091354.0e36f20a@katipo2.lan \
    --to=kentnl@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