Date   

Re: [VOTE] CNCF SIGs Proposal

alexis richardson
 

+1 binding


On Tue, 19 Mar 2019, 02:55 Doug Davis, <dug@...> wrote:

Aside from the typo [1], +1 non-binding


[1] https://github.com/cncf/toc/pull/194/files#r255297017


thanks
-Doug
_______________________________________________________
STSM | IBM Open Source, Cloud Architecture & Technology
(919) 254-6905 | IBM 444-6905 | dug@...
The more I'm around some people, the more I like my dog

"Chris Aniszczyk" ---03/18/2019 09:47:59 PM---Hey all, this is the formal vote for the CNCF SIGs proposal. https://urldefense.proofpoint.com/v2/ur

From: "Chris Aniszczyk" <caniszczyk@...>
To: CNCF TOC <cncf-toc@...>
Date: 03/18/2019 09:47 PM
Subject: [cncf-toc] [VOTE] CNCF SIGs Proposal
Sent by: cncf-toc@...





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

https://docs.google.com/document/d/1mt1LH1QJgwA91A6x-DEdjg4ZOXrOnxxc1d2xhq4Hq3I/edit

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

Doug Davis <dug@...>
 

Aside from the typo [1], +1 non-binding


[1] https://github.com/cncf/toc/pull/194/files#r255297017


thanks
-Doug
_______________________________________________________
STSM | IBM Open Source, Cloud Architecture & Technology
(919) 254-6905 | IBM 444-6905 | dug@...
The more I'm around some people, the more I like my dog

"Chris Aniszczyk" ---03/18/2019 09:47:59 PM---Hey all, this is the formal vote for the CNCF SIGs proposal. https://urldefense.proofpoint.com/v2/ur

From: "Chris Aniszczyk" <caniszczyk@...>
To: CNCF TOC <cncf-toc@...>
Date: 03/18/2019 09:47 PM
Subject: [cncf-toc] [VOTE] CNCF SIGs Proposal
Sent by: cncf-toc@...





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

https://docs.google.com/document/d/1mt1LH1QJgwA91A6x-DEdjg4ZOXrOnxxc1d2xhq4Hq3I/edit

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

Xing Yang
 

+1 non-binding 


On Tue, Mar 19, 2019 at 7:17 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: [VOTE] CNCF SIGs Proposal

Ruben Orduz <orduzr@...>
 

+1 non-binding 


On Mar 18, 2019, at 10:10 PM, Davanum Srinivas via Lists.Cncf.Io <davanum=gmail.com@...> wrote:

+1 (non-binding)

On Tue, Mar 19, 2019 at 7:17 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



--
Davanum Srinivas :: https://twitter.com/dims


Re: [VOTE] CNCF SIGs Proposal

Jon Mittelhauser
 

+1 non binding 

On Mar 18, 2019, at 7:09 PM, Davanum Srinivas <davanum@...> wrote:

+1 (non-binding)

On Tue, Mar 19, 2019 at 7:17 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



--
Davanum Srinivas :: https://twitter.com/dims


Re: [VOTE] CNCF SIGs Proposal

Davanum Srinivas
 

+1 (non-binding)

On Tue, Mar 19, 2019 at 7:17 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



--
Davanum Srinivas :: https://twitter.com/dims


Re: [VOTE] CNCF SIGs Proposal

Stephen Augustus
 

+1! (non-binding)


On Mon, Mar 18, 2019, 19:06 Zhipeng Huang <zhipengh512@...> wrote:
finally ! +1 (non-binding)

On Tue, Mar 19, 2019 at 9:55 AM Justin Cappos <jcappos@...> wrote:
+1 non-binding

On Mon, Mar 18, 2019 at 9:48 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



--
Zhipeng (Howard) Huang

Principle Engineer
OpenStack, Kubernetes, CNCF, LF Edge, ONNX, Kubeflow, OpenSDS, Open Service Broker API, OCP, Hyperledger, ETSI, SNIA, DMTF, W3C


Re: [VOTE] CNCF SIGs Proposal

Zhipeng Huang
 

finally ! +1 (non-binding)


On Tue, Mar 19, 2019 at 9:55 AM Justin Cappos <jcappos@...> wrote:
+1 non-binding

On Mon, Mar 18, 2019 at 9:48 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



--
Zhipeng (Howard) Huang

Principle Engineer
OpenStack, Kubernetes, CNCF, LF Edge, ONNX, Kubeflow, OpenSDS, Open Service Broker API, OCP, Hyperledger, ETSI, SNIA, DMTF, W3C


