|
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/194Remember 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
|
|
|
toggle quoted message
Show quoted text
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/194Remember 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
|
|
|
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/194Remember 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
|
|
|
Stephen Augustus
toggle quoted message
Show quoted text
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/194Remember 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
|
|
|
Davanum Srinivas
toggle quoted message
Show quoted text
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/194Remember 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
|
|
|
toggle quoted message
Show quoted text
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/194Remember 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
--
|
|
|
toggle quoted message
Show quoted text
+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
--
|
|
|
toggle quoted message
Show quoted text
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/194Remember 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
|
|
|
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/editThere 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/194Remember 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
|
|
|
toggle quoted message
Show quoted text
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/editThere 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/194Remember 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
|
|
|
Sonya Koptyev <sonya@...>
+1 non-binding.
Super excited to see this going through.
Thanks,
Sonya
Sonya Koptyev | Director of Product Marketing and Evangelism
On Mar 18, 2019, 9:02 PM -0700, alexis richardson <alexis@...>, wrote:
+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
|
|
|
+1 binding
From: <cncf-toc@...> on behalf of Sonya Koptyev <sonya@...>
Date: Monday, March 18, 2019 at 10:46 PM
To: Doug Davis <dug@...>, alexis richardson <alexis@...>
Cc: Chris Aniszczyk <caniszczyk@...>, Alexis Richardson via cncf-toc <cncf-toc@...>
Subject: Re: [cncf-toc] [VOTE] CNCF SIGs Proposal
This email is from an external sender.
+1 non-binding.
Super excited to see this going through.
Thanks,
Sonya
Sonya Koptyev | Director of Product Marketing and Evangelism
toggle quoted message
Show quoted text
On Mar 18, 2019, 9:02 PM -0700, alexis richardson <alexis@...>, wrote:
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
|
|
|
+1 binding (yay, my first binding vote!)
toggle quoted message
Show quoted text
+1 binding
From: <cncf-toc@...> on behalf of Sonya Koptyev <sonya@...>
Date: Monday, March 18, 2019 at 10:46 PM
To: Doug Davis <dug@...>, alexis richardson <alexis@...>
Cc: Chris Aniszczyk <caniszczyk@...>, Alexis Richardson via cncf-toc <cncf-toc@...>
Subject: Re: [cncf-toc] [VOTE] CNCF SIGs Proposal
This email is from an external sender.
+1 non-binding.
Super excited to see this going through.
Thanks,
Sonya
Sonya Koptyev | Director of Product Marketing and Evangelism
On Mar 18, 2019, 9:02 PM -0700, alexis richardson <alexis@...>, wrote:
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
|
|
|
toggle quoted message
Show quoted text
On Tue, Mar 19, 2019, 1:18 AM Liz Rice < liz@... wrote: +1 binding (yay, my first binding vote!)
+1 binding
From: <cncf-toc@...> on behalf of Sonya Koptyev <sonya@...>
Date: Monday, March 18, 2019 at 10:46 PM
To: Doug Davis <dug@...>, alexis richardson <alexis@...>
Cc: Chris Aniszczyk <caniszczyk@...>, Alexis Richardson via cncf-toc <cncf-toc@...>
Subject: Re: [cncf-toc] [VOTE] CNCF SIGs Proposal
This email is from an external sender.
+1 non-binding.
Super excited to see this going through.
Thanks,
Sonya
Sonya Koptyev | Director of Product Marketing and Evangelism
On Mar 18, 2019, 9:02 PM -0700, alexis richardson <alexis@...>, wrote:
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
|
|
|
Alex Chircop
toggle quoted message
Show quoted text
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
|
|
|
toggle quoted message
Show quoted text
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/194Remember 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
|
|
|
toggle quoted message
Show quoted text
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/194Remember 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
|
|
|
Angel Ramirez
toggle quoted message
Show quoted text
On Tue, Mar 19, 2019 at 11:41 AM Gary Brown < gbrown@...> wrote: +1 (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/194Remember 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
|
|
|
Geri Jennings
+1 non-binding
Excited to see this process kick off!
From: <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@...>
Date: Monday, March 18, 2019 at 9:48 PM
To: CNCF TOC <cncf-toc@...>
Subject: [cncf-toc] [VOTE] CNCF SIGs Proposal
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
_______________________________________________
This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure.
If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error.
|
|
|
+1 binding
From: <cncf-toc@...> on behalf of Liz Rice <liz@...>
Date: Tuesday, March 19, 2019 at 1:18 AM
To: "jeff_brewer@..." <jeff_brewer@...>
Cc: Sonya Koptyev <sonya@...>, Doug Davis <dug@...>, alexis richardson <alexis@...>, "cncf-toc@..." <cncf-toc@...>
Subject: Re: [cncf-toc] [VOTE] CNCF SIGs Proposal
+1 binding (yay, my first binding vote!)
toggle quoted message
Show quoted text
On Tue, 19 Mar 2019 at 06:29, Brewer, Jeff via
Lists.Cncf.Io <jeff_brewer= intuit.com@...> wrote:
+1 binding
From:
<cncf-toc@...> on behalf of Sonya Koptyev <sonya@...>
Date: Monday, March 18, 2019 at 10:46 PM
To: Doug Davis <dug@...>, alexis richardson <alexis@...>
Cc: Chris Aniszczyk <caniszczyk@...>, Alexis Richardson via cncf-toc <cncf-toc@...>
Subject: Re: [cncf-toc] [VOTE] CNCF SIGs Proposal
This email is from an external sender.
+1 non-binding.
Super excited to see this going through.
Thanks,
Sonya
Sonya Koptyev | Director of Product Marketing and Evangelism
On Mar 18, 2019, 9:02 PM -0700, alexis richardson <alexis@...>, wrote:
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
--
|
|
|
