Can you Market an Open Source Project?
summary
Starts by saying open source succeeds on substance then shows how a real project uses concrete marketing: an advocacy team instead of slick ads, a governance model with marketing budget to pay for conferences, an animation and booth branding, distro-neutral t-shirts, and a paid community manager who runs IRC, downloads and code reviews. Claims measurable wins: faster adoption, users reporting “two days instead of two months.” Covers tactics, channels, alliance-building and launch criteria so viewers can judge fit.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:37Agenda
- 2:32Marketing in Open Source
- 3:02Open Source Projects
- 4:23Marketing Open Source
- 8:00Open Source Marketing
- 9:52Silicon Graphics
- 10:33Red Hat
- 16:27Alliances
- 17:59How to tell the next developer
- 22:42Governance model
- 28:13Behind the scenes
- 28:39Branding
- 29:30Advocacy
- 34:58Messaging
related talks
28mOpen Source Marketing Done Right
43mPanel Discussion: Marketing is Essential (and Not Sleazy) for Open Source Projects
27mHow open source companies win
20mThe Good, The Bad, and The Data: Marketing Strategies
37mSustaining Open Source Beyond Code: The Importance of Marketing and Funding
40mHow to Open Source a Project and Possibly Not Fail While Trying
18mOpen Source Like A BOSS
47mHow to Turn Your Open Source Project Into a Company
