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

Include the non-electioneering commitment 

Rather than saying that the committee does not endorse any
of the candidates, which means something rather different!

Also remove the term "current bootstrap committee" - the future
committee is the steering committee.
This commit is contained in:
Justin Santa Barbara 2017-09-14 08:33:18 -04:00
parent 69ed58ab57
commit 775ace7a2e
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
community/elections/2017/README.md
View File

@ -1,7 +1,7 @@
# 2017 VOTERS GUIDE - KUBERNETES STEERING COMMITTEE ELECTION
# PURPOSE
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 [current bootstrap committee](https://groups.google.com/forum/#!msg/kubernetes-dev/4e8WOnMvZC0/57GYmJKfDAAJ) 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.
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](https://groups.google.com/forum/#!msg/kubernetes-dev/4e8WOnMvZC0/57GYmJKfDAAJ) 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.
# VOTING
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.
@ -62,7 +62,9 @@ Sebastien Goasguen | Bitnami | [@sebgoa](http://github.com/sebgoa)
[Timothy St. Clair](timothysc_bio.md) | Heptio | [@timothysc](https://github.com/timothysc)
<strong>Note:</strong>The current committee does not endorse any candidate.
<strong>Note:</strong>The bootstrap committee members have
recused themselves from any form of electioneering, including
campaigning, nominating, endorsing, or even asking people to run.
Please direct any questions via email to <kubernetes-governance-committee@googlegroups.com><br>
[K8s Slack](http://slack.k8s.io/)