unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: taylanbayirli@gmail.com (Taylan Ulrich Bayırlı/Kammer)
To: John Darrington <john@darrington.wattle.id.au>
Cc: guix-devel@gnu.org
Subject: Re: NEWS for 0.10.0
Date: Wed, 30 Mar 2016 22:17:14 +0200	[thread overview]
Message-ID: <87egaryb3p.fsf@T420.taylan> (raw)
In-Reply-To: <20160330172855.GA1172@jocasta.intra> (John Darrington's message of "Wed, 30 Mar 2016 19:28:55 +0200")

John Darrington <john@darrington.wattle.id.au> writes:

> 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 - 
> all the examples of unacceptable conduct I personally consider unacceptable
> in all walks of life.  
>      
>      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 
> suggestion that lies behind it.  Viz:  "You might be a person who habitually uses
> sexually explicit language, insults people, harrasses others,  assaults people, 
> ... murders them ..."

The COC is there for everyone; I don't see why anybody should take it
personally and feel accused of anything.

> 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 why 
> accuse a person of those things on the first introduction?
>
> The second is:
>
> By having an explicit coc, the explicit message is "Examples of unacceptable 
> behavior by participants include ..." The implicit message which is a logical 
> consequence is: "... and we anticipate or have already experienced such 
> behaviour by participants."

Sure.  We're on the Internet. :-)

> When I invite someone to my home for coffee, I do have a "code of conduct"  I 
> expect my guests to be resonably polite, not to insult me, not to vandalise my 
> home, fart in my face and lots of other things.  But I this "code of conduct" is
> implicit.  I don't write it down.  I don't ask my guests to agree to it before 
> they enter my home - if I did I would not be suprised if the very suggestion 
> would cause them to be extremely offended.   I would not blame them if they 
> excused themselves and departed without delay.  Likewise I think these "codes of
> conduct" in community projects do not have the effect of welcoming people.  They
> have the opposite effect.  

There's the point that things are different on the Internet, and then
there's a point to be made about one-to-one or small-group meetings
where bad behavior will stick out immediately vs. large conventions
where bad behavior might remain undetected.  Having a COC gives a
guarantee to participants that if they personally have a bad experience,
they can bring it up to the organizers and action *will* be taken.  The
same principle applies to a large online community.

> So lets HAVE a code of conduct.  But let's not have a written one.  Let's be open
> and inviting.  If somebody does come in and start harassing/insulting/sexually 
> assaulting/ people (which I think unlikely) we'll uninvite them.
>
> J'

Taylan

  reply	other threads:[~2016-03-30 20:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-27 17:45 NEWS for 0.10.0 Ludovic Courtès
2016-03-27 21:38 ` Mathieu Lirzin
2016-03-28 16:36   ` Ludovic Courtès
2016-03-30  2:01   ` Rastus Vernon
2016-03-30  2:39     ` Jookia
2016-03-30  8:52     ` Taylan Ulrich Bayırlı/Kammer
2016-03-30 11:02       ` Tobias Geerinckx-Rice
2016-03-30 17:28         ` John Darrington
2016-03-30 20:17           ` Taylan Ulrich Bayırlı/Kammer [this message]
2016-03-30 21:22       ` Ludovic Courtès
2016-03-27 21:41 ` Leo Famulari

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87egaryb3p.fsf@T420.taylan \
    --to=taylanbayirli@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=john@darrington.wattle.id.au \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).