From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Darrington Subject: Re: NEWS for 0.10.0 Date: Wed, 30 Mar 2016 19:28:55 +0200 Message-ID: <20160330172855.GA1172@jocasta.intra> References: <87h9fryfub.fsf@gnu.org> <87twjrvbyb.fsf@gnu.org> <1459303276.4007.9.camel@openmailbox.org> <87vb44xs8l.fsf@T420.taylan> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="DocE+STaALJfprDB" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54595) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1alJvV-0005u5-GZ for guix-devel@gnu.org; Wed, 30 Mar 2016 13:29:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1alJvR-0001rf-31 for guix-devel@gnu.org; Wed, 30 Mar 2016 13:29:05 -0400 Received: from de.cellform.com ([88.217.224.109]:46450 helo=jocasta.intra) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1alJvQ-0001qF-RM for guix-devel@gnu.org; Wed, 30 Mar 2016 13:29:01 -0400 Content-Disposition: inline In-Reply-To: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Tobias Geerinckx-Rice Cc: guix-devel@gnu.org --DocE+STaALJfprDB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 30, 2016 at 01:02:15PM +0200, Tobias Geerinckx-Rice wrote: There is nothing in the current coc which I particularly disagree with -=20 all the examples of unacceptable conduct I personally consider unacceptable in all walks of life. =20 =20 Unfortunately, ???be excellent to each other??? is not a CoC, and it's often an excuse not to have one. I can think of two much better "excuses" : The first is: What hurts me when somebody shoves a "code-of-conduct" in my face, is the = veiled=20 suggestion that lies behind it. Viz: "You might be a person who habituall= y uses sexually explicit language, insults people, harrasses others, assaults peo= ple,=20 =2E.. murders them ..." Of course, on a literal level this suggestion is correct, for a person who = has never met me, for all they know I might be a person who does those things. But w= hy=20 accuse a person of those things on the first introduction? The second is: By having an explicit coc, the explicit message is "Examples of unacceptabl= e=20 behavior by participants include ..." The implicit message which is a logic= al=20 consequence is: "... and we anticipate or have already experienced such=20 behaviour by participants." When I invite someone to my home for coffee, I do have a "code of conduct" = I=20 expect my guests to be resonably polite, not to insult me, not to vandalise= my=20 home, fart in my face and lots of other things. But I this "code of conduc= t" is implicit. I don't write it down. I don't ask my guests to agree to it bef= ore=20 they enter my home - if I did I would not be suprised if the very suggestio= n=20 would cause them to be extremely offended. I would not blame them if they= =20 excused themselves and departed without delay. Likewise I think these "cod= es of conduct" in community projects do not have the effect of welcoming people. = They have the opposite effect. =20 So lets HAVE a code of conduct. But let's not have a written one. Let's b= e open and inviting. If somebody does come in and start harassing/insulting/sexua= lly=20 assaulting/ people (which I think unlikely) we'll uninvite them. J' =20 --=20 Avoid eavesdropping. Send strong encryted email. PGP Public key ID: 1024D/2DE827B3=20 fingerprint =3D 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3 See http://sks-keyservers.net or any PGP keyserver for public key. --DocE+STaALJfprDB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlb8DNcACgkQimdxnC3oJ7MnxwCeMqv59RegqXlpV47wxcgI7vJe LogAniTJf7JK60HhdrlHPX4LG/hM2YMD =GL6j -----END PGP SIGNATURE----- --DocE+STaALJfprDB--