git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2 0/4] Use singular "they" when appropriate

From
Derrick Stolee <stolee@gmail.com>
Date
Jun 11, 2021, 17:18 UTC
Message-ID
<f4488360-bdaf-3e97-69c5-00087f797117@gmail.com>
In-Reply-To
<87pmwt1dz3.fsf@evledraar.gmail.com>
On 6/10/2021 6:58 PM, Ævar Arnfjörð Bjarmason wrote:
> 
> On Thu, Jun 10 2021, brian m. carlson wrote:
> 
...
Show 42 quoted lines
>> In many cases, saying less is better, I agree.  If we don't need to
>> refer to a human being, then we don't need to consider any pronouns for
>> that human being.  If we communicate things more simply with fewer
>> words, then that's clearly better overall for everyone involved.
>> Nobody's reading documentation for pleasure, after all.
>>
>> I do think that the recommendation that we refer to an anonymous user in
>> a gender-neutral way still stands, though.  Sometimes we will need to
>> refer to the user or another human actor and that will be the most
>> natural way to express the idea, so we should use gender-neutral
>> language to do so.
>>
>> So roughly here, I'm in favor of both approaches.
> 
> When do we need or even prefer to refer to a user like that?
> 
> I haven't seen an example in our documentation that's actually better
> off because we're talking about things as if two "people" we need to
> invent pronouns for are interacting.
> 
> Can anyone name one that'll stand up under scrutiny, i.e. once we can
> look at it and see if we couldn't phrase it better by avoiding the issue
> this series tries to address with a regex search-replacement?
> 
> The diffstat of this series is only:
> 
>  12 files changed, 22 insertions(+), 15 deletions(-)
> 
> I've looked at all of them and I can't see one that wouldn't be better
> if the relevant text was changed similarly to what I've suggested
> upthread.
> 
> That's why I don't think this proposal is useful. If we accept this
> series we're going to be left with an active recommendation for a
> pattern that's already almost nonexistent in our documentation.
> 
> Perhaps that's because we're doing it 98% right already and aren't using
> "he" or "she" but "they" or "their". The multiple ways you can use
> "they" or "their" in the English language makes that hard to grep for. A
> lot of our "they"'s are referring e.g. to a command-line option, or
> "their" referring to "their arguments", as in the argv vector of a
> program.

Since the examples are already few in number, it is not an overwhelming amount of work to remove third-person singular pronouns from the necessary locations. Perhaps if there were more examples then such a conversion would be too difficult and we would want to use a more mechanical replacement with singular "they".

My general approach (as specified in this v2) is:
1. Use singular "they" over "he" or "she" and other variants.
2. If you don't want to write "they", then avoid third-person
   singular pronouns.
Your approach focuses only on item 2, giving this recommendation:
* Avoid third-person singular pronouns.

I think your change to CodingGuidelines is a bit verbose to get to that point, and makes it difficult to understand one goal is to avoid gendered pronouns, which I think reduces the chance that a new contributor would discover and understand that recommendation.

A semantically similar addition would be:
	Avoid gendered pronouns such as "he/him" and "she/her". If
	necessary, alter your sentence structure to use singular "you"
	to refer to the reader or plural "they" to refer to multiple
	actors.
> The skepticism about this being needed at all isn't an opinion I hold
> about software documentation in general, but about software in Git's
> problem space specifically.

A change that says "don't use 'he' and/or 'she' unnecessarily" is important to encode as a project guideline so we can stop having discussions about their use whenever they are introduced in a patch.

There is value in having this decision encoded, and the important thing from my standpoint is that we explicitly avoid gendered pronouns and can simply point contributors to that decision if we ever notice one being introduced. That reduces friction the same way that we decide where curly braces should be placed after an "if" statement.

My preference continues to be singular "they" because it is an easy way to adapt natural sentence structures into an inclusive language. But if we decide that this grammar is too difficult for some readers to understand (due to English as a secondary language or other reasons to be more strict to older language patterns), then avoiding gendered pronouns entirely would satisfy my goals in this series.

