public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: desultory <desultory@gentoo.org>
To: gentoo-project@lists.gentoo.org, Raymond Jennings <shentino@gmail.com>
Subject: Re: [gentoo-project] Appeals of Moderation Decisions
Date: Sat, 2 Feb 2019 01:38:44 -0500	[thread overview]
Message-ID: <57b016d8-e7d2-829e-5b34-e63252226123@gentoo.org> (raw)
In-Reply-To: <CAGDaZ_q5V1sDVnWc4QwUQ9zrDjAuvTt1_FLrtfkzu=onjfar+g@mail.gmail.com>

On 01/31/19 18:21, Raymond Jennings wrote:
> On Thu, Jan 31, 2019 at 11:27 AM Rich Freeman <rich0@gentoo.org> wrote:
> 
>> On Thu, Jan 31, 2019 at 2:11 PM Rich Freeman <rich0@gentoo.org> wrote:
>>>
>>> Can Council define an appeals process for appeals of moderation
>>> decisions in general for any official Gentoo communications media?  I
>>> think we have this for mailing lists, as Proctors is the only real
>>> moderation there and Proctors does have an appeals process.  I think
>>> IRC and Forums are the areas with gaps - to the extent that either has
>>> an appeals process I can't find it documented anywhere (I welcome
>>> leads in both areas to comment).
>>>
>>
>> Proctors already has a defined appeals process.  Minor actions like
>> warnings or short bans are final, and longer bans are appealable to
>> Comrel.  IMO this is a reasonable balance.
>>
>> To the extent that either IRC or Forums formally has a process for
>> short-term bans (<1wk)/etc I would suggest those also be
>> non-appealable beyond any internal process these teams have.
>>
>> For appeals beyond this I suggest that Comrel also be the point of
>> appeal.  I think Proctors could also work, but it raises the question
>> of bureaucracy as in theory an IRC op might make a decision, then
>> Proctors takes an appeal, then Comrel takes an appeal, and then maybe
>> even Council takes an appeal.  That is a lot of appeals.
>>
> 
> My two cents:
> 
> Would there be any merit for the imposition of additional sanctions for
> abuse of process if an appeal is determined to be frivolous?
> 
> This might mitigate any concern about excessive bureaucracy.
> 
Additional bureaucracy would mitigate concern about excessive
bureaucracy? ;)

Seriously though, the option to sanction users (which expressly must
include all developers) for frivolous appeals could at least potentially
reduce concerns regarding abuse of that appeals process. However,
mishandling of appeals is also a concern which bears addressing if one
is going quite that far down the bureaucratic rabbit hole.

Cases where an appeals process, with regard to electronic media, is
being abused tend to already have some underlying issue; if they don't
the sanctions process is almost certainly being abused.

> 
>> Very long-term it might make sense to try to better harmonize how we
>> do moderation on all these different media, but I think that is really
>> a separate issue, and doesn't need to be settled right away.  I think
>> that the absence of ANY appeals process in the interim is more of an
>> issue, as it does leave people who are subject to what might be one
>> person's decision no real access to due process.  Even if all the
>> moderators are doing a perfect job there should be a process.
>>
>> I'd encourage IRC ops or Forums mods to chime in with their thoughts
>> here...
>>
>> --
>> Rich
>>
>>
> 



  reply	other threads:[~2019-02-02  6:39 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-31 16:28 [gentoo-project] Call for agenda items - Council meeting 2019-02-10 Kristian Fiskerstrand
2019-01-31 19:11 ` Rich Freeman
2019-01-31 19:18   ` Kristian Fiskerstrand
2019-01-31 19:27   ` [gentoo-project] Appeals of Moderation Decisions Rich Freeman
2019-01-31 23:21     ` Raymond Jennings
2019-02-02  6:38       ` desultory [this message]
2019-02-02  7:06         ` Raymond Jennings
2019-02-02  6:34     ` desultory
2019-02-02 13:41       ` Rich Freeman
2019-02-03  4:22         ` desultory
2019-02-03 11:44           ` Andreas K. Huettel
2019-02-03 12:23             ` Michał Górny
2019-02-04  4:56               ` desultory
2019-02-04  5:39                 ` Michał Górny
2019-02-05  5:01                   ` desultory
2019-02-03 13:41             ` Kristian Fiskerstrand
2019-02-03 13:53               ` Andreas K. Huettel
2019-02-03 14:26                 ` Kristian Fiskerstrand
2019-02-03 15:51                   ` Kristian Fiskerstrand
2019-02-04  1:38                     ` Chí-Thanh Christopher Nguyễn
2019-02-04  4:59                       ` desultory
2019-02-04 13:05                       ` Andreas K. Huettel
2019-02-05 13:05                         ` Chí-Thanh Christopher Nguyễn
2019-02-05 13:05                           ` Kristian Fiskerstrand
2019-02-05 13:17                             ` Chí-Thanh Christopher Nguyễn
2019-02-04 13:45                       ` Rich Freeman
2019-02-05  5:01                         ` desultory
2019-02-05 12:47                         ` Chí-Thanh Christopher Nguyễn
2019-02-04  4:58                     ` desultory
2019-02-04  4:57                 ` desultory
2019-02-03 11:53           ` Rich Freeman
2019-02-04  5:05             ` desultory

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=57b016d8-e7d2-829e-5b34-e63252226123@gentoo.org \
    --to=desultory@gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    --cc=shentino@gmail.com \
    /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