For what it’s worth, I poked around in some dictionaries and thesauri, and am now even more convinced that you’re all right and Governance is not the best term. Succinct alternatives seem fairly hard

I fully expect some of the SIG names to be wordsmithed by the TOC Liaison, Chairs and other interested parties of that SIG during the chartering process, where the more detailed scope of the SIG will

From: Brian Grant <briangrant@...> Date: Friday, February 1, 2019 at 07:24 To: Quinton Hoole <quinton.hoole@...> Cc: "cncf-toc@..." <cncf-toc@...>, Erin Boyd <eboyd@r

I added the following to the main doc to clarify: "SIGs are formed by the TOC. Initial SIGs are listed below, and will be adapted over time as required. If members of the community believe that additi

Oh, now I understand where the confusion arose. There is a link in the intro of the main document to a description of the differences between Kubernetes SIGs and CNCF SIGS. That’s where the following

My apologies Diane – I just reread the Operating Model section and you’re right - it’s not sufficiently clear on the point you raised. I will add some wording to the effect of my email reply below. Re

Thanks Diane I think that’s adequately covered in the doc - the TOC creates and approves SIG’s. If anyone believes we need to create more SIG’s, they should, by implication, ask the TOC to do that. Th

Greetings to the new TOC Late last year Alexis kicked off a public discussion regarding forming CNCF SIG’s (initially referred to as Categories). Since then a few of us have collaborated on soliciting

Matt, most of the things you mention are fairly well covered by the CII Best Practices program, a basic version of which is currently a CNCF graduation requirement, as Brian detailed below. I would en

I think “production ready” has a lot to do with known, accurate and well-documented limitations, as opposed to no limitations at all, or vague claims, or an absolute set of metrics that need to be met

+1 binding Q From: <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@...> Date: Tuesday, January 15, 2019 at 09:47 To: CNCF TOC <cncf-toc@...> Subject: [cncf-

Thanks Matt Nice write-up. For me, the main high-level take-away from the session was this: Lets give attendees (primarily end users) what they’re looking for (in several dimensions). To do that, lets

SGTM. I am available to sponsor. Is there an opportunity to share further information in-person at KubeCon Seattle? Posting a link to the slide deck that was to be used in early October here would be

+1 (binding) Q From:Chris Aniszczyk To:CNCF TOC, Date:2018-11-13 00:37:29 Subject:[cncf-toc] [VOTE] Envoy moving to graduation Envoy has requested to move to the graduation maturity level: https://git

Perfect! Thanks Justin. Q From: <cncf-toc@...> on behalf of Justin Garrison <justinleegarrison@...> Date: Thursday, November 8, 2018 at 13:46 To: Quinton Hoole <quinton.hoole@...

Any and all constructive feedback on project proposals from the community is definitely encouraged. Justin, may I suggest that you add your specific questions or concerns to the PR at https://github.c

To add to what Chris said, and responding directly to: "since it would be easier to go with sandbox and then jump into incubation, than do direct to incubation (which is harder). “ The above is not th

+1 binding From:Chris Aniszczyk To:CNCF TOC, Date:2018-11-06 06:27:26 Subject:[cncf-toc] [VOTE] Harbor moving to incubation The Harbor community has requested to move to the incubation maturity level

Thanks Chris I don’t think that there’s particular urgency in manually stitching together git commits, but more importantly, according to the Charter: 18. Amendments This charter may be amended by a t

I think it’s important that we have a public record of historical changes to the charter (like the one you made below, but I’m sure there are others that came before it). Could you make that historica