Date   

Re: [VOTE] NATS project proposal (incubation)

alexis richardson
 

+1 binding


On Thu, 8 Mar 2018, 15:32 Ginger Collison, <ginger@...> wrote:
+1 non-binding




Re: [VOTE] NATS project proposal (incubation)

Ginger Collison
 

+1 non-binding


Re: [VOTE] NATS project proposal (incubation)

Sam Lambert <samlambert@...>
 

+1 binding

On Thu, Mar 8, 2018 at 3:28 PM, Chris Short via Lists.Cncf.Io <chris=chrisshort.net@...> wrote:
+1 non-binding


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




Re: [VOTE] NATS project proposal (incubation)

Chris Short
 

On Thu, Mar 8, 2018 at 10:28 AM, Chris Aniszczyk <caniszczyk@...> 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



[VOTE] NATS project proposal (incubation)

Chris Aniszczyk
 

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


Interactive Cloud Native Landscape

Dan Kohn <dan@...>
 


As mentioned on today's TOC call, please take a look at CNCF's new Interactive Landscape. Clicking the example filters on the left demonstrates some of its capabilities.

It provides much more detail about each project and product in our ecosystem than the static landscape. <https://github.com/cncf/landscape#current-version>

If you see errors, please open a pull request. All data originates from a YAML file <https://github.com/cncf/landscape/blob/master/landscape.yml> which is then enriched with data from Crunchbase, GitHub, and Yahoo Finance. One fun aspect of the app is that it is "serverless"; the JSON is served as a static file and then all filtering, sorting and grouping occurs locally in your browser.
--
Dan Kohn <dan@...>
Executive Director, Cloud Native Computing Foundation https://www.cncf.io
+1-415-233-1000 https://www.dankohn.com


Re: [VOTE] Kubernetes moving to graduation

Brian Grant
 

On Mon, Mar 5, 2018 at 7:34 PM, Solomon Hykes via Lists.Cncf.Io <solomon.hykes=docker.com@...> 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...

Thanks. We appreciate it.
 

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/steeringunanimously 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



FYI: CNCF Annual Report for 2017

Chris Aniszczyk
 

Hey TOC and wider community, the CNCF has published its annual report for 2017:

Moving forward, we will be doing this every year. If you have ideas on how to improve the report, please reach out to Dee Kumar <dkumar@...> and me.

Thanks!

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


[RESULT] Kubernetes moving to graduation (PASSED)

Chris Aniszczyk
 

The vote for Kubernetes to graduate has passed: https://github.com/cncf/toc/pull/91

+1 binding TOC votes (9/9):
- Alexis Richardson: https://lists.cncf.io/g/cncf-toc/message/1720
- Camille Fournier: https://lists.cncf.io/g/cncf-toc/message/1721
- Ken Owens: https://lists.cncf.io/g/cncf-toc/message/1736
- Jon Boulle: https://lists.cncf.io/g/cncf-toc/message/1737
- Brian Grant: https://lists.cncf.io/g/cncf-toc/message/1752
- Bryan Cantrill: https://lists.cncf.io/g/cncf-toc/message/1755
- Sam Lambert: https://lists.cncf.io/g/cncf-toc/message/1757
- Ben Hindman: https://lists.cncf.io/g/cncf-toc/message/1764
- Solomon Hykes: https://lists.cncf.io/g/cncf-toc/message/1835

+1 non-binding community votes:

Thank you to everyone who voted, I'm personally thrilled to have our first project in CNCF to graduate and look forward to others in the future to follow the same path.

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


[RESULT] Sandbox proposal (PASSED)

Chris Aniszczyk
 

The vote for the Sandbox has passed: https://github.com/cncf/toc/pull/92

+1 TOC binding votes (6/9):

+1 non-binding community votes:

Thank you to everyone who voted and I look forward to us evolving this process over time. As of today, the CNCF is going to update the website, documents and other marketing resources to reflect the sandbox messaging. This includes moving existing inception projects to the sandbox and also helping the current project proposals targeted for inception to be updated for the sandbox.

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


Re: [VOTE] Kubernetes moving to graduation

Sebastien Goasguen <sebgoa@...>
 

+1 (non-binding)

On Tue, Mar 6, 2018 at 10:40 AM, Taha Ozket <taha.ozket@...> wrote:
+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




--

Sebastien Goasguen  

Senior Director of Cloud Technologies, Bitnami

+41 79 367 38 25

@sebgoa


Re: [VOTE] Kubernetes moving to graduation

Taha Ozket
 

+1 non-binding


On Tue, Mar 6, 2018 at 6:34 AM, Solomon Hykes via Lists.Cncf.Io <solomon.hykes=docker.com@...> 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@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/steeringunanimously 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


Re: [VOTE] Kubernetes moving to graduation

