Date   

Re: [VOTE] CRI-O project proposal (incubation)

Thomas Mclennan
 

+1 non-binding

On Mar 20, 2019, at 8:48 AM, Grigoriu, Marius via Lists.Cncf.Io <marius.grigoriu=nordstrom.com@...> wrote:

+1 non-binding

 

From: <cncf-toc@...> on behalf of Pengfei Ni <feiskyer@...>
Date: Wednesday, March 20, 2019 at 6:04 AM
To: iftach Schonbaum <iftachsc@...>
Cc: "sonya@..." <sonya@...>, Chris Aniszczyk <caniszczyk@...>, Ihor Dvoretskyi <ihor.dvoretskyi@...>, "cncf-toc@..." <cncf-toc@...>
Subject: Re: [cncf-toc] [VOTE] CRI-O project proposal (incubation)

 


+1 non-binding

 

 

Best regards.

 

 

---

Pengfei Ni

 

 

 

iftach Schonbaum <iftachsc@...> 2019320日周三 下午2:41写道:

+1 non-binding

 

 

<image001.gif>

Iftach Schonbaum

Senior Solution Architect

+972-52-8281751

cloudzone.io

 

<image002.jpg>

<image003.png>

 

 

 

From: <cncf-toc@...> on behalf of "Sonya Koptyev via Lists.Cncf.Io" <sonya=twistlock.com@...>
Reply-To: "sonya@..." <sonya@...>
Date: Tuesday, 19 March 2019 at 22:26
To: Chris Aniszczyk <caniszczyk@...>, Ihor Dvoretskyi <ihor.dvoretskyi@...>
Cc: "cncf-toc@..." <cncf-toc@...>
Subject: Re: [cncf-toc] [VOTE] CRI-O project proposal (incubation)

 

+1 non-binding

 

Thanks,
Sonya

Sonya Koptyev | Director of Product Marketing and Evangelism

m: +1 425 505 0100

 

<image004.png>

 

On Mar 19, 2019, 1:25 PM -0700, Ihor Dvoretskyi <ihor.dvoretskyi@...>, wrote:

+1 (non-binding). 

 

On Tue, Mar 19, 2019, 3:57 PM Chris Aniszczyk <caniszczyk@...> wrote:

The CRI-O project is being proposed as an INCUBATION level CNCF project, sponsored by Brendan Burns from the TOC: https://github.com/kubernetes-sigs/cri-o

CRI-O is a stable container runtime specifically tailored for Kubernetes. A founding principal was not "reinventing the wheel" and so the project uses shared components, refined approaches tested in production, and existing battle-tested code. Further, it is tuned for performance, stability, compatibility, and adherence to standards, particularly the Kubernetes Conformance tests. In short CRI-O is a building block of a Kubernetes cluster, to facilitate the life cycle of containers as required by the Kubernetes Container-Runtime-Interface (CRI).

CRI-O was born in kubernetes-incubator (which is now deprecated) and grew to production stable there. Some have claimed since being a kubernetes project that it is already "a CNCF project", but it is often left as an after thought in brand, awareness and support as a top-level project. This proposal is effective to promote from the kubernetes incubator a project that has fully matured.

 

Moving CRI-O is consistent with both the Kubernetes project direction (see helm https://github.com/cncf/toc/pull/114, for example) and with other container runtimes. The containerd CRI implementation moved from the Kubernetes project to the containerd project.


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

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] CRI-O project proposal (incubation)

Grigoriu, Marius <marius.grigoriu@...>
 

+1 non-binding

 

From: <cncf-toc@...> on behalf of Pengfei Ni <feiskyer@...>
Date: Wednesday, March 20, 2019 at 6:04 AM
To: iftach Schonbaum <iftachsc@...>
Cc: "sonya@..." <sonya@...>, Chris Aniszczyk <caniszczyk@...>, Ihor Dvoretskyi <ihor.dvoretskyi@...>, "cncf-toc@..." <cncf-toc@...>
Subject: Re: [cncf-toc] [VOTE] CRI-O project proposal (incubation)

 


+1 non-binding

 

 

Best regards.

 

 

---

Pengfei Ni

 

 

 

iftach Schonbaum <iftachsc@...> 2019320日周三 下午2:41写道:

+1 non-binding

 

 

Iftach Schonbaum

Senior Solution Architect

+972-52-8281751

cloudzone.io

 

 

 

 

