Best practices and (very) small projects
summary
Most popular open source packages show one-maintainer majority — Josh Bracha’s sample of 13,000 repos has single-collaborator projects nearly as many as all others combined — so recommended practices shift to lightweight tactics: use tracer bullet development (outside‑in APIs with mock data), keep a public Kanban as a to‑do and coordination board, prefer quick string edits and README expectations over heavyweight UX hiring, and run guerrilla-style user checks and targeted grants to fund peer coaching.
AI-written summary · about
chapters (14)
- 0:00Introduction and context
- 1:12What are small projects
- 3:59Why methods don’t fit small teams
- 6:06Who creates professional methods
- 9:20Practical tactics for small projects
- 12:54Design and usability tips
- 14:15Scalable and accessible advice
- 15:20Summary and outlook
- 16:45Q&A on support and tactics
- 18:28Rules of thumb in open source
- 19:54Documenting project expectations
- 21:19Avoiding burnout in maintenance
- 22:02Tactics for project clarity
- 22:44Encouraging architecture docs
related talks
27mManaging A Healthy GitHub Community
29mDon't Be A Hero: Sustainable Open Source
46mMove Slow and Try Not to Break Each Other
27mDesign Your Open Source Project
25mLessons Learned from Cultivating Open Source Projects and Communities
34mBeing Your Best Asset and Not Your Worst Enemy
36mThe Feedback Loop: Growing healthy open source projects
49mCommunities Over Code: How to Build a Successful Project