From d40eeba8810290803d585b559a4defdfe75ff281 Mon Sep 17 00:00:00 2001 From: fturib Date: Tue, 13 Nov 2018 12:37:06 -0500 Subject: [PATCH 1/4] - application for "Graduated" project hosted by CNCF --- reviews/graduation-coredns.md | 51 +++++++++++++++++++++++++++++++++++ 1 file changed, 51 insertions(+) create mode 100644 reviews/graduation-coredns.md diff --git a/reviews/graduation-coredns.md b/reviews/graduation-coredns.md new file mode 100644 index 000000000..47162831f --- /dev/null +++ b/reviews/graduation-coredns.md @@ -0,0 +1,51 @@ + +# CoreDNS Graduation Application + +CoreDNS joined CNCF in March 2017 as inception project and graduated as incubation project on February 2018 + +It has grown significantly over time either as a DNS Server available in Cloud Native environment, either as a key component of Kubernetes project: +- In Fall 2017, CoreDNS was proposed to become a DNS Discovery Service for Kubernetes. +- First version as alpha feature was released in v1.09 of Kubernetes - Dec 2017 +- CoreDNS is considered the “default” DNS Discovery Service for Kubernetes v1.13 - to be released in Dec 2018 + +The following application links to the required information to become a graduated project. + +## CoreDNS fulfills all the incubating and graduation criteria: + +### Document that it is being used successfully in production by at least three independent end users which, in the TOC’s judgement, are of adequate quality and scope. + +* Bose, Infoblox, Zalando, Tradeshift, Yandex, AdGuard are knows users of CoreDNS. More adopters are listed [here](https://github.com/coredns/coredns/blob/master/ADOPTERS.md). + +* On Kubernetes side, from [a recent CNCF Survey](https://docs.google.com/forms/d/e/1FAIpQLSehsvd0n2HKnPEifukNHej4gMBrXe2saJOmxAmPq34dTGMWKA/viewanalytics), 50% deployments of cluster are using CoreDNS as the DNS discovery service + + +### Have a healthy number of committers. A committer is defined as someone with the commit bit; i.e., someone who can accept contributions to some or all of the project. + +CoreDNS has currenlty 16 maintainers. +They are listed as ‘approvers’ on our [OWNER document](https://github.com/coredns/coredns/blob/master/OWNERS) + +### Demonstrate a substantial ongoing flow of commits and merged contributions. + +More than [100+ contributors](https://github.com/coredns/coredns/graphs/contributors) and 12 [releases](https://coredns.devstats.cncf.io/d/3/community-stats?orgId=1&var-period=d&var-repo_name=CoreDNS) since incubation graduation + +### Have committers from at least two organizations. + +We currently have [16 maintainers](https://github.com/coredns/coredns/blob/master/OWNERS). +Most of them are contributing on their spare time and each considered at its own organization, +4 maintainers are working for 2 distinct companies - Infoblox, Google - that support CoreDNS. + +### Have achieved and maintained a Core Infrastructure Initiative Best Practices Badge. + +https://bestpractices.coreinfrastructure.org/en/projects/1250 + +### Adopt the CNCF Code of Conduct. + +https://github.com/coredns/coredns/blob/master/CODE-OF-CONDUCT.md + +### Explicitly define a project governance and committer process. This preferably is laid out in a GOVERNANCE.md file and references an OWNERS.md file showing the current and emeritus committers. + +https://github.com/coredns/coredns/blob/master/GOVERNANCE.md + +### Have a public list of project adopters for at least the primary repo (e.g., ADOPTERS.md or logos on the project website). + +https://github.com/coredns/coredns/blob/master/ADOPTERS.md From dde68aae93d0c762c8ae6d49856e7b32bd1a1814 Mon Sep 17 00:00:00 2001 From: fturib Date: Tue, 13 Nov 2018 16:59:27 -0500 Subject: [PATCH 2/4] - add an important users --- reviews/graduation-coredns.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/reviews/graduation-coredns.md b/reviews/graduation-coredns.md index 47162831f..e1924e58f 100644 --- a/reviews/graduation-coredns.md +++ b/reviews/graduation-coredns.md @@ -14,7 +14,7 @@ The following application links to the required information to become a graduate ### Document that it is being used successfully in production by at least three independent end users which, in the TOC’s judgement, are of adequate quality and scope. -* Bose, Infoblox, Zalando, Tradeshift, Yandex, AdGuard are knows users of CoreDNS. More adopters are listed [here](https://github.com/coredns/coredns/blob/master/ADOPTERS.md). +* Bose, SoundCloud, Infoblox, Zalando, Tradeshift, Yandex, AdGuard are knows users of CoreDNS. More adopters are listed [here](https://github.com/coredns/coredns/blob/master/ADOPTERS.md). * On Kubernetes side, from [a recent CNCF Survey](https://docs.google.com/forms/d/e/1FAIpQLSehsvd0n2HKnPEifukNHej4gMBrXe2saJOmxAmPq34dTGMWKA/viewanalytics), 50% deployments of cluster are using CoreDNS as the DNS discovery service From 0fc3dc1184578c16682dee930157913859894f95 Mon Sep 17 00:00:00 2001 From: fturib Date: Sun, 18 Nov 2018 17:03:59 -0500 Subject: [PATCH 3/4] - nits found at review --- reviews/graduation-coredns.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/reviews/graduation-coredns.md b/reviews/graduation-coredns.md index e1924e58f..eda2f7c0f 100644 --- a/reviews/graduation-coredns.md +++ b/reviews/graduation-coredns.md @@ -5,7 +5,7 @@ CoreDNS joined CNCF in March 2017 as inception project and graduated as incubati It has grown significantly over time either as a DNS Server available in Cloud Native environment, either as a key component of Kubernetes project: - In Fall 2017, CoreDNS was proposed to become a DNS Discovery Service for Kubernetes. -- First version as alpha feature was released in v1.09 of Kubernetes - Dec 2017 +- First version as alpha feature was released in v1.9 of Kubernetes - Dec 2017 - CoreDNS is considered the “default” DNS Discovery Service for Kubernetes v1.13 - to be released in Dec 2018 The following application links to the required information to become a graduated project. @@ -21,7 +21,7 @@ The following application links to the required information to become a graduate ### Have a healthy number of committers. A committer is defined as someone with the commit bit; i.e., someone who can accept contributions to some or all of the project. -CoreDNS has currenlty 16 maintainers. +CoreDNS currently has 16 maintainers. They are listed as ‘approvers’ on our [OWNER document](https://github.com/coredns/coredns/blob/master/OWNERS) ### Demonstrate a substantial ongoing flow of commits and merged contributions. From 7b2f04b25e387d74fc115d007b807275902118f8 Mon Sep 17 00:00:00 2001 From: fturib Date: Mon, 26 Nov 2018 20:13:23 -0500 Subject: [PATCH 4/4] - tune the text according to Jonathan's comments --- reviews/graduation-coredns.md | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/reviews/graduation-coredns.md b/reviews/graduation-coredns.md index eda2f7c0f..3e49a2b3f 100644 --- a/reviews/graduation-coredns.md +++ b/reviews/graduation-coredns.md @@ -3,7 +3,7 @@ CoreDNS joined CNCF in March 2017 as inception project and graduated as incubation project on February 2018 -It has grown significantly over time either as a DNS Server available in Cloud Native environment, either as a key component of Kubernetes project: +It has grown significantly over time in maturity and user base, both as a DNS Server available in Cloud Native environment and as a key component of Kubernetes project: - In Fall 2017, CoreDNS was proposed to become a DNS Discovery Service for Kubernetes. - First version as alpha feature was released in v1.9 of Kubernetes - Dec 2017 - CoreDNS is considered the “default” DNS Discovery Service for Kubernetes v1.13 - to be released in Dec 2018 @@ -14,7 +14,14 @@ The following application links to the required information to become a graduate ### Document that it is being used successfully in production by at least three independent end users which, in the TOC’s judgement, are of adequate quality and scope. -* Bose, SoundCloud, Infoblox, Zalando, Tradeshift, Yandex, AdGuard are knows users of CoreDNS. More adopters are listed [here](https://github.com/coredns/coredns/blob/master/ADOPTERS.md). +* **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](https://github.com/coredns/coredns/blob/master/ADOPTERS.md)** use CoreDNS for their production's Kubernetes Cluster + * On Kubernetes side, from [a recent CNCF Survey](https://docs.google.com/forms/d/e/1FAIpQLSehsvd0n2HKnPEifukNHej4gMBrXe2saJOmxAmPq34dTGMWKA/viewanalytics), 50% deployments of cluster are using CoreDNS as the DNS discovery service @@ -31,8 +38,7 @@ More than [100+ contributors](https://github.com/coredns/coredns/graphs/contribu ### Have committers from at least two organizations. We currently have [16 maintainers](https://github.com/coredns/coredns/blob/master/OWNERS). -Most of them are contributing on their spare time and each considered at its own organization, -4 maintainers are working for 2 distinct companies - Infoblox, Google - that support CoreDNS. +Most of them are contributing in their spare time; but, considering organizations, 4 maintainers are working for 2 distinct companies ### Have achieved and maintained a Core Infrastructure Initiative Best Practices Badge.