Managing A Healthy GitHub Community
summary
Outlines concrete practices used on Homebrew: split users into maintainers, vocal users and quiet users (medium projects have under ~10 active maintainers per month), require a Code of Conduct, keep a private maintainer chat for sensitive coordination, actively recruit new committers, push off‑topic discussion to IRC/mailing lists, and close feature requests that maintainers won’t implement. Emphasizes shipping fewer features that work reliably, resisting full rewrites, and notes abusive incidents are rare (roughly once a year) but handled strictly.
AI-written summary · about
chapters (15)
- 0:00Start
- 0:05Managing a healthy GitHub community
- 4:46maintainers
- 5:45(quiet) users
- 7:49Code of Conduct
- 9:03Private Chat
- 10:00Always Growing
- 10:51(vocal) users
- 11:24Stop Bikeshedding
- 12:40Mailing List and IRC
- 13:26Close Feature Requests
- 16:43High Quality
- 17:33No Guilt Merges
- 18:24No v2.0
- 19:363 groups
related talks
23mKeep cool and maintain an open source project
16mTop 10 tips for project maintainers
24mBest practices and (very) small projects
08mInterview with Jono Bacon
33mA Third Way For Open-Source Maintenance
28mBuilding Open Source Communities
31mMaintaining a big open source project: lessons learned
29mDon't Be A Hero: Sustainable Open Source