From: <cncf-toc@...> on behalf of "Sonya Koptyev via Lists.Cncf.Io" <sonya=twistlock.com@...>
Reply-To: "sonya@..." <sonya@...>
Date: Tuesday, 19 March 2019 at 22:26
To: Chris Aniszczyk <caniszczyk@...>, Ihor Dvoretskyi <ihor.dvoretskyi@...>
Cc: "cncf-toc@..." <cncf-toc@...>
Subject: Re: [cncf-toc] [VOTE] CRI-O project proposal (incubation)

 

+1 non-binding

 

Thanks,
Sonya

Sonya Koptyev | Director of Product Marketing and Evangelism

m: +1 425 505 0100

 

 

On Mar 19, 2019, 1:25 PM -0700, Ihor Dvoretskyi <ihor.dvoretskyi@...>, wrote:

+1 (non-binding). 

 

On Tue, Mar 19, 2019, 3:57 PM Chris Aniszczyk <caniszczyk@...> wrote:

The CRI-O project is being proposed as an INCUBATION level CNCF project, sponsored by Brendan Burns from the TOC: https://github.com/kubernetes-sigs/cri-o

CRI-O is a stable container runtime specifically tailored for Kubernetes. A founding principal was not "reinventing the wheel" and so the project uses shared components, refined approaches tested in production, and existing battle-tested code. Further, it is tuned for performance, stability, compatibility, and adherence to standards, particularly the Kubernetes Conformance tests. In short CRI-O is a building block of a Kubernetes cluster, to facilitate the life cycle of containers as required by the Kubernetes Container-Runtime-Interface (CRI).

CRI-O was born in kubernetes-incubator (which is now deprecated) and grew to production stable there. Some have claimed since being a kubernetes project that it is already "a CNCF project", but it is often left as an after thought in brand, awareness and support as a top-level project. This proposal is effective to promote from the kubernetes incubator a project that has fully matured.

 

Moving CRI-O is consistent with both the Kubernetes project direction (see helm https://github.com/cncf/toc/pull/114, for example) and with other container runtimes. The containerd CRI implementation moved from the Kubernetes project to the containerd project.


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

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] CNCF SIGs Proposal

Lee Calcote
 

+1 non-binding 

- Lee

On Mar 18, 2019, at 8:47 PM, Chris Aniszczyk <caniszczyk@...> wrote:

Hey all, this is the formal vote for the CNCF SIGs proposal. 


There has been a long discussion on restructuring how WGs work in CNCF to help scale the community. A CNCF SIG will oversee and coordinate the interests pertaining to a logical area of needs of end users and/or projects.  Examples of such areas include security, testing, observability, storage, networking. The area overseen by a SIG is typically met by a set of CNCF projects, and may also represent a cross-cutting feature group shared by several projects (like security and observability).

A special thank you to Alexis, Quinton and many others who provided input. We will bootstrap the notion of CNCF SIGs starting with the governance/security one that has served as a pilot for this work initially and go on from there.

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

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] CRI-O project proposal (incubation)

Pengfei Ni
 


+1 non-binding



Best regards.


---
Pengfei Ni



iftach Schonbaum <iftachsc@...> 于2019年3月20日周三 下午2:41写道:

+1 non-binding

 

 

Iftach Schonbaum

Senior Solution Architect

+972-52-8281751

cloudzone.io

 

 

 

 

From: <cncf-toc@...> on behalf of "Sonya Koptyev via Lists.Cncf.Io" <sonya=twistlock.com@...>
Reply-To: "sonya@..." <sonya@...>
Date: Tuesday, 19 March 2019 at 22:26
To: Chris Aniszczyk <caniszczyk@...>, Ihor Dvoretskyi <ihor.dvoretskyi@...>
Cc: "cncf-toc@..." <cncf-toc@...>
Subject: Re: [cncf-toc] [VOTE] CRI-O project proposal (incubation)

 

+1 non-binding

 

Thanks,
Sonya

Sonya Koptyev | Director of Product Marketing and Evangelism

m: +1 425 505 0100

 

 

On Mar 19, 2019, 1:25 PM -0700, Ihor Dvoretskyi <ihor.dvoretskyi@...>, wrote:

+1 (non-binding). 

 

On Tue, Mar 19, 2019, 3:57 PM Chris Aniszczyk <caniszczyk@...> wrote:

