public inbox for gentoo-council@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ferris McCormick <fmccor@gentoo.org>
To: Donnie Berkholz <dberkholz@gentoo.org>
Cc: gentoo-council <gentoo-council@lists.gentoo.org>,
	Roy Bamford <neddyseagoon@gentoo.org>
Subject: Re: [gentoo-council] User Relations authority
Date: Thu, 10 Jul 2008 12:26:12 +0000	[thread overview]
Message-ID: <1215692772.12648.239.camel@liasis.inforead.com> (raw)
In-Reply-To: <20080710054946.GB8666@comet>

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


On Wed, 2008-07-09 at 22:49 -0700, Donnie Berkholz wrote:
> From this month's agenda:
> 
>   User Relations authority
>   ------------------------
> 
>   Ferris asks: Does userrel have the authority to enforce the Code of
>   Conduct on users in the same way devrel does for developers?
> 
>   Preparation: Donnie will start a thread on the -council list. Post 
>   your opinion there. If everyone's posted in advance of the meeting, 
>   status check at meeting to see who's ready to vote.
> 
>   Goal: Reach a decision on-list no later than July 17.
> 
> Please respond with your thoughts.

I didn't even remember that I had asked this, but here are my thoughts.

1.  Yes, Userrel has (or should have) that authority;
2.  But for both devrel and userrel, the Code of Conduct loses almost
all its impact unless response is immediate --- CoC's intent, I think,
is to help keep the mailing lists and #gentoo-dev channel on track
pretty much in real time.  I know this was the original idea behind it,
and this was one reason we felt we needed people outside devrel to help
enforce it (devrel is not set up for immediate responses);
3.  Thus, I think bugzilla bugs for Code of Conduct violations miss much
of the point.
4.  That is, we (devrel, userrel, averyone else perhaps) should use Code
of Conduct to stop elaborate flame wars before they can burn out of
control.  Whether a flame war ever merits a bug will vary from situation
to situation, but generally if we have a flame war and wish to impose
some sort of sanctions because of it, we really need to be hitting
several people or none with warnings or brief "vacations."

5.  I am not sure where the current Code of Conduct document is, but
I'll volunteer to help update it to bring it into line with how we wish
to use it and to help clarify who has what authority under it, and that
sort of thing.  I have come to support it, and I'd like to help make it
more effectively used in the rather narrow context for which it was
designed before we consider extending its reach.
6.  For example, I think we could put some sort of limited moderation
onto the -dev mailing list, citing the current Code of Conduct as
authority, any time we wanted.  And I do not think the Code of Conduct
as currently envisioned has much reach into the past (one or two days,
probably; one or two weeks, perhaps; one or two months, no; one or two
years, certainly not).

I hope you get the idea.  Although I advocate brevity, I have problems
practicing it.

Regards,
Ferris
-- 
Ferris McCormick (P44646, MI) <fmccor@gentoo.org>
Developer, Gentoo Linux (Devrel, Sparc, Userrel, Trustees)

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2008-07-10 12:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-10  5:49 [gentoo-council] User Relations authority Donnie Berkholz
2008-07-10  5:53 ` Donnie Berkholz
2008-07-16  2:46   ` Chrissy Fullam
2008-07-10 11:49 ` Jorge Manuel B. S. Vicetto
2008-07-10 13:55   ` Ferris McCormick
2008-07-10 20:27     ` Petteri Räty
2008-07-11  4:24     ` Donnie Berkholz
2008-07-11 11:39       ` Thomas Anderson
2008-07-16  3:21       ` Chrissy Fullam
2008-07-10 12:26 ` Ferris McCormick [this message]
2008-07-11  4:54   ` Donnie Berkholz
2008-07-11 12:47     ` Ferris McCormick
2008-07-11 14:21       ` Roy Bamford
2008-08-14  9:28         ` Donnie Berkholz
2008-07-11 18:31       ` Alec Warner
2008-07-16  4:05       ` Chrissy Fullam
2008-07-22  6:43   ` Mark Loeser
2008-07-22 12:00     ` Ferris McCormick
2008-07-22 14:08     ` Chrissy Fullam
2008-07-10 15:08 ` Luca Barbato
2008-07-23 21:47 ` Petteri Räty

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=1215692772.12648.239.camel@liasis.inforead.com \
    --to=fmccor@gentoo.org \
    --cc=dberkholz@gentoo.org \
    --cc=gentoo-council@lists.gentoo.org \
    --cc=neddyseagoon@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