|
Re: CNCF SIG "App Delivery"
Would it make sense to have a more general app sig? I'd be curious what other CNCF TOC members think. I know in general Kubernetes has tried to stay unopinionated "up the stack" but it seems unless we
Would it make sense to have a more general app sig? I'd be curious what other CNCF TOC members think. I know in general Kubernetes has tried to stay unopinionated "up the stack" but it seems unless we
|
By
Brewer, Jeff
·
#3370
·
|
|
CNCF SIG "App Delivery"
Michelle and I are pulling together a SIG for App Delivery.
Our next step: draft a charter. We'd love a few keen would-be
SIGonauts to join our chartering efforts, please! Also, we shall
figure
Michelle and I are pulling together a SIG for App Delivery.
Our next step: draft a charter. We'd love a few keen would-be
SIGonauts to join our chartering efforts, please! Also, we shall
figure
|
By
alexis richardson
·
#3369
·
|
|
[RESULT] CNCF Security SIG (APPROVED)
The CNCF Security SIG has been approved:
https://github.com/cncf/toc/pull/146
+1 binding TOC votes (7/9):
Alexis: https://lists.cncf.io/g/cncf-toc/message/3304
Brendan:
The CNCF Security SIG has been approved:
https://github.com/cncf/toc/pull/146
+1 binding TOC votes (7/9):
Alexis: https://lists.cncf.io/g/cncf-toc/message/3304
Brendan:
|
By
Chris Aniszczyk
·
#3368
·
|
|
CNCF TOC Agenda 6/4/2019
Here's a friendly reminder that we meet
Here's a friendly reminder that we meet
|
By
Chris Aniszczyk
·
#3367
·
|
|
Re: Encouraging diversity through the SIGs
+1.
This does seem to be going in the right direction. Thanks
From: cncf-toc@... <cncf-toc@...>On Behalf Of chrisdidato@...
Sent: Saturday, June 1, 2019 11:14 PM
To: Liz Rice
Cc:
+1.
This does seem to be going in the right direction. Thanks
From: cncf-toc@... <cncf-toc@...>On Behalf Of chrisdidato@...
Sent: Saturday, June 1, 2019 11:14 PM
To: Liz Rice
Cc:
|
By
H.Gaikwad@...
·
#3366
·
|
|
Re: [VOTE] CNCF Security SIG
I thought I had already voted but apparently sent it just to Chris. I can't email. For the record:
+1 binding!
From: cncf-toc@... on behalf of Chris Aniszczyk <caniszczyk@...>
Sent: Wednesday, May
I thought I had already voted but apparently sent it just to Chris. I can't email. For the record:
+1 binding!
From: cncf-toc@... on behalf of Chris Aniszczyk <caniszczyk@...>
Sent: Wednesday, May
|
By
Joe Beda <jbeda@...>
·
#3365
·
|
|
Re: Encouraging diversity through the SIGs
+1. Do it.
Sent from the virtual desk of Chris Didato. (Please excuse the brevity and any typos).
+1. Do it.
Sent from the virtual desk of Chris Didato. (Please excuse the brevity and any typos).
|
By
chrisdidato@gmail.com
·
#3364
·
|
|
Re: Encouraging diversity through the SIGs
Excellent points!
I'd love to see more auto transcription if that is feasible.
Excellent points!
I'd love to see more auto transcription if that is feasible.
|
By
alexis richardson
·
#3363
·
|
|
Re: Encouraging diversity through the SIGs
I applaud the definition of diversity as more than gender.... though we should be a bit careful about using the term "diversity of thought" (since that has emerged as a code word used by some who
I applaud the definition of diversity as more than gender.... though we should be a bit careful about using the term "diversity of thought" (since that has emerged as a code word used by some who
|
By
Sarah Allen
·
#3362
·
|
|
Re: Clarifying TOC Sponsor and Sandbox entry requirements
I'll work on adding an FAQ before next week's TOC meeting on this topic and some other things that have been in the backlog:
https://github.com/cncf/toc/issues/248
re 3 TOC sponsors, created an issue
I'll work on adding an FAQ before next week's TOC meeting on this topic and some other things that have been in the backlog:
https://github.com/cncf/toc/issues/248
re 3 TOC sponsors, created an issue
|
By
Chris Aniszczyk
·
#3361
·
|
|
Re: Clarifying TOC Sponsor and Sandbox entry requirements
Thanks Alexis! This helps a lot, but also highlights the need to get the docs to match the reality so that projects know what is going to be asked of them.
We need to get that full questionnaire for
Thanks Alexis! This helps a lot, but also highlights the need to get the docs to match the reality so that projects know what is going to be asked of them.
We need to get that full questionnaire for
|
By
Liz Rice
·
#3360
·
|
|
Re: Clarifying TOC Sponsor and Sandbox entry requirements
Liz
Excellent!
Let me try to clarify our previous processes, to date.
The roles of sponsor have been very different for Incubation & Sandbox.
1) Incubation: the sponsor acts as a champion for the
Liz
Excellent!
Let me try to clarify our previous processes, to date.
The roles of sponsor have been very different for Incubation & Sandbox.
1) Incubation: the sponsor acts as a champion for the
|
By
alexis richardson
·
#3359
·
|
|
Clarifying TOC Sponsor and Sandbox entry requirements
Hello TOC folks,
We have some slightly conflicting / ambiguous documentation which I’d like to get tidied up (partly inspired by this issue).
It seems odd that Sandbox requires two sponsors but
Hello TOC folks,
We have some slightly conflicting / ambiguous documentation which I’d like to get tidied up (partly inspired by this issue).
It seems odd that Sandbox requires two sponsors but
|
By
Liz Rice
·
#3358
·
|
|
Re: [VOTE] CNCF Security SIG
+1 non-binding
By
Xing Yang
·
#3357
·
|
|
Re: Encouraging diversity through the SIGs
Very good point! Suggestions on this (or pointers to existing examples) would be welcome and super-helpful
Very good point! Suggestions on this (or pointers to existing examples) would be welcome and super-helpful
|
By
Liz Rice
·
#3356
·
|
|
Re: [VOTE] CNCF Security SIG
+1 non-binding
By
Jacopo Nardiello
·
#3355
·
|
|
Re: [VOTE] CNCF Security SIG
+1 nb :)
L.
By
Leonardo Di Donato
·
#3354
·
|
|
Re: Encouraging diversity through the SIGs
Let's do the best we can, knowing it will be flawed, and get better over time.
Let's do the best we can, knowing it will be flawed, and get better over time.
|
By
Jaice Singer DuMars <jaice@...>
·
#3353
·
|
|
Re: Encouraging diversity through the SIGs
(Even without the typo. I’ll yield the floor now.)
Roger B.A. Klorese
Senior Product Manager
SUSE
705 5th Ave S, Suite 1000
Seattle WA 98104
(P)+1 206.217.7432
(M)+1
(Even without the typo. I’ll yield the floor now.)
Roger B.A. Klorese
Senior Product Manager
SUSE
705 5th Ave S, Suite 1000
Seattle WA 98104
(P)+1 206.217.7432
(M)+1
|
By
Roger Klorese <roger.klorese@...>
·
#3352
·
|
|
Re: Encouraging diversity through the SIGs
Thanks. As a Jewish (and raised before we were as widely viewed as “white”) white-skinned not entirely cis queer person, I wonder whether we need to compete for the allotted seats at the table,
Thanks. As a Jewish (and raised before we were as widely viewed as “white”) white-skinned not entirely cis queer person, I wonder whether we need to compete for the allotted seats at the table,
|
By
Roger Klorese <roger.klorese@...>
·
#3351
·
|