public inbox for gentoo-council@lists.gentoo.org
 help / color / mirror / Atom feed
From: Donnie Berkholz <dberkholz@gentoo.org>
To: Ferris McCormick <fmccor@gentoo.org>
Cc: gentoo-council <gentoo-council@lists.gentoo.org>
Subject: Re: [gentoo-council] Extent of Code of Conduct enforcement
Date: Thu, 14 Aug 2008 02:51:35 -0700	[thread overview]
Message-ID: <20080814095135.GC6477@comet> (raw)
In-Reply-To: <1216992299.10301.57.camel@liasis.inforead.com>

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

On 13:24 Fri 25 Jul     , Ferris McCormick wrote:
> Eventually, this was revised here:
> http://archives.gentoo.org/gentoo-council/msg_ba125098c929ea31f34051dfb009d436.xml
> advantage that it did not require any approval at all, but it most
> certainly *did* imply revisions to the Code of Conduct itself, because
> effectively it stripped out any authority from the (non-existent)
> proctors and instead identify a small group of people who would take
> aside CoC violators (in private) and suggest they quit doing whatever
> they were doing wrong.  For the record here, my response to this was:
> 
> [quote]
> 'Nice idea and worth a try.  I have one concern.  Since we are talking
> CoC here, I'd like to emphasise that "assholeness" should be determined
> within the guidelines of the CoC.  Not by some person's own conception
> of "assholeness" --- I'd hate to see a flame war about just who is being
> the asshole in any particular instance.'
> [/quote]
> 
> As best as I can tell, this proposal was *APPROVED*, and at 20080214, was left like this:
> 
> ================================
> Code of Conduct enforcement
> ---------------------------
> 	Promote individual devs responding to people who are being jerks.
> 	Keep responses private, unless that person gets out of hand.
> 
> 	dberkholz will get things going.
> 	To help or get advice, contact him.
> ===================================
> 
> I think the final intent was that Council expected the Code of Conduct
> to be pretty much self-enforcing, driven by members of the community who
> cared enough to take violators aside and calm them down, beat them over
> the head, or whatever.
> 
> So, my question remains:  Did this resolution ever make it into a
> revision of the Code of Conduct or not.  I thought it did, but can't
> find it.  If it didn't, it probably should, and this entire discussion
> should be interpreted with that intent.

Let me share my interpretation to make sure we're on the same page. The 
whole idea here is that there is no new official global response team 
like the proctors.

Nothing changed about the abilities & authorities of individual groups 
that were already in charge of their specific areas.

> In passing, I'll note something else.  The underlying assumption of the
> entire Code of Conduct threads over five months last year was that:
> 
> [quote from Donnie]
> 
> A primary focus of CoC enforcement is deterrence from continued 
> violation, so permanent action is unnecessary. Thus, what seems 
> necessary is a way to take rapid, private, temporary action.
> 
> [/quote from Donnie]
> 
> The focus here was on errant developers, but by validating userrel's role in
> all of this, we know it now explicitly applies to the entire community.
> However, the underlying "immediate and temporary" assumptions still apply,
> I would think.  Anything else would be a fundamental change as best as I
> can tell, and discussion should be framed and clearly understood on that
> context.

It's always desirable for people to change their behavior, but 
unfortunately it doesn't always happen.

Here, the first sentence you quoted is the important one. The second 
sentence only deals with the deterrence part of the first sentence. 
Nothing is addressed about the permanent action, because that email was 
about creating a new proctors-like group, and devrel/userrel already 
existed for permanent action.

-- 
Thanks,
Donnie

Donnie Berkholz
Developer, Gentoo Linux
Blog: http://dberkholz.wordpress.com

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-08-14  9:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-25 13:24 [gentoo-council] Extent of Code of Conduct enforcement Ferris McCormick
2008-08-14  9:51 ` Donnie Berkholz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-07-14  6:35 Donnie Berkholz
2008-07-14  8:23 ` Alec Warner
2008-07-14 14:48   ` Ferris McCormick
2008-07-14 18:23 ` Roy Bamford
2008-07-14 19:20 ` Tobias Scherbaum
2008-07-14 19:54   ` Ferris McCormick
2008-07-16  2:39 ` Chrissy Fullam
2008-07-16  2:54   ` Mike Doty
2008-07-16  3:07     ` Chrissy Fullam
2008-07-22  6:34 ` Mark Loeser
2008-07-22 12:26   ` Ferris McCormick
2008-07-22 13:33   ` Ferris McCormick
2008-07-22 14:21     ` Chrissy Fullam
2008-07-22 13:51   ` Chrissy Fullam

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=20080814095135.GC6477@comet \
    --to=dberkholz@gentoo.org \
    --cc=fmccor@gentoo.org \
    --cc=gentoo-council@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