Kubernetes Steering Committee Election Results 2017
"In case you missed it" as the modern idiom goes, please see below
---------- Forwarded message ---------
From: 'Sarah Novotny' via Kubernetes developer/contributor discussion <kubernetes-dev@...>
Date: Thu, Oct 5, 2017 at 6:31 PM
Subject: Kubernetes Steering Committee Election Results 2017
To: kubernetes-dev <kubernetes-dev@...>
please tweet with the Blog reference as you congratulate Aaron Crickenberger, Derek Carr, Michelle Noorali, Phillip Wittrock, Quinton Hoole and Timothy St. Clair
Kubernetes Community Steering Committee Election Results
Beginning with the announcement of Kubernetes 1.0 at OSCON in 2015, there has been a concerted effort to share the power and burden of leadership across the Kubernetes community.
With the work of the Bootstrap Governance Committee, consisting of Brandon Phillips, Brendan Burns, Brian Grant, Clayton Coleman, Joe Beda, Sarah Novotny and Tim Hockin - a cross section of long-time leaders representing 5 different companies with major investments of talent and effort in the Kubernetes Ecosystem - we wrote an initial Steering Committee Charter and launched a community wide election to seat a Kubernetes Steering Committee.
To quote from the Charter -
The initial role of the steering committee is to instantiate the formal process for Kubernetes governance. 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 live, responsive body that can refactor and reform as necessary to adapt to a changing project and community.
This is our largest step yet toward making an implicit governance structure explicit. Kubernetes vision has been one of an inclusive and broad community seeking to build software which empowers our users with the portability of containers. The Steering Committee will be a strong leadership voice guiding the project toward success.
The Kubernetes Community is pleased to announce the results of the 2017 Steering Committee Elections. Please congratulate Aaron Crickenberger, Derek Carr, Michelle Noorali, Phillip Wittrock, Quinton Hoole and Timothy St. Clair, who will be joining the members of the Bootstrap Governance committee on the newly formed Kubernetes Steering Committee. Derek, Michelle, and Phillip will serve for 2 years. Aaron, Quinton, and Timothy will serve for 1 year.
This group will meet regularly in order to clarify and streamline the structure and operation of the project. Early work will include electing a representative to the CNCF Governing Board, evolving project processes, refining and documenting the vision and scope of the project, and chartering and delegating to more topical community groups.
Please see the full Steering Committee backlog for more details.
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-dev+unsubscribe@....
To post to this group, send email to kubernetes-dev@....
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/CACmxMYrDJNfOf_wi%3DOYcUkdw2a0GxatvrgwUE8%3DhNqjg4ibOtQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
toggle quoted messageShow quoted text
- “Early work will include electing a representative to the CNCF Governing Board”
Is it referred to https://www.cncf.io/about/charter/:
- 5. (c) ii. b. “two Committers elected from the CNCF Projects under a process approved by the then-serving Governing Board.”?
Dan Kohn <dan@...>
toggle quoted messageShow quoted text
Correct, info on the developer seats is here: https://github.com/cncf/foundation/blob/master/gb-developer-reps.md
On Fri, Oct 6, 2017 at 1:58 AM, Donald Liu via cncf-toc <cncf-toc@...> wrote: