Open collaborations: leadership succession and leadership success
summary
A case study of the Kerbal mod index demonstrates concrete claims and fixes: an MIT‑licensed C# client (Ckan repository client) grows to 124 releases, 2,000+ mods and over 72,000 downloads, with 1,033 stars and 500+ contributors, and automates metadata ingestion within hours. A stakeholder crisis—mod authors threatening delisting—escalates when maintainers temporarily remove a critical dependency breaking many installs; resolution uses a new d‑listing policy and a rapid leadership handover that stabilizes the project.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:47KERBAL SPACE PROGRAM
- 6:29ANN SMITH
- 7:12QUESTION: HOW DOES LEADERSHIP
- 7:44CONWAY'S LAW
- 12:33FOSS TEAMS SELF-ORGANISE
- 23:33FOSS PROJECTS NETWORK
- 29:43WHERE DOES LEADERSHIP FIT IN?
- 39:43HOW CAN LEADERSHIP HELP?
- 41:29ANSWER: HOW DOES LEADERSHIP ASSIST FOSS PROJECTS TO SUCCEED?
related talks
23mScaling Open Source Communities
44mOf Queens and Other Benevolent Dictators – the Role of Succession Planning in Open Source Community
49mCommunities Over Code: How to Build a Successful Project
40mThe Accidental Maintainer: Sideways Stories Into Open Source Leadersh...
24mBest practices and (very) small projects
38mHow to bring open source to a closed community
06mOpen Source Innovation – Success Through Failure
40mJerks Are Killing Your Projects