Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Automate the management of github team membership #336
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.
@spiffxp: Reopened this issue.
In response to this:
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.