The CRI-O project is being proposed as an INCUBATION level CNCF project, sponsored by Brendan Burns from the TOC: https://github.com/kubernetes-sigs/cri-o

CRI-O is a stable container runtime specifically tailored for Kubernetes. A founding principal was not "reinventing the wheel" and so the project uses shared components, refined approaches tested in production, and existing battle-tested code. Further, it is tuned for performance, stability, compatibility, and adherence to standards, particularly the Kubernetes Conformance tests. In short CRI-O is a building block of a Kubernetes cluster, to facilitate the life cycle of containers as required by the Kubernetes Container-Runtime-Interface (CRI).

CRI-O was born in kubernetes-incubator (which is now deprecated) and grew to production stable there. Some have claimed since being a kubernetes project that it is already "a CNCF project", but it is often left as an after thought in brand, awareness and support as a top-level project. This proposal is effective to promote from the kubernetes incubator a project that has fully matured.

 

Moving CRI-O is consistent with both the Kubernetes project direction (see helm https://github.com/cncf/toc/pull/114, for example) and with other container runtimes. The containerd CRI implementation moved from the Kubernetes project to the containerd project.


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

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] CRI-O project proposal (incubation)

iftach Schonbaum
 

+1 non-binding

 

 

Iftach Schonbaum

Senior Solution Architect

+972-52-8281751

cloudzone.io

 

 

 

 

From: <cncf-toc@...> on behalf of "Sonya Koptyev via Lists.Cncf.Io" <sonya=twistlock.com@...>
Reply-To: "sonya@..." <sonya@...>
Date: Tuesday, 19 March 2019 at 22:26
To: Chris Aniszczyk <caniszczyk@...>, Ihor Dvoretskyi <ihor.dvoretskyi@...>
Cc: "cncf-toc@..." <cncf-toc@...>
Subject: Re: [cncf-toc] [VOTE] CRI-O project proposal (incubation)

 

+1 non-binding

 

Thanks,
Sonya

Sonya Koptyev | Director of Product Marketing and Evangelism

m: +1 425 505 0100

 

 

On Mar 19, 2019, 1:25 PM -0700, Ihor Dvoretskyi <ihor.dvoretskyi@...>, wrote:

+1 (non-binding). 

 

On Tue, Mar 19, 2019, 3:57 PM Chris Aniszczyk <caniszczyk@...> wrote:

The CRI-O project is being proposed as an INCUBATION level CNCF project, sponsored by Brendan Burns from the TOC: https://github.com/kubernetes-sigs/cri-o

CRI-O is a stable container runtime specifically tailored for Kubernetes. A founding principal was not "reinventing the wheel" and so the project uses shared components, refined approaches tested in production, and existing battle-tested code. Further, it is tuned for performance, stability, compatibility, and adherence to standards, particularly the Kubernetes Conformance tests. In short CRI-O is a building block of a Kubernetes cluster, to facilitate the life cycle of containers as required by the Kubernetes Container-Runtime-Interface (CRI).

CRI-O was born in kubernetes-incubator (which is now deprecated) and grew to production stable there. Some have claimed since being a kubernetes project that it is already "a CNCF project", but it is often left as an after thought in brand, awareness and support as a top-level project. This proposal is effective to promote from the kubernetes incubator a project that has fully matured.

 

Moving CRI-O is consistent with both the Kubernetes project direction (see helm https://github.com/cncf/toc/pull/114, for example) and with other container runtimes. The containerd CRI implementation moved from the Kubernetes project to the containerd project.


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

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] CNCF SIGs Proposal

Jimmy Song <jimmysong@...>
 

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

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



On Mar 20, 2019, at 3:21 AM, Brendan Burns via Lists.Cncf.Io <bburns=microsoft.com@...> wrote:

+1 binding



From: cncf-toc@... <cncf-toc@...> on behalf of Brian Grant via Lists.Cncf.Io <briangrant=google.com@...>
Sent: Tuesday, March 19, 2019 11:13 AM
To: Chris Aniszczyk
Cc: cncf-toc@...
Subject: Re: [cncf-toc] [VOTE] CNCF SIGs Proposal
 
+1 binding

On Mon, Mar 18, 2019 at 6:47 PM Chris Aniszczyk <caniszczyk@...> wrote:
Hey all, this is the formal vote for the CNCF SIGs proposal. 


