scaling up SIG Node KEPs approvers #8794
Open
+22
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As SIG Node manages so many KEPs, we want to keep the high bar for new features, while improving velocity and set clear responsibilities for moving the KEP along towards GA.
This write up formalizes the approach to scaling reviewers and approvers for KEPs in SIG Node in-principle. We will keep working on specifics and potentially automation of creating OWNERS files.
/assign @mrunalp @dchen1107 @derekwaynecarr