From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Merlin (they/them) via GitGitGadget" <gitgitgadget@gmail.com>,
git@vger.kernel.org,
"Merlin (they/them)" <merlinpatt+githubgit@gmail.com>,
"brian m. carlson" <sandals@crustytoothpaste.net>
Subject: Re: [PATCH] docs: update coding guidelines to be more inclusive
Date: Thu, 17 Feb 2022 11:02:11 +0100 [thread overview]
Message-ID: <220217.86a6epiyii.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <xmqq4k4ycvgb.fsf@gitster.g>
On Wed, Feb 16 2022, Junio C Hamano wrote:
> "Merlin (they/them) via GitGitGadget" <gitgitgadget@gmail.com>
> writes:
>
>> These changes make this documentation more inclusive.
>
> I am not sure about this claim, though.
>
>> * Using "male" and "female" as examples of gender is unnecessary.
>
> It feels somewhat more excluding for those of us who are non-native
> speakers to use a heavier-weight word "gender". After all, it warns
> against writing "he", "him", "she" or "her"---the reason why we warn
> against the first two is because the author has to implicitly assume
> the person in question is "male". Similarly the latter two needs to
> assume "female". These two words, "male" and "female", are both
> easier to understand to even non-native speakers like us, and at the
> same time quite in line with the suggestion being offered.
>
> Maybe the motivation behind this change is a misunderstanding that
> somehow the original of what this patch touches says that "male" and
> "female" are the only two possible values of "gender", but I cannot
> read it that way even when I squint my eyes.
Isn't that exactly what it's saying? I.e. for the purposes of the
English used in our documentation there's two grammatical genders "he
ran the program", "she ran the program" and gender-neutral "it/they ran
the program".
>> * The use of "it" shouldn't be used to refer to people even in an
>> example of what not to use. People are never "it"s.
>
> People are never "it", but I do not think that is relevant. Reading
> the original of what this patch touches, the subject is either a
> person or a program, and for program, referring to "it" would be
> perfectly sensible, no?
Yes, as the person who wrote this originally (in
https://lore.kernel.org/git/87a6nz2fda.fsf@evledraar.gmail.com/) that's
what I was going for. It's referring to describing a program as "it".
>> * There's no need to specify a person or group of people that learned
>> "they" is only plural.
>
> Again, this change assumes/requires too much knowledge of the
> language, which is more excluding for non-natives who may think
> there is only one kind of the English language taught everywhere in
> the world uniformly unless told explicitly. If you are familiar,
> there may be "no need", but does it actively hurt those of you who
> are familiar if the explanation gives such an example? Removing it
> may actively hurt those who did learn English as a second language.
>
> So, I can applaud for the desire to be inclusive, but I am not sure
> if the patch succeeds in doing so.
Per what I noted the last time this was discussed I think that we should
mostly drop this section entirely in favor of some guidelines describing
how to actually write the docs that we do write, not what not to do in
the rare/nonexistent cases of using grammatical genders:
https://lore.kernel.org/git/87pmwt1dz3.fsf@evledraar.gmail.com/
brian's follow-up provides a good example of what we try to aim for:
https://lore.kernel.org/git/YMKTARn368Qzsqc2@camp.crustytoothpaste.net/
The thing that's uninclusive here is asking non-native speakers of
English who are trying to contribute to this project to grasp some
fairly advanced linguistic concepts.
I think it's fair to say that the use of "they" as a personal pronoun is
fairly new/novel English language as it's commonly understood. I.e. if
you talk to any person who's not a native-level speaker of English it's
a fair assumption that their introductory textbook didn't cover it.
As noted in those old threads I'm entirely sympathetic to the goal of
avoiding gendered language if it's a thing that matters for some
readers, which clearly it does[1].
It just demonstrably isn't relevant to our documentation in practice, so
this whole advice ends up being a bridge to nowhere. It's comparable to
us carrying C++ coding guide lines in-tree.
1. To be fair, I do find it a bit odd, but then again I'm a non-native
speaker, and I'm unable to refer to even the monitor, keyboard and
laptop I'm using to type this in my in my native language without
assigning the three (different!) genders.
I can assure the concerned native English speakers that by all
accounts Iceland's got a rather good track record when it comes to
gender equlity despite that :)
next prev parent reply other threads:[~2022-02-17 10:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 16:34 [PATCH] docs: update coding guidelines to be more inclusive Merlin (they/them) via GitGitGadget
2022-02-16 22:12 ` Junio C Hamano
2022-02-17 10:02 ` Ævar Arnfjörð Bjarmason [this message]
2022-02-18 3:02 ` Junio C Hamano
[not found] ` <CAFZ26y3re+fJapXzLOpf73F-ECXhg2sCoBtm_=VUFy5nbN2UVQ@mail.gmail.com>
2022-02-18 23:18 ` Ævar Arnfjörð Bjarmason
2022-02-20 21:23 ` brian m. carlson
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=220217.86a6epiyii.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=merlinpatt+githubgit@gmail.com \
--cc=sandals@crustytoothpaste.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.
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 NNTP newsgroup(s).