When the Worst Happens: Moving Forward After the Unexpected Death of a Core Organizer
summary
A core organizer dies by suicide ten weeks before the event and the team keeps the conference more or less on schedule, uses existing event processes to co-run a celebration of life, and secures communal assets because the organizer left passwords and login credentials. The concrete lessons: document where domains/code/accounts live, set up an enduring legal home or transfer plan, get a will for creative and community work, and rebuild social ties beyond contribution metrics to reduce burnout and fragility.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 2:24Open Source Bridge
- 6:35Unexpected Death
- 7:26Moving Forward
- 10:07First Impressions
- 10:43Ego
- 16:52Millennium Trilogy
- 17:37Neil Gaiman
- 19:34Vocation vs Hobby
- 20:15Free Software Foundation
- 20:39Apache Foundation
- 21:08Open Source Production
- 23:02Open Source Development
- 23:38Why Open Source
- 24:15My Experience
- 26:24Organizations Benefit
- 28:13Individuals Benefit
- 33:06Bonus Points
- 34:59Missing Names
- 36:02Angels in America
related talks
18mSupporting employees through redundancies and business closures
28mThe Graceful Exit: Approaches for Changing One's Role in an Open Community
25mCultural post mortems: an approach to learning and recovering when your people systems fail
20mPost Mortem Culture: Learning from Failure
43mThe 10 Commandments of Community Organizing
36mWhat Part of "... for Life" Don't You Understand?
40mHow to stay excited in a world that is falling apart
26mStress Testing Your Code of Conduct in Production