search

kubernetes / steering

The Kubernetes Steering Committee
Apache License 2.0
84 stars 60 forks source link

Include SIG Leads as voting CNCF Maintainers #281

Open BenTheElder opened 5 months ago

BenTheElder commented 5 months ago

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 commented 5 months ago

+1 thanks!

parispittman commented 5 months ago

+1

cpanato commented 5 months ago

+1

MadhavJivrajani commented 5 months ago

+1

natalisucks commented 5 months ago

+1

soltysh commented 4 months ago

:+1: (steering)

BenTheElder commented 4 months ago

Steering:

justaugustus commented 4 months ago

+1 (Steering)

palnabarun commented 4 months ago

+1 (steering)

pacoxu commented 4 months ago

+1 (Steering)

cpanato commented 4 months ago

+1

BenTheElder commented 4 months ago

nudge @pohly @mrbobbytables

mrbobbytables commented 4 months ago

+1 (steering)

reylejano commented 4 months ago

+1

eddiezane commented 4 months ago

+1 (SIG CLI)

pohly commented 4 months ago

+1 (steering)

divya-mohan0209 commented 4 months ago

+1

BenTheElder commented 4 months ago

With steering unanimous (votes: https://github.com/kubernetes/steering/issues/281#issuecomment-2103027792), I will reach out to the CNCF later today.

BenTheElder commented 3 months ago

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 commented 2 months ago

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 leads@kubernetes.io 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 commented 2 months ago

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 leads@kubernetes.io (perhaps auto-generated) 4) Then steering should email the CNCF alias with the maintainer list update based on this data