From: Tobias Geerinckx-Rice <tobias.geerinckx.rice@gmail.com>
To: "Taylan Ulrich Bayırlı/Kammer" <taylanbayirli@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: NEWS for 0.10.0
Date: Wed, 30 Mar 2016 13:02:15 +0200 [thread overview]
Message-ID: <CAKFHe2TS9EXAU7GU3nLNUL5EraMo6tzmg7M+Ztg8AjE6ootaAA@mail.gmail.com> (raw)
In-Reply-To: <87vb44xs8l.fsf@T420.taylan>
I know I'm an exception, but the mere existence of that
CODE-OF-CONDUCT file was the main reason for me to give Guix a try.
Then I stayed for the rest.
On 30/03/2016, Taylan Ulrich Bayırlı/Kammer <taylanbayirli@gmail.com> wrote:
> I much prefer the current COC to both that of GNOME and Debian.
+1 to this (and the rest of Taylan's message; I think +1s are lame but
I would have written the same less concisely anyway).
> I think trying to be apolitical is naive. In practice it boils down to
> accepting the status quo. In an unjust society, some injustices appear
> normal, therefore dissent against them is seen as more "political" than
> the tolerance of those injustices, even though tolerating injustices is
> surely a political move.
That Debian CoC is conspicuous in both its vagueness and how it avoids
talking about structural issues. This sends a clear political message,
whether one likes it or not.
Unfortunately, ‘be excellent to each other’ is not a CoC, and it's
often an excuse not to have one.
Kind regards,
T G-R
next prev parent reply other threads:[~2016-03-30 11:02 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 [this message]
2016-03-30 17:28 ` John Darrington
2016-03-30 20:17 ` Taylan Ulrich Bayırlı/Kammer
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=CAKFHe2TS9EXAU7GU3nLNUL5EraMo6tzmg7M+Ztg8AjE6ootaAA@mail.gmail.com \
--to=tobias.geerinckx.rice@gmail.com \
--cc=guix-devel@gnu.org \
--cc=taylanbayirli@gmail.com \
/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).