org: Define and implement entry/exit criteria for kubernetes-maintainers GitHub team

The legacy kubernetes-maintainers GitHub team has write access to the k/k repo. This issue is to discuss pruning the team.

There has been previous discussion about removing the team in https://github.com/kubernetes/kubernetes/issues/57667. Given that we don’t have good automated solutions around editing issue/PR bodies, completely removing write access and deleting the team is not feasible today.

Having said that, the kubernetes-maintainers team hasn’t had any significant updates over the last ~3 years (!!!). There are members in that team who are no longer active in the Kubernetes project and should not have write access to k/k anymore.

My suggestion - we could limit this to milestone-maintainers + all approvers in k/k.

If there is general consensus on this GitHub issue, I’ll start a thread on the k-dev and leads mailing lists.

About this issue

Original URL
State: open
Created 4 years ago
Reactions: 3
Comments: 31 (27 by maintainers)

Commits related to this issue

Add bentheelder to Kubernetes maintainers team. I think this is accurate at this point 🙃 xref: https://github.com/kubernetes/org/issues/2332#issuecomment-729681652 https://github.com/kubernetes/o... — committed to BenTheElder/k8s-org by BenTheElder 4 years ago

Most upvoted comments

To clarify - we won’t bulk-add milestone-maintainers + k/k approvers if they aren’t already in the kubernetes-maintainers GitHub team.

If someone in milestone-maintainers + k/k approvers wants to be on the team, they can create a PR to add themselves separately.

Want to keep the team as small as possible.

nikhita on Nov 18, 2020