Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google has stopped pushing Git tags for some Android source code

grapheneos.social

Post reply on HN
Print view View original

331–340 of 350 posts

Re: Google has stopped pushing Git tags for some Android source code

#331

Post by account42 »

e12e wrote: post #304
chinathrow wrote: post #192

Earlier quoted context omitted.

> They need to do it in a reasonable amount of time. If they did that for years within hours and if we look at the tools available today, I would expect that "reasonable" equates to how they provided it prior: fast.

There's no reasonable delay. The source code needs to exist before binary distribution. When google distribute the compiled code to me, I assume the source is already available. If distribution means I buy a phone with compiled code, I expect the sources to be readily available. I distribution means my phone download updated software - I expect the code to be available. Only lasts until google pushes out gpl in favou…

GPL does explicitly allow for only providing source code on request. But of course that doesn't mean you can arbitrarily delay responses to such requests.

Re: Google has stopped pushing Git tags for some Android source code

#332

Post by account42 »

bulder wrote: post #189
steve1977 wrote: post #180

Earlier quoted context omitted.

> GPL doesn't set a standard time limit for providing the sources, but that doesn't mean they can delay it indefinitely. I wonder actually what a court would say here and if "doesn't set a time limit" could mean "the source needs to be made available immediately". IANAL.

A reasonable interpretation would be that they had a previous process that eliminated delivery latency and required no manual manpower for responding, so changing it has been done to induce artificial friction, against the intent of the license. Not that the intent of a license can be enforced.

> Not that the intent of a license can be enforced.

Why can't it? A license is not just a piece of text but a meeting of minds.

Re: Google has stopped pushing Git tags for some Android source code

#333

Post by account42 »

TheCoelacanth wrote: post #315
grapheneos wrote: post #114

They stopped pushing tags for any of the Pixel kernel or userspace driver repositories to AOSP. They also stopped pushing AOSP releases specific to Pixels which is why AOSP now only gets yearly releases, QPR2 releases and security backports to both of those. Other OEMs use the yearly and theoretically also the QPR2 releases. Both the yearly and QPR2 releases get monthly security backports. Since they dropped Pixel su…

Arguably, they aren't even distributing the source code at all anymore. The GPL defines "source code" as "the preferred form of the work for making modifications to it". I would be willing to bet any amount of money that no Google developer makes modifications using a tarball that's missing commit history. The preferred form for making modifications is a source control repository.

While it would be nice if it worked that way, I think there are too many historical examples of tarball distribution of GPL code to make that argument.

Re: Google has stopped pushing Git tags for some Android source code

#334

Post by goda90 »

Ohentis wrote: post #321
goda90 wrote: post #275

Earlier quoted context omitted.

Just need a lawyer looking for an interesting class action, to be honest. All gOS users can be in the class.

I don't think gOS users are actually the damaged party. I imagine it would be non-google copyright holders of gOS code.

Are they not damaged by delayed updates including security patches?

Re: Google has stopped pushing Git tags for some Android source code

#335

Post by account42 »

gsquaredxc wrote: post #323
ninalanyon wrote: post #303

Earlier quoted context omitted.

Was customary, it no longer is customary.

They still make printed textbooks. Google’s lawyers I’m sure are well funded enough to make this case.

They can make whatever case they want, doesn't mean that a court will accept it.

Re: Google has stopped pushing Git tags for some Android source code

#336

Post by account42 »

aleph_minus_one wrote: post #233
g6taa wrote: post #224

Earlier quoted context omitted.

This is explicitly about commemorative coins, not regular ones.

> This is explicitly about commemorative coins, not regular ones. The formulation is not so easy to read (very common for German laws), but it includes also the regulations for normal coins: "Erfolgt eine einzelne Zahlung sowohl in Euro-Münzen als auch in deutschen Euro-Gedenkmünzen, ist niemand verpflichtet, mehr als 50 Münzen anzunehmen; dies gilt auch dann, wenn der Gesamtbetrag 200 Euro unterschreitet." "If a sin…

Feels you the "single payment" clause still gives you plenty opportunity to be a massive pain about debts.

Re: Google has stopped pushing Git tags for some Android source code

#337

Post by account42 »

grapheneos wrote: post #114

They stopped pushing tags for any of the Pixel kernel or userspace driver repositories to AOSP. They also stopped pushing AOSP releases specific to Pixels which is why AOSP now only gets yearly releases, QPR2 releases and security backports to both of those. Other OEMs use the yearly and theoretically also the QPR2 releases. Both the yearly and QPR2 releases get monthly security backports. Since they dropped Pixel su…

For extra lulz you should get someone with a banned Google account to request the source code. Then Google needs to either unban the account, make an exception for Google docs or deliver via another mechanism.

Re: Google has stopped pushing Git tags for some Android source code

#338

Post by fsflover »

teekert wrote: post #227

We need something other than Android, and we need the government to make sure we can run Android apps (like government ID and banking apps) without being spied on. They've been doing whatever the f they like for long enough if you ask me.

> We need something other than Android

postmarketOS, Mobian, PureOS, and many more already exist. Support them, if you think it's important.

Re: Google has stopped pushing Git tags for some Android source code

#339

Post by fsflover »

account42 wrote: post #337
grapheneos wrote: post #114

They stopped pushing tags for any of the Pixel kernel or userspace driver repositories to AOSP. They also stopped pushing AOSP releases specific to Pixels which is why AOSP now only gets yearly releases, QPR2 releases and security backports to both of those. Other OEMs use the yearly and theoretically also the QPR2 releases. Both the yearly and QPR2 releases get monthly security backports. Since they dropped Pixel su…

For extra lulz you should get someone with a banned Google account to request the source code. Then Google needs to either unban the account, make an exception for Google docs or deliver via another mechanism.

It might be sufficient to say "I disagree with Google's ToS but want the code".

Re: Google has stopped pushing Git tags for some Android source code

#340

Post by philipallstar »

vjvjvjvjghv wrote: post #264
philipallstar wrote: post #261

Earlier quoted context omitted.

"Society" (whomever that is) uses Google services constantly, to society's constant benefit.

It seems the main benefit goes to Google.

Not from my perspective. I get free mapping anywhere on earth, with traffic information, and can route plan walking, cycling, driving, or public/private transport and likely journey times. I can search the world's web-published information. I'm using a powerful, relatively affordable mobile phone. I can watch anything anyone with a camera uploads to YouTube across the world. I can pay from my phone with a thumbprint verification only. I can take a photo of something and get back what it is and some information about it.
Post reply on HN