public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
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 23:29:51 -0500	[thread overview]
Message-ID: <d3b0d8c2-a767-0f91-6c6f-9b50026099b7@gentoo.org> (raw)
In-Reply-To: <efdcf518-141a-a2a4-d566-890281c51536@gentoo.org>

On 01/16/17 08:22, Paweł Hajdan, Jr. wrote:
> On 16/01/2017 05:56, Dean Stephens wrote:
>> I think this proposal is utterly unworkable in practice. While the
>> intention is rather obvious, and heavily geared toward actual
>> contributing members of the community at large, the proposed
>> definitional scope and structure are incompatible with actual workloads
>> already in place.
>>
>> [...]
>>
>> As it stands, disciplinary actions are handled per medium and channel,
>> with appeals going first to those with direct authority over that medium
>> or channel, then to ComRel, then the Council. This is simple,
>> consistent, and most of all it is on the whole effective; all while
>> minimizing the amount of make work. If there is meant to be an implicit
>> argument that this is somehow insufficiently documented, by all means
>> make that point, ask people to document things more pervasively, do not
>> discard a working system because someone could not be bothered to read
>> the documentation.
> 
> Good points.
> 
> IMO the proposal also has good points, and just needs to be updated to
> take scalability issues into account.
> 
The proposal is, in a nutshell, to file lots of bugs for the Council and
make them the first, last, and only point of appeal. Which effectively
makes the role of the Council to try keeping up with scrollback
literally everywhere that Gentoo staff/developers have disciplinary
authority due to their roles as Gentoo staff/developers; which, to be at
all realistic, is just not going to happen. It presents no novel net
benefits while incurring novel net costs. In short, the status quo is
superior to the proposed model.

> Maybe routine things like spam could go through forums-specific channel.
They already do, as do all other disciplinary actions on the forums. The
question should not be: "what can be special cased into being allowed to
have local handling by those responsible for a communications medium or
channel?" If anything, it should be: "what, if anything, should be
forced to be handled by people who are not necessarily involved with the
medium or channel in question?" To answer the latter with "first pass
appeals" serves to increase workloads generally and confusion on the
part of those not familiar with the process, though I suppose it would
suit functionaries fond of dismissing inquires with a quick "nothing I
can do".

> I don't see a reason to get a bug filed for each of these.
> 
Which is rather my point: filing the bugs as required by the proposal is
pointless, and rather excessive, make work. Disciplinary actions are
already documented, either in situ or privately as befits the action(s)
taken, and such documentation can be dumped to a suitable bug if and
when necessary, but making all such documentation into bugs serves no
useful purpose even if fully automated (which it most certainly is not
at the moment)... unless the goal is to force Council members to filter
their e-mail.

> Paweł
> 


  parent reply	other threads:[~2017-01-17  4:30 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 [this message]
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=d3b0d8c2-a767-0f91-6c6f-9b50026099b7@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