Need docs on how CLOWarden defines project permissions

[jberkus]

@RobertKielty posting this here because I'm not sure where else I should.

We could really use documentation on how Sheriff manages repo permissions, particularly for teams. For example, I need to add two new people to ours (and remove a few old ones), and I'm not clear on how to do it appropriately.

Are there public docs somewhere?

[RobertKielty]

@jberkus thank you for logging this.

There's a write up here that describes config.yaml from a GitHub Access point of view.

https://github.com/cncf/people#configyaml-configures-cncf-org-repository-access

I would appreciate your feed back on the above and happy to improve and add to those docs accordingly.

Right now, it's a light process, submit a PR to config.yaml.

config.yaml provides a single source of truth for access control and is cross-platform meaning that when you define a team in this file you can use that team to grant access to resources other than GitHub repos

[jberkus]

What does "maintainers" vs "members" mean for each team?