From: ludo@gnu.org (Ludovic Courtès)
To: Tonton <tonton@riseup.net>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] website: Add section section and links to code of conduct
Date: Thu, 17 May 2018 13:48:17 +0200 [thread overview]
Message-ID: <87a7sy1p1a.fsf@gnu.org> (raw)
In-Reply-To: <20180516180541.3c6c75c5@merlin.browniehive.net> (tonton@riseup.net's message of "Wed, 16 May 2018 18:05:41 +0200")
Hi,
Tonton <tonton@riseup.net> skribis:
> On Wed, 16 May 2018 16:06:07 +0100
> rain1@airmail.cc wrote:
>
>> For the section about IRC. Please add a bit that explains why you
>> shouldn't say "hi guys" when you join IRC. Instead "Hi guix" or "Hi
>> #guix" is recommended.
>>
>
> I'm not sure explaining some edge cases would be a-good-thing(tm). Instead I
> think it is better that we keep an eye out and tell each other when we make
> mistakes like this. This will also train our lenses to see these things
> better because we're using them.
I agree. I think it’s important to clearly explain the general spirit
(and have a code of conduct for that), and then handle “mistakes” like
these when they happen. For this specific case, I think it’s OK to
simply explain people when that happens that we’d prefer a
gender-neutral phrase, in line with our goal of being inclusive (I do
that from time to time on IRC and people understand, sometimes they just
didn’t realize.)
Ludo’.
prev parent reply other threads:[~2018-05-17 11:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 23:36 [PATCH] website: Add section section and links to code of conduct Tonton
2018-05-16 0:29 ` Tonton
2018-05-16 15:14 ` Nils Gillmann
2018-05-16 16:17 ` Tonton
2018-05-17 11:43 ` Ludovic Courtès
2018-05-17 13:13 ` Tonton
2018-05-17 21:28 ` Ricardo Wurmus
2018-05-16 15:06 ` Fwd: " rain1
2018-05-16 16:05 ` Tonton
2018-05-17 11:48 ` Ludovic Courtès [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a7sy1p1a.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=tonton@riseup.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.