Occupy Ruby: Why We Need to Moderate the 1%
summary
Argues for active moderation of Ruby spaces using specific actions: ban with impunity on IRC (10‑minute starts, escalate to lifetime), public shun (unsubscribe, stop reading, silent distancing), and revoke access like revoke the commit bit for team members who are misogynist or racist. Cites concrete incidents (offensive conference slides, persistent trolls, help‑vampires) and outcomes: walking out for 15–30 seconds signals disapproval and tending these “walled gardens” produces a healthier, more helpful IRC and meetup culture.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 2:33Ruby community goals
- 5:45Ruby as a walled garden
- 7:08Identifying weeds
- 10:25Trolls and sophistication
- 12:10Help vampires impact
- 13:37Crazies vs good crazy
- 15:47Handling bad behavior
- 17:11Signal to noise ratio
- 18:58Banning and shunning
- 20:45Moderating the 1%
- 22:53IRC channel moderation
- 24:36Conference incident handling
- 26:22Encouraging criticism
- 27:47Conclusion
related talks
30mDon't Be an A**hole
39mThe True Cost of Unmoderated Collaboration: A Story from the Trenches
27mWhy Open Source Fails to Protect Under-Represented Minorities
33mBuilding Compassionate Communities in Tech
05mLightning talk from Devon Lindsey
48mJudging a book by its cover - how inclusive is your community?
23mDecoupling From (Bad) Shibboleths in the Software Developer Community
27mBuilding Inclusion Through Effective Moderation