Date   

Re: [VOTE] Rook moving to incubation

Sam Lambert <samlambert@...>
 

+1 binding.

On Mon, Sep 10, 2018 at 1:39 AM, Daniel Bryant <db@...> wrote:
+1 (non-binding) 

Great to see this for a very interesting project!

On Thu, Sep 6, 2018 at 4:19 PM Chris Aniszczyk <caniszczyk@linuxfoundation.org> wrote:
Rook (https://rook.io) has requested to move to the incubation maturity level:

In the time since being accepted to the sandbox, two releases were completed, starting with v0.7 on February 21st and then v0.8 on July 18th. With those releases, Rook extended beyond just orchestration of Ceph and has built a framework of reusable specs, logic and policies for cloud-native storage orchestration of other providers. Operators and CRD types were added for both CockroachDB and Minio in the v0.8 release, initial support for NFS is nearly complete, and other storage providers are also in the works.

The Rook community believes it has fulfilled all the incubation 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: https://github.com/rook/rook/blob/master/ADOPTERS.md

Maintainers of the project are listed in https://github.com/rook/rook/blob/master/OWNERS.md.

Maintainers are added and removed from the project as per the policies outlined in the project governance: https://github.com/rook/rook/blob/master/GOVERNANCE.md

Demonstrate a substantial ongoing flow of commits and merged contributions:

Releases: https://github.com/rook/rook/releases
Roadmap: https://github.com/rook/rook/blob/master/ROADMAP.md
Contributors: https://github.com/rook/rook/graphs/contributors
Commit activity: https://github.com/rook/rook/graphs/commit-activity
CNCF DevStats: https://rook.devstats.cncf.io/

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

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] SAFE (Security) Working Group

Sam Lambert <samlambert@...>
 

+1 binding.

On Fri, Sep 7, 2018 at 9:53 AM, Camille Fournier <skamille@...> wrote:
+1 binding

On Thu, Sep 6, 2018, 10:57 AM Quinton Hoole <quinton.hoole@...> wrote:
+1 (binding)

From: <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@linuxfoundation.org>
Date: Tuesday, September 4, 2018 at 06:50
To: CNCF TOC <cncf-toc@...>
Subject: [cncf-toc] [VOTE] SAFE (Security) Working Group

A new CNCF Working Group has been proposed (sponsored by Ken Owens):

Secure Access for Everyone (SAFE) Working Group will explore secure access, policy control and safety for operators, administrators, developers, and end-users across the cloud native ecosystem

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

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] Rook moving to incubation

Daniel Bryant
 

+1 (non-binding) 

Great to see this for a very interesting project!

On Thu, Sep 6, 2018 at 4:19 PM Chris Aniszczyk <caniszczyk@...> wrote:
Rook (https://rook.io) has requested to move to the incubation maturity level:

In the time since being accepted to the sandbox, two releases were completed, starting with v0.7 on February 21st and then v0.8 on July 18th. With those releases, Rook extended beyond just orchestration of Ceph and has built a framework of reusable specs, logic and policies for cloud-native storage orchestration of other providers. Operators and CRD types were added for both CockroachDB and Minio in the v0.8 release, initial support for NFS is nearly complete, and other storage providers are also in the works.

The Rook community believes it has fulfilled all the incubation 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: https://github.com/rook/rook/blob/master/ADOPTERS.md

Maintainers of the project are listed in https://github.com/rook/rook/blob/master/OWNERS.md.

Maintainers are added and removed from the project as per the policies outlined in the project governance: https://github.com/rook/rook/blob/master/GOVERNANCE.md

Demonstrate a substantial ongoing flow of commits and merged contributions:

Releases: https://github.com/rook/rook/releases
Roadmap: https://github.com/rook/rook/blob/master/ROADMAP.md
Contributors: https://github.com/rook/rook/graphs/contributors
Commit activity: https://github.com/rook/rook/graphs/commit-activity
CNCF DevStats: https://rook.devstats.cncf.io/

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

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


2019 KubeCon + CloudNativeCon sponsorship prospectus

Dan Kohn <dan@...>
 

I'm pleased to distribute the (attached) sponsor guide for the three 2019 KubeCon + CloudNativeCon events:

Barcelona: May 20-23, 2019
Shanghai: June 26-28, 2019
San Diego: November 18-21, 2019

Sponsors select their booth locations in the order that they return a signed contract. Please contact sponsor@... with questions or to get a contract. You can also book a time to speak to Kathy at https://calendly.com/kosweiler.
--
Dan Kohn <dan@...>
Executive Director, Cloud Native Computing Foundation https://www.cncf.io
+1-415-233-1000 https://www.dankohn.com


Re: [VOTE] SAFE (Security) Working Group

Camille Fournier
 

+1 binding


On Thu, Sep 6, 2018, 10:57 AM Quinton Hoole <quinton.hoole@...> wrote:
+1 (binding)

From: <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@...>
Date: Tuesday, September 4, 2018 at 06:50
To: CNCF TOC <cncf-toc@...>
Subject: [cncf-toc] [VOTE] SAFE (Security) Working Group

A new CNCF Working Group has been proposed (sponsored by Ken Owens):

Secure Access for Everyone (SAFE) Working Group will explore secure access, policy control and safety for operators, administrators, developers, and end-users across the cloud native ecosystem

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

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] SAFE (Security) Working Group

