unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: Julien Lepiller <julien@lepiller.eu>
Cc: guix-devel@gnu.org
Subject: Re: [minor patch] Amend CoC
Date: Sun, 20 Feb 2022 13:16:51 +0000	[thread overview]
Message-ID: <9mLFuyuqpYW-qPO0Su8bn7l2Zt3ZBCkkKe3glCQe-pa5xO_1YoZ3vqjs26olVgd7ud0yFinB-TrF3U4CuJxpL_wlPHmfhDgDqIxIauoBLNA=@elenq.tech> (raw)
In-Reply-To: <0C9CC84D-C57F-4EC1-AAEC-45FF80E4B837@lepiller.eu>

[-- Attachment #1: Type: text/plain, Size: 1435 bytes --]

I have a weird question about this that might be a little bit offtopic.

Why should we specify reasons? It's like we are saying some reasons are more important than others.

Is it not ok with...

> our project and our community a harassment-free experience for everyone.

?

That should cover everything.
I don't think anyone is reading all the list and saying: "oh they are missing race so it's ok for a racist like me to join and harass people"

It's just a feeling. It would also remove the discussion about including sex or not.

WDYT?
------- Original Message -------
On Sunday, February 20th, 2022 at 2:10 PM, Julien Lepiller <julien@lepiller.eu> wrote:

> Sounds good, but isn't that included in "sexual identity" already? For reference, where does the author say that?
>
> On February 20, 2022 2:02:07 PM GMT+01:00, Taylan Kammer <taylan.kammer@gmail.com> wrote:
>
>> This is a really tiny thing.  A recent thread on the ML prompted me to
>>
>> look at our CoC and I noticed it doesn't include 'sex' in the list of
>>
>> things based on which one might be discriminated against, so attached
>>
>> is a patch that adds that one word.
>>
>> Note: The upstream Contributor Covenant wouldn't want to include it
>>
>> because the author seems to have a peculiar world-view where they don't
>>
>> acknowledge that humans actually have a sex.  I hope the Guix maintainers
>>
>> are more reasonable than that. :-)
>>
>> --
>>
>> Taylan

[-- Attachment #2: Type: text/html, Size: 2679 bytes --]

  reply	other threads:[~2022-02-20 13:18 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-20 13:02 [minor patch] Amend CoC Taylan Kammer
2022-02-20 13:10 ` Julien Lepiller
2022-02-20 13:16   ` Ekaitz Zarraga [this message]
2022-02-20 16:29     ` Taylan Kammer
2022-02-20 17:44       ` Ekaitz Zarraga
2022-02-20 16:19   ` Taylan Kammer
  -- strict thread matches above, loose matches on Subject: below --
2022-02-20 18:05 Liliana Marie Prikler
2022-02-20 18:45 ` Maxime Devos
2022-02-20 19:30   ` Liliana Marie Prikler
2022-02-20 20:56   ` Jonathan McHugh
2022-02-20 21:12     ` Liliana Marie Prikler
2022-02-20 21:47     ` Jonathan McHugh
2022-02-20 19:43 ` Taylan Kammer
2022-02-20 21:37   ` Thiago Jung Bauermann
2022-02-20 22:01     ` Taylan Kammer
2022-02-21 16:18       ` Christine Lemmer-Webber
2022-02-21 16:01   ` Christine Lemmer-Webber
2022-02-22 17:16     ` Taylan Kammer
2022-02-23  9:48       ` Andy Wingo
2022-02-23 10:10         ` Oliver Propst
2022-02-20 19:47 ` Mark H Weaver
2022-02-20 21:02   ` Liliana Marie Prikler
2022-02-20 22:45     ` Taylan Kammer
2022-02-21  8:24       ` Tissevert
2022-02-21 21:03       ` Liliana Marie Prikler
2022-02-21 21:11         ` Tobias Geerinckx-Rice
2022-02-20 21:37 Blake Shaw
2022-02-23 11:38 Blake Shaw

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='9mLFuyuqpYW-qPO0Su8bn7l2Zt3ZBCkkKe3glCQe-pa5xO_1YoZ3vqjs26olVgd7ud0yFinB-TrF3U4CuJxpL_wlPHmfhDgDqIxIauoBLNA=@elenq.tech' \
    --to=ekaitz@elenq.tech \
    --cc=guix-devel@gnu.org \
    --cc=julien@lepiller.eu \
    /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).