You Don't Need More New Contributors — You Need Onboarding That Actually Works
summary
Projects lose enthusiastic volunteers at the Git wall and on “good first” issues that lack file paths, expected outputs, or step‑by‑step setup; invisible rules (commit signing, review timelines) make people quit. Rewriting docs for true beginners with screenshots, clear who to ask and estimated time-to-complete, pairing newcomers with mentors, and committing to a 24-hour response time raises contributions noticeably — e.g., a Kiwix Hacktoberfest beginner becomes a regular contributor and eventually leads a team.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:05Onboarding vs recruitment
- 3:13Three onboarding barriers
- 7:28Why past onboarding failed
- 10:20Struggling vs successful projects
- 13:47Documentation for beginners
- 15:34Good first issue
- 18:00Mentorship pipelines
- 21:3224-hour response commitment
- 22:17Simplified onboarding success
- 24:45Onboarding must-haves
- 27:11What you don’t need
- 29:05Onboarding results timeline
- 30:31Actionable steps
- 31:59Closing thoughts
- 32:35Q&A
- 33:19Contributor feedback
- 34:42Non-technical contributors
related talks
42mBuilding On-Ramps for Non-Code Contributors in Open Source
47mThe Great Adventure of Open Source Contribution
26mOpen Source Inclusivity: Empowering Newcomers
24mSo You Want to Contribute to Open Source: ...
18mOpen communication for open development
12mHow to start contributing and still have fun
10mKeynote: How to Become an Open Source Mechanic
28mBest Practices for an Effective Open Source Contribution