Repository navigation
Include SIG Leads as voting CNCF Maintainers #281
Description
Currently the steering committee are voting + service desk access members in https://github.com/cncf/foundation/blob/main/project-maintainers.csv
A few relevant SIGs have service desk access only (Contributor Experience, Infra, Release).
Following https://github.com/cncf/foundation/pull/223/files voting changed from fractional per project to one maintainer one vote.
The Steering Committee has discussed adding SIG Leads, that is Chairs and Tech Leads to the maintainers list in a non-service-desk but voting role.
We think this will reasonably improve the representation of the project, all other subgroups should have representation via Steerings and their SIG Leads.
For the service desk specifically, we already have sufficient representation across the SIGs that are responsible for providing services to the project and Steering.
This issue will track voting on these changes because relevant policy docs currently live across multiple repos in multiple locations.
/assign @kubernetes/steering-committee
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
[-]Include SIG Leads as non-service-desk Voting CNCF Maintainers[/-][+]Include SIG Leads as voting CNCF Maintainers[/+]dims commentedon Apr 17, 2024
+1 thanks!
parispittman commentedon Apr 17, 2024
+1
cpanato commentedon Apr 18, 2024
+1
MadhavJivrajani commentedon Apr 19, 2024
+1
natalisucks commentedon Apr 19, 2024
+1
soltysh commentedon May 9, 2024
👍 (steering)
BenTheElder commentedon May 9, 2024
Steering:
justaugustus commentedon May 9, 2024
+1 (Steering)
palnabarun commentedon May 9, 2024
+1 (steering)
pacoxu commentedon May 9, 2024
+1 (Steering)
cpanato commentedon May 10, 2024
+1
BenTheElder commentedon May 14, 2024
nudge @pohly @mrbobbytables
30 remaining items
BenTheElder commentedon Jun 25, 2025
@cblecker +1, I think that will require consensus from @kubernetes/steering-committee though.
soltysh commentedon Jun 25, 2025
I'm supportive - 👍
aojea commentedon Jun 25, 2025
+1
saschagrunert commentedon Jun 26, 2025
+1
pohly commentedon Jun 26, 2025
+1
pacoxu commentedon Jun 26, 2025
+1
justaugustus commentedon Jun 26, 2025
+1 (Steering)
BenTheElder commentedon Aug 14, 2025
An update:
That last change with @cblecker is pending, and we otherwise just have "how often should we send updates and should it be a diff or can we send the full list" for future changes.
This should be more or less complete since #281 (comment) and above but we of course will need to continue to submit updates, otherwise I would've closed this out.
pacoxu commentedon Aug 15, 2025
Leads may update it themselves once there is a leader change. (We may add it to the lead change checklist of the template)
Meanwhile, we may do it every quarter or half year in case the list is not synced. At least, we will update it once a year after steering election.
BenTheElder commentedon Aug 15, 2025
I'm not sure that will work. It is not self-service yet, and the PR you see on github is only one of the steps.
Currently we have to reach out to the CNCF's maintainers updates alias, I'm not sure if they would respond to requests from unknown parties.
There was discussion of a self-service functionality at some point, but we don't have a firm ETA or any updates on that.
Yes, I should've been clearer: I've reached out to the CNCF alias to ask about what would be acceptable frequency (I suggested perhaps roughly quarterly) and format wise wise (diff versus last update, or full current desired list).
BenTheElder commentedon Oct 22, 2025
Tiny update: We still haven't heard back from our previous requests so I have bumped the thread again.
riaankleinhans commentedon Oct 22, 2025
@BenTheElder, @cblecker added to cncf-kubernetes-maintainers mailing list.
BenTheElder commentedon Oct 22, 2025
Thanks! per @jeefy (CNCF liason for kubernetes) we should send quarterly updates.
kubernetes/community#8664 will make sure the GB rep is tracked alongside our other leads going forward.
I'm going to close this out, steering will need to continue to send the ~quarterly updates to re-sync but that can just be regular business now.
We understand in the future there will be a new mechanism for projects to manage this, and we can revisit then.