kubernetes / kubernetes/community

Steering Election: Add chairs and tech leads from sigs.yaml to voters.yaml for Steering elections

Open
#9,063 4 comments 0 reactions 0 assignees View on GitHub
area/elections committee/steering
Dominant language
Jupyter Notebook
Stars
13k
Forks
5.4k
Avg merge
2d 17h
Merged PRs (30d)
29

Description

For Steering elections, org members with at least 50 contributions in the past year, members of the Security Response Committee (SRC), and Code of Conduct Committee (CoCC) members are eligible voters and included in the voters.yaml of the steering election year. IIRC, members of the SRC and CoCC are eligible voters since their work is not tracked by GitHub.
This issue discusses whether SIG chairs and tech leads (as listed in k/community/sigs.yaml) should also be automatically eligible voters and added to voters.yaml

/committee steering
/area elections

Contributor guide

Open the contributing guide

Research direction

Start by reading k/community/sigs.yaml and the relevant voters.yaml for a Steering election, then review the eligibility rules described in this issue. Done requires a decided policy on SIG chairs and tech leads and, if approved, consistent inclusion of eligible people in the election-year voters.yaml.

Written by the indexing model from the issue text.

Assessment

Tech stack
yaml
Domain
documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.