Haim Helman
 

+1 (non-binding)


Re: [VOTE] Rook moving to incubation

Jimmy Song <jimmysong@...>
 

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

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





On Sep 7, 2018, at 9:50 AM, Richard Hartmann <richih@...> wrote:

+1 non-binding

Sent by mobile; please excuse my brevity.

On Thu, Sep 6, 2018, 23:19 Chris Aniszczyk <caniszczyk@...> wrote:
Rook (https://rook.io) has requested to move to the incubation maturity level:

In the time since being accepted to the sandbox, two releases were completed, starting with v0.7 on February 21st and then v0.8 on July 18th. With those releases, Rook extended beyond just orchestration of Ceph and has built a framework of reusable specs, logic and policies for cloud-native storage orchestration of other providers. Operators and CRD types were added for both CockroachDB and Minio in the v0.8 release, initial support for NFS is nearly complete, and other storage providers are also in the works.

The Rook community believes it has fulfilled all the incubation 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: https://github.com/rook/rook/blob/master/ADOPTERS.md

Maintainers of the project are listed in https://github.com/rook/rook/blob/master/OWNERS.md.

Maintainers are added and removed from the project as per the policies outlined in the project governance: https://github.com/rook/rook/blob/master/GOVERNANCE.md

Demonstrate a substantial ongoing flow of commits and merged contributions:

Releases: https://github.com/rook/rook/releases
Roadmap: https://github.com/rook/rook/blob/master/ROADMAP.md
Contributors: https://github.com/rook/rook/graphs/contributors
Commit activity: https://github.com/rook/rook/graphs/commit-activity
CNCF DevStats: https://rook.devstats.cncf.io/

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

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] Rook moving to incubation

Richard Hartmann
 

+1 non-binding

Sent by mobile; please excuse my brevity.

On Thu, Sep 6, 2018, 23:19 Chris Aniszczyk <caniszczyk@...> wrote:
Rook (https://rook.io) has requested to move to the incubation maturity level:

In the time since being accepted to the sandbox, two releases were completed, starting with v0.7 on February 21st and then v0.8 on July 18th. With those releases, Rook extended beyond just orchestration of Ceph and has built a framework of reusable specs, logic and policies for cloud-native storage orchestration of other providers. Operators and CRD types were added for both CockroachDB and Minio in the v0.8 release, initial support for NFS is nearly complete, and other storage providers are also in the works.

The Rook community believes it has fulfilled all the incubation 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: https://github.com/rook/rook/blob/master/ADOPTERS.md

Maintainers of the project are listed in https://github.com/rook/rook/blob/master/OWNERS.md.

Maintainers are added and removed from the project as per the policies outlined in the project governance: https://github.com/rook/rook/blob/master/GOVERNANCE.md

Demonstrate a substantial ongoing flow of commits and merged contributions:

Releases: https://github.com/rook/rook/releases
Roadmap: https://github.com/rook/rook/blob/master/ROADMAP.md
Contributors: https://github.com/rook/rook/graphs/contributors
Commit activity: https://github.com/rook/rook/graphs/commit-activity
CNCF DevStats: https://rook.devstats.cncf.io/

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

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] Rook moving to incubation

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

+1 (non-binding)

Thanks & Best Regards,

徐翔轩

----------------------------------------------------



上海得帆信息技术有限公司
  SHANGHAI DEFINESYS INFORMATION TECHNOLOGY CO., LTD.

E-mail : eleven.xu@...
Mobile : +86-186-1626-0537
Website:http://www.definesys.com

----------------------------------------------------
 

在 2018年9月7日,07:17,wenqiang.feng@... 写道:

+1 non-binding

---Original---
From: "Chris Aniszczyk"<caniszczyk@...>
Date: Thu, Sep 6, 2018 23:19 PM
To: "CNCF TOC"<cncf-toc@...>;
Subject: [cncf-toc] [VOTE] Rook moving to incubation

Rook (https://rook.io) has requested to move to the incubation maturity level:

In the time since being accepted to the sandbox, two releases were completed, starting with v0.7 on February 21st and then v0.8 on July 18th. With those releases, Rook extended beyond just orchestration of Ceph and has built a framework of reusable specs, logic and policies for cloud-native storage orchestration of other providers. Operators and CRD types were added for both CockroachDB and Minio in the v0.8 release, initial support for NFS is nearly complete, and other storage providers are also in the works.

The Rook community believes it has fulfilled all the incubation 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: https://github.com/rook/rook/blob/master/ADOPTERS.md

Maintainers of the project are listed in https://github.com/rook/rook/blob/master/OWNERS.md.

Maintainers are added and removed from the project as per the policies outlined in the project governance: https://github.com/rook/rook/blob/master/GOVERNANCE.md

Demonstrate a substantial ongoing flow of commits and merged contributions:

Releases: https://github.com/rook/rook/releases
Roadmap: https://github.com/rook/rook/blob/master/ROADMAP.md
Contributors: https://github.com/rook/rook/graphs/contributors
Commit activity: https://github.com/rook/rook/graphs/commit-activity
CNCF DevStats: https://rook.devstats.cncf.io/

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

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] Rook moving to incubation

wenqiang.feng@...
 

+1 non-binding

---Original---
From: "Chris Aniszczyk"<caniszczyk@...>
Date: Thu, Sep 6, 2018 23:19 PM
To: "CNCF TOC"<cncf-toc@...>;
Subject: [cncf-toc] [VOTE] Rook moving to incubation

Rook (https://rook.io) has requested to move to the incubation maturity level:

In the time since being accepted to the sandbox, two releases were completed, starting with v0.7 on February 21st and then v0.8 on July 18th. With those releases, Rook extended beyond just orchestration of Ceph and has built a framework of reusable specs, logic and policies for cloud-native storage orchestration of other providers. Operators and CRD types were added for both CockroachDB and Minio in the v0.8 release, initial support for NFS is nearly complete, and other storage providers are also in the works.

The Rook community believes it has fulfilled all the incubation 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: https://github.com/rook/rook/blob/master/ADOPTERS.md

Maintainers of the project are listed in https://github.com/rook/rook/blob/master/OWNERS.md.

Maintainers are added and removed from the project as per the policies outlined in the project governance: https://github.com/rook/rook/blob/master/GOVERNANCE.md

Demonstrate a substantial ongoing flow of commits and merged contributions:

Releases: https://github.com/rook/rook/releases
Roadmap: https://github.com/rook/rook/blob/master/ROADMAP.md
Contributors: https://github.com/rook/rook/graphs/contributors
Commit activity: https://github.com/rook/rook/graphs/commit-activity
CNCF DevStats: https://rook.devstats.cncf.io/

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

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] SAFE (Security) Working Group

Quinton Hoole
 

