git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Jakub Narębski" <jnareb@gmail.com>
To: Mike Hommey <mh@glandium.org>,
	Johannes Schindelin <johannes.schindelin@gmx.de>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] am: counteract gender bias
Date: Thu, 7 Jul 2016 15:24:27 +0200	[thread overview]
Message-ID: <577E580B.5090000@gmail.com> (raw)
In-Reply-To: <20160707124943.GA22668@glandium.org>

W dniu 2016-07-07 o 14:49, Mike Hommey pisze:
> On Thu, Jul 07, 2016 at 01:47:19PM +0200, Johannes Schindelin wrote:
>> Since d1c5f2a (Add git-am, applymbox replacement., 2005-10-07), i.e. for
>> almost 11 years already, we demonstrated our disrespect to the pioneers
>> of software development like Ada Lovelace, Grace Hopper and Margaret
>> Hamilton, by pretending that each and every software developer is male
>> ("his_tree"). It appears almost as if we weren't fully aware that the
>> first professional software developers were all female.
>>
>> We know our field to have this unfortunate gender bias that has nothing
>> to do with qualification or biological reasons, and we are very sad
>> about the current gender imbalance of the Git developer community.
>>
>> Let's start changing that by using the variable name "her_tree" for an
>> equal number of years out of fairness, and change to the gender neutral
>> "their_tree" after that.
> 
> You make it sound like the decision to use "his" was conscious and on
> purpose. I doubt that was the case, especially 11 years ago, when these
> issues weren't as publicized. Let's not attribute to malice on part of
> the people who wrote those lines what can be attributed to linguistics.

Also, in all (?) other places we use "ours" and "theirs"; it looks like
git-am was a strange exception with "ours" and "his" (also, it was/is
inconsistent in using plural vs singular form).  Though perhaps it was
created before the terminology solidified...

As to why it was not noticed and not fixed: probably no-one worked
in this area, thus nobody noticed this (callee just don't care how the
parameter is named).

Instead of nebulous "fairness" (i.e., be unfair in other direction),
in my opinion it would be better to simply fix the issue, be consistent
and use common terminology.
-- 
Jakub Narębski


  reply	other threads:[~2016-07-07 13:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-07 11:47 [PATCH] am: counteract gender bias Johannes Schindelin
2016-07-07 12:49 ` Mike Hommey
2016-07-07 13:24   ` Jakub Narębski [this message]
2016-07-07 14:17     ` Johannes Schindelin
2016-07-07 16:04     ` Junio C Hamano
2016-07-08  7:08       ` Johannes Schindelin
2016-07-07 14:12   ` Johannes Schindelin
2016-07-08  7:17 ` [PATCH v2] " Johannes Schindelin
2016-07-08  7:50   ` Jakub Narębski
2016-07-08 21:39   ` Junio C Hamano

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: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=577E580B.5090000@gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=johannes.schindelin@gmx.de \
    --cc=mh@glandium.org \
    /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://80x24.org/mirrors/git.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).