Date   

Re: [VOTE] CoreDNS moving to graduation

Camille Fournier
 

+1 binding

On Tue, Jan 15, 2019 at 12:47 PM Chris Aniszczyk <caniszczyk@...> wrote:
CoreDNS has requested to move to the graduation maturity level:
https://github.com/cncf/toc/pull/172

The CoreDNS community was one of earlier projects that joined CNCF at the inception/sandbox level on March 2017 (sponsored by Jon Boulle) and moved to the incubation maturity level on Feb 2018. As of Kubernetes v1.13, CoreDNS is the default DNS server (https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/) and the community went under an external security audit last year sponsored by CNCF: https://coredns.io/2018/03/15/cure53-security-assessment/ 

The CoreDNS community believes it has fulfilled all the graduation criteria:

- Document that it is being used successfully in production by at least three independent end users:

* SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to handle hundreds of thousands DNS service discovery requests per second.
* Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as for Kubernetes cluster DNS.
* Admiral uses CoreDNS to handle geographic DNS requests for our public-facing microservices.
* Qunar uses CoreDNS for service discovery of its GPU machine learning cloud with TensorFlow and Kubernetes.
* Tradeshift uses CoreDNS to look up company identifiers across multiple shards/regions/zones
* AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public AdGuard DNS servers.
* Bose, Zalando, Yandex, Hellofresh, Sodimac, Kismia and many others use CoreDNS for their production's Kubernetes Cluster: https://github.com/coredns/coredns/blob/master/ADOPTERS.md

- Have a healthy number of committers and at least two from different organizations: 16+ maintainers: Google, Infoblox, Independent(s) - More than 100+ contributors - https://github.com/coredns/coredns/blob/master/OWNERS and https://github.com/coredns/coredns/graphs/contributors

- Demonstrate a substantial ongoing flow of commits and merged contributions: 10+ releases since becoming an incubating project and average about 150 PRs merged / quarter: https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

- Have achieved a CII badge: https://bestpractices.coreinfrastructure.org/projects/1250

- Define a governance model: https://github.com/coredns/coredns/blob/master/GOVERNANCE.md

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

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: RFC: Project Health Dashboard Updates

Richard Hartmann
 

This is developing nicely, thanks!

Two nitpicks:
* "Project health" vs "Projects health" is bad naming; how about
naming the latter "CNCF project overview" or something like that?
* Looking at the overview, I am unclear what entity IPB is in the
committer highscores and there's no way to click through to the data
to take a better look

On Tue, Jan 15, 2019 at 5:27 PM Chris Aniszczyk
<caniszczyk@...> wrote:

Here's the latest project health dashboard after initial rounds of feedbacks:
https://all.devstats.cncf.io/d/53/projects-health?orgId=1

If you want to filter by project, you can do that via here:
https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=Prometheus
https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

Thanks and look forward to your feedback!

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


Re: [VOTE] CoreDNS moving to graduation

heng du
 

+1

徐翔轩 <eleven.xu@...> 于2019年1月17日周四 下午12:22写道:

+1 non-binding

在 2019年1月17日,12:14,Roman Chepurnyi via Lists.Cncf.Io <roman.chepurnyi=thredup.com@...> 写道:

+1 non-binding 

Roman

On Tue, Jan 15, 2019 at 9:47 AM Chris Aniszczyk <caniszczyk@...> wrote:
CoreDNS has requested to move to the graduation maturity level:
https://github.com/cncf/toc/pull/172

The CoreDNS community was one of earlier projects that joined CNCF at the inception/sandbox level on March 2017 (sponsored by Jon Boulle) and moved to the incubation maturity level on Feb 2018. As of Kubernetes v1.13, CoreDNS is the default DNS server (https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/) and the community went under an external security audit last year sponsored by CNCF: https://coredns.io/2018/03/15/cure53-security-assessment/ 

The CoreDNS community believes it has fulfilled all the graduation criteria:

- Document that it is being used successfully in production by at least three independent end users:

* SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to handle hundreds of thousands DNS service discovery requests per second.
* Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as for Kubernetes cluster DNS.
* Admiral uses CoreDNS to handle geographic DNS requests for our public-facing microservices.
* Qunar uses CoreDNS for service discovery of its GPU machine learning cloud with TensorFlow and Kubernetes.
* Tradeshift uses CoreDNS to look up company identifiers across multiple shards/regions/zones
* AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public AdGuard DNS servers.
* Bose, Zalando, Yandex, Hellofresh, Sodimac, Kismia and many others use CoreDNS for their production's Kubernetes Cluster: https://github.com/coredns/coredns/blob/master/ADOPTERS.md

