1. cncf-toc@lists.cncf.io
  2. Messages
   Date   
Re: [VOTE] Kubernetes moving to graduation

Jon Mittelhauser
 

+1 non-binding

On 2/26/18, 9:53 AM, "Michael Hausenblas" <cncf-toc@lists.cncf.io on behalf of mhausenb@redhat.com> wrote:

+1 non-binding

Cheers,
Michael

--
Michael Hausenblas, Developer Advocate
OpenShift by Red Hat
Mobile: +353 86 0215164 | Twitter: @mhausenblas
https://urldefense.proofpoint.com/v2/url?u=http-3A__openshift.com&d=DwIFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=FHIOY6WPD2iUlYyguyR6P1yL3kZ3ufKFttWUV6c6mMg&m=1YTJCWvDUziJA-RXN4sAdRfmHhMiBol_aKpD6Zv-J8A&s=zUZjQoPh84pjaCSmfH9_2EqPAhhznwB1pefToEAbLBU&e= | https://urldefense.proofpoint.com/v2/url?u=http-3A__mhausenblas.info&d=DwIFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=FHIOY6WPD2iUlYyguyR6P1yL3kZ3ufKFttWUV6c6mMg&m=1YTJCWvDUziJA-RXN4sAdRfmHhMiBol_aKpD6Zv-J8A&s=o4WCaRMRxeYZx_l4yxItcNWBeRMnksV8JvdVSHoRG5U&e=

-----Original Message-----
From: Chris Aniszczyk <caniszczyk@linuxfoundation.org>
Reply: Chris Aniszczyk <caniszczyk@linuxfoundation.org>
Date: 26 February 2018 at 16:52:44
To: cncf-toc@lists.cncf.io <cncf-toc@lists.cncf.io>
Subject: [cncf-toc] [VOTE] Kubernetes moving to graduation

