Keynote: Technical Oversight Committee Q&A
summary
Technical governance merges steering into a single Technical Oversight Committee and focuses on concrete fixes: automated release pipeline is rebuilt after Bintray sunset, producing 128, 129 releases with 130 coming soon; priorities are improving docs, restoring public SIG activity, adding integration tests and patch releases, and hardening plugin APIs via the cloud-driver API. Planned outreach includes monthly meetings, Slack governance channel and toc@spinnaker.io, a gardening week next spring, and integrations like Spinnaker operator and EKS blueprint plugins.
AI-written summary · about
chapters (11)
- 0:00Introductions of committee
- 1:03Purpose of governance board
- 6:06Plans and roadmap for Spinnaker
- 12:29Release cadence and health
- 16:04Spinnaker in modern CD landscape
- 20:37Scaling down for simpler use cases
- 21:41Engaging with the TOC
- 25:14Sharing advanced patterns
- 28:23Extensibility and plugins
- 30:52Advice for new contributors
- 35:03Closing remarks and Q&A
related talks
32mKeynote: TSC Panel
34mSpinnaker Technical Oversight Committee Panel
48mAsk Us Anything: Spinnaker Governance
13mOpening Remarks & State of Spinnaker
35mPublic Technical Oversight Committee (TOC) Meeting
36mPublic Technical Oversight Committee (TOC) Meeting
15mKeynote: CI/CD Isn't Reserved for Software!
16mSpinnaker State of the Union (Opening Keynote)
