[Feature Request]: Replace and prevent non-inclusive terminology
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 196
Description
### What would you like to happen?
## Overview
This feature request proposes replacement and prevention of non-inclusive terminology. Filing this GitHub issue specifically functions as a reference by tasks that focus on a specific term. This feature request proposes the following methodology:
### 1) Scope the problem via search of terms and dependencies
Replacing non-inclusive terminology is more than text changes. For example, as of this writing, a [search of `master`](https://github.com/apache/beam/search?q=master) shows that there are places in the code that reference the branch name as well. Changing the term `master` as the branch name would require changing all the places in the code that reference this branch. Additionally, the search reveals there exist dependent technologies that contain symbols in their code using the term.
### 2) Assess what can be changed
It may not be possible to change non-inclusive terminology for references to code dependencies outside this repository. This feature request proposes creating a separate issue to watch for whether these dependencies change their terminology. Alternatively, it may be appropriate to file an issue on the dependencies repository and reference that issue in this repository.
### 3) Do the change
Following standard workflow, pull requests might focus on refactoring a specific term and note where a change is not possible.
### 4) Prevent future non-inclusive terminology use
Similar to the gradle `rat` task, this feature request proposes scanning the repository and pull requests for uses of non-inclusive terminology. Also, similar to the gradle `rat` task, provide a mechanism to exclude certain places where it is not possible to change the term.
## Other initiatives
There exist similar initiatives by other communities toward this aim.
- [Internet Engineering Task Force](https://www.ietf.org/about/groups/iesg/statements/statement-on-oppressive-exclusionary-language/)
- [Apache Airflow Project](https://github.com/apache/airflow/issues/15994)
- [Inclusive Naming Initiative](https://inclusivenaming.org/)
- [18F](https://content-guide.18f.gov/our-style/inclusive-language/)
- [American Psychological Association](https://content-guide.18f.gov/our-style/inclusive-language/)
- [Linguistic Society of America](https://www.linguisticsociety.org/resource/guidelines-inclusive-language)
- [GSMA](https://www.gsma.com/aboutus/wp-content/uploads/2020/11/GSMA-Inclusive-Language-Guide_2020.pdf)
### Issue Priority
Priority: 2
### Issue Component
Component: beam-community
Contributor guide
Assessment
This issue has not been assessed yet.