This election has been completed.
The initial role of the steering committee is to instantiate the formal governance process for Kubernetes. In addition to defining the initial governance process, the bootstrap committee strongly believes that it is important to provide a means for iterating the processes defined by the steering committee. We do not believe that we will get it right the first time, or possibly ever, and won’t even complete the governance development in a single shot. The role of the steering committee is to be a living, responsive body that can refactor and reform as necessary to adapt to a changing project and community.
This election will shape the future of Kubernetes as a project and community. You will be voting on six (6) seats up for election, three with a two year term and three with an initial one year term. The motivation for these different terms is to set up an initial stagger so that the entire committee isn’t replaced every election cycle. After this first election, every elected community member will serve a two year term.
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. Some examples of responsibilities to consider as you are voting:
* Define, evolve, and defend the vision, values, mission, and scope of the project - to establish and maintain the soul of Kubernetes * 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.
* Define, evolve, and defend a Code of Conduct, which must include a neutral, unbiased process for resolving conflict
Full scope of responsibilities, goals, and/or future election timelines, see steering committee charter.
Elections will be held using time-limited Condorcet ranking on CIVS using the Schulze method. 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, with the top 3 filling the 2 year term seats, and the next 3 filling the 1 year term seats.
You will be ranking your choices 1-20 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, 2017 at 09:00am PDT and end two weeks after on October 3, 2017 at 06:00pm PDT. 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.
Members of Standing are defined by the union of: * SIG leads * Approvers and reviewers in any Kubernetes owned repositories * Anyone with write access to a Kubernetes owned repository * Active members of our community If you believe you are a Member of Standing, please fill out this form before September 13, 2017.
The newly elected body will be announced in the weekly Kubernetes Community Meeting on October 5, 2017 at 10:00am US Pacific Time. Please join us.
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, see full steering committee charter.
Don’t know someone on this list? We asked the nominees to provide a <300 word bio about their k8s experience that we’ll link to their name in this table.
|Aaron Crickenberger||Samsung SDS||@spiffxp|
|Derek Carr||Red Hat||@derekwaynecarr|
|Jaice Singer DuMars||Microsoft||@jdumars|
|Justin Santa Barbara||Independent||@justinsb|
|Matt Farina||Samsung SDS||@mattfarina|
|Timothy St. Clair||Heptio||@timothysc|
Note:The bootstrap committee members have recused themselves from any form of electioneering, including campaigning, nominating, endorsing, or even asking people to run.