Re: [VOTE] CNCF SIGs Proposal

Justin Cappos
 

+1 non-binding

On Mon, Mar 18, 2019 at 9:48 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


[VOTE] CNCF SIGs Proposal

Chris Aniszczyk
 

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


TOC Agenda for 3/19/2019

Chris Aniszczyk
 

Here's the agenda for tomorrow:

https://docs.google.com/document/d/1jpoKT12jf2jTf-2EJSAl4iTdA7Aoj_uiI19qIaECNFc/edit#

We will cover new TOC members, new sandbox projects, SIGs, status of cri-o, project presentation feedback and an annual review of SPIFFE/SPIRE.

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


Re: FYI: TOC-selected seat March 2019 - Michelle Noorali

Shiven Ramji <sramji@...>
 

Congrats, Michelle. 


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

Shannon Williams <shannon@...>
 

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

Erin Boyd
 

Thanks, Quinton for all your hard work. Excited for you, Michelle! Well deserved.



On Mon, Mar 18, 2019 at 3:30 PM Matt Klein <mattklein123@...> wrote:
Yay congrats Michelle and thank you Quinton.

On Mon, Mar 18, 2019 at 7:48 AM Dee Kumar <dkumar@...> wrote:
Congrats Michelle! 

On Mon, Mar 18, 2019 at 6:09 AM Chris Aniszczyk <caniszczyk@...> wrote:
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



--
Dee Kumar
Vice President, Marketing
Cloud Native Computing Foundation
@deesprinter
408 242 3535


Re: FYI: TOC-selected seat March 2019 - Michelle Noorali

Matt Klein
 

Yay congrats Michelle and thank you Quinton.


On Mon, Mar 18, 2019 at 7:48 AM Dee Kumar <dkumar@...> wrote:
Congrats Michelle! 

On Mon, Mar 18, 2019 at 6:09 AM Chris Aniszczyk <caniszczyk@...> wrote:
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



--
Dee Kumar
Vice President, Marketing
Cloud Native Computing Foundation
@deesprinter
408 242 3535


Re: FYI: TOC-selected seat March 2019 - Michelle Noorali

Dee Kumar <dkumar@...>
 

Congrats Michelle! 


On Mon, Mar 18, 2019 at 6:09 AM Chris Aniszczyk <caniszczyk@...> wrote:
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



--
Dee Kumar
Vice President, Marketing
Cloud Native Computing Foundation
@deesprinter
408 242 3535


Re: FYI: TOC-selected seat March 2019 - Michelle Noorali

Brian Grant
 

+1

On Mon, Mar 18, 2019 at 6:40 AM alexis richardson <alexis@...> wrote:
Congratulations Michelle, and thank-you very much Quinton!

On Mon, Mar 18, 2019 at 1:09 PM Chris Aniszczyk <caniszczyk@...> wrote:
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: FYI: TOC-selected seat March 2019 - Michelle Noorali

Lee Calcote
 

Thank you for your stewardship, Quinton. Congratulations, Michelle!

- Lee

Sent from my mobile


From: cncf-toc@... <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@...>
Sent: Monday, March 18, 2019 8:08:49 AM
To: CNCF TOC
Cc: Michelle Noorali
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: FYI: TOC-selected seat March 2019 - Michelle Noorali

Sarah Novotny <sarahnovotny@...>
 

well deserved, Michelle.  and, thank you for your service, Quinton!


On Mon, Mar 18, 2019 at 7:09 AM Liz Rice <liz@...> wrote:
+100!
On Mon, 18 Mar 2019 at 13:40, alexis richardson <alexis@...> wrote:
Congratulations Michelle, and thank-you very much Quinton!

On Mon, Mar 18, 2019 at 1:09 PM Chris Aniszczyk <caniszczyk@...> wrote:
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

--
Liz Rice
@lizrice  | lizrice.com+44 (0) 780 126 1145


Re: FYI: TOC-selected seat March 2019 - Michelle Noorali

Liz Rice
 

+100!

On Mon, 18 Mar 2019 at 13:40, alexis richardson <alexis@...> wrote:
Congratulations Michelle, and thank-you very much Quinton!

On Mon, Mar 18, 2019 at 1:09 PM Chris Aniszczyk <caniszczyk@...> wrote:
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

--
Liz Rice
@lizrice  | lizrice.com+44 (0) 780 126 1145