Open roadmaps for your open communities. Not a success story, but you may have one
summary
Large projects (Jenkins: ~2,500 repos, ~5,000 contributors) publish roadmaps but maintenance collapses: a custom YAML+JavaScript dashboard is built, attracts initial attention, then becomes stale with only three contributions in a year, a single maintainer bus factor and no ongoing facilitation. Dates cause harm; use horizons (now/preview/future), include docs and infra items, and prefer built-in trackers—GitHub Projects + issues and labels—over bespoke UIs to reduce upkeep and keep the roadmap actionable.
AI-written summary · about
chapters (4)
related talks
32mOpen roadmaps for your open communities
27mHow to Grow and Mentor an Open Source Community
22mYour Open Source Repo Needs A Project Manager
49mCommunities Over Code: How to Build a Successful Project
39mManaging an Open Source Project
16mMaintaining an OSS Project (Babel)
23mScaling Open Source Communities
51mBuilding Strong and Sustainable Open Source Projects