There has been a long discussion on restructuring how WGs work in CNCF to help scale the community. A CNCF SIG will oversee and coordinate the interests pertaining to a logical area of needs of end users and/or projects.  Examples of such areas include security, testing, observability, storage, networking. The area overseen by a SIG is typically met by a set of CNCF projects, and may also represent a cross-cutting feature group shared by several projects (like security and observability).

A special thank you to Alexis, Quinton and many others who provided input. We will bootstrap the notion of CNCF SIGs starting with the governance/security one that has served as a pilot for this work initially and go on from there.

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

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] CRI-O project proposal (incubation)

Nick Chase
 

+1 non-binding

On Tue, Mar 19, 2019 at 6:15 PM "Li, Xiang <x.li@...> wrote:
+1 binding


Re: [VOTE] CRI-O project proposal (incubation)

Li, Xiang
 

+1 binding


Re: [VOTE] CRI-O project proposal (incubation)

Sonya Koptyev <sonya@...>
 

+1 non-binding

Thanks,
Sonya

Sonya Koptyev | Director of Product Marketing and Evangelism
m: +1 425 505 0100



On Mar 19, 2019, 1:25 PM -0700, Ihor Dvoretskyi <ihor.dvoretskyi@...>, wrote:

+1 (non-binding). 

On Tue, Mar 19, 2019, 3:57 PM Chris Aniszczyk <caniszczyk@...> wrote:
The CRI-O project is being proposed as an INCUBATION level CNCF project, sponsored by Brendan Burns from the TOC: https://github.com/kubernetes-sigs/cri-o

CRI-O is a stable container runtime specifically tailored for Kubernetes. A founding principal was not "reinventing the wheel" and so the project uses shared components, refined approaches tested in production, and existing battle-tested code. Further, it is tuned for performance, stability, compatibility, and adherence to standards, particularly the Kubernetes Conformance tests. In short CRI-O is a building block of a Kubernetes cluster, to facilitate the life cycle of containers as required by the Kubernetes Container-Runtime-Interface (CRI).

CRI-O was born in kubernetes-incubator (which is now deprecated) and grew to production stable there. Some have claimed since being a kubernetes project that it is already "a CNCF project", but it is often left as an after thought in brand, awareness and support as a top-level project. This proposal is effective to promote from the kubernetes incubator a project that has fully matured.

Moving CRI-O is consistent with both the Kubernetes project direction (see helm https://github.com/cncf/toc/pull/114, for example) and with other container runtimes. The containerd CRI implementation moved from the Kubernetes project to the containerd project.

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

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] CRI-O project proposal (incubation)

Yassine Tijani <ytijani@...>
 

+1 nb


Le mar. 19 mars 2019 à 14:57, Chris Aniszczyk <caniszczyk@...> a écrit :
The CRI-O project is being proposed as an INCUBATION level CNCF project, sponsored by Brendan Burns from the TOC: https://github.com/kubernetes-sigs/cri-o

CRI-O is a stable container runtime specifically tailored for Kubernetes. A founding principal was not "reinventing the wheel" and so the project uses shared components, refined approaches tested in production, and existing battle-tested code. Further, it is tuned for performance, stability, compatibility, and adherence to standards, particularly the Kubernetes Conformance tests. In short CRI-O is a building block of a Kubernetes cluster, to facilitate the life cycle of containers as required by the Kubernetes Container-Runtime-Interface (CRI).

CRI-O was born in kubernetes-incubator (which is now deprecated) and grew to production stable there. Some have claimed since being a kubernetes project that it is already "a CNCF project", but it is often left as an after thought in brand, awareness and support as a top-level project. This proposal is effective to promote from the kubernetes incubator a project that has fully matured.

Moving CRI-O is consistent with both the Kubernetes project direction (see helm https://github.com/cncf/toc/pull/114, for example) and with other container runtimes. The containerd CRI implementation moved from the Kubernetes project to the containerd project.

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

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] CRI-O project proposal (incubation)

Ihor Dvoretskyi
 

+1 (non-binding). 


On Tue, Mar 19, 2019, 3:57 PM Chris Aniszczyk <caniszczyk@...> wrote:
The CRI-O project is being proposed as an INCUBATION level CNCF project, sponsored by Brendan Burns from the TOC: https://github.com/kubernetes-sigs/cri-o

