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

Social Justice Movements [was: Rename offensive terminology (master)]

From
LLLuke Kenneth Casson Leighton <lkcl@lkcl.net>
Date
Jun 21, 2020, 19:50 UTC
Message-ID
<20200621195023.3881634-1-lkcl@lkcl.net>
In-Reply-To
<CAOAHyQwyXC1Z3v7BZAC+Bq6JBaM7FvBenA-1fcqeDV==apdWDg@mail.gmail.com>
From: lkcl@lkcl.net
Show 5 quoted lines
> From: Simon Pieters @ 2020-05-04 17:20 UTC (permalink / raw)
>   To: git
> 
> "master" is an offensive term, as it can be interpreted as being
> slavery-origin terminology. See
simon,

sadly i regret to inform you that both the subject line that you've used, and the assertion that you make - that "master" is automatically an inherently offensive term - is what a lawyer would call "leading the witness". it is a false correlation and unfortunately nobody has picked up on this in a significant way.

it would have been far better and much less problematic not to have made any false language-based assumptions as the *fundamental basis* for this entire conversation, by using, for example, the following neutral and objective words:

    "some people may believe that there is an implication - false or
    otherwise - that the use of the word master in git implies a
    corresponding association with slavery.  whilst i appreciate that
    this is a technical list, in light of today's current social
    climate i would welcome open and honest discussion on this subject"

do you see the difference? instead of indicating that you respect that this is a technical list, and *invite* people to discuss it, you opened with a *demand*, backed up by not one but *two* false correlative assertions: one in the subject and the second in the opening sentence, which has proven difficult for people to unpack.

i notice also in follow-ups that you also use similar language and make similar assumptions, which _are_ picked up on and found to themselves be *offensive by readers*. in light of the topic being to change the use of an offensive word, this is highly ironic! (i am delighted to then see that you apologised and indicate that this was in no way intentional).

my observation is however that you have a pattern of this type of false-correlative language usage that you may wish to examine more closely, in order to not mislead or offend others. do not think that you are alone in this! we all do it, myself included, unintentionally. our strength of character is in how we react when it is *pointed out* to us our mistakes, and it is a hugely positive sign to see that you are well-intended and wish not to cause offense to others.

we have also engaged in a discussion on our list, provided some insights into this topic. as an ethical technology advocate with a responsibility and a duty to consider the full implications of the use of my skill, i have been thinking about this "political movement" to change the landscape of engineering terminology for some years.

summary: it's not a good sign.

interestingly, one of our team members opened the discussion with a similarly loaded question: http://lists.libre-riscv.org/pipermail/libre-riscv-dev/2020-June/008259.html

    "should we avoid the association with slavery?"

which is again a highly loaded / charged / false-correlative question (that i immediately picked up on).

the first follow-up simply pointed out that there are a huge number of alternative overload meanings for the word "master": http://lists.libre-riscv.org/pipermail/libre-riscv-dev/2020-June/008263.html

    Record-master
    Film-master
    Tape-master
    Digital-master
    Master (as in teacher)
followups on this include document management commonly-used phrases:
    Master copy
    Master document
    Master Bill of Materials

do you notice that *at no time* is there *any* association in any one's mind with "slavery"? nobody gets offended in Eastern countries when they meet a "Master"! it is a word of *deep* respect!

another follow-up goes into detail about the critical importance of the use of the words "master" and "slave" from an engineering perspective (we are implementing a processor: the Wishbone Specification for example *has* to use the terms) as well as providing further insights: http://lists.libre-riscv.org/pipermail/libre-riscv-dev/2020-June/008264.html

    the engineering meaning of master and slave is as follows:
    * master specifies unequivocably the action required.  this is
      an atomic contract
    * slave carries out that action unequivocably and atomically.
    in other words it is an atomically guaranteed 100 percent
    inviolate and 100% accurate transferrance of *information* from
    one source to another.
    any violation of that contract has such severe consequences in
    engineering (catastrophic data loss in the case of git, and loss
    of life in the case of mission critical real time control systems)
    that to consider anything other than this type of contract is
    unthinkable and flat-out impractical.

this reply also points out that the current motivation for changing the meaning of the word is, sadly, for the purposes of "Social Justice" that have at their heart a guilt-ridden desire to forget history by eradicating words from common usage, with complete disregard for the fact that the word has multiple meanings. the "if you're not with us you're against us" false-correlative argument that has caused untold misery and strife throughout human history.

