From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id A5A6B1381F3 for ; Sun, 26 May 2013 13:58:02 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 105C2E0B66; Sun, 26 May 2013 13:58:00 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 66A23E0B4E for ; Sun, 26 May 2013 13:57:59 +0000 (UTC) Received: from [192.168.1.160] (bas1-ottawa09-2925287262.dsl.bell.ca [174.92.87.94]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: axs) by smtp.gentoo.org (Postfix) with ESMTPSA id 6904233DF13 for ; Sun, 26 May 2013 13:57:58 +0000 (UTC) Message-ID: <51A214E8.5070509@gentoo.org> Date: Sun, 26 May 2013 09:58:00 -0400 From: Ian Stakenvicius User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130523 Thunderbird/17.0.6 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Project discussion list X-BeenThere: gentoo-project@lists.gentoo.org Reply-To: gentoo-project@lists.gentoo.org MIME-Version: 1.0 To: gentoo-project@lists.gentoo.org Subject: Re: [gentoo-project] Gentoo Code of Conduct References: <1369567950.2793.0@NeddySeagoon_SSD> In-Reply-To: X-Enigmail-Version: 1.6a1pre Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: b6f5ba4f-d36e-4b36-b47a-f29ab5bb2cc4 X-Archives-Hash: 0dcb6ac57940af65097ba2a3dbd48981 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 26/05/13 08:40 AM, Rich Freeman wrote: > On Sun, May 26, 2013 at 7:32 AM, Roy Bamford > wrote: > >> 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. Alternatively, it empowers any dev to help stop this behaviour, rather than just the moderators. Sort of the same way bullying needs to be dealt with -- if the whole community takes responsibility for treating it as unacceptable, and calls on it right away, then things are a lot more effective than relegating to a relatively small set of authorities (although of course, there will always be a need for those authorities too). -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlGiFOgACgkQ2ugaI38ACPDETAD/cG1BBrDSfsQHQrZjgnsUanw7 JfM5RAPRaA3C9wVPuEYA/jgHoGwGRkBVYvywNn7lnAZqw8vVDOR/ivy41QOkiUJC =YCot -----END PGP SIGNATURE-----