Review Netlify team member permissions for CNCF Projects & CNCF Projects 2

[nate-double-u]

Ensure that all members of the CNCF Projects and CNCF Projects 2 teams have appropriate permissions.

• Most teammembers should be: Collaborators, specific sites
• Exceptions can be made for folks who work across multiple projects, or need higher permissions

https://docs.netlify.com/accounts-and-billing/team-management/manage-team-members/#team-member-roles

[nate-double-u]

I need to double check that Collaborators are able to manage DNS. If not, I'll revise the issue.

Question: what would warrant a team member being an owner?

/cc @caniszczyk @amye @jeefy @chalin @thisisobate

[nate-double-u]

Collaborators are able to manage DNS--confirmed with the crossplane.io folks in the CNCF Projects 2 team

[nate-double-u]

/cc @RobertKielty

[nate-double-u]

I've been chatting with @caniszczyk and @jeefy, and here is a suggested policy for permissions across CNCF Netlify teams:

I’d like to suggest that @caniszczyk, @jeefy, and @nate-double-u are the CNCF admins/owners for Netlify. If any of the three of us aren’t on a Netlify team, we should add the other two.

For others, on the principle of granting the fewest permissions needed:

• LF/CNCF employees (beyond the three mentioned above, if needed): Owners
• Project Maintainers: Owners
• LF/CNCF Contractors: Collaborators
• Project contributors the Maintainers have suggested: Collaborators

The team exceptions:

• Kubernetes as they have their own processes in place around this. I’ve been working with the docs team over there to get someone from techdocs to be an admin on their system: https://github.com/kubernetes/website/discussions/38019
• CNCF Projects & CNCF Projects 2: as @RobertKielty is helping with automation and process, they should be made Owners on these teams.

Happy to discuss here -- we also need to figure out the best place to put this info, some options:

• https://github.com/cncf/techdocs/tree/main/docs
• https://github.com/cncf/servicedesk
• other?

[chalin]

Re. Kubernetes, the previously mentioned discussion has been locked; tracking happens via:

• https://github.com/kubernetes/website/issues/38839