this then led another of our team, who has a degree in Liberal Studies and Literature, specialising in the study of slavery, to write about the dismaying ongoing inversion and distortion of ethical and liberal movements: http://lists.libre-riscv.org/pipermail/libre-riscv-dev/2020-June/008277.html

he points out in particular that the current "Social Justice" movement has all the hallmarks of a modern-day religion!

https://newdiscourses.com/2020/06/postmodern-religion-faith-social-justice/

so i leave that with you to consider, and the observation that i am witnessing a huge amount of guilt and deep-seated unease over this topic, which is perfectly understandable and we - all of us - need to feel comfortable being able to express that unease in a public way (being part of an open movement after all), and to feel that we are being heard and respected.

yet... at the same time recognising that this is *engineering terminology*, for which, due to ongoing legacy usage, a substitute word would cause far more harm than allowing the continuing use of that word. further, that in an *engineering context* and in other contexts, that word simply does not have or cause offense in any way except in the minds of those who - and this is a whole new subject - *choose to be victims*, and in some contexts its usage is a deep and fundamental sign of respect!

in short: i invite everyone here to consider whether to choose to "react" to the Social Justice Movement / Religion - (become mired and victimised by it), and instead to focus on continuing to apply their superb engineering skills to develop technically excellent code, whilst at the same time remembering at all times to be deeply respectful and conscious of the fact that people *are* going to raise these and many other Social Justice style topics on public technical mailing lists, and to give such people the space they need whilst also reminding them of the core goals of the project on which they have brought up that Social Justice topic.

