diff options
| author | Celeste Horgan <celeste@cncf.io> | 2020-06-26 12:09:58 -0700 |
|---|---|---|
| committer | Stephen Augustus <saugustus@vmware.com> | 2020-06-30 00:32:28 -0400 |
| commit | 3b35f49a683784cef9cbf74b3649df0f74a1ea41 (patch) | |
| tree | 2eeb9ddfaca6e8d782c33504fbe228e01e3cc8d3 | |
| parent | 53e7d0a9423591c04a9cf593ab38885fceb13ccb (diff) | |
wg-naming: Implement all existing suggestions from PR
Signed-off-by: Celeste Horgan <celeste@cncf.io>
| -rw-r--r-- | wg-naming/README.md | 15 |
1 files changed, 6 insertions, 9 deletions
diff --git a/wg-naming/README.md b/wg-naming/README.md index c728f4c5..394b3094 100644 --- a/wg-naming/README.md +++ b/wg-naming/README.md @@ -36,15 +36,13 @@ Working Group has been approved by the Steering Committee.** - Evaluate language and naming choices within the Kubernetes organization, with a specific initial focus of: - - Removing language which cannot be fully separated from racist, sexist or - homophobic connotations in cultural contexts outside of computer - programming + - Removing barriers to contribution and adoption by replacing harmful language with neutral terms whenever possible, including but not limited to language linked to racism, sexism, homophobia, transphobia, ableism, or discrimination against any protected or historically underrepresented group. - Improving clarity of codebases and documentation by replacing idioms, metaphors and slang specific to the English language -- Create a list of terms to avoid and propose alternatives -- Define a process by which any member of the Kubernetes organization can - propose a language recommendation, have them evaluated based on a rubric, and - see them implemented across all codebases. +- Create a list of harmful terms with proposed replacements +- Define how any member of the Kubernetes project can + recommend language, how others can evaluate that proposal, and how to + implement replacements across all codebases. - Provide an easily findable location for language recommendations and follow-up issues, similar to an architectural decision record. - Work with stakeholder SIGs to implement the changes recommended. We @@ -63,9 +61,8 @@ Working Group has been approved by the Steering Committee.** When this WG dissolves, the Kubernetes community should have: - A process in place to evaluate language changes on an ongoing basis -- A list of terms to avoid in codebases across the organization +- A binding list of terms to avoid in codebases across the organization - A timeline on which to replace component names in the kubernetes/kubernetes codebase -- A revised Code of Conduct including the list of terms to avoid <!-- END CUSTOM CONTENT --> |