kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Rewrite 2018 voting guideline 

This points to kubernetes/steering as the source of truth
for eligibility requirements for voting and candidacy

I also word wrapped the 2018 voting guide to 80 chars, which
makes for an awful diff, so I'll explain what I changed as
notes in the PR

I swear I didn't sneak in a "all votes secretly go to Aaron"
policy. Promise.  Really.
This commit is contained in:
Aaron Crickenberger 2018-08-15 17:17:32 -07:00
parent 1afca8f610
commit 4268a2f226
2 changed files with 103 additions and 55 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

125
events/elections/2018/README.md
View File

@ -2,63 +2,91 @@
## Purpose ## Purpose
The role of this election is to fill out the three(3) seats due for reelection this year on the [Kubernetes Steering Committee](https://github.com/kubernetes/steering). The role of this election is to fill out the three (3) seats due for
reelection this year on the [Kubernetes Steering Committee]. Each elected
member will serve a two year term.
## Voting ## Background
This election will shape the future of Kubernetes as a project and community. You will be voting on three (3) seats up for election. This election will shape the future of Kubernetes as a community and project.
Every elected community member will serve a two year term. While SIGs and WGs help shape the technical direction of the project, the
[Steering Committee Charter] covers the health of the project and community
as a whole. Some examples of responsibilities to consider as you are deciding
whether to run or who to vote for:
The candidates you are voting on will be meeting regularly to strategically grow the project with contributors in mind. Most of the technical decisions, architecture planning, and the like come out of SIGs and other working groups. - Define, evolve, and defend the vision, values, mission, and scope of the
Some examples of responsibilities to consider as you are voting: project.
- Define, evolve, and defend the vision, values, mission, and scope of the project - to establish and maintain the soul of Kubernetes. - Define and evolve project governance structures and policies, including how
- Charter and refine policy for defining new community groups (including Special Interest Groups, Working Groups, and Committees), and establish transparency and accountability policies for such groups. contributors become committers/maintainers, approvers, reviewers, members,
- Define, evolve, and defend a Code of Conduct, which must include a neutral, unbiased process for resolving conflict etc.
- Charter and refine policy for defining new community groups (including
Special Interest Groups, Working Groups, and Committees), and establish
transparency and accountability policies for such groups
Full scope of responsibilities, goals, and/or future election timelines, see [steering committee charter](https://github.com/kubernetes/steering/blob/master/charter.md). For more context, please see the [current steering committee backlog] or a
previous [governance meeting video] which led to this whole process.
For more context, please see the [current issues](https://github.com/kubernetes/steering/blob/master/backlog.md) that need to be resolved or a previous governance [meeting video](https://www.youtube.com/watch?v=ltRKXLl0RaE&list=PL69nYSiGNLP1pkHsbPjzAewvMgGUpkCnJ&index=23) which led to this whole process. ## Eligibility
## Process Please refer to the [Steering Committee Election Charter] for:
Elections will be held using time-limited [Condorcet](https://en.wikipedia.org/wiki/Condorcet_method) ranking on [CIVS](http://civs.cs.cornell.edu/) using the [Schulze method](https://en.wikipedia.org/wiki/Schulze_method). - [elegibility for candidacy]
The top vote getters, modulo the corporate diversity requirement of no more than 1/3 of the committee from a single company, will be elected to the respective positions. - [eligibility for voting]
You will be ranking your choices of the candidates with an option for "no opinion". In the event of a tie, a coin will be flipped. ### Schedule
The election will open for voting on September 19, 2018 at 04:00pm UTC and end two weeks after on October 3, 2018 at 01:00am UTC. You will receive an email to the address on file at the start of the election from Jorge Castro (jorge@heptio), Community Manager, please whitelist if necessary. Detailed voting instructions will be addressed in email and the CIVS polling page. | Date | Event |
| ------------ | ------------------------ |
| August 15 | Announcement of Election |
| September 14 | All candidate bios / statements of intent due. Voting exemption forms due. |
| September 19 | Election Begins |
| October 3 | Election Closes |
| October 4 | Announcement of Results |
## Candidacy Process
Candidates must submit a pull request with a biography in this directory with
their platform and intent to run. This statement is **limited to 300 words**
and must follow the format of `firstnamelastname.md`. Please refer to the
[2017 candidate bios] for examples.
## Voting Process
Elections will be held using time-limited [Condorcet] ranking on [CIVS]
using the [Schulze method]. The top vote getters will be elected to the open
seats.
Employer diversity is encouraged, and thus [maximal representation] will be
enforced as spelled out in the [Steering Committee Election Charter].
You will be ranking your choices of the candidates with an option for
"no opinion". In the event of a tie, a coin will be flipped.
The election will open for voting on September 19, 2018 at 04:00pm UTC and
end two weeks after on October 3, 2018 at 01:00am UTC. You will receive an
email to the address on file at the start of the election from Jorge Castro
(jorge@heptio), Community Manager, please whitelist if necessary. Detailed
voting instructions will be addressed in email and the CIVS polling page.
### Officers ### Officers
The Steering Committee has selected the following people as [election officers](https://github.com/kubernetes/community/tree/master/events/elections#election-officers): The Steering Committee has selected the following people as [election officers]:
- Paris Pittman, @parispittman, Google - Paris Pittman, @parispittman, Google
- Ihor Dvoretskyi, @idvoretskyi, CNCF - Ihor Dvoretskyi, @idvoretskyi, CNCF
- Jorge Castro, @castrojo, Heptio - Jorge Castro, @castrojo, Heptio
### Schedule Please direct any questions via email to <elections@k8s.io>.
August 15 - Announcement of Election
September 14 - All candidate bios / statement of intents due. Voting exemption forms due.
September 19 - Election Begins
October 3 - Election Closes
October 4 - Announcement of Results
### Eligibility
Members of Standing are defined by the union of:
- SIG Chairs/Leads
- Approvers and reviewers in any Kubernetes owned repositories
- Anyone with write access to a Kubernetes owned repository
- Active members of our community with at least [50 contributions to core Kubernetes](https://k8s.devstats.cncf.io/d/13/developer-activity-counts-by-repository-group?orgId=1&var-period_name=Last%20year&var-metric=contributions&var-repogroup_name=All)
- People who have non-code contributions can submit a [voting exemption form](URL TBD) to account for contributions not measured by devstats.
Candidates must submit a pull request with a biography in this directory with their platform and intent to run. This statement is **limited to 300 words** and must follow the format of `firstnamelastname.md`. See [last year's submissions](https://github.com/kubernetes/community/tree/master/events/elections/2017) for some examples.
### Decision ### Decision
The newly elected body will be announced in the weekly [Kubernetes Community Meeting](https://github.com/kubernetes/community/blob/master/events/community-meeting.md) on October 4, 2018.
Following the meeting, the raw voting results and winners will be published on the [Kubernetes Blog](http://blog.kubernetes.io/). The newly elected body will be announced in the weekly [Kubernetes Community Meeting]
on October 4, 2018.
For more information, definitions, and/or detailed election process, see full [steering committee charter](https://github.com/kubernetes/steering/blob/master/charter.md). Following the meeting, the raw voting results and winners will be published on the
[Kubernetes Blog]
For more information, definitions, and/or detailed election process, please refer to
the [Steering Committee Election Charter]
## Nominees ## Nominees
@ -67,7 +95,24 @@ Name | Organization/Company | GitHub
[Jane Container](janecontainer.md) | ContainerCo | [@github](link this) | [Jane Container](janecontainer.md) | ContainerCo | [@github](link this) |
<strong>Note:</strong>The steering committee members and election officers have <strong>Note:</strong>The steering committee members and election officers have
recused themselves from any form of electioneering, including recused themselves from any form of electioneering, including campaigning,
campaigning, nominating, endorsing, or even asking people to run. nominating, endorsing, or even asking people to run.
Please direct any questions via email to <elections@k8s.io>.
[Kubernetes Steering Committee]: https://github.com/kubernetes/steering
[Steering Committee Charter]: https://github.com/kubernetes/steering/blob/master/charter.md
[current steering committee backlog]: https://github.com/kubernetes/steering/projects/1
[governance meeting video]: https://www.youtube.com/watch?v=ltRKXLl0RaE&list=PL69nYSiGNLP1pkHsbPjzAewvMgGUpkCnJ&index=23
[Steering Committee Election Charter]: https://git.k8s.io/steering/elections.md
[eligibility for voting]: https://github.com/kubernetes/steering/blob/master/elections.md#elegibility-for-voting
[eligibility for candidacy]: https://github.com/kubernetes/steering/blob/master/elections.md#elegibility-for-candidacy
[Condorcet]: https://en.wikipedia.org/wiki/Condorcet_method
[CIVS]: http://civs.cs.cornell.edu/
[Schulze method]: https://en.wikipedia.org/wiki/Schulze_method
[2017 candidate bios]: https://github.com/kubernetes/community/tree/master/events/elections/2017
[election officers]: https://github.com/kubernetes/community/tree/master/events/elections#election-officers
[Kubernetes Community Meeting]: https://github.com/kubernetes/community/blob/master/events/community-meeting.md
[Kubernetes Blog]: http://blog.kubernetes.io/

5
events/elections/README.md
View File

@ -1,6 +1,9 @@
## Kubernetes Elections ## Kubernetes Elections
This document will outline how to conduct a Kubernetes Steering Committee Election. See the [Steering Committee Charter](https://git.k8s.io/steering/charter.md) for more information of how the committee decides when to have an election, the method, and the maximal representation. This document will outline how to conduct a Kubernetes Steering Committee
Election. See the [Steering Committee Election Charter](https://git.k8s.io/steering/elections.md)
for more information of how the committee decides when to have elections,
eligibility for voting, eligibility for candidacy, maximal representation, etc.
## Steering Committee chooses Election Officers ## Steering Committee chooses Election Officers