Don't Be an A**hole
summary
Ruby is mature and attracting newcomers but community behavior and maintenance practices block growth: public Twitter bashing and a Ruby-dramas feed shame a new author, a rude issue about the devise gem shows tone problems, and a fix for the earthquake gem sits unmerged for nearly a year until a talk forces action. Concrete remedies include contributing.md files (GitHub surfaces them on PRs), novice/intermediate/advanced labels on issues, written handbooks, recruiting co‑maintainers, and an open source Manifesto for community norms.
AI-written summary · about
chapters (9)
- 0:00Introduction and context
- 0:55Ruby community history and growth
- 3:22Community culture and respect issues
- 8:19Maintaining open source projects
- 11:49Learning from other communities
- 14:57Mentorship and collaboration
- 17:23Practical solutions for better projects
- 22:36Open Source Manifesto proposal
- 23:47Q&A and closing remarks
related talks
30mOccupy Ruby: Why We Need to Moderate the 1%
48mJudging a book by its cover - how inclusive is your community?
23mDecoupling From (Bad) Shibboleths in the Software Developer Community
13mBuilding an Inclusive, Diverse Community From the Ground Up
35mPanel: Developer Happiness through Getting Involved
18mOpen Open Source
32mBuilding inclusive Open Source communities
38mAddressing sexism to build a better Ruby community