Building On-Ramps for Non-Code Contributors in Open Source
summary
Shows concrete practices from Kubernetes and SIG Docs: mandate 5 PRs for org membership, run a twice‑year contributor summit and yearly awards, use enhancement proposals for non‑code changes, and expect three releases per year for some roles. Focuses on measurable wins—triage, docs and UX from the Tidelift maintainer survey—and operational tools: good first issues, clear role documentation and a buddy/mentoring program. Claims these reduce maintainer toil, increase stability and diversity and that emeritus/unretire paths and office hours actually work.
AI-written summary · about
chapters (20)
- 0:00Intro
- 1:36Meet Natalie
- 4:33Easier now than ever
- 5:51Accept help
- 8:13Onboarding to Open Source
- 10:45Contribution Docs
- 13:14Project Management
- 15:00Buddy Up
- 16:37Be Flexible
- 19:29Less Toil
- 21:00More Stability
- 24:00More Diversity
- 25:48Tips for Smaller Projects
- 30:47How to Encourage Recognition
- 34:24Organically
- 36:00Consistency
- 37:57Mission
- 39:22Gender Disparity
- 40:34Call Out
- 41:51The Real Problem
related talks
42mBuilding On-Ramps for Non-Code Contributors in Open Source
21mLeading and Growing an Open Source Comunity
41mContributor Growth Strategies for OSS Projects
13mOpen Web, Open Source, Open Communities
40mContributor Growth Strategies for OSS Projects
35mFrom Storming to Performing: Growing Your Project's Contributor Experience
15mMaking Meaningful Contributions to Open Source Contributions
27mNo Code Needed: From Emojis To Glory on the Contribution Ladder