What Part of "... for Life" Don't You Understand?
summary
Project governance shifts from a self-appointed Benevolent Dictator for Life model to community control after a resignation and a slow fade from core contributions The narrative names three concrete failure modes: personal burnout, lack of sustainable funding, and unchecked toxic contributors It cites paid fixes that worked like a crowdfunded migrations rewrite and a funded Django Fellowship while noting most corporations profit without paying and that toxicity drives people away leaving the project brittle
AI-written summary · about
chapters (26)
- 0:00Intro
- 3:26Django Software Foundation
- 4:39Three Things
- 5:14Burnout and Depression
- 6:22Burnout Resources
- 7:14My Burnout
- 10:56The Email
- 11:54Burnout
- 12:36Money
- 13:34Loss of Control
- 14:07Django Community
- 14:58Money in Open Source
- 15:42Working on Open Source
- 18:31Hypothesis
- 22:54Radical Solutions
- 23:13Toxic Community
- 23:35Jeremy Dunk
- 25:08Reactions
- 26:07Revolution Starts at Home
- 26:58Community Accountability
- 27:29Denial
- 30:27Legalistic Frame
- 32:03Neutrality is Unbalanced
- 32:37This Has Become Common
- 33:54Codes of Conduct
- 34:41Removing Toxic People
related talks
44mOf Queens and Other Benevolent Dictators – the Role of Succession Planning in Open Source Community
45mAvoiding Maslow’s Hammer: Or the Problem of the Birmingham Screwdriver in Open So...
15mLessons Learned from Cultivating Open Source Projects and Communities
15mWhy open source communities do(n’t) work (anymore)
23mGood Governance Practices for Healthy Open Source Projects
33mThe Death of Consequences
23mConsumption Is Fractal: Open Source...
36mThe Feedback Loop: Growing healthy open source projects