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
+10-6Lines changed: 10 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,9 +32,9 @@ To understand how this file is generated, see https://git.k8s.io/community/gener
32
32
**The following section will be reworked and formalized as a charter once the
33
33
Working Group has been approved by the Steering Committee.**
34
34
35
-
###Goals
35
+
## Goals
36
36
37
-
- Evaluate language and naming choices within the Kubernetes organization, with
37
+
- Evaluate language and naming choices within the Kubernetes project, with
38
38
a specific initial focus of:
39
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.
40
40
- Improving clarity of codebases and documentation by replacing idioms,
@@ -44,7 +44,8 @@ Working Group has been approved by the Steering Committee.**
44
44
recommend language, how others can evaluate that proposal, and how to
45
45
implement replacements across all codebases.
46
46
- Provide an easily findable location for language recommendations and
47
-
follow-up issues, similar to an architectural decision record.
47
+
follow-up issues, similar to an architectural decision record
48
+
- Define long-term ownership of this process
48
49
- Work with stakeholder SIGs to implement the changes recommended. We
49
50
anticipate the following:
50
51
- Provide stakeholder SIGs with guidance on naming, language conventions, and
@@ -56,13 +57,16 @@ Working Group has been approved by the Steering Committee.**
56
57
language recommendations and processes
57
58
- Work with the Code of Conduct Committee to add code architecture to the COC
58
59
59
-
###Dissolution Criteria
60
+
## Dissolution Criteria
60
61
61
-
When this WG dissolves, the Kubernetes community should have:
62
+
Once the Kubernetes community has:
62
63
63
64
- A process in place to evaluate language changes on an ongoing basis
64
-
- A binding list of terms to avoid in codebases across the organization
65
+
- A binding list of terms to avoid in codebases across the project
65
66
- A timeline on which to replace component names in the kubernetes/kubernetes
66
67
codebase
68
+
- Defined long-term ownership of the policies and processes this WG creates
0 commit comments