+1 (binding)

From: <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@...>
Date: Tuesday, September 4, 2018 at 06:50
To: CNCF TOC <cncf-toc@...>
Subject: [cncf-toc] [VOTE] SAFE (Security) Working Group

A new CNCF Working Group has been proposed (sponsored by Ken Owens):

Secure Access for Everyone (SAFE) Working Group will explore secure access, policy control and safety for operators, administrators, developers, and end-users across the cloud native ecosystem

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

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] Rook moving to incubation

Raymond Maika <raymond.maika@...>
 

+1 (non-binding). 

Using Rook in production at CENGN, it has been highly useful to us. 

Raymond Maika

Cloud Infrastructure Engineer

CENGN - Centre of Excellence in Next Generation Networks

555 Legget Drive | Tower A | Suite 600 | Ottawa ON | K2K 2X3

www.cengn.ca  Follow us @CENGNCanada


Re: [VOTE] Rook moving to incubation

Chris Short
 

+1 non-binding

Chris Short


On Thu, Sep 6, 2018 at 1:19 PM Quinton Hoole <quinton.hoole@...> wrote:
+1 (binding)

From: <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@...>
Date: Thursday, September 6, 2018 at 08:19
To: CNCF TOC <cncf-toc@...>
Subject: [cncf-toc] [VOTE] Rook moving to incubation

Rook (https://rook.io) has requested to move to the incubation maturity level:

In the time since being accepted to the sandbox, two releases were completed, starting with v0.7 on February 21st and then v0.8 on July 18th. With those releases, Rook extended beyond just orchestration of Ceph and has built a framework of reusable specs, logic and policies for cloud-native storage orchestration of other providers. Operators and CRD types were added for both CockroachDB and Minio in the v0.8 release, initial support for NFS is nearly complete, and other storage providers are also in the works.

The Rook community believes it has fulfilled all the incubation 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: https://github.com/rook/rook/blob/master/ADOPTERS.md

Maintainers of the project are listed in https://github.com/rook/rook/blob/master/OWNERS.md.

Maintainers are added and removed from the project as per the policies outlined in the project governance: https://github.com/rook/rook/blob/master/GOVERNANCE.md

Demonstrate a substantial ongoing flow of commits and merged contributions:

Releases: https://github.com/rook/rook/releases
Roadmap: https://github.com/rook/rook/blob/master/ROADMAP.md
Contributors: https://github.com/rook/rook/graphs/contributors
Commit activity: https://github.com/rook/rook/graphs/commit-activity
CNCF DevStats: https://rook.devstats.cncf.io/

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

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] Rook moving to incubation

Quinton Hoole
 

+1 (binding)

From: <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@...>
Date: Thursday, September 6, 2018 at 08:19
To: CNCF TOC <cncf-toc@...>
Subject: [cncf-toc] [VOTE] Rook moving to incubation

Rook (https://rook.io) has requested to move to the incubation maturity level:

In the time since being accepted to the sandbox, two releases were completed, starting with v0.7 on February 21st and then v0.8 on July 18th. With those releases, Rook extended beyond just orchestration of Ceph and has built a framework of reusable specs, logic and policies for cloud-native storage orchestration of other providers. Operators and CRD types were added for both CockroachDB and Minio in the v0.8 release, initial support for NFS is nearly complete, and other storage providers are also in the works.

The Rook community believes it has fulfilled all the incubation 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: https://github.com/rook/rook/blob/master/ADOPTERS.md

Maintainers of the project are listed in https://github.com/rook/rook/blob/master/OWNERS.md.

Maintainers are added and removed from the project as per the policies outlined in the project governance: https://github.com/rook/rook/blob/master/GOVERNANCE.md

Demonstrate a substantial ongoing flow of commits and merged contributions:

Releases: https://github.com/rook/rook/releases
Roadmap: https://github.com/rook/rook/blob/master/ROADMAP.md
Contributors: https://github.com/rook/rook/graphs/contributors
Commit activity: https://github.com/rook/rook/graphs/commit-activity
CNCF DevStats: https://rook.devstats.cncf.io/

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

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] Rook moving to incubation

