Include SIG Leads as voting CNCF Maintainers

[BenTheElder]

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

[dims]

+1 thanks!

[parispittman]

+1

[cpanato]

+1

[MadhavJivrajani]

+1

[natalisucks]

+1

[soltysh]

👍 (steering)

[BenTheElder]

Steering:

• @BenTheElder Include SIG Leads as voting CNCF Maintainers #281 (comment)
• @mrbobbytables Include SIG Leads as voting CNCF Maintainers #281 (comment)
• @palnabarun Include SIG Leads as voting CNCF Maintainers #281 (comment)
• @soltysh Include SIG Leads as voting CNCF Maintainers #281 (comment)
• @pacoxu Include SIG Leads as voting CNCF Maintainers #281 (comment)
• @pohly Include SIG Leads as voting CNCF Maintainers #281 (comment)
• @justaugustus Include SIG Leads as voting CNCF Maintainers #281 (comment)

[justaugustus]

+1 (Steering)

[palnabarun]

+1 (steering)

[pacoxu]

+1 (Steering)

[cpanato]

+1

[BenTheElder]

nudge @pohly @mrbobbytables

[mrbobbytables]

+1 (steering)

[reylejano]

+1

[eddiezane]

+1 (SIG CLI)

[pohly]

+1 (steering)

[divya-mohan0209]

+1

[BenTheElder]

With steering unanimous (votes: #281 (comment)), I will reach out to the CNCF later today.

[BenTheElder]

Circling back to leave a quick update here:

I did reach out previously. This will take a bit of coordinating but nominally we can email updated maintainer lists to the CNCF. The processes are manual (and multiple places need updating?) so we'll have to discuss how we'd keep this in sync.

I plan to follow-up at the next steering meeting.

[BenTheElder]

We discussed this in the private meeting today where we had quorum.

We need correct email addresses for the chairs & tech leads to make this work.

We think the best course of action is to ensure that lead emails are included in the sigs.yaml metadata which we can then use to automatically check that our [email protected] group is up to date (and include a comment cross referencing the email to the SIG(s), which is something the community recently discussed), currently this information is a bit disjoint and we think sigs.yaml will be the best source of truth to keep all lists up to date.

We can then use this information to have steering regularly update the CNCF when changes to our leads list are made, we'll need to email the special alias for this with the list of emails / github and make sure to mention that these are non-service-desk-access maintainers.

[BenTheElder]

1. I intend to work on the sigs.yaml change soon.
2. Then we can reach out to leads to get that information added
3. Then we can update [email protected] (perhaps auto-generated)
4. Then steering should email the CNCF alias with the maintainer list update based on this data

[BenTheElder]

To be honest, this one got punted in favor of finishing infra migration, with the nearest deadline for this probably being December TOC elections.

I spoke to bob [cncf hat] about handling the bulk update yesterday.

[BenTheElder]

/lifecycle active

[BenTheElder]

kubernetes/community#8138 merged, I sent a PSA to [email protected] and #chairs-and-techleads in slack regarding backfilling current lead emails.

[joelsmith]

@BenTheElder do you think that the CNCF list will be updated before December 11? No worries if not -- that just means that I would have to recruit someone who is on the current CNCF list to submit my CFP for me before the Maintainer Track / CNCF Maintainer Summit Europe 2025 deadline.

https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/features-add-ons/project-opportunities/#description-of-opportunities

[pacoxu]

IIUC, kubernetes member can submit CFP, according to https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/features-add-ons/maintainer-summit/#eligibility.

[natalisucks]

@joelsmith All Kubernetes org members can submit a CFP for the CNCF Maintainer Summit! No need to wait for this PR to merge 👍

[BenTheElder]

@BenTheElder do you think that the CNCF list will be updated before December 11? No worries if not -- that just means that I would have to recruit someone who is on the current CNCF list to submit my CFP for me before the Maintainer Track / CNCF Maintainer Summit Europe 2025 deadline.

In addition to the comments above about being able to submit CFPs, remaining steps are:

1. Make sure we've collected emails from everyone
2. We will need to dump that data into a categorized, de-duped list (some people are already included, some will be voting + service desk, some will be voting only), I think we'll script that.
3. Email CNCF

1) still has some open PRs, I'm doing another sweep after the steering meeting today.

optional follow-up:
4. look at reconciling the [email protected] list now that we have an authoritative dataset