Your Open Source Repo Needs A Project Manager
summary
Claim: an open source repo needs a project manager to turn users into contributors and prevent burnout. Concrete practices: scoped merge rights that let low‑impact PRs land with two community approvals, CI with Cargo format/clippy/test but avoid flaky checks, and org tools like labels, issue/PR templates, milestones, and project boards. Measured effects: Bevy runs with 500 contributors and ~half a dozen PRs a day and reports faster merges and clearer triage. The work built is documentation, automation, and delegated triage, and it measurably reduces backlog.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:21Your Open Source Repo Needs a Project Manager
- 3:10You Are Not the Boss
- 3:43Three Goals
- 9:26One Tip To Make Your Code More Reliable and Your Pi Is Easier To Review
- 12:14Issue and Pr Templates
- 12:42Milestones
- 14:30User Stories
- 16:55Conclusion
related talks
06mThe Open Source Baggage We Carry
27mDesign Your Open Source Project
15mHow to achieve effective Open source collaboration
20mManaging In The Open, Managing Contributions: The challenges of OSPO developers management
39mManaging an Open Source Project
42mBuilding On-Ramps for Non-Code Contributors in Open Source
44mBuilding On-Ramps for Non-Code Contributors in Open Source
28mIt's not just code: managing an open source project