Re: [cncf-toc] Kubernetes Steering Committee Recommendation Regarding Project Naming

12 views
Skip to first unread message

Stephen Augustus

unread,
Jan 6, 2025, 3:07:05 PMJan 6
to dav...@gmail.com, benth...@google.com, CNCF TOC, steering
Dims and TOC folks—
Thanks for putting together some language to review!
cc-ing Steering to raise viz.

— Stephen

On Mon, Jan 6, 2025 at 9:55 AM Davanum Srinivas via lists.cncf.io <davanum=gmai...@lists.cncf.io> wrote:
Dear Kubernetes Steering,

Thanks for bringing up the topic with us. Following the discussion in TOC (notes here https://github.com/cncf/toc/issues/1432#issuecomment-2548919414), we have drafted a bit of language around the concern about naming projects.

Can you please review https://github.com/cncf/toc/pull/1514 to see if the language is sufficient and addresses your concerns? There are follow up requests from us in the PR text as well, so please take a look at them as well.

Thanks,
Dims

On Wed, Nov 20, 2024 at 2:14 PM Benjamin Elder via lists.cncf.io <bentheelder=googl...@lists.cncf.io> wrote:

The Kubernetes Steering Committee has recently been made aware of new projects in the CNCF using “k8s” “kube” or “kubernetes” in their name rather than being donated to the Kubernetes project. (In this case, k8sgateway, since it was announced very visibly on the keynote stage, but we’re more interested in the general case).

We would like to formally request that new projects pick alternate branding that does not conflict with the Kubernetes organization, our trademarks and subprojects. 


We do NOT expect that existing projects would be asked to go through renaming.

For newly donated projects we would appreciate reserving “k8s”, “kube” and “kubernetes” substrings in project names for our own subprojects to avoid confusion, to avoid users thinking Kubernetes SIGs are responsible for these projects, and to use that namespace for our future projects just as other projects have in the past (e.g. CRI-OCI => CRI-O). We would ask that the TOC request an alternate name/branding for all new projects using Kubernetes’ brand, or direct them to our own repo donation process for becoming a Kubernetes-sponsored subproject.


We hope to avoid future project-specific discussions about this sort of confusion with a generic policy.


Thank you, - Benjamin Elder on behalf of the Kubernetes Steering Committee



--
Davanum Srinivas :: https://twitter.com/dims
_._,_._,_

Links:

You receive all messages sent to this group.

View/Reply Online (#8738) | Reply to Sender | Reply to Group | Mute This Topic | New Topic
Your Subscription | Contact Group Owner | Unsubscribe [h...@auggie.dev]

_._,_._,_

Reply all
Reply to author
Forward
0 new messages