-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Create api-machinery charter.md #2927
Conversation
As per the request, drafted SIG API Machinery charter file.
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://git.k8s.io/community/CLA.md#the-contributor-license-agreement 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. |
Hi @maulin9. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
@maulin9 A charter is a very detailed document created by the sig in question. An empty template isn't helpful in this situation. If you want to get involved please have a look at our contributors guide: https://git.k8s.io/community/contributors/guide /close |
@cblecker here is the template for creating charter.md file. https://github.com/kubernetes/community/edit/master/committee-steering/governance/sig-charter-template.md |
sig-api-machinery/charter.md
Outdated
|
||
|
||
[sig-governance]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md | ||
[sig-subprojects]: https://github.com/kubernetes/community/blob/master/sig-YOURSIG/README.md#subprojects |
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 think you forgot to fill this 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.
+1
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.
Hi,
Verified with @lavalamp https://github.com/kubernetes/community/tree/master/sig-api-machinery is up to date so that should address last two lines.
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.
Verified with @lavalamp https://github.com/kubernetes/community/tree/master/sig-api-machinery is up to date so that should address last two lines.
YOURSIG
doesn't need to be 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.
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.
Ping
sig-api-machinery/charter.md
Outdated
|
||
### Subproject Creation | ||
|
||
1. SIG Technical Leads |
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.
@cblecker I think this pull filled in values that match our existing readme. /reopen |
@deads2k: Reopened this PR. In response to this:
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. |
Thanks, Maulin! CLA + fix comments & it's ready to go. |
I signed it |
@cblecker Thanks. The Steering Committee has iterated on the SIG charter template and tried to minimize hard-to-maintain copy/paste text in it. https://github.com/kubernetes/community/tree/master/committee-steering/governance I'll work with the SIG on the charter. |
Removed WIP statement and added "Technical leads seeded by legacy SIG chairs from existing subproject owners"
@lavalamp let me know if anything is needed merge the PR. |
/ok-to-test 😺 |
/ok-to-test |
Added bullets to scope list. Added 'The informer libraries' to scope. Added 'Client library releases' to ### Cross-cutting and Externally Facing Processes
@maulin9 if you go to file view and scroll to the bottom I think you'll find a comment that github has been hiding from you :) |
Fixed the link to README.md.
|
||
#### Cross-cutting and Externally Facing Processes | ||
|
||
Client library releases |
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.
It would be helpful to link to a doc that describes the process
Removed scheduler from the scope as scheduler is the responsibility of SIG Scheduler.
/committee steering |
Looks like everything critical was resolved. Thanks! /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bgrant0607 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 |
As per the request, drafted SIG API Machinery charter file.