Ask Us Anything: Spinnaker Governance
summary
Governance explains concrete contribution paths: use the RFC template in spinnaker/community to propose features (cloud provider RFCs live there), join SIGs for domain ownership, and expect issue triage to tag issues to SIGs instead of an auto-closing bot that closed after ~45 days. Repos add a code owners file for contact points; releases target a 6–8 week cadence with branch cut then roughly a week to validate before publishing. Work in progress items: moving build/release tooling off internal Google infra, consolidating forums to StackOverflow, and piloting a mentorship RFC.
AI-written summary · about
chapters (5)
- 0:00Start
- 1:36How Can Someone Get Involved with Spinnaker the Project Community
- 17:15Fcc Proposals
- 27:25How To Improve the Governor's Process
- 43:41What's the One Thing You Want To See Improved
related talks
29mBuild your career as a Spinnaker contributor
13mOpening Remarks & State of Spinnaker
35mKeynote: Technical Oversight Committee Q&A
23mRenaissance, Act 1: Building the Next Generation of the Spinnaker Community
34mSpinnaker Technical Oversight Committee Panel
21mWhat's Community Got to Do with It? Navigating Open Source Contributions in the Financial Industry
08mSpinnaker as Code SIG Update
16mKeynote: Ingredients for Spinnaker Success: Creating an Open Source Movement to Accele...