CRI-O is a stable container runtime specifically tailored for Kubernetes. A founding principal was not "reinventing the wheel" and so the project uses shared components, refined approaches tested in production, and existing battle-tested code. Further, it is tuned for performance, stability, compatibility, and adherence to standards, particularly the Kubernetes Conformance tests. In short CRI-O is a building block of a Kubernetes cluster, to facilitate the life cycle of containers as required by the Kubernetes Container-Runtime-Interface (CRI).

CRI-O was born in kubernetes-incubator (which is now deprecated) and grew to production stable there. Some have claimed since being a kubernetes project that it is already "a CNCF project", but it is often left as an after thought in brand, awareness and support as a top-level project. This proposal is effective to promote from the kubernetes incubator a project that has fully matured.

Moving CRI-O is consistent with both the Kubernetes project direction (see helm https://github.com/cncf/toc/pull/114, for example) and with other container runtimes. The containerd CRI implementation moved from the Kubernetes project to the containerd project.

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

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] CRI-O project proposal (incubation)

Gilbert Song
 

+1 (non-binding)

On Tue, Mar 19, 2019 at 9:21 AM Erin Boyd <eboyd@...> wrote:
+1 (non-binding)

On Tue, Mar 19, 2019 at 1:57 PM Chris Aniszczyk <caniszczyk@...> wrote:
The CRI-O project is being proposed as an INCUBATION level CNCF project, sponsored by Brendan Burns from the TOC: https://github.com/kubernetes-sigs/cri-o

CRI-O is a stable container runtime specifically tailored for Kubernetes. A founding principal was not "reinventing the wheel" and so the project uses shared components, refined approaches tested in production, and existing battle-tested code. Further, it is tuned for performance, stability, compatibility, and adherence to standards, particularly the Kubernetes Conformance tests. In short CRI-O is a building block of a Kubernetes cluster, to facilitate the life cycle of containers as required by the Kubernetes Container-Runtime-Interface (CRI).

CRI-O was born in kubernetes-incubator (which is now deprecated) and grew to production stable there. Some have claimed since being a kubernetes project that it is already "a CNCF project", but it is often left as an after thought in brand, awareness and support as a top-level project. This proposal is effective to promote from the kubernetes incubator a project that has fully matured.

Moving CRI-O is consistent with both the Kubernetes project direction (see helm https://github.com/cncf/toc/pull/114, for example) and with other container runtimes. The containerd CRI implementation moved from the Kubernetes project to the containerd project.

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

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] CNCF SIGs Proposal

Brendan Burns
 

+1 binding



From: cncf-toc@... <cncf-toc@...> on behalf of Brian Grant via Lists.Cncf.Io <briangrant=google.com@...>
Sent: Tuesday, March 19, 2019 11:13 AM
To: Chris Aniszczyk
Cc: cncf-toc@...
Subject: Re: [cncf-toc] [VOTE] CNCF SIGs Proposal
 
+1 binding

On Mon, Mar 18, 2019 at 6:47 PM Chris Aniszczyk <caniszczyk@...> wrote:

Hey all, this is the formal vote for the CNCF SIGs proposal. 


There has been a long discussion on restructuring how WGs work in CNCF to help scale the community. A CNCF SIG will oversee and coordinate the interests pertaining to a logical area of needs of end users and/or projects.  Examples of such areas include security, testing, observability, storage, networking. The area overseen by a SIG is typically met by a set of CNCF projects, and may also represent a cross-cutting feature group shared by several projects (like security and observability).

A special thank you to Alexis, Quinton and many others who provided input. We will bootstrap the notion of CNCF SIGs starting with the governance/security one that has served as a pilot for this work initially and go on from there.

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

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] CNCF SIGs Proposal

Brian Grant
 

+1 binding

On Mon, Mar 18, 2019 at 6:47 PM Chris Aniszczyk <caniszczyk@...> wrote:
Hey all, this is the formal vote for the CNCF SIGs proposal. 


There has been a long discussion on restructuring how WGs work in CNCF to help scale the community. A CNCF SIG will oversee and coordinate the interests pertaining to a logical area of needs of end users and/or projects.  Examples of such areas include security, testing, observability, storage, networking. The area overseen by a SIG is typically met by a set of CNCF projects, and may also represent a cross-cutting feature group shared by several projects (like security and observability).

A special thank you to Alexis, Quinton and many others who provided input. We will bootstrap the notion of CNCF SIGs starting with the governance/security one that has served as a pilot for this work initially and go on from there.

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

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] CNCF SIGs Proposal

Eduardo Silva
 

