Public Technical Oversight Committee (TOC) Meeting
summary
Overview of how the TOC makes technical calls, how projects move from sandbox to incubation to graduation, and why the sandbox process is being rewritten and moved to GitHub sandbox repo to handle scaling. Notes that the TOC accepted about ~30 projects this year, flags real gaps (no standard secrets manager, weak multi‑tenancy, messy developer UX), and spotlights trends like WebAssembly and sidecar‑less approaches. Mentions upcoming TOC elections and invites community contributions and tag participation.
AI-written summary · about
chapters (12)
- 0:00CNCF TOC introduction
- 3:19CNCF organization structure
- 5:04CNCF project principles
- 7:32Getting involved via TAGs
- 8:34Project maturity levels
- 9:57Ecosystem gaps and future
- 15:21KubeCon trends and innovations
- 19:57Q&A with TOC
- 24:31Project failures and archives
- 28:32Improving sandbox process
- 32:25Matching contributors to projects
- 33:27Closing remarks and TOC elections
related talks
35mPublic Technical Oversight Committee (TOC) Meeting
41mPublic Technical Oversight Committee (TOC) Meeting
36mPublic Technical Oversight Committee (TOC) Meeting
23mOne-on-One Discussion
29mMeet the Continuous Delivery Foundation Technical Oversight Committee
13mKeynote: 221B Cloud Native Street
33mTOC Project Reviews WG: Let's Work on It Together!
26mKeynote: Welc...
