From: Dean Stephens <desultory@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] ComRel / disciplinary action reform proposal
Date: Mon, 16 Jan 2017 00:00:52 -0500 [thread overview]
Message-ID: <6e9b63ee-371d-2e4a-dd7a-caeeeff52c7d@gentoo.org> (raw)
In-Reply-To: <44e25740-6b88-43b9-e63b-aea93eff5caf@gmail.com>
On 01/15/17 16:59, Dale wrote:
>
> Again, this may not be possible for Gentoo. However, it may give some
> out of the Gentoo box thinking. One thing about it, the person may not
> even have to appeal what John did. If it is set so that the ComRel lead
> or council can see what happened and why, and they disagree, it could be
> corrected fairly quickly. It all depends on just how you can set this
> up on Gentoo. The private staff area may be bugzilla or something
> else. On mailing lists, I'm not sure how this would work unless a email
> is sent to the mailing list the person is subscribed to that says member
> xyz is restricted. Maybe some automatic method that is scripted or
> something.
>
It is historically significant, in this context, to note that merely
reporting a disciplinary action was enough to force the disbanding of
the entire Proctors project.
next prev parent reply other threads:[~2017-01-16 5:00 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 [this message]
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=6e9b63ee-371d-2e4a-dd7a-caeeeff52c7d@gentoo.org \
--to=desultory@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