From: Ned Ludd <solar@gentoo.org>
To: Donnie Berkholz <dberkholz@gentoo.org>
Cc: Ferris McCormick <fmccor@gentoo.org>, gentoo-council@lists.gentoo.org
Subject: Re: [gentoo-council] CoC: informal enforcement
Date: Thu, 14 Feb 2008 11:39:19 -0800 [thread overview]
Message-ID: <1203017959.4132.0.camel@hangover> (raw)
In-Reply-To: <20080214173141.GA3768@comet.science.oregonstate.edu>
On Thu, 2008-02-14 at 09:31 -0800, Donnie Berkholz wrote:
> On 12:36 Thu 14 Feb , Ferris McCormick wrote:
> > On Thu, 2008-02-14 at 02:13 -0800, Donnie Berkholz wrote:
> > > What I want to do is build a core culture of people who refuse to
> > > tolerate assholes. We can do this by getting together a small group
> > > who will reply to any gentoo-dev posts or #gentoo-dev comments by
> > > people who are being jerks, telling them that they're being a jerk
> > > and not replying to the substance of the jerk's post at all. Replies
> > > to the substance of a post would come separately or not at all.
> > > Having a group of people reply to hostile posters should begin
> > > rebuilding a culture that doesn't tolerate that type of action.
> > >
> > > People who are consistently jerks are incompetent developers and
> > > should be treated as such.
> >
> > 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.
>
> You make a good point. The CoC [1] is subject to some level of
> interpretation, and I think that these two provisions pretty much
> provide for what I'm suggesting:
>
> Be courteous. Though respect is earned, it must start somewhere.
> Respect someones right for their own opinion and acknowledge that they
> do deserve a measure of politeness in your response.
>
> Respectfully disagree with or challenge other members. The operative
> word here is respectfully.
>
> One thought I've had is that once we get this small group of people, we
> could talk in an IRC channel about whether a particular instance
> qualifies before responding.
>
> Thanks,
> Donnie
>
> 1. http://www.gentoo.org/proj/en/council/coc.xml
So in other words.. proctors all over again..
--
Ned Ludd <solar@gentoo.org>
Gentoo Linux
--
gentoo-council@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-02-14 19:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 10:13 [gentoo-council] CoC: informal enforcement Donnie Berkholz
2008-02-14 11:51 ` Luca Barbato
2008-02-14 12:36 ` Ferris McCormick
2008-02-14 17:31 ` Donnie Berkholz
2008-02-14 19:31 ` Wernfried Haas
2008-02-14 19:39 ` Ned Ludd [this message]
2008-02-14 19:44 ` Donnie Berkholz
2008-02-14 20:03 ` Ned Ludd
2008-02-14 20:08 ` Donnie Berkholz
2008-02-14 20:45 ` Roy Bamford
2008-02-14 21:24 ` Ned Ludd
2008-02-14 21:34 ` Donnie Berkholz
2008-02-14 21:22 ` Jorge Manuel B. S. Vicetto
2008-02-14 20:21 ` Roy Bamford
2008-02-14 21:25 ` Donnie Berkholz
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=1203017959.4132.0.camel@hangover \
--to=solar@gentoo.org \
--cc=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