Open roadmaps for your open communities
summary
Jenkins creates a public roadmap using GitHub Projects and a roadmap.yaml but the roadmap goes stale after about two years because one person owns updates (high bus factor) and contributors don’t consistently add items. The effort delivers many feature wins—checks API, Kubernetes integrations, dark theme—and produces 50 pages of contributor docs and a contributor onboarding flow, while infrastructure costs hit ~$20K/month. It fails to attract sustained company contributors and event managers, and the open roadmap becomes hard to maintain and partly obsolete.
AI-written summary · about
chapters (8)
- 0:00Introduction to open roadmaps
- 2:13What is a roadmap
- 4:43Jenkins community challenges
- 11:03Introducing Jenkins public roadmap
- 16:40What didn’t work in the roadmap
- 23:22Better roadmap practices today
- 28:41Key lessons and recommendations
- 29:44Q&A: Gaining leadership trust
related talks
21mOpen roadmaps for your open communities. Not a success story, but you may have one
29mJenkins 2022 and Beyond?
21mThe Power of Open Source Community
27mHow to Grow and Mentor an Open Source Community
16mAmazon’s Commitment to Open Source
39mManaging an Open Source Project
42mBuilding On-Ramps for Non-Code Contributors in Open Source
51mBuilding Strong and Sustainable Open Source Projects