Google has stopped pushing Git tags for some Android source code (grapheneos.social)

Article summary

The article discusses Google's new method of distributing source code for certain products, which involves requesting access through a Google Form and downloading the code from Google Drive. This change has raised concerns about compliance with the GPLv2 license. The previous method of pushing Git tags has been replaced, and the new process is seen as slower and more cumbersome. The impact of this change on open-source projects and the tech community is being debated.

Main themes

• GPLv2 compliance
• Open-source distribution
• Google's stewardship
• Software licensing
• Community impact
• Technicality vs. spirit of the law

What commenters say

• Google's new method of distributing source code may be in violation of the GPLv2 license due to the requirement to use Google Forms and Drive.
• The GPLv2 license does not specify a time limit for compliance, but Google's slow response to requests may be considered unreasonable.
• The use of Google Drive to distribute source code is not a violation of the GPLv2 license, as it is a medium that can be used for software distribution.
• The GPL license is intended to ensure that distributors share and share alike, and Google's actions may be seen as not meeting this spirit.
• The change in distribution method may be seen as a deliberate attempt to make it more difficult for users to access the source code.
• The GPLv2 license allows for a fee to be charged for distributing the source code, but it does not specify how the distribution should be handled.
• The issue is not about the technicality of the license, but about Google's stewardship of open-source projects and its impact on the community.
• The compliance with the GPL license should be tested by requesting the source code and seeing how Google responds.