Shane Curcuru - Ignite OSCON 2014
summary
Argues that a project's brand drives adoption and contributors more than technical merits, citing 150+ Apache projects and trademark/branding policy work as the tool that shapes external stories. Gives examples: choosing a JavaScript stack by reputation (Node or jQuery) rather than exhaustive evaluation, and the cloud comparison Apache CloudStack vs OpenStack to show brand reach versus install counts. Warns that governance splits — code contributors vs company-owned trademark — create conflicting images (yellow vs green elephant) that hurt growth.
AI-written summary · about
chapters (4)
- 0:00Start
- 0:10Why Your Projects Brand Is More Important than the Code
- 2:31Network Effect
- 3:20How Do You Optimize Your Eval Process
related talks
27mKeeping the flame alive: storytelling for open source
15mWhat brand design can learn from software developments
20mPretend it’s a Movie: How to Build Excitement for Your Apache Project
52mHow Indie Developers Can Polish Their Branding
23mHow to build a community brand
01h 01mBranding Is Your Secret Weapon!
24mBranding for tech Startups: how to turn products into Brands
28mMaking a Splash with your Open Source Project