Org: Automate the management of github team membership

[spiffxp]

/kind design
/sig contributor-experience
/area github

I was unable to find an issue to point to for "we intend to one day automate team membership via peribolos" so now I've gone and created one.

I have used peribolos in the past to mass-create some teams for kubernetes-csi repos, but it wasn't a very friendly experience. I used a file to generate the teams and populate members/maintainers, but I still had to go through and manually assign ACLs to repos.

Ultimately I think we want to make this a self-service experience akin to test-infra's config/jobs directory, where files are sharded and OWNERS files allow sigs to control their thing. But I hazily recall we have discussed in the past the idea of iterating with one massive file per org to start with.

There's also the question of whether we want to disallow team maintainers as a role, and instead just use members + OWNERS files here. Today I can find no documented policy on who is supposed to be a Team Maintainer and what their responsibilities are.

/assign @cblecker @fejta
as the two who have the most hands on experience and best chance of enumerating what remains to be done here

[spiffxp]

/reopen

I think this needs some more polish before we can consider it closed:

• what's the process to add new teams?
• are we sure we're not going to exhaust our tokens anymore?

[k8s-ci-robot]

@spiffxp: Reopened this issue.

In response to this:

/reopen

I think this needs some more polish before we can consider it closed:

• what's the process to add new teams?
• are we sure we're not going to exhaust our tokens anymore?

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[fejta]

are we sure we're not going to exhaust our tokens anymore?

😆

[nikhita]

what's the process to add new teams?

Created https://github.com/kubernetes/community/issues/3102

[nikhita]

@spiffxp @cblecker Looks like this can be closed? https://github.com/kubernetes/community/issues/3102 is the issue for improving documentation around this.

[cblecker]

Yup, IMO.
/close

[k8s-ci-robot]

@cblecker: Closing this issue.

In response to this:

Yup, IMO.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.