unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: taylanbayirli@gmail.com (Taylan Ulrich Bayırlı/Kammer)
To: Mathieu Lirzin <mthl@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Contributor covenant
Date: Thu, 10 Dec 2015 21:22:39 +0100	[thread overview]
Message-ID: <87vb865a0g.fsf@T420.taylan> (raw)
In-Reply-To: <877fkn33sa.fsf@gnu.org> (Mathieu Lirzin's message of "Wed, 09 Dec 2015 18:55:33 +0100")

Mathieu Lirzin <mthl@gnu.org> writes:

>> In commit e15fcdd, I added a ‘CODE-OF-CONDUCT’ file taken from
>> <http://contributor-covenant.org/>, which is essentially a way of
>> telling the lurkers out there: yes, we do our best to be welcoming and
>> we’re committed to doing so, so join us!  The guix-maintainers@gnu.org
>> address it mentions is currently an alias for ludo@gnu.org (though I’d
>> like it to become more than just me!).
>
> Since Guix has (in my experience) always be a nice place, I don't think
> this is necessary to have this.  As much goodwill is the intention of
> this code of conduct, the ideas behind it don't make consensus in Free
> Software communities which can lead into unnecessary divisions (and we
> have already a lot of them).  See:
>
>   http://esr.ibiblio.org/?p=6918
>
> The problem is that this code of conduct pretends to give a warranty of
> an "harassment-free experience", which is is a slippery slope (Sorry to
> not be able to expand more on it in english).  IMHO it would be
> preferable to revert this commit, and let the necessary decisions be
> taken case by case when a bad behavior among Guix contributors arise.

ESR has some great technical contributions (most recent I know of being
moving Emacs to git), and social too (I owe him one for maintaining the
Hacker-Howto which was *the* document that initially got me into FLOSS,
Unix, etc.), but when it comes to "social justice" issues like sexism
and racism, I'm afraid his blog is not the best place to look...

Taylan


P.S.: if I were to go full-out on social ideology, I cannot recommend
Andrea Dworkin's books any more strongly.  There are free PDFs here:
<http://radfem.org/dworkin>.  /off-topic

      parent reply	other threads:[~2015-12-10 20:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09 13:39 Contributor covenant Ludovic Courtès
2015-12-09 13:58 ` Andreas Enge
2015-12-09 15:18   ` Alex Sassmannshausen
2015-12-09 15:27     ` Eric Bavier
2015-12-09 15:29     ` Taylan Ulrich Bayırlı/Kammer
2015-12-09 15:49 ` Ricardo Wurmus
2015-12-09 16:36   ` Alex Sassmannshausen
2015-12-09 16:46     ` Ludovic Courtès
2015-12-09 16:58     ` Ricardo Wurmus
2015-12-09 17:55 ` Mathieu Lirzin
2015-12-09 18:32   ` Ludovic Courtès
2015-12-10 11:08   ` Amirouche Boubekki
2015-12-10 13:13   ` Ricardo Wurmus
2015-12-10 18:56     ` Efraim Flashner
2015-12-10 20:22   ` Taylan Ulrich Bayırlı/Kammer [this message]

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=87vb865a0g.fsf@T420.taylan \
    --to=taylanbayirli@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=mthl@gnu.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.
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).