Behind the Scenes of Maintaining an Open Source Project
summary
Maintaining Composer and Packagist means juggling real bugs, PRs and people: a five‑year project, surprise performance wins (a change makes Composer twice as fast), scary incidents (an rm -rf mistake, death‑threats in another ecosystem), and countless small fixes that help users. Workflows matter: edit links and thank‑yous speed contributions, large messy PRs (one had 57 commits 800 lines) waste time, community events produce fan gifts and 500 comments on a celebratory thread, and issue locking or codes of conduct stop burnout.
AI-written summary · about
chapters (30)
- 0:00Intro
- 2:00Time
- 4:00WorkLife Balance
- 5:10Burnout
- 8:15Pride
- 11:25Anger
- 13:40Death threats
- 15:05Culture
- 16:05Code of Conduct
- 17:25Angry People
- 17:55Negative Feelings
- 19:30Criticism
- 20:20Not interested
- 21:05Respect
- 21:40Uncalled for
- 23:50Bumblebee
- 24:55Open Source Responsibility
- 25:40Communication
- 26:50Reporting Issues
- 28:15Communication in Public
- 29:05Micro Bubbles
- 30:25Community
- 31:00Cake
- 32:05Composer
- 32:50Contribution
- 34:10Pull Requests
- 35:05Contributing
- 35:30Troubleshooting
- 36:10Recap
- 38:20Bad Actors
related talks
39mManaging an Open Source Project
42mcomposer++
20mManaging In The Open, Managing Contributions: The challenges of OSPO developers management
24mThe Art of Open-Source Development
41mFrom Users to Maintainers - Tales from the Open Source World
43m'ProTalking' Your Way into Open Source
32mRebuilding the Cathedral
35mTending Your Open Source Garden