-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Added doc on SIG Node KEP wrangler program #8614
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
Added doc on SIG Node KEP wrangler program #8614
Conversation
- Once the board is created and KEPs are added, feel free to assign KEPs to yourself by adding your name in the `Wranglers` column | ||
- Once you've assigned KEPs to yourself, follow up on the status of the KEPs and ping the KEP authors as and when necessary to make sure that all the different deadlines are met | ||
|
||
## Reporting |
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.
should we specify it's the wrangler lead for a release that posts these updates?
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.
also: I think codifying the role of wrangler lead in the process would be good. there is someone each time who wrangles the wranglers and we should document what that entails and what the selection process for that role could look like. could be rough
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.
also happy to have that all be a follow up
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.
Please take a look at 0f2edc0! I've added a section for the wrangler lead's responsibilities. We can keep updating this over the course of v1.35 if we realize we need to add more details down the road.
|
||
In order to facilitate the wrangling process, we have a SIG Node KEP Wrangler lead. The person serving as the lead is responsible for making sure that KEPs are wrangled and that the reporting is done properly in that cycle. | ||
|
||
The responsibilities of the KEP wrangler lead includes the following: |
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.
One responsibility missing is gathering the wranglers through an interest form
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.
Added, thanks!
one more note but looks great thank you for taking this on |
/lgtm |
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.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: SergeyKanzhelev, sreeram-venkitesh 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 |
Which issue(s) this PR fixes:
This PR adds a page to the sig-node docs describing the KEP wrangler role and all the different responsibilities of the wranglers. A part of the content is based on this brainstorming doc which used to be the only documentation relating to the wrangler program until now. I've added details about some new processes on status reporting, which is something we want to try for v1.35, and is up for review.
CC: @SergeyKanzhelev @haircommander