Prometheus Governance 2.0: A Case-study in Evolving the Governance With Gr...
summary
Prometheus moves from a single-tier team to a three-role model: contributor, member, and maintainer; membership requires 20 contributions in 12 months (with exceptions for talks/blogs) and grants voting rights. Members elect a 5–7 member steering committee (staggered two-year terms, max two per company) that delegates security, releases and subproject maintainers. The committee-election algorithm is still unresolved; the project already invited dozens of eligible members to bootstrap the new governance and aims to scale membership substantially.
AI-written summary · about
chapters (12)
- 0:00Prometheus governance evolution
- 1:06Becoming a team member
- 4:20Early governance model
- 6:46Challenges with governance
- 8:09Flaws in governance v1
- 10:38Designing Governance 2.0
- 13:25Steering committee model
- 15:32Three roles and criteria
- 17:17Committee structure and voting
- 18:44Current status and next steps
- 20:50Lessons for open-source projects
- 21:51Q&A
related talks
06mNew Prometheus Governance
03mPrometheus 3.0 release coordination
03mPrometheus Adoption Numbers
06mLightning Talk: Prometheus Bug Scrub
23mGood Governance Practices for Healthy Open Source Projects
18mMaking Prometheus even more open
10mTossing Our Caps: gRPC Governance Changes and the Path To CNCF Graduation
46mOpenTelemetry Governance Panel