Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP]: naming guidelines #8238

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

BenTheElder
Copy link
Member

Which issue(s) this PR fixes:

Fixes https://lists.cncf.io/g/cncf-toc/message/8738
/hold

@k8s-ci-robot k8s-ci-robot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. area/github-management Issues or PRs related to GitHub Management subproject committee/steering Denotes an issue or PR intended to be handled by the steering committee. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jan 8, 2025
@k8s-ci-robot k8s-ci-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Jan 8, 2025
@BenTheElder
Copy link
Member Author

/assign @kubernetes/steering-committee

FYI @dims as requested in #8238 and discussed (in broad strokes) in this morning's steering meeting.

@aojea
Copy link
Member

aojea commented Jan 8, 2025

LGTM

Copy link
Contributor

@pohly pohly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, just some minor nits.

@@ -0,0 +1,11 @@
# Project Naming

The Kubernetes project has historically named most of our components/projects with a "kube" substring like `kube-proxy`, `kubectl`, `kube-apiserver`, `kube-controller-manager`, `kube-scheduler`, `minikube`, ...
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: can you line wrap?


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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.

Copy link
Contributor

@soltysh soltysh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minor nit, otherwise lgtm


"Kubernetes" and "K8s" are registered [trademarks under the Linux Foundation](https://www.linuxfoundation.org/legal/trademarks).

We recommend *but do not require* Kubernetes SIGS consider leveraging these when naming new subprojects, to further identify as an official project.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
We recommend *but do not require* Kubernetes SIGS consider leveraging these when naming new subprojects, to further identify as an official project.
We recommend *but do not require* Kubernetes SIGs consider leveraging these when naming new subprojects, to further identify as an official project.

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BenTheElder, soltysh

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/github-management Issues or PRs related to GitHub Management subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. committee/steering Denotes an issue or PR intended to be handled by the steering committee. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants