Alexis - since you mentioned that PaaS and serverless isn't in scope, in your opinion, does this mean that you see defining how to deliver a "serverless app" as something distinct from a "PaaS app" or

Yep, they are.

As long as app templates are part of the SIG, then it should be fine. Just need to be explicit with the charter (the name at least caused me a little confusion). I agree don't go too broad

Jeff I think the intent is already pretty broad, including app templates and so on (eg Helm), plus various pieces of the CD pipe, plus supporting dev tools. IMO stuff like PaaS & serverless is out

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

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

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:

Here's a friendly reminder that we meet

+1. This does seem to be going in the right direction. Thanks

I thought I had already voted but apparently sent it just to Chris. I can't email. For the record: +1 binding!

+1. Do it. Sent from the virtual desk of Chris Didato. (Please excuse the brevity and any typos).

Excellent points! I'd love to see more auto transcription if that is feasible.

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'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

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

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

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

+1 non-binding

Very good point! Suggestions on this (or pointers to existing examples) would be welcome and super-helpful

+1 non-binding