Building an Open Source Strategy Before Building Your Product
summary
Embark Studios builds its open source strategy before product release and claims that starting early yields hiring, reputation, and ecosystem advantages. Specific moves include open source by default, public tooling in Rust, hired two engineers dedicated to OSS, monetary sponsorships and a Blender sponsorship, and projects that now depend on 500 dependencies. Results reported: faster community feedback, clearer partnership paths, easier hiring of Rust engineers, and an established brand association with game dev and Rust.
AI-written summary · about
chapters (8)
- 0:00Intro
- 1:02The developer ecosystem
- 2:25embark Embark Studios
- 4:13Building a product team
- 6:43Parts of an open source strategy How do we support people working on open source? Monetary sponsorship, skills/time? How do we contribute to open source? Open sourcing everything, writing posts, sharing knowledge? How do we communicate with the ecosystem? • Discussion forums, use cases, idea exchange?
- 8:14Open source by default Lead the conversation Support strategically
- 10:39Results What does the community think?
- 13:37Let's thrive together
related talks
35mOpen Source as a Product: Strategies for Building and Scaling Successful Open Source..
43mSo You Want to Open Source Your Project? Hold Your Horses!
25mProduct Strategies from Open Source
48mLessons Learned from Open Source in Business
23mThe Open Source Journey of the Most Unlikely Participant
33mBuilding an OSS-Centric Company (and Why You Want To)
27mOpen Source: Supporting, Contributing and Evangelising
48mBeyond OSPOs - Build a Strategic Open Source Business Unit