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
Process for selecting maintainers of each repo #6
Comments
To me it makes sense to designate lead maintainers from the repo to approve adding/removing. |
Also need to document who has triage permissions, e.g., to add assignees and labels |
#22 is the first pass on a CODEOWNERS file for this repo, but we still need to:
I'll spin the Triage question off into a different issue so it doesn't block completing this one. |
While there are PRs pending to update their CODEOWNERs files, the file does exist in the other repos. That's one step complete. |
Trying to keep this lightweight for now, but we still need to document it. #6
Trying to keep this lightweight for now, but we still need to document it. #6 Signed-off-by: VM Brasseur <vm.brasseur@wipro.com>
Trying to keep this lightweight for now, but we still need to document it. #6 Signed-off-by: VM Brasseur <vm.brasseur@wipro.com> Signed-off-by: erictice <eric.tice@wipro.com>
Initial process for maintainers is merged #29 |
Should document the process for selecting/updating maintainers of each repo
Presumably for new repos (issue #5), the maintainers are approved by the TSC at the time the repo is created.
For existing repos, does adding/removing someone as a maintainer need TSC approval or is that delegated to the existing maintainers of that repo or what? We should document the answer.
The text was updated successfully, but these errors were encountered: