kubernetes / steering

The Kubernetes Steering Committee

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Include SIG Leads as voting CNCF Maintainers

BenTheElder opened this issue · comments

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

+1 thanks!

+1

👍 (steering)

+1 (Steering)

+1 (steering)

+1 (Steering)

+1 (steering)

+1 (SIG CLI)

+1 (steering)

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

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.