kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update committee-steering/governance/project-naming.md 

Co-authored-by: Patrick Ohly <patrick.ohly@intel.com>
This commit is contained in:
Benjamin Elder 2025-01-30 16:31:11 -08:00 committed by GitHub
parent 98e5d0b8ad
commit aa81e313b3
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
committee-steering/governance/project-naming.md
View File

@ -6,6 +6,6 @@ The Kubernetes project has historically named most of our components/projects wi
We recommend *but do not require* Kubernetes SIGS consider leveraging these when naming new subprojects, to further identify as an official project.
We ask that third-party projects refrain from confusing names that sound like an official Kubernetes subproject, IE "kube", "k8s", "kubernetes" substrings and pick some alternate creative name, with a notable exception for [Conformant Distros](https://www.cncf.io/training/certification/software-conformance/). Many existing projects have not done this, and we are not seeking to alter them, but do remember that "k8s" and "kubernetes" are protected trademarks.
We ask that third-party projects refrain from using confusing names that sound like an official Kubernetes subproject, i.e. "kube", "k8s", "kubernetes" substrings and pick some alternate creative name, with a notable exception for [Conformant Distros](https://www.cncf.io/training/certification/software-conformance/). Many existing projects have not done this, and we are not seeking to alter them, but do remember that "k8s" and "kubernetes" are protected trademarks.
If you'd like to start a new sub-project within the Kubernetes project, see our [repository donation / creation guidelines](https://git.k8s.io/community/github-management/kubernetes-repositories.md)