- Have a healthy number of committers and at least two from different organizations: 16+ maintainers: Google, Infoblox, Independent(s) - More than 100+ contributors - https://github.com/coredns/coredns/blob/master/OWNERSand https://github.com/coredns/coredns/graphs/contributors

- Demonstrate a substantial ongoing flow of commits and merged contributions: 10+ releases since becoming an incubating project and average about 150 PRs merged / quarter: https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

- Have achieved a CII badge: https://bestpractices.coreinfrastructure.org/projects/1250

- Define a governance model: https://github.com/coredns/coredns/blob/master/GOVERNANCE.md

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

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




-- 
Thanks,
Roman 


Re: [VOTE] CoreDNS moving to graduation

徐翔轩 <eleven.xu@...>
 

+1 non-binding

在 2019年1月17日,12:14,Roman Chepurnyi via Lists.Cncf.Io <roman.chepurnyi=thredup.com@...> 写道:

+1 non-binding 

Roman

On Tue, Jan 15, 2019 at 9:47 AM Chris Aniszczyk <caniszczyk@...> wrote:
CoreDNS has requested to move to the graduation maturity level:
https://github.com/cncf/toc/pull/172

The CoreDNS community was one of earlier projects that joined CNCF at the inception/sandbox level on March 2017 (sponsored by Jon Boulle) and moved to the incubation maturity level on Feb 2018. As of Kubernetes v1.13, CoreDNS is the default DNS server (https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/) and the community went under an external security audit last year sponsored by CNCF: https://coredns.io/2018/03/15/cure53-security-assessment/ 

The CoreDNS community believes it has fulfilled all the graduation criteria:

- Document that it is being used successfully in production by at least three independent end users:

* SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to handle hundreds of thousands DNS service discovery requests per second.
* Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as for Kubernetes cluster DNS.
* Admiral uses CoreDNS to handle geographic DNS requests for our public-facing microservices.
* Qunar uses CoreDNS for service discovery of its GPU machine learning cloud with TensorFlow and Kubernetes.
* Tradeshift uses CoreDNS to look up company identifiers across multiple shards/regions/zones
* AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public AdGuard DNS servers.
* Bose, Zalando, Yandex, Hellofresh, Sodimac, Kismia and many others use CoreDNS for their production's Kubernetes Cluster: https://github.com/coredns/coredns/blob/master/ADOPTERS.md

- Have a healthy number of committers and at least two from different organizations: 16+ maintainers: Google, Infoblox, Independent(s) - More than 100+ contributors - https://github.com/coredns/coredns/blob/master/OWNERSand https://github.com/coredns/coredns/graphs/contributors

- Demonstrate a substantial ongoing flow of commits and merged contributions: 10+ releases since becoming an incubating project and average about 150 PRs merged / quarter: https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

- Have achieved a CII badge: https://bestpractices.coreinfrastructure.org/projects/1250

- Define a governance model: https://github.com/coredns/coredns/blob/master/GOVERNANCE.md

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

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




-- 
Thanks,
Roman 


Re: [VOTE] CoreDNS moving to graduation

Roman Chepurnyi
 

+1 non-binding 

Roman

On Tue, Jan 15, 2019 at 9:47 AM Chris Aniszczyk <caniszczyk@...> wrote:
CoreDNS has requested to move to the graduation maturity level:
https://github.com/cncf/toc/pull/172

The CoreDNS community was one of earlier projects that joined CNCF at the inception/sandbox level on March 2017 (sponsored by Jon Boulle) and moved to the incubation maturity level on Feb 2018. As of Kubernetes v1.13, CoreDNS is the default DNS server (https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/) and the community went under an external security audit last year sponsored by CNCF: https://coredns.io/2018/03/15/cure53-security-assessment/ 

The CoreDNS community believes it has fulfilled all the graduation criteria:

- Document that it is being used successfully in production by at least three independent end users:

* SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to handle hundreds of thousands DNS service discovery requests per second.
* Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as for Kubernetes cluster DNS.
* Admiral uses CoreDNS to handle geographic DNS requests for our public-facing microservices.
* Qunar uses CoreDNS for service discovery of its GPU machine learning cloud with TensorFlow and Kubernetes.
* Tradeshift uses CoreDNS to look up company identifiers across multiple shards/regions/zones
* AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public AdGuard DNS servers.
* Bose, Zalando, Yandex, Hellofresh, Sodimac, Kismia and many others use CoreDNS for their production's Kubernetes Cluster: https://github.com/coredns/coredns/blob/master/ADOPTERS.md

- Have a healthy number of committers and at least two from different organizations: 16+ maintainers: Google, Infoblox, Independent(s) - More than 100+ contributors - https://github.com/coredns/coredns/blob/master/OWNERS and https://github.com/coredns/coredns/graphs/contributors

- Demonstrate a substantial ongoing flow of commits and merged contributions: 10+ releases since becoming an incubating project and average about 150 PRs merged / quarter: https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

- Have achieved a CII badge: https://bestpractices.coreinfrastructure.org/projects/1250

- Define a governance model: https://github.com/coredns/coredns/blob/master/GOVERNANCE.md

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

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



--
Thanks,
Roman 


Re: [VOTE] CoreDNS moving to graduation

GolfenGuo
 

+1 non-binding

 

 

Thanks

--

郭峰  Golfen Guo

+86 18016427071

Shanghai DaoCloud Network Technology Co,. Ltd

#Your Containers. Delivered!#

 

发件人: <cncf-toc@...> 代表 Chris Aniszczyk <caniszczyk@...>
日期: 2019116 星期三 上午1:47
收件人: CNCF TOC <cncf-toc@...>
主题: [cncf-toc] [VOTE] CoreDNS moving to graduation

 

CoreDNS has requested to move to the graduation maturity level:
https://github.com/cncf/toc/pull/172

 

The CoreDNS community was one of earlier projects that joined CNCF at the inception/sandbox level on March 2017 (sponsored by Jon Boulle) and moved to the incubation maturity level on Feb 2018. As of Kubernetes v1.13, CoreDNS is the default DNS server (https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/) and the community went under an external security audit last year sponsored by CNCF: https://coredns.io/2018/03/15/cure53-security-assessment/ 

The CoreDNS community believes it has fulfilled all the graduation criteria:

- Document that it is being used successfully in production by at least three independent end users:

 

* SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to handle hundreds of thousands DNS service discovery requests per second.
* Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as for Kubernetes cluster DNS.
* Admiral uses CoreDNS to handle geographic DNS requests for our public-facing microservices.

* Qunar uses CoreDNS for service discovery of its GPU machine learning cloud with TensorFlow and Kubernetes.
* Tradeshift uses CoreDNS to look up company identifiers across multiple shards/regions/zones
* AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public AdGuard DNS servers.
* Bose, Zalando, Yandex, Hellofresh, Sodimac, Kismia and many others use CoreDNS for their production's Kubernetes Cluster: https://github.com/coredns/coredns/blob/master/ADOPTERS.md


- Have a healthy number of committers and at least two from different organizations: 16+ maintainers: Google, Infoblox, Independent(s) - More than 100+ contributors - https://github.com/coredns/coredns/blob/master/OWNERS and https://github.com/coredns/coredns/graphs/contributors


- Demonstrate a substantial ongoing flow of commits and merged contributions: 10+ releases since becoming an incubating project and average about 150 PRs merged / quarter: https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

- Have achieved a CII badge: https://bestpractices.coreinfrastructure.org/projects/1250

- Define a governance model: https://github.com/coredns/coredns/blob/master/GOVERNANCE.md

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

 

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


本邮件及附件含 DaoCloud 保密信息,仅限发送给上面地址中列出的个人或群组,禁止任何其他人以任何形式使用本邮件中的信息。若误收本邮件,请务必通知发送人并直接删去,不得使用、传播或复制本邮件。


Re: [VOTE] CoreDNS moving to graduation

Payne, Michael H
 

+1 non-binding

 

From: cncf-toc@... [mailto:cncf-toc@...] On Behalf Of Chris Aniszczyk
Sent: Tuesday, January 15, 2019 9:47 AM
To: CNCF TOC
Subject: [cncf-toc] [VOTE] CoreDNS moving to graduation

 

CoreDNS has requested to move to the graduation maturity level:
https://github.com/cncf/toc/pull/172

 

The CoreDNS community was one of earlier projects that joined CNCF at the inception/sandbox level on March 2017 (sponsored by Jon Boulle) and moved to the incubation maturity level on Feb 2018. As of Kubernetes v1.13, CoreDNS is the default DNS server (https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/) and the community went under an external security audit last year sponsored by CNCF: https://coredns.io/2018/03/15/cure53-security-assessment/ 

The CoreDNS community believes it has fulfilled all the graduation criteria:

- Document that it is being used successfully in production by at least three independent end users:

 

* SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to handle hundreds of thousands DNS service discovery requests per second.
* Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as for Kubernetes cluster DNS.
* Admiral uses CoreDNS to handle geographic DNS requests for our public-facing microservices.

* Qunar uses CoreDNS for service discovery of its GPU machine learning cloud with TensorFlow and Kubernetes.
* Tradeshift uses CoreDNS to look up company identifiers across multiple shards/regions/zones
* AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public AdGuard DNS servers.
* Bose, Zalando, Yandex, Hellofresh, Sodimac, Kismia and many others use CoreDNS for their production's Kubernetes Cluster: https://github.com/coredns/coredns/blob/master/ADOPTERS.md


- Have a healthy number of committers and at least two from different organizations: 16+ maintainers: Google, Infoblox, Independent(s) - More than 100+ contributors - https://github.com/coredns/coredns/blob/master/OWNERS and https://github.com/coredns/coredns/graphs/contributors


- Demonstrate a substantial ongoing flow of commits and merged contributions: 10+ releases since becoming an incubating project and average about 150 PRs merged / quarter: https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

- Have achieved a CII badge: https://bestpractices.coreinfrastructure.org/projects/1250

- Define a governance model: https://github.com/coredns/coredns/blob/master/GOVERNANCE.md

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

 

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

This message is confidential and subject to terms at: https://www.jpmorgan.com/emaildisclaimer including on confidentiality, legal privilege, viruses and monitoring of electronic messages. If you are not the intended recipient, please delete this message and notify the sender immediately. Any unauthorized use is strictly prohibited.


Re: [VOTE] CoreDNS moving to graduation

Phil Estes
 

+1 non-binding

Phil Estes
IBM Cloud

Chris Aniszczyk wrote on 1/15/19 12:47 PM:

CoreDNS has requested to move to the graduation maturity level:
https://github.com/cncf/toc/pull/172

The CoreDNS community was one of earlier projects that joined CNCF at the inception/sandbox level on March 2017 (sponsored by Jon Boulle) and moved to the incubation maturity level on Feb 2018. As of Kubernetes v1.13, CoreDNS is the default DNS server (https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/) and the community went under an external security audit last year sponsored by CNCF: https://coredns.io/2018/03/15/cure53-security-assessment/ 

The CoreDNS community believes it has fulfilled all the graduation criteria:

- Document that it is being used successfully in production by at least three independent end users:

* SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to handle hundreds of thousands DNS service discovery requests per second.
* Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as for Kubernetes cluster DNS.
* Admiral uses CoreDNS to handle geographic DNS requests for our public-facing microservices.
* Qunar uses CoreDNS for service discovery of its GPU machine learning cloud with TensorFlow and Kubernetes.
* Tradeshift uses CoreDNS to look up company identifiers across multiple shards/regions/zones
* AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public AdGuard DNS servers.
* Bose, Zalando, Yandex, Hellofresh, Sodimac, Kismia and many others use CoreDNS for their production's Kubernetes Cluster: https://github.com/coredns/coredns/blob/master/ADOPTERS.md

- Have a healthy number of committers and at least two from different organizations: 16+ maintainers: Google, Infoblox, Independent(s) - More than 100+ contributors - https://github.com/coredns/coredns/blob/master/OWNERS and https://github.com/coredns/coredns/graphs/contributors

- Demonstrate a substantial ongoing flow of commits and merged contributions: 10+ releases since becoming an incubating project and average about 150 PRs merged / quarter: https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

- Have achieved a CII badge: https://bestpractices.coreinfrastructure.org/projects/1250

- Define a governance model: https://github.com/coredns/coredns/blob/master/GOVERNANCE.md

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

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] CoreDNS moving to graduation

