Google’s initiative for more inclusive language in open source projects
Certain terms in open source projects reinforce negative associations and unconscious biases. At Google, we want our language to be inclusive. The Google Open Source Programs Office (OSPO) created and posted a policy for new Google-run projects to remove the terms “slave,” “whitelist,” and “blacklist,” and replace them with more inclusive alternatives, such as “replica,” “allowlist,” and “blocklist.” OSPO required that new projects follow this policy beginning October 2020, and has plans to enforce these changes on more complex, established projects beginning in 2021.
For more information on why inclusive language matters to us, you can check out Google Developer Documentation Style Guide which contains a section on word-choice with useful, clearer alternatives. Regardless of the phrases used, it is necessary to understand that certain terms reinforce biases and that replacing them is a positive step, both in creating a more welcoming atmosphere for everyone and in being more technically accurate. In short, words matter.
By Erin Balabanian, Open Source Compliance.
Related Google News:
- Picture this: 10 whiteboard sketch videos that bring Google Cloud to life March 24, 2021
- Google BigQuery is a Leader in The 2021 Forrester Wave: Cloud Data Warehouse March 24, 2021
- India’s Google Developer Groups meet up to ace their Google Cloud Certifications March 24, 2021
- Meet the Google for Startups Accelerator Canada Class of 2021 March 24, 2021
- Google Search sends more traffic to the open web every year March 24, 2021
- A Google Cloud VMware Engine cheat sheet March 23, 2021
- Progress and Challenges in Long-Form Open-Domain Question Answering March 23, 2021
- Safeguarding time and attention with Google Workspace and Gmail March 23, 2021