-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Propose KEP template #1124
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
Propose KEP template #1124
Conversation
6e07eb8
to
6dd34b9
Compare
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://github.com/kubernetes/kubernetes/wiki/CLA-FAQ to sign the CLA. It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
6dd34b9
to
3c61d78
Compare
preferably in a mailing list so that the discussion is saved for future Kubernauts. | ||
|
||
|
||
### Section: Metadata |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This nesting is confusing. I was expecting a template that could be copied and filled in.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
extracted empty template from section explanations. I agree that the nesting was confusing and let me know if extracting an empty template doesn't help
The `Examples` section should describe the intended user experience for an | ||
KEP. | ||
|
||
### Section: How Do I Teach This? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is intended to be in this section?
will be the primary description of use cases | ||
- `Requirements` is replaced by `Detailed Design` within a KEP | ||
|
||
[design template]: https://github.com/pwittrock/community/blob/design/contributors/design-proposals/api-proposal-design-template.md |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm fine with making a separate (sub-)template specific to API changes.
3c61d78
to
62eabfa
Compare
62eabfa
to
6dca8c2
Compare
6dca8c2
to
6386171
Compare
I think this is at a good place to checkpoint and iterate further, so I'm going to merge. |
Automatic merge from submit-queue. . |
/remove-sig pm |
Automatic merge from submit-queue. . Propose KEP template Propose a template for the [KEP process][] [KEP process]: kubernetes#967
Propose a template for the KEP process