Google replaced Git tags for certain source code with obtaining via Google Drive

If you're like me and struggled to parse the title, my understanding is, "To obtain certain source code from Google, you could previously reference git tags, but now you have to fill out a form and wait for a human to give you a google drive link."

Relevant: https://keepandroidopen.org/

> Starting in 2027*, a silent update, nonconsensually pushed by Google, will block every Android app whose developer hasn't registered with Google, signed their contract, paid up, and handed over government ID.

“In violation of GPL” is a stretch.

Can’t imagine Google is making the process of obtaining source code easier on themselves though.

Android has always been more source-open than “open source”. The vast majority of community contributions that make it into the codebase are security fixes and small bug fixes.

Everything else is essentially all the work of Google and (to some extent) Samsung.

> Google replaced pushing Git tags for certain source code with obtaining source code via Google Drive after making a request through Google Forms. It's completely ridiculous and they've gradually become very slow at handling requests. They're in clear violation of the GPLv2 now.

Give them a few years and they'll only provide it by printing out a copy and mailing it to you.

isn't this just malicious compliance? not clear how this would violate GPLv2?

GPL says that you can give that link to anyone you want.

If someone on HN has received one of these links, feel free to post it here.

Can't help but wonder if making it costly for themselves the entire point. So that they can later turn around and bill that distribution fee to the recipient.

Can someone explain what this means? Am not familiar with the terminology

Every year a new low.

Yo Louis Rossmann, do your thing!

hanlon's razor comes to mind. which trees are these? weird device trees that have complicated third party licensing nonsense attached?

i remember jumping through crazy hoops to interact with a google open source project years ago. i wouldn't be surprised if it's just megacorp bureaucracy.

It's a bit unclear what this is about exactly. What releases are we talking about? How git tags come into play here?

That's like this fun fact where Microsoft needs to send you source code via post when you mail them a 5$ check. lol

This is a direct consequence of their loss to Epic. They saw Apple win because they didn't have any competition to stifle, and they want the same. Pretty shit.

I really don't understand the thought process here.

Judging by public statements, Google is one of the 3 big western AI companies. Surely they should be rolling in cash and working hard towards AGI.

And yet, for whatever reason, they can't help themselves from further restricting user freedoms on Android. Why?

I don't want to be conspiratorial, but surely it's not money, right? It has to be control. Someone high up at Google just seems to resent people having control over their own devices.

The era of big tech cooperation around free software is obviously over.

Those kind of moves are petty but there are worst tricks they can pull unfortunately.

It seems Grapheneos is the rare actor willing to put up a fight nowadays, and their "partnership" with Motorola seems to be a first step. They need to ensure a hardware platform.

My guess is at some point they will have to fork AOSP, just because Google will take it in directions that go against Grapheneos principles.

Google needs to lose in court here. This company is getting more and more evil by the day.

Source code of which components is that? It's not very clear from the mastodon thread.

Shameful acts.

I have feeling that is related to their upcoming changes that make sideloading harder

I think leadership in Google is getting worst day by day. The main reason to use Android is mostly sideloading and open source and they are trying to sabotage both.