Thanks, -Stolee

Previous: Felipe ContrerasNext: Felipe Contreras
Message 83 of 124 in “Use singular "they" when appropriate”
  1. 0/4 Use singular "they" when appropriateDerrick Stolee via GitGitGadget, Jun 7, 2021
  2. 2/4 *: use singular they in commentsDerrick Stolee via GitGitGadget, Jun 7, 2021
  3. Ævar Arnfjörð BjarmasonJun 7, 2021
  4. Derrick StoleeJun 7, 2021
  5. Johannes SchindelinJun 10, 2021
  6. Junio C HamanoJun 7, 2021
  7. Felipe ContrerasJun 7, 2021
  8. Emily ShafferJun 8, 2021
  9. 1/4 Documentation: use singular they when appropriateDerrick Stolee via GitGitGadget, Jun 7, 2021
  10. Ævar Arnfjörð BjarmasonJun 7, 2021
  11. Derrick StoleeJun 7, 2021
  12. Andrei RybakJun 7, 2021
  13. Ævar Arnfjörð BjarmasonJun 7, 2021
  14. Johannes SchindelinJun 10, 2021
  15. Felipe ContrerasJun 10, 2021
  16. Felipe ContrerasJun 7, 2021
  17. Phillip SusiJun 9, 2021
  18. Felipe ContrerasJun 9, 2021
  19. Phillip SusiJun 11, 2021
  20. Felipe ContrerasJun 11, 2021
  21. Derrick StoleeJun 10, 2021
  22. Junio C HamanoJun 11, 2021
  23. Felipe ContrerasJun 11, 2021
  24. Phillip SusiJun 12, 2021
  25. Junio C HamanoJun 8, 2021
  26. Kerry, RichardJun 8, 2021
  27. Junio C HamanoJun 8, 2021
  28. Derrick StoleeJun 9, 2021
  29. Junio C HamanoJun 10, 2021
  30. Emily ShafferJun 8, 2021
  31. Felipe ContrerasJun 8, 2021
  32. Kerry, RichardJun 9, 2021
  33. Felipe ContrerasJun 9, 2021
  34. Kerry, RichardJun 25, 2021
  35. Junio C HamanoJun 9, 2021
  36. Johannes SchindelinJun 10, 2021
  37. Felipe ContrerasJun 10, 2021
  38. Robert KarszniewiczJun 14, 2021
  39. 4/4 CodingGuidelines: recommend singular theyDerrick Stolee via GitGitGadget, Jun 7, 2021
  40. Junio C HamanoJun 7, 2021
  41. Derrick StoleeJun 7, 2021
  42. Junio C HamanoJun 8, 2021
  43. brian m. carlsonJun 10, 2021
  44. Johannes SchindelinJun 10, 2021
  45. Ævar Arnfjörð BjarmasonJun 7, 2021
  46. Felipe ContrerasJun 8, 2021
  47. Felipe ContrerasJun 7, 2021
  48. Phillip SusiJun 9, 2021
  49. Felipe ContrerasJun 9, 2021
  50. Robert KarszniewiczJun 7, 2021
  51. Felipe ContrerasJun 7, 2021
  52. Jeff KingJun 8, 2021
  53. Felipe ContrerasJun 8, 2021
  54. Derrick StoleeJun 9, 2021
  55. Felipe ContrerasJun 9, 2021
  56. brian m. carlsonJun 10, 2021
  57. Felipe ContrerasJun 11, 2021
  58. Emily ShafferJun 8, 2021
  59. Junio C HamanoJun 9, 2021
  60. Derrick StoleeJun 9, 2021
  61. 3/4 *: fix typosDerrick Stolee via GitGitGadget, Jun 7, 2021
  62. Emily ShafferJun 8, 2021
  63. Johannes SchindelinJun 10, 2021
  64. Derrick StoleeJun 10, 2021
  65. Johannes SchindelinJun 11, 2021
  66. Felipe ContrerasJun 7, 2021
  67. 0/4 Use singular "they" when appropriateDerrick Stolee via GitGitGadget, Jun 9, 2021
  68. 4/4 CodingGuidelines: recommend singular theyDerrick Stolee via GitGitGadget, Jun 9, 2021
  69. Felipe ContrerasJun 9, 2021
  70. 3/4 *: fix typosDerrick Stolee via GitGitGadget, Jun 9, 2021
  71. 2/4 *: use singular they in commentsDerrick Stolee via GitGitGadget, Jun 9, 2021
  72. Felipe ContrerasJun 9, 2021
  73. 1/4 Documentation: use singular they when appropriateDerrick Stolee via GitGitGadget, Jun 9, 2021
  74. Felipe ContrerasJun 9, 2021
  75. Ævar Arnfjörð BjarmasonJun 9, 2021
  76. Felipe ContrerasJun 9, 2021
  77. Junio C HamanoJun 10, 2021
  78. Junio C HamanoJun 10, 2021
  79. Felipe ContrerasJun 10, 2021
  80. brian m. carlsonJun 10, 2021
  81. Ævar Arnfjörð BjarmasonJun 10, 2021
  82. Felipe ContrerasJun 11, 2021
  83. Derrick StoleeJun 11, 2021
  84. Felipe ContrerasJun 11, 2021
  85. Ævar Arnfjörð BjarmasonJun 13, 2021
  86. Junio C HamanoJun 15, 2021
  87. Derrick StoleeJun 15, 2021
  88. Felipe ContrerasJun 15, 2021
  89. Junio C HamanoJun 14, 2021
  90. 0/4 Avoid gendered pronounsDerrick Stolee via GitGitGadget, Jun 15, 2021
  91. 2/4 comments: avoid using the gender of our usersFelipe Contreras via GitGitGadget, Jun 15, 2021
  92. 1/4 doc: avoid using the gender of other peopleFelipe Contreras via GitGitGadget, Jun 15, 2021
  93. 3/4 *: fix typosDerrick Stolee via GitGitGadget, Jun 15, 2021
  94. 4/4 CodingGuidelines: recommend singular theyDerrick Stolee via GitGitGadget, Jun 15, 2021
  95. Ævar Arnfjörð BjarmasonJun 15, 2021
  96. Felipe ContrerasJun 15, 2021
  97. Junio C HamanoJun 16, 2021
  98. Junio C HamanoJun 16, 2021
  99. Bagas SanjayaJun 16, 2021
  100. Derrick StoleeJun 16, 2021
  101. Ævar Arnfjörð BjarmasonJun 16, 2021
  102. Felipe ContrerasJun 16, 2021
  103. Junio C HamanoJun 17, 2021
  104. Derrick StoleeJun 17, 2021
  105. Felipe ContrerasJun 17, 2021
  106. Ævar Arnfjörð BjarmasonJun 17, 2021
  107. Felipe ContrerasJun 17, 2021
  108. brian m. carlsonJun 18, 2021
  109. Felipe ContrerasJun 18, 2021
  110. Felipe ContrerasJun 17, 2021
  111. Ævar Arnfjörð BjarmasonJun 17, 2021
  112. brian m. carlsonJun 18, 2021
  113. Ævar Arnfjörð BjarmasonJun 18, 2021
  114. Felipe ContrerasJun 18, 2021
  115. Junio C HamanoJun 19, 2021
  116. Junio C HamanoJun 28, 2021
  117. Felipe ContrerasJun 29, 2021
  118. Derrick StoleeJun 29, 2021
  119. Ævar Arnfjörð BjarmasonJun 29, 2021
  120. Felipe ContrerasJun 17, 2021
  121. Felipe ContrerasJun 17, 2021
  122. Felipe ContrerasJun 15, 2021
  123. Bagas SanjayaJun 12, 2021
  124. Phillip SusiJun 12, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.