+1

Nice idea, and very well written doc. I can't help thinking that it might promote excess and undesirable bureaucracy though, unless quite carefully scoped. Anecdotally, the most common failure modes

Agreed - makes sense. We should also merge the new sandbox proposal process into main workflow doc too: https://github.com/cncf/toc/blob/master/process/project_proposals.adoc Thanks, Alex

+1 NB. Sound logic here. - Lee

+1

Now that we have the new Sandbox application process running, it might make sense to make similar tweaks to the Sandbox annual review process too. Specifically I'd like to suggest: * Moving from

Thanks Quinton, you raise good points. The SC is indeed meant to add value to the project and not introduce bureaucracy or 'interference'. Most projects are pretty good at running themselves. We

Josh Thanks! I would like to keep this at top level (TOC) for now, to maximise the attention on it. Once the foundational principles have been established (or rejected) by the TOC, I would be very

+1 binding

+1 binding

+1 binding

+1 NB Thank you, Tina ^ ^ IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender

+1 non-binding -- Chris Short He/Him/His Web | Twitch | Twitter | LinkedIn

+1 non-binding

+1 NB

Contour has requested to join at the incubation level. (https://github.com/cncf/toc/pull/330/commits) https://lists.cncf.io/g/cncf-toc/message/4653 +1 Binding: *note: Quorum is 10 as Jeff Brewer has

+1 NB -- Erin A. Boyd Distinguished Engineer, OCTO Red Hat eboyd@...

+1 NB --Kiran Mova | Co-Founder, Chief Architect MayaData | kiran.mova@... https://github.com/openebs/openebs

+1 non-binding

+1 NB -- Brendan O'Leary Sr. Developer Evangelist | Direct +1 415.830.4859