respectfully,
l.
Previous: Sérgio Augusto ViannaNext: Gunnar Liljas
Message 115 of 140 in “Rename offensive terminology (master)”
  1. Simon PietersMay 4, 2020
  2. Robert P. J. DayMay 4, 2020
  3. N6GhostMay 4, 2020
  4. Konstantin RyabitsevMay 4, 2020
  5. Simon PietersMay 4, 2020
  6. Robert P. J. DayMay 4, 2020
  7. Randall S. BeckerMay 4, 2020
  8. brian m. carlsonMay 5, 2020
  9. Simon PietersJun 9, 2020
  10. Junio C HamanoJun 9, 2020
  11. demerphqJun 9, 2020
  12. Johannes SixtJun 9, 2020
  13. Junio C HamanoJun 9, 2020
  14. Simon PietersJun 9, 2020
  15. Junio C HamanoJun 9, 2020
  16. Simon PietersJun 9, 2020
  17. Robert P. J. DayJun 10, 2020
  18. Kevin SwintonJun 10, 2020
  19. Don Goodman-WilsonJun 10, 2020
  20. Konstantin RyabitsevJun 10, 2020
  21. Sérgio Augusto ViannaJun 14, 2020
  22. Sérgio Augusto ViannaJun 14, 2020
  23. Junio C HamanoJun 14, 2020
  24. Sérgio Augusto ViannaJun 14, 2020
  25. Don Goodman-WilsonJun 14, 2020
  26. Don Goodman-WilsonJun 14, 2020
  27. Sergey LapinJun 14, 2020
  28. Sergey LapinJun 14, 2020
  29. Sérgio Augusto ViannaJun 14, 2020
  30. demerphqJun 16, 2020
  31. OlegJun 16, 2020
  32. Elijah NewrenJun 16, 2020
  33. Sergey LapinJun 17, 2020
  34. OlegJun 17, 2020
  35. Alex SmithJun 16, 2020
  36. Konstantin TokarevJun 16, 2020
  37. OlegJun 16, 2020
  38. Robert P. J. DayJun 16, 2020
  39. Sergey OrganovJun 17, 2020
  40. Konstantin RyabitsevJun 9, 2020
  41. Don Goodman-WilsonJun 9, 2020
  42. Sérgio Augusto ViannaJun 14, 2020
  43. brian m. carlsonJun 14, 2020
  44. Sérgio Augusto ViannaJun 14, 2020
  45. Johannes SchindelinJun 14, 2020
  46. Taylor BlauJun 15, 2020
  47. Sérgio Augusto ViannaJun 15, 2020
  48. brian m. carlsonJun 9, 2020
  49. Michal SuchánekJun 16, 2020
  50. Johannes SchindelinJun 10, 2020
  51. Edward ThomsonJun 10, 2020
  52. brian m. carlsonJun 10, 2020
  53. Michal SuchánekJun 11, 2020
  54. Don Goodman-WilsonJun 11, 2020
  55. Derrick StoleeJun 11, 2020
  56. Junio C HamanoJun 11, 2020
  57. Johannes SchindelinJun 14, 2020
  58. Michal SuchánekJun 15, 2020
  59. Philip OakleyJun 12, 2020
  60. Elijah NewrenJun 14, 2020
  61. Philip OakleyJun 14, 2020
  62. Sérgio Augusto ViannaJun 14, 2020
  63. Don Goodman-WilsonJun 14, 2020
  64. Sérgio Augusto ViannaJun 14, 2020
  65. Andrew ArdillJun 15, 2020
  66. J. Paul ReedJun 15, 2020
  67. Andrew ArdillJun 15, 2020
  68. Michal SuchánekJun 17, 2020
  69. Konstantin RyabitsevJun 14, 2020
  70. Sérgio Augusto ViannaJun 14, 2020
  71. Konstantin RyabitsevJun 14, 2020
  72. Sérgio Augusto ViannaJun 14, 2020
  73. Konstantin RyabitsevJun 14, 2020
  74. Philip OakleyJun 14, 2020
  75. demerphqJun 16, 2020
  76. Michal SuchánekJun 16, 2020
  77. demerphqJun 16, 2020
  78. Michal SuchánekJun 16, 2020
  79. Junio C HamanoJun 17, 2020
  80. Jonathan NiederJun 17, 2020
  81. Jonathan NiederJun 17, 2020
  82. demerphqJun 18, 2020
  83. OlegJun 18, 2020
  84. demerphqJun 18, 2020
  85. Konstantin RyabitsevJun 18, 2020
  86. demerphqJun 18, 2020
  87. Junio C HamanoJun 18, 2020
  88. Junio C HamanoJun 14, 2020
  89. Eric WongJun 14, 2020
  90. Junio C HamanoJun 14, 2020
  91. Jonathan NiederJun 15, 2020
  92. Sérgio Augusto ViannaJun 15, 2020
  93. James RamsayJun 15, 2020
  94. Elijah NewrenJun 15, 2020
  95. Elijah NewrenJun 15, 2020
  96. ZeeVriendJun 16, 2020
  97. OlegJun 17, 2020
  98. ZeeVriendJun 17, 2020
  99. OlegJun 18, 2020
  100. ZeeVriendJun 17, 2020
  101. Sérgio Augusto ViannaJun 13, 2020
  102. Sérgio Augusto ViannaJun 13, 2020
  103. Thomas AdamJun 14, 2020
  104. Michael Felt (aixtools)Jun 14, 2020
  105. George Of The JungleJun 14, 2020
  106. Johannes SchindelinJun 14, 2020
  107. Johannes SchindelinJun 14, 2020
  108. Sérgio Augusto ViannaJun 14, 2020
  109. Sérgio Augusto ViannaJun 15, 2020
  110. Sérgio Augusto ViannaJun 15, 2020
  111. Sérgio Augusto ViannaJun 15, 2020
  112. Sérgio Augusto ViannaJun 15, 2020
  113. Fang-Pen LinJun 16, 2020
  114. Sérgio Augusto ViannaJun 16, 2020
  115. Social Justice Movements [was: Rename offensive terminology (master)]Luke Kenneth Casson Leighton, Jun 21, 2020
  116. Gunnar LiljasJun 23, 2020
  117. WhinisJun 24, 2020
  118. lego_12239@rambler.ruJun 24, 2020
  119. Gunnar LiljasJun 26, 2020
  120. OlegJun 26, 2020
  121. Sérgio Augusto ViannaJun 15, 2020
  122. Alexandru PătrănescuJun 15, 2020
  123. Elijah NewrenJun 15, 2020
  124. Randall S. BeckerJun 15, 2020
  125. WhinisJun 16, 2020
  126. OlegJun 16, 2020
  127. Konstantin RyabitsevJun 16, 2020
  128. John TurnerJun 16, 2020
  129. Michal SuchánekJun 16, 2020
  130. WhinisJun 16, 2020
  131. Alex SmithJun 16, 2020
  132. Konstantin RyabitsevJun 16, 2020
  133. WhinisJun 16, 2020
  134. Sérgio Augusto ViannaJun 16, 2020
  135. OlegJun 16, 2020
  136. Konstantin RyabitsevJun 16, 2020
  137. OlegJun 16, 2020
  138. Konstantin RyabitsevJun 16, 2020
  139. Sergey LapinJun 16, 2020
  140. OlegJun 16, 2020

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.