Skip to content
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

Closed
dthaler opened this issue Feb 16, 2022 · 5 comments
Closed

Process for selecting maintainers of each repo #6

dthaler opened this issue Feb 16, 2022 · 5 comments

Comments

@dthaler
Copy link
Collaborator

dthaler commented Feb 16, 2022

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.

@jniesz
Copy link
Contributor

jniesz commented Mar 1, 2022

To me it makes sense to designate lead maintainers from the repo to approve adding/removing.

@dthaler
Copy link
Collaborator Author

dthaler commented Mar 9, 2022

Also need to document who has triage permissions, e.g., to add assignees and labels

@vmbrasseur
Copy link
Contributor

vmbrasseur commented Mar 16, 2022

#22 is the first pass on a CODEOWNERS file for this repo, but we still need to:

  • Do the same for all the others (l3afd, l3af-arch, eBPF-Package-Repository)
  • Document how to manage (add/remove) people to these files

I'll spin the Triage question off into a different issue so it doesn't block completing this one.

@vmbrasseur
Copy link
Contributor

While there are PRs pending to update their CODEOWNERs files, the file does exist in the other repos. That's one step complete.

vmbrasseur added a commit that referenced this issue Mar 29, 2022
Trying to keep this lightweight for now, but we still need to document it.

#6
vmbrasseur added a commit that referenced this issue Mar 29, 2022
Trying to keep this lightweight for now, but we still need to document it.

#6

Signed-off-by: VM Brasseur <vm.brasseur@wipro.com>
erictice pushed a commit that referenced this issue Apr 6, 2022
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>
@jniesz
Copy link
Contributor

jniesz commented Apr 7, 2022

Initial process for maintainers is merged #29

@jniesz jniesz closed this as completed Apr 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants