Google has stopped pushing Git tags for some Android source code
Points and comments are a snapshot, not live.
GrapheneOS claims Google's switch to Google Drive for source code violates GPLv2.
GrapheneOS reports that Google replaced pushing Git tags for certain Android source code with a process requiring requests via Google Forms and access through Google Drive. Initially, tarballs were provided within hours; now responses often take weeks. GrapheneOS states this violates GPLv2 obligations to provide source promptly. The changes affect Pixel devices, not Motorola ones. Google previously squashed Git history before moving to Drive.
What commenters are saying
Commenters are split on whether this violates GPLv2. Some argue that a manual, slow request process is maliciously compliant but legal, noting GPLv2 allows charging for distribution. Others suggest that requiring non-free JavaScript for access could violate section 6. A correction notes the affected code is not AOSP but Pixel OS kernel drivers and other GPL/LGPL components. One commenter proposes testing compliance by having many users request source on each security update.