Generational Relay: Passing the Open Source Torch
summary
Plone documents a concrete recovery plan: 87 releases since 2001, a measured shift from single-founder control to a multigenerational model, and explicit metrics — a ~30-month ramp to full contributor and a developer half‑life of ~7.5 years (Plone ~5–6). The community funds travel and co‑working with a $25,000 sprint fund, runs hop-on hop-off mentorship and sprint-driven onboarding, tracks knowledge across mailing lists, tickets and readthedocs, and reports 18 funded sprints last year that demonstrably rebuilt momentum.
AI-written summary · about
chapters (12)
- 0:00Generational change in open source
- 3:19Plone’s origins and culture
- 8:17Plone’s community model
- 10:43Senior contributors leaving Plone
- 13:57Research on turnover in open source
- 18:09Surviving generational turnover
- 23:01New team structures for momentum
- 27:04Leadership transitions
- 31:20Successful community practices
- 34:12Rebuilding leadership skills
- 36:42Next generation of contributors
- 38:06Q&A
related talks
44mBuilding On-Ramps for Non-Code Contributors in Open Source
42mBuilding On-Ramps for Non-Code Contributors in Open Source
53mCan we optimize communities
36mDesigned for Longevity: Why Mature Open Source Projects Need a Culture of Mentorship
15mKeynote: Sustaining a Contributor Community’s Next Generation
39m5 Years, 10 Sprints, A scikit-learn Open Source Journey (Keynote)
36mScaling Non-Traditional Contributor Mentoring Initiatives - Paris Pittman, Google
37mKeynote – Naomi Ceder