So You Want to Open Source Your Project? Hold Your Horses!
summary
Argues that going open source requires explicit choices about community, licensing and productization, not just tossing code online. Uses a concrete case: Enarx is written in Rust, donated to the Confidential Computing Consortium, and spawned a startup (Profium) that burned VC funding; core runtime is Apache 2.0 while service components use LGPLv3 and community utilities use Apache 2.0. Recommends joining ecosystems (ByteCode Alliance, Rust), keep copyright control, treat releases as supported products with reproducible builds and security patching.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 3:57Open source mistakes
- 5:05Success vs control paradox
- 6:11Strategic fit
- 8:28Software types
- 10:15Monetizing open source
- 13:31Open source licensing
- 17:12Licensing and business
- 17:33Copyright and patents
- 20:08Building communities
- 23:45Ecosystem responsibility
- 26:37Open source foundations
- 31:22Preparing for release
- 31:45Enarx project overview
- 33:14Enarx licensing
- 35:01Engaging communities
- 36:05Balancing needs
- 37:35Security considerations
- 39:27Next steps
- 41:18Q&A
related talks
55mOpen source is just about the source, isn't it?
01h 03mThe Value of Open Source
50mRunning a Successful Open Source Project
47mHow to Turn Your Open Source Project Into a Company
23mInvesting in Open-Source
14mBuilding an Open Source Strategy Before Building Your Product
27mDesign Your Open Source Project
23mGrowing A Successful and Sustainable Project