unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ryan Sundberg via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: guix-devel@gnu.org, Taylan Kammer <taylan.kammer@gmail.com>,
	Blake Shaw <blake@nonconstructivism.com>,
	zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Update CoC adapted from upstream 2.1 (instead of 1.4)
Date: Fri, 25 Feb 2022 11:29:16 -0800	[thread overview]
Message-ID: <0ABE8334-99D8-43AC-A526-65975361084E@arctype.co> (raw)
In-Reply-To: <e7784759-9f11-10a9-167b-83dcfe2e8514@gmail.com>

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

I'm a hetero white male from the USA and I would appreciate it if we could keep this mailing focused on software development instead of feminist transgender meta discussion. It seems quite settled nobody else finds the code of conduct lacking in practice so we should probably just move on and accept that this is a place for discussing Guix and not for making every paragraph of text conform perfectly with everyone's worldview.


Sincerely,

Ryan Sundberg
Principal Software Engineer
Arctype Corporation
(916) 622-2449


-------- Original Message --------
From: Taylan Kammer <taylan.kammer@gmail.com>
Sent: February 25, 2022 9:29:29 AM PST
To: Blake Shaw <blake@nonconstructivism.com>, zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Update CoC adapted from upstream 2.1 (instead of 1.4)

On 25.02.2022 16:18, Blake Shaw wrote:
> zimoun <zimon.toutoune@gmail.com> writes:
> 
> My position remains unchanged: our codes of conduct should do everything
> possible to be as inclusive as and open to peoples of marginalized
> groups that are discriminated against. White cis men shouldn't be in
> charge of deciding whats best for these people. 
> 
> As far as I can see, not a single woman has come forward to say that
> proposed CoC amendments would benefit or protect them in any way. In
> fact the opposite is the case: two have come forward to say that this
> appears as ploy by men to debate their gender and experience.
> 
> Why are white men so insistent on making changes that would supposedly
> increase inclusivity, despite those from marginalized backgrounds saying
> the opposite is the case here?
> 
> Until a fem contributor comes forward to say that they feel changes
> to the current CoC would bring about some tangible protection to them,
> it seems to me that this discourse is a case of the dominant white cis
> males making changes to "protect women" without the consent of women,
> which has never fared well in history.
> 
> So with that said, I think decisions concerning women should be left to
> women (all women!) to decide.
> 
> ez,
> b
> 

I'm a visibly middle-eastern person living in Germany, and I'm not
cisgender.  Not that it matters.

The worldview I've wished for the CoC to respect, in addition to
those it already respects, is one that comes from a long line of
feminist scholars and activists.

The inclusion of 'sex' in the CoC would be to recognize the issues
faced by female-born people.  As far as I'm aware, no female-born
person has taken part in the discussion at all, because none seem
to exist in the community.  (What a coincidence.)

Anyhow, Zimoun's proposal is merely to update the CoC to upstream,
which continues to be authored by a transwoman, if that matters.

-- 
Taylan

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

  reply	other threads:[~2022-02-25 19:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-25 15:18 Update CoC adapted from upstream 2.1 (instead of 1.4) Blake Shaw
2022-02-25 17:29 ` Taylan Kammer
2022-02-25 19:29   ` Ryan Sundberg via Development of GNU Guix and the GNU System distribution. [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-02-25 22:20 Blake Shaw
2022-02-25  0:05 zimoun
2022-02-25  0:09 ` Tobias Geerinckx-Rice
2022-02-25  7:47   ` Tissevert
2022-02-25  8:26     ` zimoun
2022-02-25  9:38     ` Thorsten Wilms
2022-02-25  8:16   ` Jonathan McHugh
2022-02-25 16:59 ` Taylan Kammer
2022-02-25 20:38   ` Philip McGrath
2022-02-25 20:50     ` Taylan Kammer
2022-02-26  0:48 ` Liliana Marie Prikler
2022-02-26  1:20   ` Tobias Geerinckx-Rice
2022-02-26  9:08   ` Thorsten Wilms
2022-02-26 18:17     ` elais

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=0ABE8334-99D8-43AC-A526-65975361084E@arctype.co \
    --to=guix-devel@gnu.org \
    --cc=blake@nonconstructivism.com \
    --cc=ryan@arctype.co \
    --cc=taylan.kammer@gmail.com \
    --cc=zimon.toutoune@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).