Challenge
How does LFN assure that we are using language in our documentation and code that is inclusive and does not include any implicit or explicit bias?
Goal
TAC working group to provide to LFN projects:
- terminology list with suggested replacements
- guidance on how to implement (docs, code, tooling, versions, etc)
LFN Projects to implement suggestions/guidance as appropriate for their projects
Background Information Gathered
(thanks Trevor Cooper )
Python joins movement to dump 'offensive' master, slave terms - https://www.theregister.co.uk/2018/09/11/python_purges_master_and_slave_in_political_pogrom/
Redis replaces master/slave language - https://www.theregister.co.uk/2018/09/13/redis_master_slave/
Salvatore Sanfilippo (aka Antirez), creator of Redis, ran an on-line Twitter poll of his followers, and found that 53% out of 6242 participants wanted to replace master-slave language; with 19% wanting to keep it and 28% that didn’t care. https://twitter.com/antirez/status/1038094104129937408
Microsoft Style Guide advises alternatives to master/slave - https://docs.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/m/master-slave-master-subordinate
Google told Employees to Delete Politically Incorrect Language From Code - https://reason.com/2019/07/11/google-code-pc-master-slave-respectful/
Los Angeles, CA asked manufactures, suppliers & contractors to stop using master/slave terminology, calling it unacceptable & offensive - http://www.cnn.com/2003/TECH/ptech/11/26/master.term.reut/index.html
Drupal - https://www.drupal.org/project/drupal/issues/2275877
Django - https://github.com/django/django/pull/2692 . Lots of discussion on this thread from those on both sides of the issue.
IETF (Internet Engineering Task Force) - https://tools.ietf.org/id/draft-knodel-terminology-00.html . Proposal in process to replace master/slave and blacklist/whitelist language.
GitHub – “Microsoft's Github is removing coding terms like 'master' and 'slave’”
Washington Post – “There’s an industry that talks daily about ‘masters’ and ‘slaves.’ It needs to stop.”
ZDNET (7/11/20) – “Linux team approves new terminology, bans terms like 'blacklist' and 'slave’”
Red Hat blog from CTO (and LFN board member) Chris Wright https://www.redhat.com/en/blog/making-open-source-more-inclusive-eradicating-problematic-language
ODPI open source project discussion: https://github.com/odpi/egeria/issues/3486
Team
(to be confirmed)