You’ve probably noticed that “open source” has become the tech industry’s favorite buzzword—a badge of honor worn by giants to dodge antitrust scrutiny and look friendly. But if you actually try to use the source code, you’ll quickly realize the gates are closing.
Take Android. For years, we’ve operated under the assumption that Android is the open alternative to Apple’s walled garden. But recently, the team at GrapheneOS noticed something chilling: Google has quietly stopped pushing Git tags for certain Android source code components. Instead of simply pulling the code from a repository, developers now have to submit a request via a Google Form and wait for someone to manually hand over the files via Google Drive.
Open source isn’t a marketing slogan; it’s a legally binding social contract. And Google just defaulted on it.
At first glance, this looks like sheer laziness. You might think, “Oh, Google is just cutting corners,” or “It’s a compliance slip.” But if you look closer, the narrative shifts. You don’t replace a globally accessible, one-click Git clone with a bureaucratic Google Form by accident. You do it when you want to see exactly who is building on your lawn.
By moving from an automated, decentralized distribution model to a manual, centralized approval process, Google has installed a tollbooth right in the middle of the open source highway. It’s a strategic choke point. They aren’t just slowing down access; they are actively profiling who wants the code. Custom ROM builders, independent security researchers, and potential competitors now have to identify themselves and ask for permission to build on a platform that was supposedly built for everyone.
You don’t accidentally replace a Git tag with a Google Form. You do it when you want to audit every developer who dares to fork your empire.
Let’s be clear about what this means for you. If you develop apps, if you care about digital privacy, or if you just use an Android device, this trend threatens the very freedom that made Android valuable. The GPLv2 license doesn’t just exist to make lawyers happy; it ensures that the code running our lives is transparent and accountable. When a company buries that code behind a wall of red tape and slow human handlers, they aren’t just violating the spirit of the license—they are eroding the trust of the community that built their empire.
The community has always been Android’s greatest weapon against Apple. Independent developers find the bugs. Security researchers patch the vulnerabilities. Custom builders push the OS to its limits. But you can’t build a community on a foundation of forms and red tape.
A platform that requires you to beg for its source code isn’t open. It’s just a proprietary empire wearing a GitHub mask.
Google is betting that you won’t care. They’re betting that the inconvenience is small enough to ignore, and that developers will just fill out the forms and comply. But if we accept this bureaucratic bottleneck as the new normal, we are giving every tech giant a blueprint for how to kill open source without ever closing a repository. They don’t need to lock the doors anymore; they just need to make you wait in line.
FAQ
Q: Isn't this just Google being lazy with their internal tools?
A: No. You don't replace a globally accessible Git tag with a manual Google Drive request form by accident. It's a calculated bottleneck. Google knows exactly who requests code when there's a paper trail, giving them unprecedented visibility into potential competitors and custom ROM builders.
Q: Does this actually violate the GPLv2 license?
A: It's a legal gray area, but it violates the spirit of the license. GPLv2 guarantees access to corresponding source code. Forcing developers to wait on a human to approve a Google Form creates a barrier that effectively chills the freedom to modify and distribute.
Q: Why would Google sabotage their own developer ecosystem?
A: Because an empowered developer ecosystem creates forks and competition. Google doesn't want a thriving community of custom Android builds; they want a monoculture where they control the timeline, the features, and the data. Restricting source access starves the competition.