|
Re: [VOTE] Envoy moving to graduation
Jonathan Boulle <jon@...>
toggle quoted messageShow quoted text
On Mon, 12 Nov 2018 at 18:15, Benjamin Hindman < benh@...> wrote: +1 binding
On Mon, Nov 12, 2018 at 8:37 AM Chris Aniszczyk < caniszczyk@...> wrote:
The Envoy 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: Known end users include: AirBnb, Alibaba, Apple, Booking.com, Cookpad, DigitalOcean, eBay, Google, GO-JEK, GroupOn, IBM, Lyft, Medium, Microsoft, Netflix, Pinterest, Salesforce, Snap, Square, Stripe, Tencent, Twilio, Two Sigma, Uber, Verizon, VMware, VSCO, Yahoo Japan, and Yelp. Many of these logos are listed here: https://www.envoyproxy.io (this is not an exclusive list and it's likely that other organizations are also Envoy users). Envoy is being used by numerous other companies, both large and small, to build higher layer products and services. This includes Covalent, Datawire, HashiCorp, Heptio, Istio (F5 Networks, Google, IBM, RedHat, Tetrate, Tigera, VMware, etc.), Solo.io, and many others.
- Have a healthy number of committers and at least two from different organizations: See the current list of Envoy owners, who are also committers: https://github.com/envoyproxy/envoy/blob/master/OWNERS.md Currently, we have 11 and are on the constant lookout for new maintainers to join our ranks.
Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/167Remember 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
--
Benjamin Hindman
Founder of Mesosphere and Co-Creator of Apache Mesos
|
|
|
Re: [VOTE] Envoy moving to graduation
Sonya Koptyev <sonya@...>
toggle quoted messageShow quoted text
On Mon, Nov 12, 2018 at 9:15 AM Benjamin Hindman < benh@...> wrote: +1 binding
On Mon, Nov 12, 2018 at 8:37 AM Chris Aniszczyk < caniszczyk@...> wrote:
The Envoy 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: Known end users include: AirBnb, Alibaba, Apple, Booking.com, Cookpad, DigitalOcean, eBay, Google, GO-JEK, GroupOn, IBM, Lyft, Medium, Microsoft, Netflix, Pinterest, Salesforce, Snap, Square, Stripe, Tencent, Twilio, Two Sigma, Uber, Verizon, VMware, VSCO, Yahoo Japan, and Yelp. Many of these logos are listed here: https://www.envoyproxy.io (this is not an exclusive list and it's likely that other organizations are also Envoy users). Envoy is being used by numerous other companies, both large and small, to build higher layer products and services. This includes Covalent, Datawire, HashiCorp, Heptio, Istio (F5 Networks, Google, IBM, RedHat, Tetrate, Tigera, VMware, etc.), Solo.io, and many others.
- Have a healthy number of committers and at least two from different organizations: See the current list of Envoy owners, who are also committers: https://github.com/envoyproxy/envoy/blob/master/OWNERS.md Currently, we have 11 and are on the constant lookout for new maintainers to join our ranks.
Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/167Remember 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
--
Benjamin Hindman
Founder of Mesosphere and Co-Creator of Apache Mesos
-- Thanks, Sonya
- Sonya Koptyev | Director of Evangelism | m: +1 425 505 0100
|
|
|
Re: [VOTE] Envoy moving to graduation
toggle quoted messageShow quoted text
On Mon, Nov 12, 2018 at 4:37 PM Chris Aniszczyk < caniszczyk@...> wrote:
The Envoy 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: Known end users include: AirBnb, Alibaba, Apple, Booking.com, Cookpad, DigitalOcean, eBay, Google, GO-JEK, GroupOn, IBM, Lyft, Medium, Microsoft, Netflix, Pinterest, Salesforce, Snap, Square, Stripe, Tencent, Twilio, Two Sigma, Uber, Verizon, VMware, VSCO, Yahoo Japan, and Yelp. Many of these logos are listed here: https://www.envoyproxy.io (this is not an exclusive list and it's likely that other organizations are also Envoy users). Envoy is being used by numerous other companies, both large and small, to build higher layer products and services. This includes Covalent, Datawire, HashiCorp, Heptio, Istio (F5 Networks, Google, IBM, RedHat, Tetrate, Tigera, VMware, etc.), Solo.io, and many others.
- Have a healthy number of committers and at least two from different organizations: See the current list of Envoy owners, who are also committers: https://github.com/envoyproxy/envoy/blob/master/OWNERS.md Currently, we have 11 and are on the constant lookout for new maintainers to join our ranks.
Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/167Remember 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] Envoy moving to graduation
toggle quoted messageShow quoted text
On Mon, Nov 12, 2018 at 8:37 AM Chris Aniszczyk < caniszczyk@...> wrote:
The Envoy 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: Known end users include: AirBnb, Alibaba, Apple, Booking.com, Cookpad, DigitalOcean, eBay, Google, GO-JEK, GroupOn, IBM, Lyft, Medium, Microsoft, Netflix, Pinterest, Salesforce, Snap, Square, Stripe, Tencent, Twilio, Two Sigma, Uber, Verizon, VMware, VSCO, Yahoo Japan, and Yelp. Many of these logos are listed here: https://www.envoyproxy.io (this is not an exclusive list and it's likely that other organizations are also Envoy users). Envoy is being used by numerous other companies, both large and small, to build higher layer products and services. This includes Covalent, Datawire, HashiCorp, Heptio, Istio (F5 Networks, Google, IBM, RedHat, Tetrate, Tigera, VMware, etc.), Solo.io, and many others.
- Have a healthy number of committers and at least two from different organizations: See the current list of Envoy owners, who are also committers: https://github.com/envoyproxy/envoy/blob/master/OWNERS.md Currently, we have 11 and are on the constant lookout for new maintainers to join our ranks.
Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/167Remember 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
-- Benjamin Hindman
Founder of Mesosphere and Co-Creator of Apache Mesos
|
|
|
Re: [VOTE] Envoy moving to graduation
Bassam Tabbara
toggle quoted messageShow quoted text
The Envoy 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: Known end users include: AirBnb, Alibaba, Apple, Booking.com, Cookpad, DigitalOcean, eBay, Google, GO-JEK, GroupOn, IBM, Lyft, Medium, Microsoft, Netflix, Pinterest, Salesforce, Snap, Square, Stripe, Tencent, Twilio, Two Sigma, Uber, Verizon, VMware, VSCO, Yahoo Japan, and Yelp. Many of these logos are listed here: https://www.envoyproxy.io (this is not an exclusive list and it's likely that other organizations are also Envoy users). Envoy is being used by numerous other companies, both large and small, to build higher layer products and services. This includes Covalent, Datawire, HashiCorp, Heptio, Istio (F5 Networks, Google, IBM, RedHat, Tetrate, Tigera, VMware, etc.), Solo.io, and many others.
- Have a healthy number of committers and at least two from different organizations: See the current list of Envoy owners, who are also committers: https://github.com/envoyproxy/envoy/blob/master/OWNERS.md Currently, we have 11 and are on the constant lookout for new maintainers to join our ranks.
Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/167Remember 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] Envoy moving to graduation
toggle quoted messageShow quoted text
On Nov 12, 2018, at 8:37 AM, Chris Aniszczyk < caniszczyk@...> wrote:
The Envoy 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: Known end users include: AirBnb, Alibaba, Apple, Booking.com, Cookpad, DigitalOcean, eBay, Google, GO-JEK, GroupOn, IBM, Lyft, Medium, Microsoft, Netflix, Pinterest, Salesforce, Snap, Square, Stripe, Tencent, Twilio, Two Sigma, Uber, Verizon, VMware, VSCO, Yahoo Japan, and Yelp. Many of these logos are listed here: https://www.envoyproxy.io (this is not an exclusive list and it's likely that other organizations are also Envoy users). Envoy is being used by numerous other companies, both large and small, to build higher layer products and services. This includes Covalent, Datawire, HashiCorp, Heptio, Istio (F5 Networks, Google, IBM, RedHat, Tetrate, Tigera, VMware, etc.), Solo.io, and many others.
- Have a healthy number of committers and at least two from different organizations: See the current list of Envoy owners, who are also committers: https://github.com/envoyproxy/envoy/blob/master/OWNERS.md Currently, we have 11 and are on the constant lookout for new maintainers to join our ranks.
Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/167Remember 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] Envoy moving to graduation
Justin Garrison <justinleegarrison@...>
toggle quoted messageShow quoted text
On Mon, Nov 12, 2018 at 8:52 AM Mark Peek < markpeek@...> wrote:
+1 non-binding
From: <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@...>
Date: Monday, November 12, 2018 at 8:37 AM
To: CNCF TOC <cncf-toc@...>
Subject: [cncf-toc] [VOTE] Envoy moving to graduation
The Envoy 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: Known end users include: AirBnb, Alibaba, Apple, Booking.com, Cookpad, DigitalOcean, eBay, Google, GO-JEK, GroupOn, IBM, Lyft, Medium,
Microsoft, Netflix, Pinterest, Salesforce, Snap, Square, Stripe, Tencent, Twilio, Two Sigma, Uber, Verizon, VMware, VSCO, Yahoo Japan, and Yelp. Many of these logos are listed here: https://www.envoyproxy.io
(this is not an exclusive list and it's likely that other organizations are also Envoy users). Envoy is being used by numerous other companies, both large and small, to build higher layer products and services. This includes Covalent, Datawire, HashiCorp,
Heptio, Istio (F5 Networks, Google, IBM, RedHat, Tetrate, Tigera, VMware, etc.), Solo.io, and many others.
- Have a healthy number of committers and at least two from different organizations: See the current list of Envoy owners, who are also committers: https://github.com/envoyproxy/envoy/blob/master/OWNERS.md
Currently, we have 11 and are on the constant lookout for new maintainers to join our ranks.
Please vote (+1/0/-1) by replying to this thread; the full proposal located here:
https://github.com/cncf/toc/pull/167
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] Envoy moving to graduation
+1 non-binding
From: <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@...>
Date: Monday, November 12, 2018 at 8:37 AM
To: CNCF TOC <cncf-toc@...>
Subject: [cncf-toc] [VOTE] Envoy moving to graduation
The Envoy 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: Known end users include: AirBnb, Alibaba, Apple, Booking.com, Cookpad, DigitalOcean, eBay, Google, GO-JEK, GroupOn, IBM, Lyft, Medium,
Microsoft, Netflix, Pinterest, Salesforce, Snap, Square, Stripe, Tencent, Twilio, Two Sigma, Uber, Verizon, VMware, VSCO, Yahoo Japan, and Yelp. Many of these logos are listed here: https://www.envoyproxy.io
(this is not an exclusive list and it's likely that other organizations are also Envoy users). Envoy is being used by numerous other companies, both large and small, to build higher layer products and services. This includes Covalent, Datawire, HashiCorp,
Heptio, Istio (F5 Networks, Google, IBM, RedHat, Tetrate, Tigera, VMware, etc.), Solo.io, and many others.
- Have a healthy number of committers and at least two from different organizations: See the current list of Envoy owners, who are also committers: https://github.com/envoyproxy/envoy/blob/master/OWNERS.md
Currently, we have 11 and are on the constant lookout for new maintainers to join our ranks.
Please vote (+1/0/-1) by replying to this thread; the full proposal located here:
https://github.com/cncf/toc/pull/167
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] Envoy moving to graduation
toggle quoted messageShow quoted text
On Mon, Nov 12, 2018 at 4:37 PM Chris Aniszczyk < caniszczyk@...> wrote:
The Envoy 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: Known end users include: AirBnb, Alibaba, Apple, Booking.com, Cookpad, DigitalOcean, eBay, Google, GO-JEK, GroupOn, IBM, Lyft, Medium, Microsoft, Netflix, Pinterest, Salesforce, Snap, Square, Stripe, Tencent, Twilio, Two Sigma, Uber, Verizon, VMware, VSCO, Yahoo Japan, and Yelp. Many of these logos are listed here: https://www.envoyproxy.io (this is not an exclusive list and it's likely that other organizations are also Envoy users). Envoy is being used by numerous other companies, both large and small, to build higher layer products and services. This includes Covalent, Datawire, HashiCorp, Heptio, Istio (F5 Networks, Google, IBM, RedHat, Tetrate, Tigera, VMware, etc.), Solo.io, and many others.
- Have a healthy number of committers and at least two from different organizations: See the current list of Envoy owners, who are also committers: https://github.com/envoyproxy/envoy/blob/master/OWNERS.md Currently, we have 11 and are on the constant lookout for new maintainers to join our ranks.
Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/167Remember 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] Envoy moving to graduation
toggle quoted messageShow quoted text
On Mon, Nov 12, 2018 at 11:37 AM Chris Aniszczyk < caniszczyk@...> wrote:
The Envoy 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: Known end users include: AirBnb, Alibaba, Apple, Booking.com, Cookpad, DigitalOcean, eBay, Google, GO-JEK, GroupOn, IBM, Lyft, Medium, Microsoft, Netflix, Pinterest, Salesforce, Snap, Square, Stripe, Tencent, Twilio, Two Sigma, Uber, Verizon, VMware, VSCO, Yahoo Japan, and Yelp. Many of these logos are listed here: https://www.envoyproxy.io (this is not an exclusive list and it's likely that other organizations are also Envoy users). Envoy is being used by numerous other companies, both large and small, to build higher layer products and services. This includes Covalent, Datawire, HashiCorp, Heptio, Istio (F5 Networks, Google, IBM, RedHat, Tetrate, Tigera, VMware, etc.), Solo.io, and many others.
- Have a healthy number of committers and at least two from different organizations: See the current list of Envoy owners, who are also committers: https://github.com/envoyproxy/envoy/blob/master/OWNERS.md Currently, we have 11 and are on the constant lookout for new maintainers to join our ranks.
Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/167Remember 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] Envoy moving to graduation
Michael Hausenblas <mhausenb@...>
toggle quoted messageShow quoted text
-----Original Message----- From: Chris Aniszczyk <caniszczyk@...> Reply: Chris Aniszczyk <caniszczyk@...> Date: 12 November 2018 at 16:37:20 To: CNCF TOC <cncf-toc@...> Subject: [cncf-toc] [VOTE] Envoy moving to graduation Envoy has requested to move to the graduation maturity level:
https://github.com/cncf/toc/pull/167
The Envoy 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: Known end users include: AirBnb, Alibaba,
Apple, Booking.com, Cookpad, DigitalOcean, eBay, Google, GO-JEK, GroupOn,
IBM, Lyft, Medium, Microsoft, Netflix, Pinterest, Salesforce, Snap, Square,
Stripe, Tencent, Twilio, Two Sigma, Uber, Verizon, VMware, VSCO, Yahoo
Japan, and Yelp. Many of these logos are listed here:
https://www.envoyproxy.io (this is not an exclusive list and it's likely
that other organizations are also Envoy users). Envoy is being used by
numerous other companies, both large and small, to build higher layer
products and services. This includes Covalent, Datawire, HashiCorp, Heptio,
Istio (F5 Networks, Google, IBM, RedHat, Tetrate, Tigera, VMware, etc.),
Solo.io, and many others.
- Have a healthy number of committers and at least two from different
organizations: See the current list of Envoy owners, who are also
committers: https://github.com/envoyproxy/envoy/blob/master/OWNERS.md
Currently, we have 11 and are on the constant lookout for new maintainers
to join our ranks.
- Demonstrate a substantial ongoing flow of commits and merged
contributions: https://github.com/envoyproxy/envoy/graphs/contributors
- Have achieved a CII badge:
https://bestpractices.coreinfrastructure.org/en/projects/1266
- Define a governance model:
https://github.com/envoyproxy/envoy/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/167
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] Envoy moving to graduation
toggle quoted messageShow quoted text
The Envoy 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: Known end users include: AirBnb, Alibaba, Apple,
Booking.com, Cookpad, DigitalOcean, eBay, Google, GO-JEK, GroupOn, IBM, Lyft, Medium, Microsoft, Netflix, Pinterest, Salesforce, Snap, Square, Stripe, Tencent, Twilio, Two Sigma, Uber, Verizon, VMware, VSCO, Yahoo Japan,
and Yelp. Many of these logos are listed here: https://www.envoyproxy.io (this is not an exclusive list and it's likely that other organizations are also Envoy users). Envoy is being used by
numerous other companies, both large and small, to build higher layer products and services. This includes Covalent, Datawire, HashiCorp, Heptio, Istio (F5 Networks, Google, IBM, RedHat, Tetrate, Tigera, VMware, etc.),
Solo.io, and many others.
- Have a healthy number of committers and at least two from different organizations: See the current list of Envoy owners, who are also committers: https://github.com/envoyproxy/envoy/blob/master/OWNERS.md
Currently, we have 11 and are on the constant lookout for new maintainers to join our ranks.
Please vote (+1/0/-1) by replying to this thread; the full proposal located here:
https://github.com/cncf/toc/pull/167
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] Envoy moving to graduation
Alex Chircop
+1 non-binding
From: <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@...>
Date: Monday, 12 November 2018 at 16:37
To: CNCF TOC <cncf-toc@...>
Subject: [cncf-toc] [VOTE] Envoy moving to graduation
The Envoy 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: Known end users include: AirBnb, Alibaba, Apple, Booking.com, Cookpad, DigitalOcean, eBay, Google, GO-JEK, GroupOn, IBM, Lyft, Medium,
Microsoft, Netflix, Pinterest, Salesforce, Snap, Square, Stripe, Tencent, Twilio, Two Sigma, Uber, Verizon, VMware, VSCO, Yahoo Japan, and Yelp. Many of these logos are listed here: https://www.envoyproxy.io
(this is not an exclusive list and it's likely that other organizations are also Envoy users). Envoy is being used by numerous other companies, both large and small, to build higher layer products and services. This includes Covalent, Datawire, HashiCorp,
Heptio, Istio (F5 Networks, Google, IBM, RedHat, Tetrate, Tigera, VMware, etc.), Solo.io, and many others.
- Have a healthy number of committers and at least two from different organizations: See the current list of Envoy owners, who are also committers: https://github.com/envoyproxy/envoy/blob/master/OWNERS.md
Currently, we have 11 and are on the constant lookout for new maintainers to join our ranks.
Please vote (+1/0/-1) by replying to this thread; the full proposal located here:
https://github.com/cncf/toc/pull/167
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] Envoy moving to graduation
toggle quoted messageShow quoted text
On Mon, Nov 12, 2018 at 4:37 PM Chris Aniszczyk < caniszczyk@...> wrote:
The Envoy 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: Known end users include: AirBnb, Alibaba, Apple, Booking.com, Cookpad, DigitalOcean, eBay, Google, GO-JEK, GroupOn, IBM, Lyft, Medium, Microsoft, Netflix, Pinterest, Salesforce, Snap, Square, Stripe, Tencent, Twilio, Two Sigma, Uber, Verizon, VMware, VSCO, Yahoo Japan, and Yelp. Many of these logos are listed here: https://www.envoyproxy.io (this is not an exclusive list and it's likely that other organizations are also Envoy users). Envoy is being used by numerous other companies, both large and small, to build higher layer products and services. This includes Covalent, Datawire, HashiCorp, Heptio, Istio (F5 Networks, Google, IBM, RedHat, Tetrate, Tigera, VMware, etc.), Solo.io, and many others.
- Have a healthy number of committers and at least two from different organizations: See the current list of Envoy owners, who are also committers: https://github.com/envoyproxy/envoy/blob/master/OWNERS.md Currently, we have 11 and are on the constant lookout for new maintainers to join our ranks.
Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/167Remember 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
|
|
|
[VOTE] Envoy moving to graduation
Chris Aniszczyk
The Envoy 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: Known end users include: AirBnb, Alibaba, Apple, Booking.com, Cookpad, DigitalOcean, eBay, Google, GO-JEK, GroupOn, IBM, Lyft, Medium, Microsoft, Netflix, Pinterest, Salesforce, Snap, Square, Stripe, Tencent, Twilio, Two Sigma, Uber, Verizon, VMware, VSCO, Yahoo Japan, and Yelp. Many of these logos are listed here: https://www.envoyproxy.io (this is not an exclusive list and it's likely that other organizations are also Envoy users). Envoy is being used by numerous other companies, both large and small, to build higher layer products and services. This includes Covalent, Datawire, HashiCorp, Heptio, Istio (F5 Networks, Google, IBM, RedHat, Tetrate, Tigera, VMware, etc.), Solo.io, and many others.
- Have a healthy number of committers and at least two from different organizations: See the current list of Envoy owners, who are also committers: https://github.com/envoyproxy/envoy/blob/master/OWNERS.md Currently, we have 11 and are on the constant lookout for new maintainers to join our ranks.
Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/167Remember 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] Harbor moving to incubation
Ayrat Khayretdinov <akhayretdinov@...>
toggle quoted messageShow quoted text
Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/163Remember 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] Harbor moving to incubation
Sam Lambert <samlambert@...>
toggle quoted messageShow quoted text
On Fri, Nov 9, 2018 at 8:19 AM, Camille Fournier <skamille@...> wrote: +1 binding
Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/163Remember 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] Harbor moving to incubation
toggle quoted messageShow quoted text
On Tue, Nov 6, 2018 at 2:27 PM Chris Aniszczyk < caniszczyk@...> wrote: Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/163Remember 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] Harbor moving to incubation
Perfect! Thanks Justin.
Q
toggle quoted messageShow quoted text
Any and all constructive feedback on project proposals from the community is definitely encouraged.
That way the project team and other users of Harbor can respond to specifics.
Regards
Q
Quinton Hoole
Technical Vice President
America Research Center
2330 Central Expressway, Santa Clara, CA 95050
Tel: 408-330-4721 Cell: 408-320-8917 Office # C2-27
Email:
quinton.hoole@...
ID#Q00403160
I genuinely appreciate Justin's feedback on these votes. If I'm not intimately familiar with the project/product I often wait for Justin's input prior to voting. I wholeheartedly encourage Justin's input on these votes. They bring up bigger points
and provide levity to the process. Any effort to not have this feedback on the record should be discouraged, in my opinion.
I'm well aware of the adoption and uses of Harbor. My company runs it and my criticisms come from first hand experience as a user and operator of the software.
I'm happy to move my feedback out of this thread so voting can continue without any extra noise.
On Tue, Nov 6, 2018 at 4:27 PM Haining Zhang < hi@...> wrote:
(in reponse to Justin's comment)
Though Harbor may not be the only solution to a private registry, thousands of users choose Harbor to manage container images in their production environments. The user base includes many large internet companies and enterprises in the world. In some environments,
Harbor manages tens of thousands of images and supports thousands of container hosts. Typical use cases of Harbor include RBAC on images, image replication across geographically distributed locations, vulnerability scanning etc.
Haining
On 11/7/18 3:21 AM, Justin Garrison wrote:
-1 nb
I understand the need for container registries in a containerized environment, but I'm not sold Harbor being the solution for most people's needs when they need to run their own registry.
+1 non-binding
Please vote (+1/0/-1) by replying to this thread; the full proposal located here:
https://github.com/cncf/toc/pull/163
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] Harbor moving to incubation
Justin Garrison <justinleegarrison@...>
toggle quoted messageShow quoted text
Any and all constructive feedback on project proposals from the community is definitely encouraged.
That way the project team and other users of Harbor can respond to specifics.
Regards
Q
Quinton Hoole
Technical Vice President
America Research Center
2330 Central Expressway, Santa Clara, CA 95050
Tel: 408-330-4721 Cell: 408-320-8917 Office # C2-27
Email:
quinton.hoole@...
ID#Q00403160
I genuinely appreciate Justin's feedback on these votes. If I'm not intimately familiar with the project/product I often wait for Justin's input prior to voting. I wholeheartedly encourage Justin's input on these votes. They bring up bigger points
and provide levity to the process. Any effort to not have this feedback on the record should be discouraged, in my opinion.
I'm well aware of the adoption and uses of Harbor. My company runs it and my criticisms come from first hand experience as a user and operator of the software.
I'm happy to move my feedback out of this thread so voting can continue without any extra noise.
On Tue, Nov 6, 2018 at 4:27 PM Haining Zhang < hi@...> wrote:
(in reponse to Justin's comment)
Though Harbor may not be the only solution to a private registry, thousands of users choose Harbor to manage container images in their production environments. The user base includes many large internet companies and enterprises in the world. In some environments,
Harbor manages tens of thousands of images and supports thousands of container hosts. Typical use cases of Harbor include RBAC on images, image replication across geographically distributed locations, vulnerability scanning etc.
Haining
On 11/7/18 3:21 AM, Justin Garrison wrote:
-1 nb
I understand the need for container registries in a containerized environment, but I'm not sold Harbor being the solution for most people's needs when they need to run their own registry.
+1 non-binding
Please vote (+1/0/-1) by replying to this thread; the full proposal located here:
https://github.com/cncf/toc/pull/163
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
|
|
|