Jeff Billimek
 

+1 (non-binding)


Re: [VOTE] Rook moving to incubation

Benjamin Hindman
 

+1 binding

On Thu, Sep 6, 2018 at 8:19 AM Chris Aniszczyk <caniszczyk@...> wrote:
Rook (https://rook.io) has requested to move to the incubation maturity level:

In the time since being accepted to the sandbox, two releases were completed, starting with v0.7 on February 21st and then v0.8 on July 18th. With those releases, Rook extended beyond just orchestration of Ceph and has built a framework of reusable specs, logic and policies for cloud-native storage orchestration of other providers. Operators and CRD types were added for both CockroachDB and Minio in the v0.8 release, initial support for NFS is nearly complete, and other storage providers are also in the works.

The Rook community believes it has fulfilled all the incubation 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: https://github.com/rook/rook/blob/master/ADOPTERS.md

Maintainers of the project are listed in https://github.com/rook/rook/blob/master/OWNERS.md.

Maintainers are added and removed from the project as per the policies outlined in the project governance: https://github.com/rook/rook/blob/master/GOVERNANCE.md

Demonstrate a substantial ongoing flow of commits and merged contributions:

Releases: https://github.com/rook/rook/releases
Roadmap: https://github.com/rook/rook/blob/master/ROADMAP.md
Contributors: https://github.com/rook/rook/graphs/contributors
Commit activity: https://github.com/rook/rook/graphs/commit-activity
CNCF DevStats: https://rook.devstats.cncf.io/

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

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

--
Benjamin Hindman
Founder of Mesosphere and Co-Creator of Apache Mesos

Follow us on Twitter: @mesosphere

Follow Us Twitter LinkedIn Facebook YouTube
 


Re: [VOTE] Rook moving to incubation

Wilson, Dan <dan.wilson01@...>
 

+1 non-binding

 

From: <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@...>
Date: Thursday, September 6, 2018 at 8:19 AM
To: CNCF TOC <cncf-toc@...>
Subject: [cncf-toc] [VOTE] Rook moving to incubation

 

Rook (https://rook.io) has requested to move to the incubation maturity level:

 

In the time since being accepted to the sandbox, two releases were completed, starting with v0.7 on February 21st and then v0.8 on July 18th. With those releases, Rook extended beyond just orchestration of Ceph and has built a framework of reusable specs, logic and policies for cloud-native storage orchestration of other providers. Operators and CRD types were added for both CockroachDB and Minio in the v0.8 release, initial support for NFS is nearly complete, and other storage providers are also in the works.


The Rook community believes it has fulfilled all the incubation 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: https://github.com/rook/rook/blob/master/ADOPTERS.md

Maintainers of the project are listed in https://github.com/rook/rook/blob/master/OWNERS.md.

Maintainers are added and removed from the project as per the policies outlined in the project governance: https://github.com/rook/rook/blob/master/GOVERNANCE.md

Demonstrate a substantial ongoing flow of commits and merged contributions:

Releases: https://github.com/rook/rook/releases
Roadmap: https://github.com/rook/rook/blob/master/ROADMAP.md
Contributors: https://github.com/rook/rook/graphs/contributors
Commit activity: https://github.com/rook/rook/graphs/commit-activity
CNCF DevStats: https://rook.devstats.cncf.io/

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

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] Rook moving to incubation

JJ
 

+1 non-binding


On Thu, Sep 6, 2018, 8:36 AM Yassine Tijani <ytijani@...> wrote:
+1 non-binding

Le jeu. 6 sept. 2018 à 17:36, Ken Owens <kenchristineowens@...> a écrit :
+1 binding

On Thu, Sep 6, 2018 at 10:19 AM Chris Aniszczyk <caniszczyk@...> wrote:
Rook (https://rook.io) has requested to move to the incubation maturity level:

In the time since being accepted to the sandbox, two releases were completed, starting with v0.7 on February 21st and then v0.8 on July 18th. With those releases, Rook extended beyond just orchestration of Ceph and has built a framework of reusable specs, logic and policies for cloud-native storage orchestration of other providers. Operators and CRD types were added for both CockroachDB and Minio in the v0.8 release, initial support for NFS is nearly complete, and other storage providers are also in the works.

The Rook community believes it has fulfilled all the incubation 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: https://github.com/rook/rook/blob/master/ADOPTERS.md

Maintainers of the project are listed in https://github.com/rook/rook/blob/master/OWNERS.md.

Maintainers are added and removed from the project as per the policies outlined in the project governance: https://github.com/rook/rook/blob/master/GOVERNANCE.md

Demonstrate a substantial ongoing flow of commits and merged contributions:

Releases: https://github.com/rook/rook/releases
Roadmap: https://github.com/rook/rook/blob/master/ROADMAP.md
Contributors: https://github.com/rook/rook/graphs/contributors
Commit activity: https://github.com/rook/rook/graphs/commit-activity
CNCF DevStats: https://rook.devstats.cncf.io/

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

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] Rook moving to incubation

Yassine Tijani <ytijani@...>
 

+1 non-binding

Le jeu. 6 sept. 2018 à 17:36, Ken Owens <kenchristineowens@...> a écrit :
+1 binding

On Thu, Sep 6, 2018 at 10:19 AM Chris Aniszczyk <caniszczyk@...> wrote:
Rook (https://rook.io) has requested to move to the incubation maturity level:

In the time since being accepted to the sandbox, two releases were completed, starting with v0.7 on February 21st and then v0.8 on July 18th. With those releases, Rook extended beyond just orchestration of Ceph and has built a framework of reusable specs, logic and policies for cloud-native storage orchestration of other providers. Operators and CRD types were added for both CockroachDB and Minio in the v0.8 release, initial support for NFS is nearly complete, and other storage providers are also in the works.

The Rook community believes it has fulfilled all the incubation 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: https://github.com/rook/rook/blob/master/ADOPTERS.md

Maintainers of the project are listed in https://github.com/rook/rook/blob/master/OWNERS.md.

Maintainers are added and removed from the project as per the policies outlined in the project governance: https://github.com/rook/rook/blob/master/GOVERNANCE.md

Demonstrate a substantial ongoing flow of commits and merged contributions:

Releases: https://github.com/rook/rook/releases
Roadmap: https://github.com/rook/rook/blob/master/ROADMAP.md
Contributors: https://github.com/rook/rook/graphs/contributors
Commit activity: https://github.com/rook/rook/graphs/commit-activity
CNCF DevStats: https://rook.devstats.cncf.io/

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

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] Rook moving to incubation

Ken Owens
 

+1 binding

On Thu, Sep 6, 2018 at 10:19 AM Chris Aniszczyk <caniszczyk@...> wrote:
Rook (https://rook.io) has requested to move to the incubation maturity level:

In the time since being accepted to the sandbox, two releases were completed, starting with v0.7 on February 21st and then v0.8 on July 18th. With those releases, Rook extended beyond just orchestration of Ceph and has built a framework of reusable specs, logic and policies for cloud-native storage orchestration of other providers. Operators and CRD types were added for both CockroachDB and Minio in the v0.8 release, initial support for NFS is nearly complete, and other storage providers are also in the works.

The Rook community believes it has fulfilled all the incubation 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: https://github.com/rook/rook/blob/master/ADOPTERS.md

Maintainers of the project are listed in https://github.com/rook/rook/blob/master/OWNERS.md.

Maintainers are added and removed from the project as per the policies outlined in the project governance: https://github.com/rook/rook/blob/master/GOVERNANCE.md

Demonstrate a substantial ongoing flow of commits and merged contributions:

Releases: https://github.com/rook/rook/releases
Roadmap: https://github.com/rook/rook/blob/master/ROADMAP.md
Contributors: https://github.com/rook/rook/graphs/contributors
Commit activity: https://github.com/rook/rook/graphs/commit-activity
CNCF DevStats: https://rook.devstats.cncf.io/

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

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

4601 - 4620 of 6990