+1 non-binding

On Mar 8, 2018, at 9:28 AM, Chris Aniszczyk <caniszczyk@linuxfoundation.org> wrote:

The TOC has decided to invite NATS (https://github.com/nats-io) as an INCUBATION level CNCF project, sponsored by Alexis Richardson from the TOC: https://nats.io/

NATS is a mature, seven year old messaging technology, built from the ground up to be cloud native, implementing the publish/subscribe, request/reply and distributed queue patterns to help create a performant and secure method of InterProcess Communication (IPC). Simplicity, performance, scalability, and security constitute the core tenets of NATS. It is being adopted by organizations such as Apcera, Apporeto, Clarifai, Comcast, General Electric (GE), Greta.io, CloudFoundry, HTC, Samsung, Netlify, Pivotal, Platform9, Sensay, Workiva and VMware.

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

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

The TOC has decided to invite NATS (https://github.com/nats-io) as an INCUBATION level CNCF project, sponsored by Alexis Richardson from the TOC: https://nats.io/

NATS is a mature, seven year old messaging technology, built from the ground up to be cloud native, implementing the publish/subscribe, request/reply and distributed queue patterns to help create a performant and secure method of InterProcess Communication (IPC). Simplicity, performance, scalability, and security constitute the core tenets of NATS. It is being adopted by organizations such as Apcera, Apporeto, Clarifai, Comcast, General Electric (GE), Greta.io, CloudFoundry, HTC, Samsung, Netlify, Pivotal, Platform9, Sensay, Workiva and VMware.

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

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

+1 non-binding

---

From: cncf-toc@... <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@linuxfoundation.org>
Sent: 08 March 2018 15:28
To: cncf-toc@...
Subject: [cncf-toc] [VOTE] NATS project proposal (incubation)

 

The TOC has decided to invite NATS (https://github.com/nats-io) as an INCUBATION level CNCF project, sponsored by Alexis Richardson from the TOC: https://nats.io/

NATS Cloud Native Messaging System · GitHub github.com GitHub is where people build software. More than 28 million people use GitHub to discover, fork, and contribute to over 79 million projects.

NATS - Documentation nats.io NATS is a high performance messaging system that acts as a distributed messaging queue for cloud native applications, IoT device messaging, and microservices ...

NATS is a mature, seven year old messaging technology, built from the ground up to be cloud native, implementing the publish/subscribe, request/reply and distributed queue patterns to help create a performant and secure method of InterProcess Communication (IPC). Simplicity, performance, scalability, and security constitute the core tenets of NATS. It is being adopted by organizations such as Apcera, Apporeto, Clarifai, Comcast, General Electric (GE), Greta.io, CloudFoundry, HTC, Samsung, Netlify, Pivotal, Platform9, Sensay, Workiva and VMware.

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

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

+1 non-binding

+1 non-binding

Chris Short

https://chrisshort.net

https://devopsish.com

On Thu, Mar 8, 2018 at 10:28 AM, Chris Aniszczyk <caniszczyk@linuxfoundation.org> wrote:

The TOC has decided to invite NATS (https://github.com/nats-io) as an INCUBATION level CNCF project, sponsored by Alexis Richardson from the TOC: https://nats.io/

NATS is a mature, seven year old messaging technology, built from the ground up to be cloud native, implementing the publish/subscribe, request/reply and distributed queue patterns to help create a performant and secure method of InterProcess Communication (IPC). Simplicity, performance, scalability, and security constitute the core tenets of NATS. It is being adopted by organizations such as Apcera, Apporeto, Clarifai, Comcast, General Electric (GE), Greta.io, CloudFoundry, HTC, Samsung, Netlify, Pivotal, Platform9, Sensay, Workiva and VMware.

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

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

The TOC has decided to invite NATS (https://github.com/nats-io) as an INCUBATION level CNCF project, sponsored by Alexis Richardson from the TOC: https://nats.io/

NATS is a mature, seven year old messaging technology, built from the ground up to be cloud native, implementing the publish/subscribe, request/reply and distributed queue patterns to help create a performant and secure method of InterProcess Communication (IPC). Simplicity, performance, scalability, and security constitute the core tenets of NATS. It is being adopted by organizations such as Apcera, Apporeto, Clarifai, Comcast, General Electric (GE), Greta.io, CloudFoundry, HTC, Samsung, Netlify, Pivotal, Platform9, Sensay, Workiva and VMware.

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

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

+1 non-binding

On Tue, Mar 6, 2018 at 6:34 AM, Solomon Hykes via Lists.Cncf.Io <solomon.hykes=docker.com@lists.cncf.io> wrote:

+1 binding

Hats off to the maintainers, sustaining this kind of growth without compromising quality and consistency of design is much harder than it looks...

On Feb 26, 2018, at 8:52 AM, Chris Aniszczyk <caniszczyk@...g> wrote:

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

--

Taha Ozket                                  

Senior IT Consultant taha.ozket@...

ACEDEMAND IT Consulting Services http://www.acedemand.com

Maslak Eclipse A 164 Tel: +90-212 803 0 231

Maslak / ISTANBUL Mobile: +90-532 683 43 37

+1 binding

Hats off to the maintainers, sustaining this kind of growth without compromising quality and consistency of design is much harder than it looks...

On Feb 26, 2018, at 8:52 AM, Chris Aniszczyk <caniszczyk@linuxfoundation.org> wrote:

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

As long as we are playing around with names in a non-blocking way, might I add to the list "greenhouse"?

In favor of this idea it is more aligned to selective nuturing things as they start to grow, rather than playing around and experimentation - "sandbox".

-Bob

On Sun, Mar 4, 2018 at 12:18 PM, Richard Hartmann <richih@...> wrote:

This might be overly colo[u]rful, but what about playground[ or
kindergarten]? It implies no quality whatsoever, that breaking stuff
is fine and with little consequence, and clearly carries an
expectation for things to grow up before any progression.


Richard