All the Things they didnt teach you at University
summary
Explains concrete habits that matter for open source: use git as the de facto workflow, pick one chat and one issue tracker, and run an automatic code formatter so nobody argues about style. Shows data: responding to pull requests within 24 hours strongly increases retention, while responses after a week make new contributors unlikely to return. Argues maintainers must share rights, document processes, enforce a code of conduct, and prioritize quick feedback and burnout prevention to keep a community alive.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 0:23Who am I
- 1:06History
- 2:39Infrastructure
- 4:06People
- 7:01Community
- 8:20Communication
- 12:10Code of Conduct
- 15:53Open Source Contributions
- 19:58Conflicts
- 21:19Open Source Maintainer
- 23:26Make your project more popular
- 25:47How to onboard people
- 28:42Dont burn yourself out
- 29:45Feedback
- 32:51Conclusion
related talks
16mThere's More to Open Source than Code
27mDesign Your Open Source Project
38mHow to bring open source to a closed community
30mHow you write matters in open source
18mOpen Source Like A BOSS
15mOpen Source Protips from the Trenches
28mBest Practices for an Effective Open Source Contribution
26mMake The Most Out Of Open Source