From: Rich Freeman <rich@thefreemanclan.net>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Gentoo Code of Conduct
Date: Sun, 26 May 2013 08:40:55 -0400 [thread overview]
Message-ID: <CAGfcS_mrbCH8gKZF=J5Vha+7S2yV6zE9Kgtx5m+7MRXU9nJbow@mail.gmail.com> (raw)
In-Reply-To: <1369567950.2793.0@NeddySeagoon_SSD>
On Sun, May 26, 2013 at 7:32 AM, Roy Bamford <neddyseagoon@gentoo.org> wrote:
> I would delete everything from "Examples of inappropriate behavior" to
> the credits at the end. Escalation, punishment and appeal is already
> covered by devrel documentation.
>
I suspect that lack of punishment was basically the whole reason the
original CoC was written, and the whole reason the topic came up
again.
> If you want to say anything about enforcement in the CoC remind readers
> that everyone is responsible for enforcement.
That sounds a bit like nobody is responsible for enforcement. The
only thing devs can do to basically do what they're already doing -
having running arguments on the lists. The only way to block
inappropriate behavior is to moderate it.
Whether we want to do that is up to the community, but the existing
CoC is fine as-is if you don't want to do anything about enforcement,
IMHO.
Rich
next prev parent reply other threads:[~2013-05-26 12:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 11:46 [gentoo-project] Gentoo Code of Conduct Tomáš Chvátal
2013-05-24 12:59 ` Rich Freeman
2013-05-24 13:16 ` Tomáš Chvátal
2013-05-24 13:46 ` Rich Freeman
2013-05-24 17:13 ` Markos Chandras
2013-05-25 10:18 ` Tomáš Chvátal
2013-05-26 11:32 ` Roy Bamford
2013-05-26 12:40 ` Rich Freeman [this message]
2013-05-26 13:10 ` Roy Bamford
2013-05-26 13:58 ` Ian Stakenvicius
2013-05-26 14:46 ` Rich Freeman
2013-05-26 15:06 ` Denis Dupeyron
2013-05-26 17:06 ` Andreas K. Huettel
2013-05-26 19:03 ` Panagiotis Christopoulos
2013-05-26 20:00 ` Dale
2013-05-26 19:51 ` Robin H. Johnson
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_mrbCH8gKZF=J5Vha+7S2yV6zE9Kgtx5m+7MRXU9nJbow@mail.gmail.com' \
--to=rich@thefreemanclan.net \
--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