Designed for Longevity: Why Mature Open Source Projects Need a Culture of Mentorship
summary
WordPress has 20 years of history, tens of thousands of contributors across ~22 teams, and roughly 5–800 code contributors per release, yet newcomer retention is weak. A Contributor Mentorship Program pilot runs four weeks with 13 mentor‑mentee pairs using self‑directed courses on learn.wordpress.org; results show some mentees becoming active and a few getting core props. The ongoing Five for the Future pledge lists ~200 companies, ~50% doing high‑impact work and about 60% inactive, so mentorship and dedicated resources become the proposed solution.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:50WordPress maturity challenges
- 3:58Diverse contributors
- 6:27Retention and gaps
- 9:57Five for the Future origins
- 11:26Company pledges impact
- 13:35Burnout and mentorship
- 15:02WordPress long-term survival
- 16:27Mentorship report insights
- 17:34Mentorship pilot program
- 21:06Program creation
- 22:32Matching mentors
- 24:20Building awareness
- 25:27Next steps expansion
- 27:33Encouraging mentorship
- 28:38Q&A
- 29:26Workshop content
- 31:14Cohort size aspirations
- 32:18Mentorship culture training
- 35:51Five for the Future relationship
related talks
19mSponsored Session: Open Source Leadership in Practice: How WordPress Builds the...
14mMentorship as a Pathway to Open-Source Project Sustainability
36mWho Will Maintain the Future? Tackling the Graying of Open Source Software
27mHow to Grow and Mentor an Open Source Community
39mPanel Discussion: The Mentoring Effect: Measurin...
26mFostering a Diamond in the Rough: Being a Good Mentor in Open Source
36mBuilding Mentorship Opportunities at Your Open-source Organizations
36mScaling Non-Traditional Contributor Mentoring Initiatives - Paris Pittman, Google