Open palnabarun opened 3 months ago
I just noticed this seems a bit stale: https://kubernetes.slack.com/archives/C1TU9EB9S/p1731916285394959
I wonder if there's a better way we can do this for other teams as well ... something to think about.
This is a little tough to quantify and prune using a tool as the definition of membership to a SIG isn't very concrete.
Yeah, but we could do something like asking leads to review this periodically with some low frequency? There has to be a better answer than filing one-off issues.
Agreed. This should be something that should be part of an yearly-checklist of each lead.
(partly this is how I created the issue)
Describe the issue
Historically the GitHub team was used to document the contributors working in a specific community group. As of now, it's not very relevant as GitHub team membership is not tied to group membership.
/sig contributor-experience /priority important-longterm /kind cleanup
/assign