Public Technical Oversight Committee (TOC) Meeting
summary
The TOC lays out concrete process changes: a 9-member TOC delegates day-to-day work to SIGs to scale decision making, uses sandbox/incubation/graduation levels with informal but variable timelines, and archives stale projects by moving IP into the LF so revival stays possible. Specific gaps called out include identity, canary tooling and service mesh interoperability—examples named are Flux and Flagger, Argo CD, Envoy, Linkerd, SMI, Spire, CNI/CSI and Keycloak—while 80+ end users push for conformance, docs and a commercial “kite mark.”
AI-written summary · about
chapters (12)
- 0:00CNCF TOC introduction
- 1:04TOC member roles
- 5:53SIG evolution and scaling
- 8:28Project archiving and sustainability
- 10:14Non-code projects discussion
- 14:54Conformance testing programs
- 18:46Community-driven SIGs
- 22:41Project onboarding process
- 25:11Balancing acceptance and growth
- 26:45CNCF’s cloud native role
- 31:51Missing cloud native projects
- 35:11Closing remarks and Q&A
related talks
35mPublic Technical Oversight Committee (TOC) Meeting
41mPublic Technical Oversight Committee (TOC) Meeting
35mPublic Technical Oversight Committee (TOC) Meeting
34mPublic Technical Oversight Committee (TOC) Meeting
29mMeet the Continuous Delivery Foundation Technical Oversight Committee
23mOne-on-One Discussion
15mKeynote: CI/CD Isn't Reserved for Software!
32mAsk the Experts: CNCF CTO and TOC Members Open Q&A