-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Update the k8s.io/component-base KEP #653
Conversation
Looks good Thoughts on calling the wg "Component Standard"? All these sound ok to me for a repo name:
|
0b69cb6
to
f300591
Compare
As agreed with @mtaufen & @sttts and other stakeholders at the contrib summit, we're going with this WG name. This doc is updated to reflect that
After some bikeshedding on the names back and forth, we agreed that this is the best name we have at the moment. Before this is going "GA/stable", we could technically always rename this if there's a strong case later. Updated this proposal to reflect the This is ready to merge. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: luxas, mtaufen 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 |
Follow-up of kubernetes/community#2977
xref: kubernetes/community#2354 kubernetes/community#2515
cc @kubernetes/sig-cluster-lifecycle-pr-reviews @kubernetes/sig-api-machinery-pr-reviews
/assign @thockin @mtaufen @sttts @jbeda @DirectXMan12 @bgrant0607