Jimmy Song <jimmysong@...>
 

+1 Non-binding
---------------------------------------
Best Regards.
 
Jimmy Song(宋净超)

Developer Advocate
Ant Financial
CNCF Ambassador
Co-founder of ServiceMesher community
 
WeChat: jimmysong






On Jan 16, 2019, at 7:42 AM, Jonathan Boulle <jon@...> wrote:

+1 binding 

Am Di., 15. Jan. 2019, 18:47 hat Chris Aniszczyk <caniszczyk@...> geschrieben:
CoreDNS has requested to move to the graduation maturity level:
https://github.com/cncf/toc/pull/172

The CoreDNS community was one of earlier projects that joined CNCF at the inception/sandbox level on March 2017 (sponsored by Jon Boulle) and moved to the incubation maturity level on Feb 2018. As of Kubernetes v1.13, CoreDNS is the default DNS server (https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/) and the community went under an external security audit last year sponsored by CNCF: https://coredns.io/2018/03/15/cure53-security-assessment/ 

The CoreDNS community believes it has fulfilled all the graduation criteria:

- Document that it is being used successfully in production by at least three independent end users:

* SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to handle hundreds of thousands DNS service discovery requests per second.
* Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as for Kubernetes cluster DNS.
* Admiral uses CoreDNS to handle geographic DNS requests for our public-facing microservices.
* Qunar uses CoreDNS for service discovery of its GPU machine learning cloud with TensorFlow and Kubernetes.
* Tradeshift uses CoreDNS to look up company identifiers across multiple shards/regions/zones
* AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public AdGuard DNS servers.
* Bose, Zalando, Yandex, Hellofresh, Sodimac, Kismia and many others use CoreDNS for their production's Kubernetes Cluster: https://github.com/coredns/coredns/blob/master/ADOPTERS.md

- Have a healthy number of committers and at least two from different organizations: 16+ maintainers: Google, Infoblox, Independent(s) - More than 100+ contributors - https://github.com/coredns/coredns/blob/master/OWNERSand https://github.com/coredns/coredns/graphs/contributors

- Demonstrate a substantial ongoing flow of commits and merged contributions: 10+ releases since becoming an incubating project and average about 150 PRs merged / quarter: https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

- Have achieved a CII badge: https://bestpractices.coreinfrastructure.org/projects/1250

- Define a governance model: https://github.com/coredns/coredns/blob/master/GOVERNANCE.md

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

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: RFC: Project Health Dashboard Updates

alexis richardson
 

Hi all

Please DO speak up on the topic of "what can CNCF do and where can it
spend money to track and improve project health, as transparently as
possible".

a



On Tue, Jan 15, 2019 at 4:27 PM Chris Aniszczyk
<caniszczyk@...> wrote:

Here's the latest project health dashboard after initial rounds of feedbacks:
https://all.devstats.cncf.io/d/53/projects-health?orgId=1

If you want to filter by project, you can do that via here:
https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=Prometheus
https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

Thanks and look forward to your feedback!

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


This Friday, Jan 18 deadline for CFP to KubeCon + CloudNativeCon Barcelona

Dan Kohn <dan@...>
 

End of day this Friday, Jan 18, is the deadline for the call for proposals for KubeCon + CloudNativeCon Barcelona. 


Re: [VOTE] CoreDNS moving to graduation

Jonathan Boulle <jon@...>
 

+1 binding 

Am Di., 15. Jan. 2019, 18:47 hat Chris Aniszczyk <caniszczyk@...> geschrieben:

CoreDNS has requested to move to the graduation maturity level:
https://github.com/cncf/toc/pull/172

The CoreDNS community was one of earlier projects that joined CNCF at the inception/sandbox level on March 2017 (sponsored by Jon Boulle) and moved to the incubation maturity level on Feb 2018. As of Kubernetes v1.13, CoreDNS is the default DNS server (https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/) and the community went under an external security audit last year sponsored by CNCF: https://coredns.io/2018/03/15/cure53-security-assessment/ 

The CoreDNS community believes it has fulfilled all the graduation criteria:

- Document that it is being used successfully in production by at least three independent end users:

* SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to handle hundreds of thousands DNS service discovery requests per second.
* Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as for Kubernetes cluster DNS.
* Admiral uses CoreDNS to handle geographic DNS requests for our public-facing microservices.
* Qunar uses CoreDNS for service discovery of its GPU machine learning cloud with TensorFlow and Kubernetes.
* Tradeshift uses CoreDNS to look up company identifiers across multiple shards/regions/zones
* AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public AdGuard DNS servers.
* Bose, Zalando, Yandex, Hellofresh, Sodimac, Kismia and many others use CoreDNS for their production's Kubernetes Cluster: https://github.com/coredns/coredns/blob/master/ADOPTERS.md

- Have a healthy number of committers and at least two from different organizations: 16+ maintainers: Google, Infoblox, Independent(s) - More than 100+ contributors - https://github.com/coredns/coredns/blob/master/OWNERS and https://github.com/coredns/coredns/graphs/contributors

- Demonstrate a substantial ongoing flow of commits and merged contributions: 10+ releases since becoming an incubating project and average about 150 PRs merged / quarter: https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

- Have achieved a CII badge: https://bestpractices.coreinfrastructure.org/projects/1250

- Define a governance model: https://github.com/coredns/coredns/blob/master/GOVERNANCE.md

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

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] CoreDNS 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@...>
Reply: Chris Aniszczyk <caniszczyk@...>
Date: 15 January 2019 at 17:47:20
To: CNCF TOC <cncf-toc@...>
Subject:  [cncf-toc] [VOTE] CoreDNS moving to graduation

CoreDNS has requested to move to the graduation maturity level:
https://github.com/cncf/toc/pull/172

The CoreDNS community was one of earlier projects that joined CNCF at the
inception/sandbox level on March 2017 (sponsored by Jon Boulle) and moved
to the incubation maturity level on Feb 2018. As of Kubernetes v1.13,
CoreDNS is the default DNS server (
https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/)
and the community went under an external security audit last year sponsored
by CNCF: https://coredns.io/2018/03/15/cure53-security-assessment/

The CoreDNS community believes it has fulfilled all the graduation criteria:

- Document that it is being used successfully in production by at least
three independent end users:

* SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to
handle hundreds of thousands DNS service discovery requests per second.
* Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as
for Kubernetes cluster DNS.
* Admiral uses CoreDNS to handle geographic DNS requests for our
public-facing microservices.
* Qunar uses CoreDNS for service discovery of its GPU machine learning
cloud with TensorFlow and Kubernetes.
* Tradeshift uses CoreDNS to look up company identifiers across multiple
shards/regions/zones
* AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public
AdGuard DNS servers.
* Bose, Zalando, Yandex, Hellofresh, Sodimac, Kismia and many others use
CoreDNS for their production's Kubernetes Cluster:
https://github.com/coredns/coredns/blob/master/ADOPTERS.md

- Have a healthy number of committers and at least two from different
organizations: 16+ maintainers: Google, Infoblox, Independent(s) - More
than 100+ contributors -
https://github.com/coredns/coredns/blob/master/OWNERS and
https://github.com/coredns/coredns/graphs/contributors

- Demonstrate a substantial ongoing flow of commits and merged
contributions: 10+ releases since becoming an incubating project and
average about 150 PRs merged / quarter:
https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

- Have achieved a CII badge:
https://bestpractices.coreinfrastructure.org/projects/1250

- Define a governance model:
https://github.com/coredns/coredns/blob/master/GOVERNANCE.md

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

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] CoreDNS moving to graduation

Quinton Hoole
 

+1 binding

Q

From: <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@...>
Date: Tuesday, January 15, 2019 at 09:47
To: CNCF TOC <cncf-toc@...>
Subject: [cncf-toc] [VOTE] CoreDNS moving to graduation

CoreDNS has requested to move to the graduation maturity level:
https://github.com/cncf/toc/pull/172

The CoreDNS community was one of earlier projects that joined CNCF at the inception/sandbox level on March 2017 (sponsored by Jon Boulle) and moved to the incubation maturity level on Feb 2018. As of Kubernetes v1.13, CoreDNS is the default DNS server (https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/) and the community went under an external security audit last year sponsored by CNCF: https://coredns.io/2018/03/15/cure53-security-assessment/ 

The CoreDNS community believes it has fulfilled all the graduation criteria:

- Document that it is being used successfully in production by at least three independent end users:

* SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to handle hundreds of thousands DNS service discovery requests per second.
* Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as for Kubernetes cluster DNS.
* Admiral uses CoreDNS to handle geographic DNS requests for our public-facing microservices.
* Qunar uses CoreDNS for service discovery of its GPU machine learning cloud with TensorFlow and Kubernetes.
* Tradeshift uses CoreDNS to look up company identifiers across multiple shards/regions/zones
* AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public AdGuard DNS servers.
* Bose, Zalando, Yandex, Hellofresh, Sodimac, Kismia and many others use CoreDNS for their production's Kubernetes Cluster: https://github.com/coredns/coredns/blob/master/ADOPTERS.md

- Have a healthy number of committers and at least two from different organizations: 16+ maintainers: Google, Infoblox, Independent(s) - More than 100+ contributors - https://github.com/coredns/coredns/blob/master/OWNERS and https://github.com/coredns/coredns/graphs/contributors

- Demonstrate a substantial ongoing flow of commits and merged contributions: 10+ releases since becoming an incubating project and average about 150 PRs merged / quarter: https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

- Have achieved a CII badge: https://bestpractices.coreinfrastructure.org/projects/1250

- Define a governance model: https://github.com/coredns/coredns/blob/master/GOVERNANCE.md

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

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] CoreDNS moving to graduation

Justin Cappos
 

+1 nb


Re: [VOTE] CoreDNS moving to graduation

Justin Garrison <justinleegarrison@...>
 

+1 nb


--
Justin Garrison
justingarrison.com


On Tue, Jan 15, 2019 at 11:11 AM Vlad Voskoboynikov <v.voskoboynikov@...> wrote:
+1 non-binding

Vlad Voskoboynikov
Exon LV


Re: [VOTE] CoreDNS moving to graduation

v.voskoboynikov@...
 

+1 non-binding

Vlad Voskoboynikov
Exon LV


Re: [VOTE] CoreDNS moving to graduation

Julien SENON
 

+1 nb

On 15 Jan 2019, at 7:40 PM, Roger Klorese <roger.klorese@...> wrote:

+1 (non-binding)


Roger B.A. Klorese
Senior Product Manager
SUSE
705 5th Ave S
Suite 1000
Seattle WA 98104
(P)+1 206.217.7432
(M)+1 425.444.5493
roger.klorese@...
Schedule a meeting: https://doodle.com/RogerKlorese
GPG Key: D567 F186 A6AE D244 067E  95E4 E67D 019F 0670 D9CC


From: cncf-toc@... <cncf-toc@...> on behalf of alexis richardson <alexis@...>
Sent: Tuesday, January 15, 2019 10:36:45 AM
To: Richard Hartmann
Cc: Chris Aniszczyk; CNCF TOC
Subject: Re: [cncf-toc] [VOTE] CoreDNS moving to graduation
 
+1 binding



On Tue, 15 Jan 2019, 18:33 Richard Hartmann, <richih@...> wrote:
+1 NB

On Tue, Jan 15, 2019 at 6:47 PM Chris Aniszczyk
<caniszczyk@...> wrote:
>
> CoreDNS has requested to move to the graduation maturity level:
> https://github.com/cncf/toc/pull/172
>
> The CoreDNS community was one of earlier projects that joined CNCF at the inception/sandbox level on March 2017 (sponsored by Jon Boulle) and moved to the incubation maturity level on Feb 2018. As of Kubernetes v1.13, CoreDNS is the default DNS server (https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/) and the community went under an external security audit last year sponsored by CNCF: https://coredns.io/2018/03/15/cure53-security-assessment/
>
> The CoreDNS community believes it has fulfilled all the graduation criteria:
>
> - Document that it is being used successfully in production by at least three independent end users:
>
> * SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to handle hundreds of thousands DNS service discovery requests per second.
> * Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as for Kubernetes cluster DNS.
> * Admiral uses CoreDNS to handle geographic DNS requests for our public-facing microservices.
> * Qunar uses CoreDNS for service discovery of its GPU machine learning cloud with TensorFlow and Kubernetes.
> * Tradeshift uses CoreDNS to look up company identifiers across multiple shards/regions/zones
> * AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public AdGuard DNS servers.
> * Bose, Zalando, Yandex, Hellofresh, Sodimac, Kismia and many others use CoreDNS for their production's Kubernetes Cluster: https://github.com/coredns/coredns/blob/master/ADOPTERS.md
>
> - Have a healthy number of committers and at least two from different organizations: 16+ maintainers: Google, Infoblox, Independent(s) - More than 100+ contributors - https://github.com/coredns/coredns/blob/master/OWNERS and https://github.com/coredns/coredns/graphs/contributors
>
> - Demonstrate a substantial ongoing flow of commits and merged contributions: 10+ releases since becoming an incubating project and average about 150 PRs merged / quarter: https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS
>
> - Have achieved a CII badge: https://bestpractices.coreinfrastructure.org/projects/1250
>
> - Define a governance model: https://github.com/coredns/coredns/blob/master/GOVERNANCE.md
>
> Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/172
>
> 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] CoreDNS moving to graduation

