What being a Biker Gang Investigator taught me about FOSS
summary
Argument: open source culture mirrors outlaw biker norms in concrete ways — shared thumbs up/thumbs down rituals, visible reputation as three-piece patch style patches and stickers, and formal codes that govern behavior. Examples: GitHub PRs, forks and emergency patches (Spectre/Meltdown coordination across projects and cloud providers) are real-world tools used successfully; community triage rolled out emergency fixes. Surprising data point: a stunt analogy of 275 jumps with 260 landings illustrates realistic failure rates and maintainer burnout. Practical note: licensing and attribution matter; make sure to maintain thyself.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:01Shared community values
- 2:06Camaraderie and brotherhood
- 3:53Roles, hierarchy, and names
- 8:16Identity and sponsorship
- 9:13Common lingo
- 10:08The DIY spirit
- 11:07Modification and innovation
- 13:19Patches and symbols
- 16:25Knowing your limits
- 19:11Codes of conduct
- 20:43Conflict and governance
- 23:30Contribution and inclusivity
- 25:13Authentic participation
- 26:44Leaving the community
- 28:46Q&A session
related talks
31mOperationalizing Open Source Projects: When the Rubber Meets the Road
34mFOSS like a Boss!
18mOpen Source Like A BOSS
22mLessons from HasGeek's FOSS Journey
25mLessons Learned from Cultivating Open Source Projects and Communities
27mWhat Is Open Source & Why Do I Feel So Guilty?
36mEverything I needed to know about open source, I learned from punk rock
35mThe Benefits and Pitfalls of OSS Project Metrics: Measuring Health and Risk in Open Source Communities