search

kubernetes / sig-release

Repo for SIG release
Apache License 2.0
521 stars 379 forks source link

Determine access levels for SIG subproject leads #2515

Open justaugustus opened 1 month ago

justaugustus commented 1 month ago

Now that we have subproject leads (hi @gracenng @katcosgrove @xmudrii), we have a gap in documentation and access grants (and an opportunity to allow them to review/approve additional areas).

ref: https://github.com/kubernetes/sig-release/issues/2516

xmudrii commented 1 month ago

I was thinking about this, especially about how should we treat subproject leads in terms of Google Groups, GitHub, and Slack teams. I'm wondering if it makes sense to add us to the leads group (e.g. @kubernetes/sig-release-leads), because we're kind of leads and want to stay informed on all the things just like chairs and TLs. A dedicated group/team probably wouldn't make sense because I imagine it'll be rare to ping only subproject leads and not chairs/TLs. I don't know what implications on permissions this might have though.