For years, Google used an in-house Linux distribution called Goobuntu (based on Ubuntu LTS releases), as its development platform. No more.
After more than five years with Ubuntu, Google is replacing Goobuntu with gLinux, a Linux distribution based on Debian Testing.
[...] As MuyLinux reports, gLinux is being built from the source code of the packages and Google introduces its own changes to it. The changes will also be contributed to the upstream.
[...] How does Google plan to move to Debian Testing? The current Debian Testing release is upcoming Debian 10 Buster. Google has developed an internal tool to migrate the existing systems from Ubuntu 14.04 LTS to Debian 10 Buster. Project leader Margarita claimed in the Debconf talk that tool was tested to be working fine.
Google also plans to send the changes to Debian Upstream and hence contributing to its development.
[...] Back in 2012, Canonical had clarified that Google is not their largest business desktop customer. However, it is safe to say that Google was a big customer for them. As Google prepares to switch to Debian, this will surely result in revenue loss for Canonical.
(Score: 1, Offtopic) by Runaway1956 on Tuesday January 23 2018, @11:18PM
Another speculation, to go along with DannyB's?
Maybe Ubuntu is too restrictive, in some way. I can't name any, this is just speculation, after all. But, I remember making my own move away from Ubuntu, because Ubuntu was moving toward Unity. Basically, Ubuntu said, "This is the way we are going, like it or leave." So, I left. It's been years since I ran Ubuntu now, maybe they have become more responsive to the community's wishes. Maybe not. And, maybe Ubuntu has simply turned into a heap of shit - I don't know. But, I can speculate that something about Ubuntu has put a burr under Google's saddle, so they've gone upstream where there are fewer burrs.
No matter about any of that, though. If you're interested in source code, then why not go directly to the source? Some middle man's version of what the source is all about may or may not be accurate. Go to the source for the source code, and you know you've got it straight.