Open Source Leadership: What to Give Away and What to Bring In
summary
Rule of thumb: if a task demands roughly 30–40 hours a week or carries legal/security risk, move it to paid staff or contractors; if it’s edifying, optional, or benefits from enthusiasm keep it volunteer-run. Automate repetitive work; pay for payroll, taxes, design, event logistics, infrastructure and repo cleanup. Transition by creating aliases, documenting processes, staff shadowing volunteers, and publicly acknowledging contributions. Watch for single points of failure, growing backlogs, or workflows split across many people.
AI-written summary · about
chapters (13)
- 0:00Open source leadership intro
- 1:05Why projects grow unpredictably
- 2:50Respecting volunteers
- 5:40Tasks for volunteers
- 7:46What to pay pros for
- 10:18Delegation strategies
- 13:06Moving tasks to staff
- 16:36Wrong task bucket signs
- 19:02Scaling task allocation
- 22:13Giving away your Legos
- 24:22Project growth caveats
- 26:31Listening for burnout
- 28:59Q&A
related talks
45mHow to Create a Sustainable Community
49mOpen Source At Work - How Contribute On The Clock
42mBuilding On-Ramps for Non-Code Contributors in Open Source
01h 39mWorkshop: Building and Managing an Open Source Program Office
41mThe Work No One Notices—Until It’s Missing: Scaling Open Source Community Teams
30mShould I open source this code?
28mThe Graceful Exit: Approaches for Changing One's Role in an Open Community
23mOpen Source Contribution Policies that Don't Suck