+1 non-binding 

On Tue, Mar 19, 2019 at 11:43 AM Matt Klein <mattklein123@...> wrote:
+1 binding

On Mon, Mar 18, 2019 at 6:47 PM Chris Aniszczyk <caniszczyk@...> wrote:
Hey all, this is the formal vote for the CNCF SIGs proposal. 


There has been a long discussion on restructuring how WGs work in CNCF to help scale the community. A CNCF SIG will oversee and coordinate the interests pertaining to a logical area of needs of end users and/or projects.  Examples of such areas include security, testing, observability, storage, networking. The area overseen by a SIG is typically met by a set of CNCF projects, and may also represent a cross-cutting feature group shared by several projects (like security and observability).

A special thank you to Alexis, Quinton and many others who provided input. We will bootstrap the notion of CNCF SIGs starting with the governance/security one that has served as a pilot for this work initially and go on from there.

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

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



--

Eduardo Silva
Principal Engineer  | Arm
. . . . . . . . . . . . . . . . . . . . . . . . . . . 
m. +506 70138007
Arm.com
Treasuredata.com


   



Re: [VOTE] CNCF SIGs Proposal

Matt Klein
 

+1 binding

On Mon, Mar 18, 2019 at 6:47 PM Chris Aniszczyk <caniszczyk@...> wrote:
Hey all, this is the formal vote for the CNCF SIGs proposal. 


There has been a long discussion on restructuring how WGs work in CNCF to help scale the community. A CNCF SIG will oversee and coordinate the interests pertaining to a logical area of needs of end users and/or projects.  Examples of such areas include security, testing, observability, storage, networking. The area overseen by a SIG is typically met by a set of CNCF projects, and may also represent a cross-cutting feature group shared by several projects (like security and observability).

A special thank you to Alexis, Quinton and many others who provided input. We will bootstrap the notion of CNCF SIGs starting with the governance/security one that has served as a pilot for this work initially and go on from there.

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

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: FYI: TOC-selected seat March 2019 - Michelle Noorali

Michelle Noorali
 

Thank you all so much for the warm welcome!

From: cncf-toc@... <cncf-toc@...> on behalf of Quinton Hoole via Lists.Cncf.Io <quinton.hoole=huawei.com@...>
Sent: Tuesday, March 19, 2019 12:57 PM
To: sramji@...; Darren Shepherd
Cc: cncf-toc@...
Subject: Re: [cncf-toc] FYI: TOC-selected seat March 2019 - Michelle Noorali
 
Awesome!  Well deserved Michelle.  Great to see even more technical horsepower and passion on the TOC.

I look forward to continuing to assist the TOC in any useful way I can.  Just yell if you need me :-)

Regards

Q


From: cncf-toc@... [cncf-toc@...] on behalf of Shiven Ramji via Lists.Cncf.Io [sramji=digitalocean.com@...]
Sent: Monday, March 18, 2019 12:00 PM
To: Shannon Williams
Cc: cncf-toc@...
Subject: Re: [cncf-toc] FYI: TOC-selected seat March 2019 - Michelle Noorali

Congrats, Michelle. 
Shiven Ramji
SVP, Product



On Mon, Mar 18, 2019 at 2:57 PM Shannon Williams <shannon@...> wrote:

Thanks for all the hard work Quinton!  

 

Michelle, congratulations!

 

Best Regards,

 

Shannon Williams

Rancher Labs

shannon@...

+1 650-521-6902

 

From: cncf-toc@... <cncf-toc@...> On Behalf Of Chris Aniszczyk via Lists.Cncf.Io
Sent: Monday, March 18, 2019 6:09 AM
To: CNCF TOC <cncf-toc@...>
Cc: cncf-toc@...
Subject: [cncf-toc] FYI: TOC-selected seat March 2019 - Michelle Noorali

 

Hey all, Michelle Noorali has been selected for the TOC-selected seat:

 

We would also like to thank Quinton for all his work during his term:


The next step is for the TOC to elect a chair, if you're on the TOC and interested in running, please nominate yourself here by end of week: https://github.com/cncf/toc/issues/209

 

--

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


Re: [VOTE] CNCF SIGs Proposal

Quinton Hoole
 

+1 (no longer binding) :-)

Q


