You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: wg-naming/README.md
+6-9Lines changed: 6 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,15 +36,13 @@ Working Group has been approved by the Steering Committee.**
36
36
37
37
- Evaluate language and naming choices within the Kubernetes organization, with
38
38
a specific initial focus of:
39
-
- Removing language which cannot be fully separated from racist, sexist or
40
-
homophobic connotations in cultural contexts outside of computer
41
-
programming
39
+
- 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.
42
40
- Improving clarity of codebases and documentation by replacing idioms,
43
41
metaphors and slang specific to the English language
44
-
- Create a list of terms to avoid and propose alternatives
45
-
- Define a process by which any member of the Kubernetes organization can
46
-
propose a language recommendation, have them evaluated based on a rubric, and
47
-
see them implemented across all codebases.
42
+
- Create a list of harmful terms with proposed replacements
43
+
- Define how any member of the Kubernetes project can
44
+
recommend language, how others can evaluate that proposal, and how to
45
+
implement replacements across all codebases.
48
46
- Provide an easily findable location for language recommendations and
49
47
follow-up issues, similar to an architectural decision record.
50
48
- Work with stakeholder SIGs to implement the changes recommended. We
@@ -63,9 +61,8 @@ Working Group has been approved by the Steering Committee.**
63
61
When this WG dissolves, the Kubernetes community should have:
64
62
65
63
- A process in place to evaluate language changes on an ongoing basis
66
-
- A list of terms to avoid in codebases across the organization
64
+
- A binding list of terms to avoid in codebases across the organization
67
65
- A timeline on which to replace component names in the kubernetes/kubernetes
68
66
codebase
69
-
- A revised Code of Conduct including the list of terms to avoid
0 commit comments