The Value of Open Source
summary
Argues that value lives equally in code and in the developer community, with practical advice: use GitHub/Bitbucket, choose MIT/Apache 2.0/GPL carefully, and favor modular repos to attract contributors. Cites a success: open sourcing API documentation on GitHub produced 59 new contributors and 30x growth in doc contributions in one year. Explains revenue via dual licensing and enterprise support (Couchbase model), warns of real risk — leaked AWS keys caused a $15,000 fraud.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:48What is Open Source
- 3:34Licenses
- 10:25Why Open Source
- 17:12The Value of Open Source
- 19:08The Value of the Community
- 22:17Transparency
- 24:59GitHub
- 26:31Bitbucket
- 27:11Project Management
- 28:51Open Source Wins
- 30:41Licensing
- 35:21Getting Involved
- 38:55Technical Writing
- 42:09Community Events
- 44:09Problems
- 49:11Stats
- 51:01Getting Contributors
- 55:48Questions
related talks
27mDesign Your Open Source Project
23mInvesting in Open-Source
34mConsumers To Contributors: Open Source As a Competitive Advantage
01h 01mKeynote - Open source is just about the source, isn't it?
55mOpen source is just about the source, isn't it?
05mOpen Source and Inner Source for APIs
43mFostering an Open Source Culture
27mHow open source companies win