How to Disengage the Open Source Community
summary
Company open-sources enterprise features in 2011, funding a team of 8 full-time engineers and a community manager, then sees revenue crashed because customers take features but refuse to pay for maintenance. Tooling for builds, tests and docs never ships, so upstream contributors can’t effectively work. In 2017 the free cluster limit drops 64 to 3, driving hobbyist bug-finders away and prompting a fork (xcpng). Lessons: protect revenue, provide tooling, entice enthusiasts, map the whole community.
AI-written summary · about
chapters (8)
- 0:00Citrix and Xen relationship
- 3:11Upstream community tensions
- 5:17Freemium model revenue impact
- 8:32Why open sourcing fails
- 10:39Limits and contributor loss
- 14:14Supporting the full community
- 17:50Four lessons from mistakes
- 19:39Q&A
related talks
23mThe Open Source Journey of the Most Unlikely Participant
47mGame of Open Source: A Tale of Hype & Mire
29mOpen Source Contribution - How does it even work?
54mWho Pays for Open Source? A Case for Open Governance & Enterprise Contributions
15mLessons learned: Guidance on how to make open source development a success
55mBuilding Business Around Open Source Projects | Panel Discussion
01h 03mThe Value of Open Source
22mLessons from HasGeek's FOSS Journey