Solomon Hykes
 

+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@...> 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


TOC Agenda 3/6/2018

Chris Aniszczyk
 

Here's the agenda deck for tomorrow: https://goo.gl/LcE3TC

The formal agenda is fairly brief so there should be time for Q&A with the TOC but we will focus on an update to the TOC election due to missing a required evaluation period (see the deck), sandbox, graduation review schedule, kubernetes graduation and working group process.

Thanks!

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


Re: [VOTE] CNCF Sandbox proposal

Gou Rao <grao@...>
 

FWIW, I believe the inspiration for sandbox came from the Apache project, which uses the same term.

On Sun, Mar 4, 2018 at 12:54 PM, Bob Wise <bob@...> wrote:
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






Re: [VOTE] CNCF Sandbox proposal

alexis richardson
 

Bob, All,

Thank-you all for your feedback on the Sandbox doc.

Please don't send any more new names as suggestions. While all
feedback is always welcome, I think the TOC settled on "Sandbox"
already.

We *can* share some nomenclature with other OSS foundations. That is
a Good Thing. But, sharing nomenclature does not imply that each
stage is identical. For example CNCF and ASF share "Incubation" but
use it differently. Both express an idea of relative immaturity. At
CNCF, Incubation stage is a straight up precursor for Graduation.
Incubation and Graduation let us express CNCF values and operating
principles: https://www.cncf.io/projects/graduation-criteria/ Do also
please note that maturity criteria may evolve. For example, the
number of independent maintainers has been raised as a metric for
"community". The CNCF certainly values community.

HOWEVER: If there is still confusion about the meaning of the Sandbox
stage, then let us make the document clearer.

alexis

On Mon, Mar 5, 2018 at 1:39 AM, Bob Wise <bob@...> wrote:
It's a good callout, but I think it makes my point even stronger.

From https://commons.apache.org/sandbox.html

"The Sandbox is a Subversion repository for Commons committers to function
as an open workspace for sharing and collaboration."

I think we are creating confusion by calling it that. It isn't an open
workspace, it requires limited TOC support, which seems clearly intended to
nuture possible projects towards the next stage but with a lower bar. We
might ALSO need a sandbox. That seems less clear.

-Bob


On Sun, Mar 4, 2018 at 1:24 PM, Gou Rao <grao@...> wrote:

FWIW, I believe the inspiration for sandbox came from the Apache project,
which uses the same term.

On Sun, Mar 4, 2018 at 12:54 PM, Bob Wise <bob@...> wrote:

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



Re: [VOTE] CNCF Sandbox proposal

Bob Wise
 

It's a good callout, but I think it makes my point even stronger.


"The Sandbox is a Subversion repository for Commons committers to function as an open workspace for sharing and collaboration."

I think we are creating confusion by calling it that. It isn't an open workspace, it requires limited TOC support, which seems clearly intended to nuture possible projects towards the next stage but with a lower bar. We might ALSO need a sandbox. That seems less clear.

-Bob


On Sun, Mar 4, 2018 at 1:24 PM, Gou Rao <grao@...> wrote:
FWIW, I believe the inspiration for sandbox came from the Apache project, which uses the same term.

On Sun, Mar 4, 2018 at 12:54 PM, Bob Wise <bob@...> wrote:
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







Re: RexRay follow up

mueller@...
 

No worries. My recommendation is simple: don't pull in REX-Ray as a separate CNCF project. Instead allow the CSI community to decide how to best deliver the tooling necessary to make it easier for everyone to build, support and extend CSI artifacts like storage plugins, and deliver all of that under the guise of CSI. Perhaps we will decide to pull in REX-Ray to do that, as a whole or in part.

After all, the CSI itself isn't even a CNCF project yet. The community believes it's heading in that direction, though. And once that happens, it will be better for everyone if there's one stop shopping for all things CSI. Even prior to that, it's better for us in the community if we limit the number of places where CSI-related things are discussed and developed.

..Garrett


Re: [VOTE] CNCF Sandbox proposal

Bob Wise
 

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





Re: [VOTE] CNCF Sandbox proposal

Michael Hausenblas <mhausenb@...>
 

+1 to "playground"


Cheers,
Michael

--
Michael Hausenblas, Developer Advocate
OpenShift by Red Hat
Mobile: +353 86 0215164 | Twitter: @mhausenblas
http://openshift.com | http://mhausenblas.info

From: Richard Hartmann <richih@...>
Reply: Richard Hartmann <richih@...>
Date: 4 March 2018 at 20:18:38
To: cncf-toc@... <cncf-toc@...>
Cc: Alexis Richardson via cncf-toc <cncf-toc@...>
Subject:  Re: [cncf-toc] [VOTE] CNCF Sandbox proposal

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



5321 - 5340 of 7167