|
| 1 | +<!--- |
| 2 | +This is an autogenerated file! |
| 3 | +
|
| 4 | +Please do not edit this file directly, but instead make changes to the |
| 5 | +sigs.yaml file in the project root. |
| 6 | +
|
| 7 | +To understand how this file is generated, see https://git.k8s.io/community/generator/README.md |
| 8 | +---> |
| 9 | +# Naming Working Group |
| 10 | + |
| 11 | + |
| 12 | +## Stakeholder SIGs |
| 13 | +* SIG Architecture |
| 14 | +* SIG Contributor Experience |
| 15 | +* SIG Docs |
| 16 | + |
| 17 | + |
| 18 | + |
| 19 | +## Organizers |
| 20 | + |
| 21 | +* Celeste Horgan (**[@celestehorgan](https://github.com/celestehorgan)**), CNCF |
| 22 | +* Jaice Singer DuMars (**[@jdumars](https://github.com/jdumars)**), Apple |
| 23 | +* Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**), VMware |
| 24 | +* Zach Corleissen (**[@zacharysarah](https://github.com/zacharysarah)**), Linux Foundation |
| 25 | + |
| 26 | +## Contact |
| 27 | +- Slack: [#wg-naming](https://kubernetes.slack.com/messages/wg-naming) |
| 28 | +- [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-wg-naming) |
| 29 | +- [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/wg%2Fnaming) |
| 30 | +<!-- BEGIN CUSTOM CONTENT --> |
| 31 | + |
| 32 | +**The following section will be reworked and formalized as a charter once the |
| 33 | +Working Group has been approved by the Steering Committee.** |
| 34 | + |
| 35 | +### Goals |
| 36 | + |
| 37 | +- Evaluate language and naming choices within the Kubernetes organization, with |
| 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 |
| 42 | + - Improving clarity of codebases and documentation by replacing idioms, |
| 43 | + 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. |
| 48 | + - Provide an easily findable location for language recommendations and |
| 49 | + follow-up issues, similar to an architectural decision record. |
| 50 | +- Work with stakeholder SIGs to implement the changes recommended. We |
| 51 | + anticipate the following: |
| 52 | + - Provide stakeholder SIGs with guidance on naming, language conventions, and |
| 53 | + processes |
| 54 | + - Collaborate with SIG Architecture and other stakeholders on an |
| 55 | + implementation timeline and strategies for dealing with follow-up issues |
| 56 | + from renaming, like deprecations |
| 57 | + - Collaborate with SIG Docs and SIG Contributor Experience on documenting |
| 58 | + language recommendations and processes |
| 59 | + - Work with the Code of Conduct Committee to add code architecture to the COC |
| 60 | + |
| 61 | +### Dissolution Criteria |
| 62 | + |
| 63 | +When this WG dissolves, the Kubernetes community should have: |
| 64 | + |
| 65 | +- A process in place to evaluate language changes on an ongoing basis |
| 66 | +- A list of terms to avoid in codebases across the organization |
| 67 | +- A timeline on which to replace component names in the kubernetes/kubernetes |
| 68 | + codebase |
| 69 | +- A revised Code of Conduct including the list of terms to avoid |
| 70 | + |
| 71 | +<!-- END CUSTOM CONTENT --> |
0 commit comments