Re: [VOTE] Kubernetes moving to graduation
Doug Davis <dug@...>
STSM | IBM Open Source, Cloud Architecture & Technology
(919) 254-6905 | IBM 444-6905 | dug@...
The more I'm around some people, the more I like my dog
"Chris Aniszczyk" ---02/26/2018 08:52:47 AM---After last week's TOC call, we decided to start moving forward with graduation reviews. Kubernetes w
From: "Chris Aniszczyk" <caniszczyk@...>
Date: 02/26/2018 08:52 AM
Subject: [cncf-toc] [VOTE] Kubernetes moving to graduation
Sent by: cncf-toc@...
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