Interview with Chris DiBona, the Director of Open Source at Google
How open source changed Google - and how Google changed open source — INTERVIEW We chat to Google's head of open source software … Google has just celebrated its 15th birthday, and much of its success is thanks to Linux and open source software.
Context & Ripple Effects
The interview lands at an awkward moment for Google's open-source story. In October 2013, Ars Technica published its investigation into how tightly Google controls Android despite its open-source license, arguing that openness stops at the code drop while everything that matters ships through Google's own channels. DiBona's retelling of how Linux underpinned Google's first fifteen years is, in effect, the counter-narrative from inside the company.
It also caps a year in which Google made open source a legal battleground: DiBona's own blog laid out Google's position on open source and patents in March 2013, against the backdrop of the Oracle v Google Java dispute that had run since 2010. The TechRadar piece travels only modestly beyond its original publication, picked up by a handful of developer-focused accounts, which suggests the audience here is the open-source community itself rather than the mainstream.
First-order effects
- DiBona gives Google an official narrative crediting Linux and open source for its success — a direct rebuttal to the 'open source in name, controlled in practice' critique Ars Technica leveled two months earlier.
- The timing puts Google's stewardship claims on the record while the company's Android governance model and patent positions are under active community scrutiny.
Second-order effects
- Rivals and litigants like Oracle now face a Google that frames open source as core identity rather than tactic — raising the reputational stakes of any future licensing or patent confrontation, where Google can be painted as contradicting its own stated principles.
- Developer goodwill becomes a measurable asset: projects like the Tor work Google highlighted in 2010 function as proof points the company can cite when defending its openness record.
Third-order effects
- If the pattern holds, large platform companies will keep running two parallel strategies — contributing upstream for legitimacy while retaining control of distribution and key APIs — forcing the open-source community to judge firms by release processes rather than licenses alone.
- That dynamic points toward open-source participation becoming a formal corporate function with executive ownership, as it already is under DiBona at Google.
The trend: Open source at platform-scale companies is shifting from engineering culture to governed strategy, where contribution records double as competitive and legal positioning.