> After last week's TOC call, we decided to start moving forward with
> graduation reviews. Kubernetes was the project that motivated the creation
> of the CNCF, and was its first (seed) project. It has sustained a fast pace
> of growth of contributors, contributing organizations, and users, and now
> operates at massive scale. The project's governance and
> community-management practices continue to evolve and mature as the project
> grows, but the Kubernetes Steering Committee (
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_kubernetes_steering&d=DwIFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=FHIOY6WPD2iUlYyguyR6P1yL3kZ3ufKFttWUV6c6mMg&m=1YTJCWvDUziJA-RXN4sAdRfmHhMiBol_aKpD6Zv-J8A&s=DT1D3XCtzJJi3rEYKP86jvtDj49kvVn6f_43iRPq4_o&e=) unanimously believes that
> Kubernetes fulfills all the CNCF incubating and graduation criteria:
>
> - Used successfully in production by at least three independent end users
> of sufficient scale and quality: https://urldefense.proofpoint.com/v2/url?u=https-3A__kubernetes.io_case-2Dstudies&d=DwIFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=FHIOY6WPD2iUlYyguyR6P1yL3kZ3ufKFttWUV6c6mMg&m=1YTJCWvDUziJA-RXN4sAdRfmHhMiBol_aKpD6Zv-J8A&s=RaH3otq1Wz2rLs1rha4_Rf6L9Y3siFUlsnIDv5nc0RU&e=
> - Have a healthy number of committers: Kubernetes is so large, with
> thousands of contributors and nearly 100 repositories, that we had to
> develop our own mechanism to manage approval permissions. We have hundreds
> of approvers, listed in more than 4000 OWNERS files across the project (
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_search-3Futf8-3D-25E2-259C-2593-26q-3Dorg-253Akubernetes-2Bfilename-253AOWNERS-26type-3DCode&d=DwIFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=FHIOY6WPD2iUlYyguyR6P1yL3kZ3ufKFttWUV6c6mMg&m=1YTJCWvDUziJA-RXN4sAdRfmHhMiBol_aKpD6Zv-J8A&s=gmfZeVcSLEy-m-iIl8P0bICNUP3A-OaE5n5TayWMTEQ&e=
> )
> - Demonstrate a substantial ongoing flow of commits and merged
> contributions: Devstats shows that we have thousands of PRs merged per
> month (https://urldefense.proofpoint.com/v2/url?u=https-3A__k8s.devstats.cncf.io_&d=DwIFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=FHIOY6WPD2iUlYyguyR6P1yL3kZ3ufKFttWUV6c6mMg&m=1YTJCWvDUziJA-RXN4sAdRfmHhMiBol_aKpD6Zv-J8A&s=2ZXoRn5Xc14xds6NucpLPsTW4KdFMDDCOtgU-Xtkd6Q&e=)
>
> Please vote (+1/0/-1) by replying to this thread; the full proposal located
> here: https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_cncf_toc_pull_91&d=DwIFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=FHIOY6WPD2iUlYyguyR6P1yL3kZ3ufKFttWUV6c6mMg&m=1YTJCWvDUziJA-RXN4sAdRfmHhMiBol_aKpD6Zv-J8A&s=RaoKaMsBvN8xlY0Sexj2gftoMZ9aYExmdikoGX4EknY&e=
>
> Remember that the TOC has binding votes only, but we do appreciate
> non-binding votes from the community as a sign of support!
>
> --
> Chris Aniszczyk (@cra) | +1-512-961-6719
>
Re: [VOTE] Kubernetes moving to graduation

Karan Gupta <karan@...>
 

+1 non-binding

On Mon, Feb 26, 2018 at 9:41 AM, Thangavelu, Kapil via Lists.Cncf.Io <kapil.thangavelu=capitalone.com@...> wrote:

+1 non-binding

From: cncf-toc@... <cncf-toc@...> on behalf of Niraj Tolia <ntolia@...>
Sent: Monday, February 26, 2018 12:40:46 PM
To: cncf-toc@...
Cc: cncf-toc@...
Subject: Re: [cncf-toc] [VOTE] Kubernetes moving to graduation
 
+1 non-binding


On Mon, Feb 26, 2018 at 8:52 AM, Chris Aniszczyk <caniszczyk@linuxfoundation.org> wrote:
After last week's TOC call, we decided to start moving forward with graduation reviews. Kubernetes was the project that motivated the creation of the CNCF, and was its first (seed) project. It has sustained a fast pace of growth of contributors, contributing organizations, and users, and now operates at massive scale. The project's governance and community-management practices continue to evolve and mature as the project grows, but the Kubernetes Steering Committee (https://github.com/kubernetes/steering) unanimously believes that Kubernetes fulfills all the CNCF incubating and graduation criteria:

- Used successfully in production by at least three independent end users of sufficient scale and quality: https://kubernetes.io/case-studies
- Have a healthy number of committers: Kubernetes is so large, with thousands of contributors and nearly 100 repositories, that we had to develop our own mechanism to manage approval permissions. We have hundreds of approvers, listed in more than 4000 OWNERS files across the project (https://github.com/search?utf8=%E2%9C%93&q=org%3Akubernetes+filename%3AOWNERS&type=Code)
- Demonstrate a substantial ongoing flow of commits and merged contributions: Devstats shows that we have thousands of PRs merged per month (https://k8s.devstats.cncf.io/)

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/91

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

--
Chris Aniszczyk (@cra) | +1-512-961-6719



The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.
Re: [VOTE] Kubernetes moving to graduation

Thangavelu, Kapil
 

+1 non-binding

From: cncf-toc@... <cncf-toc@...> on behalf of Niraj Tolia <ntolia@...>
Sent: Monday, February 26, 2018 12:40:46 PM
To: cncf-toc@...
Cc: cncf-toc@...
Subject: Re: [cncf-toc] [VOTE] Kubernetes moving to graduation
 
+1 non-binding


On Mon, Feb 26, 2018 at 8:52 AM, Chris Aniszczyk <caniszczyk@...> wrote:
After last week's TOC call, we decided to start moving forward with graduation reviews. Kubernetes was the project that motivated the creation of the CNCF, and was its first (seed) project. It has sustained a fast pace of growth of contributors, contributing organizations, and users, and now operates at massive scale. The project's governance and community-management practices continue to evolve and mature as the project grows, but the Kubernetes Steering Committee (https://github.com/kubernetes/steering) unanimously believes that Kubernetes fulfills all the CNCF incubating and graduation criteria:

- Used successfully in production by at least three independent end users of sufficient scale and quality: https://kubernetes.io/case-studies
- Have a healthy number of committers: Kubernetes is so large, with thousands of contributors and nearly 100 repositories, that we had to develop our own mechanism to manage approval permissions. We have hundreds of approvers, listed in more than 4000 OWNERS files across the project (https://github.com/search?utf8=%E2%9C%93&q=org%3Akubernetes+filename%3AOWNERS&type=Code)
- Demonstrate a substantial ongoing flow of commits and merged contributions: Devstats shows that we have thousands of PRs merged per month (https://k8s.devstats.cncf.io/)

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/91

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

--
Chris Aniszczyk (@cra) | +1-512-961-6719



The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.
Re: [VOTE] Kubernetes moving to graduation

Niraj Tolia
 

+1 non-binding


On Mon, Feb 26, 2018 at 8:52 AM, Chris Aniszczyk <caniszczyk@...> wrote:
After last week's TOC call, we decided to start moving forward with graduation reviews. Kubernetes was the project that motivated the creation of the CNCF, and was its first (seed) project. It has sustained a fast pace of growth of contributors, contributing organizations, and users, and now operates at massive scale. The project's governance and community-management practices continue to evolve and mature as the project grows, but the Kubernetes Steering Committee (https://github.com/kubernetes/steering) unanimously believes that Kubernetes fulfills all the CNCF incubating and graduation criteria:

- Used successfully in production by at least three independent end users of sufficient scale and quality: https://kubernetes.io/case-studies
- Have a healthy number of committers: Kubernetes is so large, with thousands of contributors and nearly 100 repositories, that we had to develop our own mechanism to manage approval permissions. We have hundreds of approvers, listed in more than 4000 OWNERS files across the project (https://github.com/search?utf8=%E2%9C%93&q=org%3Akubernetes+filename%3AOWNERS&type=Code)
- Demonstrate a substantial ongoing flow of commits and merged contributions: Devstats shows that we have thousands of PRs merged per month (https://k8s.devstats.cncf.io/)

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/91

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

--
Chris Aniszczyk (@cra) | +1-512-961-6719
Re: [VOTE] Kubernetes moving to graduation

Gou Rao <grao@...>
 

+1 non binding

On Mon, Feb 26, 2018 at 8:52 AM, Chris Aniszczyk <caniszczyk@...> wrote:
After last week's TOC call, we decided to start moving forward with graduation reviews. Kubernetes was the project that motivated the creation of the CNCF, and was its first (seed) project. It has sustained a fast pace of growth of contributors, contributing organizations, and users, and now operates at massive scale. The project's governance and community-management practices continue to evolve and mature as the project grows, but the Kubernetes Steering Committee (https://github.com/kubernetes/steering) unanimously believes that Kubernetes fulfills all the CNCF incubating and graduation criteria:

- Used successfully in production by at least three independent end users of sufficient scale and quality: https://kubernetes.io/case-studies
- Have a healthy number of committers: Kubernetes is so large, with thousands of contributors and nearly 100 repositories, that we had to develop our own mechanism to manage approval permissions. We have hundreds of approvers, listed in more than 4000 OWNERS files across the project (https://github.com/search?utf8=%E2%9C%93&q=org%3Akubernetes+filename%3AOWNERS&type=Code)
- Demonstrate a substantial ongoing flow of commits and merged contributions: Devstats shows that we have thousands of PRs merged per month (https://k8s.devstats.cncf.io/)

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/91

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

--
Chris Aniszczyk (@cra) | +1-512-961-6719
Re: [VOTE] Kubernetes moving to graduation

Michael Hausenblas <mhausenb@...>
 

+1 non-binding

Cheers,
Michael

--
Michael Hausenblas, Developer Advocate
OpenShift by Red Hat
Mobile: +353 86 0215164 | Twitter: @mhausenblas
http://openshift.com | http://mhausenblas.info

-----Original Message-----
From: Chris Aniszczyk <caniszczyk@linuxfoundation.org>
Reply: Chris Aniszczyk <caniszczyk@linuxfoundation.org>
Date: 26 February 2018 at 16:52:44
To: cncf-toc@lists.cncf.io <cncf-toc@lists.cncf.io>
Subject:  [cncf-toc] [VOTE] Kubernetes moving to graduation

After last week's TOC call, we decided to start moving forward with
graduation reviews. Kubernetes was the project that motivated the creation
of the CNCF, and was its first (seed) project. It has sustained a fast pace
of growth of contributors, contributing organizations, and users, and now
operates at massive scale. The project's governance and
community-management practices continue to evolve and mature as the project
grows, but the Kubernetes Steering Committee (
https://github.com/kubernetes/steering) unanimously believes that
Kubernetes fulfills all the CNCF incubating and graduation criteria:

- Used successfully in production by at least three independent end users
of sufficient scale and quality: https://kubernetes.io/case-studies
- Have a healthy number of committers: Kubernetes is so large, with
thousands of contributors and nearly 100 repositories, that we had to
develop our own mechanism to manage approval permissions. We have hundreds
of approvers, listed in more than 4000 OWNERS files across the project (
https://github.com/search?utf8=%E2%9C%93&q=org%3Akubernetes+filename%3AOWNERS&type=Code
)
- Demonstrate a substantial ongoing flow of commits and merged
contributions: Devstats shows that we have thousands of PRs merged per
month (https://k8s.devstats.cncf.io/)

Please vote (+1/0/-1) by replying to this thread; the full proposal located
here: https://github.com/cncf/toc/pull/91

Remember that the TOC has binding votes only, but we do appreciate
non-binding votes from the community as a sign of support!

--
Chris Aniszczyk (@cra) | +1-512-961-6719
Re: [VOTE] Kubernetes moving to graduation

Richard Li
 

+1 non-binding

On Mon, Feb 26, 2018 at 12:28 PM, Louis Fourie <louis.fourie@...> wrote:

+1 non-binding

 

From: cncf-toc@... [mailto:cncf-toc@...] On Behalf Of Chris Aniszczyk
Sent: Monday, February 26, 2018 8:53 AM
To: cncf-toc@...
Subject: [cncf-toc] [VOTE] Kubernetes moving to graduation

 

After last week's TOC call, we decided to start moving forward with graduation reviews. Kubernetes was the project that motivated the creation of the CNCF, and was its first (seed) project. It has sustained a fast pace of growth of contributors, contributing organizations, and users, and now operates at massive scale. The project's governance and community-management practices continue to evolve and mature as the project grows, but the Kubernetes Steering Committee (https://github.com/kubernetes/steering) unanimously believes that Kubernetes fulfills all the CNCF incubating and graduation criteria:

 

- Used successfully in production by at least three independent end users of sufficient scale and quality: https://kubernetes.io/case-studies
- Have a healthy number of committers: Kubernetes is so large, with thousands of contributors and nearly 100 repositories, that we had to develop our own mechanism to manage approval permissions. We have hundreds of approvers, listed in more than 4000 OWNERS files across the project (https://github.com/search?utf8=%E2%9C%93&q=org%3Akubernetes+filename%3AOWNERS&type=Code)

- Demonstrate a substantial ongoing flow of commits and merged contributions: Devstats shows that we have thousands of PRs merged per month (https://k8s.devstats.cncf.io/)

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/91

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

 

--

Chris Aniszczyk (@cra) | +1-512-961-6719
Re: [VOTE] Kubernetes moving to graduation

Louis Fourie <louis.fourie@...>
 

+1 non-binding

 

From: cncf-toc@... [mailto:cncf-toc@...] On Behalf Of Chris Aniszczyk
Sent: Monday, February 26, 2018 8:53 AM
To: cncf-toc@...
Subject: [cncf-toc] [VOTE] Kubernetes moving to graduation

 

After last week's TOC call, we decided to start moving forward with graduation reviews. Kubernetes was the project that motivated the creation of the CNCF, and was its first (seed) project. It has sustained a fast pace of growth of contributors, contributing organizations, and users, and now operates at massive scale. The project's governance and community-management practices continue to evolve and mature as the project grows, but the Kubernetes Steering Committee (https://github.com/kubernetes/steering) unanimously believes that Kubernetes fulfills all the CNCF incubating and graduation criteria:

 

- Used successfully in production by at least three independent end users of sufficient scale and quality: https://kubernetes.io/case-studies
- Have a healthy number of committers: Kubernetes is so large, with thousands of contributors and nearly 100 repositories, that we had to develop our own mechanism to manage approval permissions. We have hundreds of approvers, listed in more than 4000 OWNERS files across the project (https://github.com/search?utf8=%E2%9C%93&q=org%3Akubernetes+filename%3AOWNERS&type=Code)

- Demonstrate a substantial ongoing flow of commits and merged contributions: Devstats shows that we have thousands of PRs merged per month (https://k8s.devstats.cncf.io/)

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/91

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

 

--

Chris Aniszczyk (@cra) | +1-512-961-6719
Re: [VOTE] Kubernetes moving to graduation

Mark Peek
 

+1 non-binding

 

From: <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@...>
Date: Monday, February 26, 2018 at 8:52 AM
To: "cncf-toc@..." <cncf-toc@...>
Subject: [cncf-toc] [VOTE] Kubernetes moving to graduation

 

After last week's TOC call, we decided to start moving forward with graduation reviews. Kubernetes was the project that motivated the creation of the CNCF, and was its first (seed) project. It has sustained a fast pace of growth of contributors, contributing organizations, and users, and now operates at massive scale. The project's governance and community-management practices continue to evolve and mature as the project grows, but the Kubernetes Steering Committee (https://github.com/kubernetes/steering) unanimously believes that Kubernetes fulfills all the CNCF incubating and graduation criteria:

 

- Used successfully in production by at least three independent end users of sufficient scale and quality: https://kubernetes.io/case-studies
- Have a healthy number of committers: Kubernetes is so large, with thousands of contributors and nearly 100 repositories, that we had to develop our own mechanism to manage approval permissions. We have hundreds of approvers, listed in more than 4000 OWNERS files across the project (https://github.com/search?utf8=%E2%9C%93&q=org%3Akubernetes+filename%3AOWNERS&type=Code)

- Demonstrate a substantial ongoing flow of commits and merged contributions: Devstats shows that we have thousands of PRs merged per month (https://k8s.devstats.cncf.io/)

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/91

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

 

--

Chris Aniszczyk (@cra) | +1-512-961-6719
Re: [VOTE] Kubernetes moving to graduation

Justin Cormack
 

+1 (non binding)

On Mon, Feb 26, 2018 at 4:52 PM, Chris Aniszczyk <caniszczyk@...> wrote:
After last week's TOC call, we decided to start moving forward with graduation reviews. Kubernetes was the project that motivated the creation of the CNCF, and was its first (seed) project. It has sustained a fast pace of growth of contributors, contributing organizations, and users, and now operates at massive scale. The project's governance and community-management practices continue to evolve and mature as the project grows, but the Kubernetes Steering Committee (https://github.com/kubernetes/steering) unanimously believes that Kubernetes fulfills all the CNCF incubating and graduation criteria:

- Used successfully in production by at least three independent end users of sufficient scale and quality: https://kubernetes.io/case-studies
- Have a healthy number of committers: Kubernetes is so large, with thousands of contributors and nearly 100 repositories, that we had to develop our own mechanism to manage approval permissions. We have hundreds of approvers, listed in more than 4000 OWNERS files across the project (https://github.com/search?utf8=%E2%9C%93&q=org%3Akubernetes+filename%3AOWNERS&type=Code)
- Demonstrate a substantial ongoing flow of commits and merged contributions: Devstats shows that we have thousands of PRs merged per month (https://k8s.devstats.cncf.io/)

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/91

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

--
Chris Aniszczyk (@cra) | +1-512-961-6719
Re: [VOTE] Kubernetes moving to graduation

Daniel Bryant
 

+1 (non-binding)

On Mon, Feb 26, 2018 at 11:52 AM, Chris Aniszczyk <caniszczyk@...> wrote:
After last week's TOC call, we decided to start moving forward with graduation reviews. Kubernetes was the project that motivated the creation of the CNCF, and was its first (seed) project. It has sustained a fast pace of growth of contributors, contributing organizations, and users, and now operates at massive scale. The project's governance and community-management practices continue to evolve and mature as the project grows, but the Kubernetes Steering Committee (https://github.com/kubernetes/steering) unanimously believes that Kubernetes fulfills all the CNCF incubating and graduation criteria:

- Used successfully in production by at least three independent end users of sufficient scale and quality: https://kubernetes.io/case-studies
- Have a healthy number of committers: Kubernetes is so large, with thousands of contributors and nearly 100 repositories, that we had to develop our own mechanism to manage approval permissions. We have hundreds of approvers, listed in more than 4000 OWNERS files across the project (https://github.com/search?utf8=%E2%9C%93&q=org%3Akubernetes+filename%3AOWNERS&type=Code)
- Demonstrate a substantial ongoing flow of commits and merged contributions: Devstats shows that we have thousands of PRs merged per month (https://k8s.devstats.cncf.io/)

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/91

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

--
Chris Aniszczyk (@cra) | +1-512-961-6719
Re: [VOTE] Kubernetes moving to graduation

Christian Posta
 

+1 non binding 


On Mon, Feb 26, 2018 at 11:52 AM Chris Aniszczyk <caniszczyk@...> wrote:
After last week's TOC call, we decided to start moving forward with graduation reviews. Kubernetes was the project that motivated the creation of the CNCF, and was its first (seed) project. It has sustained a fast pace of growth of contributors, contributing organizations, and users, and now operates at massive scale. The project's governance and community-management practices continue to evolve and mature as the project grows, but the Kubernetes Steering Committee (https://github.com/kubernetes/steering) unanimously believes that Kubernetes fulfills all the CNCF incubating and graduation criteria:

- Used successfully in production by at least three independent end users of sufficient scale and quality: https://kubernetes.io/case-studies
- Have a healthy number of committers: Kubernetes is so large, with thousands of contributors and nearly 100 repositories, that we had to develop our own mechanism to manage approval permissions. We have hundreds of approvers, listed in more than 4000 OWNERS files across the project (https://github.com/search?utf8=%E2%9C%93&q=org%3Akubernetes+filename%3AOWNERS&type=Code)
- Demonstrate a substantial ongoing flow of commits and merged contributions: Devstats shows that we have thousands of PRs merged per month (https://k8s.devstats.cncf.io/)

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/91

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

--
Chris Aniszczyk (@cra) | +1-512-961-6719

--
Christian Posta
twitter: @christianposta
Re: [VOTE] Kubernetes moving to graduation

Lachlan Evenson
 

+1 non-binding
Re: [VOTE] Kubernetes moving to graduation

Jonathan Boulle <jon@...>
 

+1 binding

On 26 February 2018 at 17:52, Chris Aniszczyk <caniszczyk@...> wrote:
After last week's TOC call, we decided to start moving forward with graduation reviews. Kubernetes was the project that motivated the creation of the CNCF, and was its first (seed) project. It has sustained a fast pace of growth of contributors, contributing organizations, and users, and now operates at massive scale. The project's governance and community-management practices continue to evolve and mature as the project grows, but the Kubernetes Steering Committee (https://github.com/kubernetes/steering) unanimously believes that Kubernetes fulfills all the CNCF incubating and graduation criteria:

- Used successfully in production by at least three independent end users of sufficient scale and quality: https://kubernetes.io/case-studies
- Have a healthy number of committers: Kubernetes is so large, with thousands of contributors and nearly 100 repositories, that we had to develop our own mechanism to manage approval permissions. We have hundreds of approvers, listed in more than 4000 OWNERS files across the project (https://github.com/search?utf8=%E2%9C%93&q=org%3Akubernetes+filename%3AOWNERS&type=Code)
- Demonstrate a substantial ongoing flow of commits and merged contributions: Devstats shows that we have thousands of PRs merged per month (https://k8s.devstats.cncf.io/)

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/91

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

--
Chris Aniszczyk (@cra) | +1-512-961-6719
Re: [VOTE] Kubernetes moving to graduation

Ken Owens
 

+1 Binding

On Mon, Feb 26, 2018 at 10:52 AM, Chris Aniszczyk <caniszczyk@...> wrote:
After last week's TOC call, we decided to start moving forward with graduation reviews. Kubernetes was the project that motivated the creation of the CNCF, and was its first (seed) project. It has sustained a fast pace of growth of contributors, contributing organizations, and users, and now operates at massive scale. The project's governance and community-management practices continue to evolve and mature as the project grows, but the Kubernetes Steering Committee (https://github.com/kubernetes/steering) unanimously believes that Kubernetes fulfills all the CNCF incubating and graduation criteria:

- Used successfully in production by at least three independent end users of sufficient scale and quality: https://kubernetes.io/case-studies
- Have a healthy number of committers: Kubernetes is so large, with thousands of contributors and nearly 100 repositories, that we had to develop our own mechanism to manage approval permissions. We have hundreds of approvers, listed in more than 4000 OWNERS files across the project (https://github.com/search?utf8=%E2%9C%93&q=org%3Akubernetes+filename%3AOWNERS&type=Code)
- Demonstrate a substantial ongoing flow of commits and merged contributions: Devstats shows that we have thousands of PRs merged per month (https://k8s.devstats.cncf.io/)

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/91

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

--
Chris Aniszczyk (@cra) | +1-512-961-6719
Re: [VOTE] Kubernetes moving to graduation

Alex Chircop
 

+1 non-binding

 

From: <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@...>
Date: Monday, 26 February 2018 at 16:52
To: "cncf-toc@..." <cncf-toc@...>
Subject: [cncf-toc] [VOTE] Kubernetes moving to graduation

 

After last week's TOC call, we decided to start moving forward with graduation reviews. Kubernetes was the project that motivated the creation of the CNCF, and was its first (seed) project. It has sustained a fast pace of growth of contributors, contributing organizations, and users, and now operates at massive scale. The project's governance and community-management practices continue to evolve and mature as the project grows, but the Kubernetes Steering Committee (https://github.com/kubernetes/steering) unanimously believes that Kubernetes fulfills all the CNCF incubating and graduation criteria:

 

- Used successfully in production by at least three independent end users of sufficient scale and quality: https://kubernetes.io/case-studies
- Have a healthy number of committers: Kubernetes is so large, with thousands of contributors and nearly 100 repositories, that we had to develop our own mechanism to manage approval permissions. We have hundreds of approvers, listed in more than 4000 OWNERS files across the project (https://github.com/search?utf8=%E2%9C%93&q=org%3Akubernetes+filename%3AOWNERS&type=Code)

- Demonstrate a substantial ongoing flow of commits and merged contributions: Devstats shows that we have thousands of PRs merged per month (https://k8s.devstats.cncf.io/)

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/91

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

 

--

Chris Aniszczyk (@cra) | +1-512-961-6719
Re: [VOTE] Kubernetes moving to graduation

Justin Garrison <justinleegarrison@...>
 

​+1 non-binding​



--
Justin Garrison
justingarrison.com

On Mon, Feb 26, 2018 at 9:05 AM, Rob Lalonde <rlalonde@...> wrote:
+1 non-binding

On Feb 26, 2018, at 11:52 AM, Chris Aniszczyk <caniszczyk@linuxfoundation.org> wrote:

After last week's TOC call, we decided to start moving forward with graduation reviews. Kubernetes was the project that motivated the creation of the CNCF, and was its first (seed) project. It has sustained a fast pace of growth of contributors, contributing organizations, and users, and now operates at massive scale. The project's governance and community-management practices continue to evolve and mature as the project grows, but the Kubernetes Steering Committee (https://github.com/kubernetes/steering) unanimously believes that Kubernetes fulfills all the CNCF incubating and graduation criteria:

- Used successfully in production by at least three independent end users of sufficient scale and quality: https://kubernetes.io/case-studies
- Have a healthy number of committers: Kubernetes is so large, with thousands of contributors and nearly 100 repositories, that we had to develop our own mechanism to manage approval permissions. We have hundreds of approvers, listed in more than 4000 OWNERS files across the project (https://github.com/search?utf8=%E2%9C%93&q=org%3Akubernetes+filename%3AOWNERS&type=Code)
- Demonstrate a substantial ongoing flow of commits and merged contributions: Devstats shows that we have thousands of PRs merged per month (https://k8s.devstats.cncf.io/)

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/91

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

--
Chris Aniszczyk (@cra) | +1-512-961-6719
Re: Final RFC: CNCF Sandbox

alexis richardson
 

Chris

I think the right way to reflect our governance values is in the
Graduation criteria and Incubation criteria. Therefore the Sandbox
doc could add a statement of the form "The CNCF will help projects
adopt good principles of governance in preparation for future
Incubation, if the project leads so desire".

alexis


On Mon, Feb 26, 2018 at 5:00 PM, Chris Aniszczyk
<caniszczyk@linuxfoundation.org> wrote:
Thanks for your feedback here Stephen, a big tenant of CNCF has always been
that projects are self governing and can bring their own governance as long
as it's transparent + fair (we call this minimum viable governance):
https://github.com/cncf/toc/blob/master/PRINCIPLES.md#projects-are-self-governing

Over time (especially these days), I find that successful projects evolve
towards more open governance (we've even had this happen in CNCF with
containerd moving from bdfl to committee model) due to community/adopter
pressure.

I'll look at seeing how I can codify your point in the sandbox proposal that
open governance is important and the earlier the better. I'm looking to
finalize the proposal the next day or so before calling for a vote.

Thanks!

On Wed, Feb 21, 2018 at 5:48 AM, Stephen Watt <swatt@redhat.com> wrote:

Thanks Chris. Firstly, I think the way the sandbox doc is articulated in
the doc is great. However, I imagine sandbox projects should be aware of the
TLP graduation criteria and trying to steer their ship towards those goals,
and as such, it prompted a broader meta question that I thought might be
better suited to the TOC list, rather than a comment on the doc.

When I look at the graduation criteria from Sandbox -> Incubation ->
Graduated, I see in the criteria for "graduated" that one needs to have
committers from at least 2 organizations. This hints at a desire for CNCF
projects to have some measure of open governance but stops short of calling
it out directly. Why not do so?

I believe I've heard it stated by the TOC before that you don't want to
preclude healthy important projects where the vast majority of committers
happen to be from one organization. I agree. However, I don't think that is
at odds with an open governance model. For example, you could have an open
governance model where it just so happened to be, that the participation in
the project is all from a single company, however, because of the governance
model, should contributors join later from other companies, they would have
a path to equal influence in the project decision making and contributions
being committed.

Why am I bringing this up? An ounce of prevention is worth a pound of
cure. I believe the advantage of calling open gov out explicitly in the
graduation criteria helps avoid a future scenario where a CNCF project is
governed by a cabal largely dominated by one company, that has a token
committer from outside, that actively or passively ignores contributions
from the community (the incentives can differ from project to project). I
suspect you have come across github projects with open source licenses that
behave this way. Projects like this are bad for the project's and
foundation's brand. The ASF had to deal with this issue a number of times
with popular projects in their Big Data stack. It was painful, but they were
able to deal with it because they are prescriptive about how ASF projects
are to be governed. I realize this can be a slippery slope because the next
step would be to become prescriptive about what type(s) of open governance
model CNCF projects would deem acceptable. However, perhaps something worth
anticipating and discussing.

Regards
Steve Watt

On Tue, Feb 20, 2018 at 12:06 PM, Chris Aniszczyk
<caniszczyk@linuxfoundation.org> wrote:

At today's TOC call there was consensus on the CNCF Sandbox proposal is
close to being ready for a formal vote. We will leave the document open for
any community comments for a week and do a formal vote next week:
https://goo.gl/gZhBjY

After the vote and assuming the sandbox is approved, we will resume
voting on new project proposals (existing inception proposals will be
slotted for the sandbox).

Thanks.

--
Chris Aniszczyk (@cra) | +1-512-961-6719


--
Chris Aniszczyk (@cra) | +1-512-961-6719
Re: [VOTE] Kubernetes moving to graduation

Rob Lalonde
 

+1 non-binding

On Feb 26, 2018, at 11:52 AM, Chris Aniszczyk <caniszczyk@...> wrote:

After last week's TOC call, we decided to start moving forward with graduation reviews. Kubernetes was the project that motivated the creation of the CNCF, and was its first (seed) project. It has sustained a fast pace of growth of contributors, contributing organizations, and users, and now operates at massive scale. The project's governance and community-management practices continue to evolve and mature as the project grows, but the Kubernetes Steering Committee (https://github.com/kubernetes/steering) unanimously believes that Kubernetes fulfills all the CNCF incubating and graduation criteria:

- Used successfully in production by at least three independent end users of sufficient scale and quality: https://kubernetes.io/case-studies
- Have a healthy number of committers: Kubernetes is so large, with thousands of contributors and nearly 100 repositories, that we had to develop our own mechanism to manage approval permissions. We have hundreds of approvers, listed in more than 4000 OWNERS files across the project (https://github.com/search?utf8=%E2%9C%93&q=org%3Akubernetes+filename%3AOWNERS&type=Code)
- Demonstrate a substantial ongoing flow of commits and merged contributions: Devstats shows that we have thousands of PRs merged per month (https://k8s.devstats.cncf.io/)

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/91

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

--
Chris Aniszczyk (@cra) | +1-512-961-6719
Re: [VOTE] Kubernetes moving to graduation

Santosa, Andy
 

+1

Regards,
-Andy

From: <cncf-toc@...> on behalf of John Belamaric <jbelamaric@...>
Date: Monday, February 26, 2018 at 8:59 AM
To: "cncf-toc@..." <cncf-toc@...>
Cc: "cncf-toc@..." <cncf-toc@...>
Subject: Re: [cncf-toc] [VOTE] Kubernetes moving to graduation

+1 non-binding

On Feb 26, 2018, at 11:52 AM, Chris Aniszczyk <caniszczyk@...> wrote:

After last week's TOC call, we decided to start moving forward with graduation reviews. Kubernetes was the project that motivated the creation of the CNCF, and was its first (seed) project. It has sustained a fast pace of growth of contributors, contributing organizations, and users, and now operates at massive scale. The project's governance and community-management practices continue to evolve and mature as the project grows, but the Kubernetes Steering Committee (https://github.com/kubernetes/steering) unanimously believes that Kubernetes fulfills all the CNCF incubating and graduation criteria:

- Used successfully in production by at least three independent end users of sufficient scale and quality: https://kubernetes.io/case-studies
- Have a healthy number of committers: Kubernetes is so large, with thousands of contributors and nearly 100 repositories, that we had to develop our own mechanism to manage approval permissions. We have hundreds of approvers, listed in more than 4000 OWNERS files across the project (https://github.com/search?utf8=%E2%9C%93&q=org%3Akubernetes+filename%3AOWNERS&type=Code)
- Demonstrate a substantial ongoing flow of commits and merged contributions: Devstats shows that we have thousands of PRs merged per month (https://k8s.devstats.cncf.io/)

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/91

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

--
Chris Aniszczyk (@cra) | +1-512-961-6719
5241 - 5260 of 6990