Hi kubefolx,
We've had several conversations in the past across various issues/pull requests/mailing threads about how we should name things. After all, naming is one of the hardest problems in computer science, right?
After speaking with a few Community members, we think the next step is to create a Working Group to improve how we handle naming across the project.
Some goals:
- Create a governance group to centralize naming conventions
- Provide naming guidance across the project
- Establish canonical policies and reviewer guidelines for naming
- Assist SIGs with implementing name changes
- Create tooling to prevent problematic naming from entering our repos (presubmits checks, etc.)
- Wider adoption (CNCF-level): Build comprehensive practices for reuse/adoption by other CNCF projects
Scope/Proposed Sponsors:
- Steering Committee
- SIG Contributor Experience
- SIG Docs
- SIG Architecture
Proposed Leads:
- Celeste Horgan, CNCF
- Zach Corleissen, Linux Foundation
- Stephen Augustus, VMware
The goals above are intentionally ambiguous to allow for further refinement.
We will not let excessive bikeshedding distract from our immediate goals:
eliminating racist/non-inclusive language from the project.
Examples:
- Master/slave (including discussions on changing git default branch naming)
- Whitelist/blacklist
Steering Committee, SIG Contributor Experience, SIG Docs, and SIG Architecture --
Are you interested in sponsoring WG Naming?
-- Stephen / Celeste / Zach