Re: [VOTE] Kubernetes moving to graduation
Ruben Orduz <ruben@...>
+1 non-binding
On Mon, Feb 26, 2018 at 11:55 AM, Ihor Dvoretskyi <ihor.dvoretskyi@...> wrote:
|
|||||
|
|||||
Re: [VOTE] Kubernetes moving to graduation
Deepak Vij <deepak.vij@...>
+1 (non-binding).
From: cncf-toc@... [mailto:cncf-toc@...]
On Behalf Of Chris Aniszczyk
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 - 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/)
-- Chris Aniszczyk (@cra) | +1-512-961-6719
|
|||||
|
|||||
Re: [VOTE] Kubernetes moving to graduation
Ihor Dvoretskyi
+1 non-binding.
On Mon, Feb 26, 2018 at 8:52 AM, Chris Aniszczyk <caniszczyk@...> wrote:
|
|||||
|
|||||
Re: [VOTE] Kubernetes moving to graduation
Doug Davis <dug@...>
+1 non-binding 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
Camille Fournier
+1 binding
On Feb 26, 2018 11:52 AM, "Chris Aniszczyk" <caniszczyk@...> wrote:
|
|||||
|
|||||
Re: [VOTE] Kubernetes moving to graduation
alexis richardson
+1 binding
toggle quoted messageShow quoted text
On Mon, 26 Feb 2018, 16:52 Chris Aniszczyk, <caniszczyk@...> wrote:
|
|||||
|
|||||
[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
|
|||||
|
|||||
[RESULT] CoreDNS moving to incubation (PASSED)
CoreDNS is now an incubating project at CNCF, here are the results: - Alexis Richardson: https://lists.cncf.io/g/cncf-toc/message/1692 - Brian Grant: https://lists.cncf.io/g/cncf-toc/message/1703 - Ben Hindman: https://lists.cncf.io/g/cncf-toc/message/1706 - Ken Owens: https://lists.cncf.io/g/cncf-toc/message/1708 - Jon Boulle: https://lists.cncf.io/g/cncf-toc/message/1711 - Sam Lambert: https://lists.cncf.io/g/cncf-toc/message/1713 +1 non-binding community votes: - Lee Calcote: https://lists.cncf.io/g/cncf-toc/message/1688 - Richard Hartmann: https://lists.cncf.io/g/cncf-toc/message/1689 - Eduardo Silva: https://lists.cncf.io/g/cncf-toc/message/1690 - John Belamaric: https://lists.cncf.io/g/cncf-toc/message/1691 - Doug Davis: https://lists.cncf.io/g/cncf-toc/message/1693 - Christopher Liljenstolpe: https://lists.cncf.io/g/cncf-toc/message/1695 - Ihor Dvoretskyi: https://lists.cncf.io/g/cncf-toc/message/1696 - Mark Interrante: https://lists.cncf.io/g/cncf-toc/message/1698 - Justin Garrison: https://lists.cncf.io/g/cncf-toc/message/1699 - Quinton Hoole: https://lists.cncf.io/g/cncf-toc/message/1701 - Bassam Tabbara: https://lists.cncf.io/g/cncf-toc/message/1704 - Kapil Thangavelu: https://lists.cncf.io/g/cncf-toc/message/1707- Nick Chase: https://lists.cncf.io/g/cncf-toc/message/1714 - Mark Coleman: https://lists.cncf.io/g/cncf-toc/message/1715 - Mark Peek: https://lists.cncf.io/g/cncf-toc/message/1716 - Daniel Bryant: https://lists.cncf.io/g/cncf-toc/message/1717
|
|||||
|
|||||
Re: [VOTE] CoreDNS moving to incubation
+1 (non-binding)
On Tue, Feb 20, 2018 at 11:57 AM, Chris Aniszczyk <caniszczyk@...> wrote:
|
|||||
|
|||||
Re: [VOTE] CoreDNS moving to incubation
Mark Peek
+1 non-binding
From: <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@...>
At today's TOC call, we had the CoreDNS team perform their annual inception project review and request to move to the incubation level. You can see the project statistics here: https://coredns.devstats.cncf.io and they meet the incubation criteria requirements:
- Used successfully in production by at least three independent end users of sufficient scale and quality: seven listed in the ADOPTERS file, others may be discussed privately
Please vote (+1/0/-1) by replying to this thread; the full incubation proposal located here:
https://github.com/cncf/toc/pull/66
-- Chris Aniszczyk (@cra) | +1-512-961-6719
|
|||||
|
|||||
Re: [VOTE] CoreDNS moving to incubation
Mark Coleman <mark@...>
+ 1 non-binding
On Wed, Feb 21, 2018 at 2:30 PM Nick Chase <nchase@...> wrote: +1 non-binding --
|
|||||
|
|||||
Re: [VOTE] CoreDNS moving to incubation
Nick Chase
+1 non-binding
toggle quoted messageShow quoted text
On Wednesday, February 21, 2018, Sam Lambert <samlambert@...> wrote:
|
|||||
|
|||||
Re: [VOTE] CoreDNS moving to incubation
Sam Lambert <samlambert@...>
+1 binding
On Tue, Feb 20, 2018 at 10:55 PM, Jonathan Boulle <jon@...> wrote:
|
|||||
|
|||||
Re: Final RFC: CNCF Sandbox
Stephen Watt
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@...> wrote:
|
|||||
|
|||||
Re: [VOTE] CoreDNS moving to incubation
Jonathan Boulle <jon@...>
+1 binding Am 20.02.2018 23:53 schrieb "Ken Owens" <kenchristineowens@...>:
|
|||||
|
|||||
making final changes to the Sandbox doc
alexis richardson
Hi all
This is a further reminder to speak up on the list or in the Sandbox doc, if you have concerns about the content, tone or emphasis. I'd like to attempt any redrafting of passages early next week, with Chris, based on your feedback. https://docs.google.com/document/d/1MkuVT7Q6itn9ESW-iyqIXsEqTPBrStXlvzESg94933A/edit?ts=5a7c49ae Eg: There was discussion on the call yesterday about how we encourage projects into the Sandbox as the preferred path, and ensuring that it is perceived as such. This needs clarifying (I think Brian took the action to have a go). a
|
|||||
|
|||||
nomination
Erin Boyd
Hello TOC, I am wishing to be nominated for the open seat on the TOC board. Alexis and Chris asked I reach out to the board to request one of you nominate me.
|
|||||
|
|||||
Re: [VOTE] CoreDNS moving to incubation
Ken Owens
+1 Binding
On Tue, Feb 20, 2018, 10:57 AM Chris Aniszczyk <caniszczyk@...> wrote:
|
|||||
|
|||||
Re: [VOTE] CoreDNS moving to incubation
Thangavelu, Kapil
+1 non-binding From: cncf-toc@... <cncf-toc@...> on behalf of Benjamin Hindman <benh@...>
Sent: Tuesday, February 20, 2018 4:09:35 PM To: cncf-toc@... Cc: cncf-toc@... Subject: Re: [cncf-toc] [VOTE] CoreDNS moving to incubation +1 binding
On Tue, Feb 20, 2018 at 8:57 AM Chris Aniszczyk <caniszczyk@...> wrote:
Benjamin Hindman
Founder of Mesosphere and Co-Creator of Apache Mesos
Follow us on Twitter: @mesosphere
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] CoreDNS moving to incubation
Benjamin Hindman
+1 binding
On Tue, Feb 20, 2018 at 8:57 AM Chris Aniszczyk <caniszczyk@...> wrote:
--
Benjamin Hindman Founder of Mesosphere and Co-Creator of Apache Mesos Follow us on Twitter: @mesosphere
|
|||||
|