Contributor Growth Strategies for OSS Projects
summary
Maintainer burnout is common and sustained contributor growth requires concrete investments: document governance and onboarding so new contributors can spin up a dev environment and run tests, create a contributor ladder with roles/requirements/privileges to promote reviewers into maintainers, track metrics like backlog, contributor cohorts and bus factor, and prototype permission automation with a GitHub Actions prototype (prow scales but is heavy). Start small—an hour a week on onboarding often pays off.
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker background
- 2:35Challenges of contributor growth
- 4:44Long-term growth strategies
- 7:30Governance and clear rules
- 10:44Onboarding documentation importance
- 12:50Diversity and inclusion in OSS
- 13:51Contributor ladders for leadership
- 15:55Leadership selection processes
- 17:18Mentoring and scaling contributors
- 19:24Strategic focus and metrics
- 24:00Resources and final thoughts
- 26:30Q&A on balancing contributor work
related talks
41mContributor Growth Strategies for OSS Projects
40mContributor Growth Strategies for OSS Projects
35mFrom Storming to Performing: Growing Your Project's Contributor Experience
21mLeading and Growing an Open Source Comunity
42mBuilding On-Ramps for Non-Code Contributors in Open Source
44mBuilding On-Ramps for Non-Code Contributors in Open Source
34mBreaking Out of the Open Source Burnout Cycle
36mWho Will Maintain the Future? Tackling the Graying of Open Source Software