public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: desultory <desultory@gentoo.org>
Cc: gentoo-project <gentoo-project@lists.gentoo.org>
Subject: Re: [gentoo-project] Appeals of Moderation Decisions
Date: Sun, 3 Feb 2019 06:53:56 -0500	[thread overview]
Message-ID: <CAGfcS_m6k28gLHm9fOb9A0fCbX2z-nT86_hdGPDmZ+SveYOWtA@mail.gmail.com> (raw)
In-Reply-To: <6a80c6d4-3f4e-2492-f883-e57fa457b7af@gentoo.org>

On Sat, Feb 2, 2019 at 11:22 PM desultory <desultory@gentoo.org> wrote:
>
> On 02/02/19 08:41, Rich Freeman wrote:
> >
> > So far the proctors have mainly focused on areas like the
> > lists/bugzilla where productive Gentoo development occur which lack
> > any other moderation.  When other moderation teams are already
> > creating a place for productive Gentoo work we haven't gotten as
> > involved yet, such as:
> >
> > https://forums.gentoo.org/viewtopic-t-1090810-postdays-0-postorder-asc-start-50.html
> > https://forums.gentoo.org/viewtopic-t-1080592-postdays-0-postorder-asc-start-25.html
> > https://forums.gentoo.org/viewtopic-t-1049438-start-0-postdays-0-postorder-asc-highlight-.html
> > https://forums.gentoo.org/viewtopic-t-1091348.html
> >
> Four topics in an expressly off-topic forum, none of which were actually
> in the state that was claimed by the complainant, makes for a rather
> poor example of where proctors have not "gotten as involved yet". Given
> that there was nothing to get involved in.

They simply illustrate that the code of conduct not really being applied.

The Code of Conduct simply states that it applies to Gentoo's "public
communication mediums."  It makes no exceptions for forums that claim
to be off-topic.

If we think that part of Gentoo's mission ought to be competing with
4chan or whatever maybe it needs to be amended...

>
> > I'm not saying that we need some kind of mad rush to consolidate all
> > moderation activity (otherwise I'd be proposing this).
>
> CoC enforcement does not
> appear to be effectively implemented even in that limited scope; despite
> evident efforts to engage in scope creep. This is a distinctly
> concerning trend, as it rather strongly indicates that the current
> proctors project either cannot or will not actually undertake its
> mandate, while it seeks to expand its direct sphere of responsibility;

Citation?

I am speaking only for myself, not for proctors, and insofar as I'm
stating my own opinion so far I've said:

1.  We shouldn't move to consolidate Forum/IRC moderators under Proctors.

2.  Proctors shouldn't receive appeals from these teams, but that like
Proctors appeals ought to go to Comrel.

How this suggests that Proctors is trying to increase its scope is
unclear to me.  I personally agree that Proctors is still getting
re-established and should continue to focus more on areas lacking
moderation until processes/etc are better documented and are working
well in practice.

That said, the lists haven't been that terrible of late, certainly not
compared to years past.  Proctors has generally been trying to avoid
issuing warnings for every sentence that is a bit snarky.

-- 
Rich


  parent reply	other threads:[~2019-02-03 11:54 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
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 [this message]
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=CAGfcS_m6k28gLHm9fOb9A0fCbX2z-nT86_hdGPDmZ+SveYOWtA@mail.gmail.com \
    --to=rich0@gentoo.org \
    --cc=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