From: cncf-toc@... [cncf-toc@...] on behalf of Michelle Noorali via Lists.Cncf.Io [michelle.noorali=microsoft.com@...]
Sent: Tuesday, March 19, 2019 9:24 AM
To: Chris Aniszczyk; eboyd@...
Cc: cncf-toc@...
Subject: Re: [cncf-toc] [VOTE] CNCF SIGs Proposal

+1 binding

From: cncf-toc@... <cncf-toc@...> on behalf of Erin Boyd via Lists.Cncf.Io <eboyd=redhat.com@...>
Sent: Tuesday, March 19, 2019 11:33 AM
To: Chris Aniszczyk
Cc: cncf-toc@...
Subject: Re: [cncf-toc] [VOTE] CNCF SIGs Proposal
 
+100 (non-binding)

On Tue, Mar 19, 2019 at 1:47 AM Chris Aniszczyk <caniszczyk@...> wrote:

Hey all, this is the formal vote for the CNCF SIGs proposal. 


There has been a long discussion on restructuring how WGs work in CNCF to help scale the community. A CNCF SIG will oversee and coordinate the interests pertaining to a logical area of needs of end users and/or projects.  Examples of such areas include security, testing, observability, storage, networking. The area overseen by a SIG is typically met by a set of CNCF projects, and may also represent a cross-cutting feature group shared by several projects (like security and observability).

A special thank you to Alexis, Quinton and many others who provided input. We will bootstrap the notion of CNCF SIGs starting with the governance/security one that has served as a pilot for this work initially and go on from there.

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

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: FYI: TOC-selected seat March 2019 - Michelle Noorali

Quinton Hoole
 

Awesome!  Well deserved Michelle.  Great to see even more technical horsepower and passion on the TOC.

I look forward to continuing to assist the TOC in any useful way I can.  Just yell if you need me :-)

Regards

Q


From: cncf-toc@... [cncf-toc@...] on behalf of Shiven Ramji via Lists.Cncf.Io [sramji=digitalocean.com@...]
Sent: Monday, March 18, 2019 12:00 PM
To: Shannon Williams
Cc: cncf-toc@...
Subject: Re: [cncf-toc] FYI: TOC-selected seat March 2019 - Michelle Noorali

Congrats, Michelle. 
Shiven Ramji
SVP, Product



On Mon, Mar 18, 2019 at 2:57 PM Shannon Williams <shannon@...> wrote:

Thanks for all the hard work Quinton!  

 

Michelle, congratulations!

 

Best Regards,

 

Shannon Williams

Rancher Labs

shannon@...

+1 650-521-6902

 

From: cncf-toc@... <cncf-toc@...> On Behalf Of Chris Aniszczyk via Lists.Cncf.Io
Sent: Monday, March 18, 2019 6:09 AM
To: CNCF TOC <cncf-toc@...>
Cc: cncf-toc@...
Subject: [cncf-toc] FYI: TOC-selected seat March 2019 - Michelle Noorali

 

Hey all, Michelle Noorali has been selected for the TOC-selected seat:

 

We would also like to thank Quinton for all his work during his term:


The next step is for the TOC to elect a chair, if you're on the TOC and interested in running, please nominate yourself here by end of week: https://github.com/cncf/toc/issues/209

 

--

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


Re: [VOTE] CNCF SIGs Proposal

Michelle Noorali
 

+1 binding

From: cncf-toc@... <cncf-toc@...> on behalf of Erin Boyd via Lists.Cncf.Io <eboyd=redhat.com@...>
Sent: Tuesday, March 19, 2019 11:33 AM
To: Chris Aniszczyk
Cc: cncf-toc@...
Subject: Re: [cncf-toc] [VOTE] CNCF SIGs Proposal
 
+100 (non-binding)

On Tue, Mar 19, 2019 at 1:47 AM Chris Aniszczyk <caniszczyk@...> wrote:

Hey all, this is the formal vote for the CNCF SIGs proposal. 


There has been a long discussion on restructuring how WGs work in CNCF to help scale the community. A CNCF SIG will oversee and coordinate the interests pertaining to a logical area of needs of end users and/or projects.  Examples of such areas include security, testing, observability, storage, networking. The area overseen by a SIG is typically met by a set of CNCF projects, and may also represent a cross-cutting feature group shared by several projects (like security and observability).

A special thank you to Alexis, Quinton and many others who provided input. We will bootstrap the notion of CNCF SIGs starting with the governance/security one that has served as a pilot for this work initially and go on from there.

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

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

4681 - 4700 of 7724