Default to Open - Steps and Traps
summary
Percona (15 years) runs its own MySQL/Postgres/MongoDB builds and argues companies must pick concrete tradeoffs: choose whether bug trackers, roadmaps, salaries or engineer travel are public, measure contributors vs adoption as distinct goals, and require practical actions like a one git commit requirement for new hires. Success hinges on clear contribution guidelines, active evangelism, treating external users as team members, and small wins such as a Mattermost contributor building a snake‑feeding bot to prove adoption pathways.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 0:38Who is Matt
- 1:07Default to Open
- 1:48Matching Goals
- 2:24Why Open Source
- 3:24Different Types of Open
- 5:12Defining Openness
- 6:17Connecting People
- 6:37The fallacy
- 7:37People
- 8:59External Contributions
- 10:25Connect with People
- 11:17Willingness to Share
- 12:30Regular Contact
- 13:37Contribution Guidelines
- 14:34Alignment
- 14:50Passion
- 15:09Evangelism
- 16:17Passion and Process
- 17:13Competition
- 17:29Walk the Line
- 18:24Build Relationships
- 19:12Assumptions
- 22:07Outcomes
- 22:59Questions
related talks
15mThe Path to MySQL Open Innovation
12mContribution Over Control Open Source Responsibility in PostgreSQL
41mCreating a Profitable Open Source Company Without Venture Capital
23mChampioning Open Source Databases
42mPanel Discussion: Build a Great Business on Open Source Without Selling Your Soul
10mWhy Open Sourcing our Database Tooling was a Smart Decision
18mOpen communication for open development
22mA beginner's guide to Open Source