Out of Maintenance Mode: Refactoring a Community
summary
Claim: putting the project into maintenance mode and pausing PR work for months lets contributors rethink structure. Action: interview ~50 top contributors, extract social vs technical debt, create a central community repo on GitHub, move synchronous chat to Slack and run biweekly video meetups with a ten-person core. Outcome: over 1,000 Slack members, 5,000+ on the mailing list, 100+ community issues documenting policies — a measurable reboot that improves coordination though it remains iterative.
AI-written summary · about
chapters (22)
- 0:00Intro
- 0:18REfactoring a Community
- 2:02100s of plugins
- 2:24maintainers
- 5:56Codified tribal knowledge
- 6:12Latent Resilience
- 6:43Community is a map of human intention
- 7:21Spreadsheet Science
- 7:59Sensu Plugins
- 8:23Technical Debt
- 8:38Social = Technical
- 10:41newcontrib_2 quit
- 15:221. No PR merges 2. Default issue reply only 3. All options on the table
- 17:01Communication
- 19:036 months later
- 23:12better perfect
- 24:46Maintenance ModeTM
- 25:071. Give it a name 2. Have a why 3. Permission to pivot
- 25:58Resiliency in stopping
- 26:23Communities Companies People
- 26:40Personal Note
- 29:11Resiliency is not persistence, it's the permission to pivot
related talks
27mManaging A Healthy GitHub Community
39mCommunity and Contributors Panel
31mMaintain Less, Mentor More: Community Building Techniques from Open Source
16mTop 10 tips for project maintainers
16mThe Open Source Community Playbook: What Works, What Doesn’t, and Why
47mProject Talk: Maintenance Update
42mBuilding On-Ramps for Non-Code Contributors in Open Source
32mRebuilding the Cathedral