Roger Klorese <roger.klorese@...>
 

+1 (non-binding)


Roger B.A. Klorese
Senior Product Manager
SUSE
705 5th Ave S
Suite 1000
Seattle WA 98104
(P)+1 206.217.7432
(M)+1 425.444.5493
roger.klorese@...
Schedule a meeting: https://doodle.com/RogerKlorese
GPG Key: D567 F186 A6AE D244 067E  95E4 E67D 019F 0670 D9CC


From: cncf-toc@... <cncf-toc@...> on behalf of alexis richardson <alexis@...>
Sent: Tuesday, January 15, 2019 10:36:45 AM
To: Richard Hartmann
Cc: Chris Aniszczyk; CNCF TOC
Subject: Re: [cncf-toc] [VOTE] CoreDNS moving to graduation
 
+1 binding



On Tue, 15 Jan 2019, 18:33 Richard Hartmann, <richih@...> wrote:

+1 NB

On Tue, Jan 15, 2019 at 6:47 PM Chris Aniszczyk
<caniszczyk@...> wrote:
>
> CoreDNS has requested to move to the graduation maturity level:
> https://github.com/cncf/toc/pull/172
>
> The CoreDNS community was one of earlier projects that joined CNCF at the inception/sandbox level on March 2017 (sponsored by Jon Boulle) and moved to the incubation maturity level on Feb 2018. As of Kubernetes v1.13, CoreDNS is the default DNS server (https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/) and the community went under an external security audit last year sponsored by CNCF: https://coredns.io/2018/03/15/cure53-security-assessment/
>
> The CoreDNS community believes it has fulfilled all the graduation criteria:
>
> - Document that it is being used successfully in production by at least three independent end users:
>
> * SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to handle hundreds of thousands DNS service discovery requests per second.
> * Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as for Kubernetes cluster DNS.
> * Admiral uses CoreDNS to handle geographic DNS requests for our public-facing microservices.
> * Qunar uses CoreDNS for service discovery of its GPU machine learning cloud with TensorFlow and Kubernetes.
> * Tradeshift uses CoreDNS to look up company identifiers across multiple shards/regions/zones
> * AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public AdGuard DNS servers.
> * Bose, Zalando, Yandex, Hellofresh, Sodimac, Kismia and many others use CoreDNS for their production's Kubernetes Cluster: https://github.com/coredns/coredns/blob/master/ADOPTERS.md
>
> - Have a healthy number of committers and at least two from different organizations: 16+ maintainers: Google, Infoblox, Independent(s) - More than 100+ contributors - https://github.com/coredns/coredns/blob/master/OWNERS and https://github.com/coredns/coredns/graphs/contributors
>
> - Demonstrate a substantial ongoing flow of commits and merged contributions: 10+ releases since becoming an incubating project and average about 150 PRs merged / quarter: https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS
>
> - Have achieved a CII badge: https://bestpractices.coreinfrastructure.org/projects/1250
>
> - Define a governance model: https://github.com/coredns/coredns/blob/master/GOVERNANCE.md
>
> Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/172
>
> 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] CoreDNS moving to graduation

Christian Jantz <chris@...>
 

+1 nb

Kind regards
Christian `Chris` Jantz


AWS Certified Solutions Architect - ProfessionalAWS Certified DevOps Engineer - ProfessionalAWS Certified Security - Specialty

I try to keep response times low but, that means being the most efficient. 
Taking this into account, please excuse my brevity of keeping messages to the point. 




On Tue, Jan 15 2019 at 7:54 PM, <nicolas.frankel@...> wrote:

+1 non-binding

Best regards,

Nicolas Fränkel

4921 - 4940 of 7717