You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildstream.apache.org by GitBox <gi...@apache.org> on 2021/09/07 04:25:19 UTC

[GitHub] [buildstream] gtristan commented on issue #1473: Switch to inclusive naming

gtristan commented on issue #1473:
URL: https://github.com/apache/buildstream/issues/1473#issuecomment-913980505


   As far as I know, there is nothing *"problematic"* with the common terms blacklist and whitelist, these are not derogatory racist slurs.
   
   The common argument for avoiding this particular terminology is based on the idea that *we should try not using terminology which **might** hypothetically offend someone* regardless of intent, rather than only avoiding terminology that is inherently offensive.
   
   An example of this is how we have mostly removed the *master / slave* nomenclature of software component relationships, which seem to be inherently offensive terms, but now there is a completely unjustified move to remove the term *master* completely out of context, like the *masterpiece* or *master copy* of a git repository.
   
   We are on a slippery slope where people are increasingly walking on egg shells as they articulate their thoughts in public forums, people are increasingly afraid of being flogged in the town square of public opinion in the case that they might use a *wrong word*, and the rules of what words are safe to use are changing on a weekly basis.
   
   This has the effect of shutting down all rational civil discourse, at any time someone wants to play the trump card of being emotionally triggered. I firmly believe the future this leads to can be a very dark place.
   
   Merging this pull request would mean to agree that we should continue to *blacklist* vocabulary for public use based on the rationale where *someone **might** be triggered*, and it would be to further lend credit to this new age toxic ideology which is counter free speech and counter human freedom.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@buildstream.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org