How to get people to use your open-source project
summary
Explains concrete criteria and tactics: require at least 1,000 engineers who need it and a year in production before asking others to depend on it, show why a technical or market insight exists, and use specific tools — clear error messages with docs links, semver and dev/prod parity, focused support channels (IRC/mailing list → Stack Overflow), and integrations. Gives examples: React’s documentation and advocacy, webpack’s code splitting tradeoff, Kafka’s ordering and production pedigree, and shows what worked and why.
AI-written summary · about
chapters (5)
- 0:00Start
- 0:01how to get people to use your open. source project
- 17:45CROSSING THE CHASM
- 20:00react is like angular.js, but we trade- off usability by non-programmers for more expressive power, maintainability and performance.
- 32:26Funding Open Source: How Webpack Reached $400k+/year
related talks
22mHow to Talk About your Open Source Project so People Get It
49mCommunities Over Code: How to Build a Successful Project
56mEffective Documentation: The Key to Open Source Growth
27mDesign Your Open Source Project
29mBeing Successful at Open Source
29mThe Open Source Development Surprise
39mTalking with Management About Open Source
20mOpen up to Open Source