Treating Open Source as Core Engineering Work
At Spotify's internal engineering conference (SpEC), the company's current and future approach to open source was laid out for developers. The central message: open source efforts need to align with Spotify's internal operating principles, or projects suffer from unhealthy side effects that degrade quality and longevity.
The core argument is that meaningful open source impact requires making external work look as much like internal work as possible. Spotify has identified five key areas to make that happen.
The Five Principles
1. Establish ownership. Just as with the internal codebase, every open source project needs a clear owner. Clear ownership is the foundation for clear accountability.
2. Make ownership sustainable. Project maintenance time should be budgeted into regular working hours. Open source contributions are not meant to be an extracurricular activity reserved for evenings and weekends.
3. Be ambitious, but set goals first. Engineers should have the freedom to pursue big bets and small experiments alike, but they need to be clear about why they're undertaking a project before diving in.
4. Measure, learn, and adapt. Data-driven metrics should determine whether a project is succeeding. Not everything will work out — and that's acceptable. The preference is for a small number of high-quality projects over a large number of neglected ones.
5. Watch external dependencies. Sustainability gaps across the broader open source ecosystem pose a risk. Spotify addresses this through its FOSS fund and through direct upstream contributions.
Applying Internal Standards Externally
Spotify's engineering culture has long emphasized ownership, clear goals, data-driven decisions, and fast iteration. Those principles have helped the engineering organization scale while maintaining quality as the business grew into a platform serving hundreds of millions of listeners and tens of millions of creators.
The logic is straightforward: the same standards that work internally should apply to open source work, extending that impact beyond the company. If that standard holds, the results should show up in the quality of the projects Spotify maintains and contributes to across the ecosystem.
