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

11–20 of 350 posts

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

#11

Post by gowld »

dgellow wrote: post #2

Quoting the first tweet: > 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.

How slow is "very slow" ? What is "certain source code"? Why is the OP being so coy about describing the problem?

Here is the form:

https://source.android.com/opensourcerequest

This is interesting:

> We might charge you a fee to cover the cost of processing. Your request must be sent according to whichever of the following rules applies:

> Within three years of the date you received the product from Google that included the component or binary files that are the subject of your request.

That "three years" is the minimum named in the GPLv2: https://opensource.org/license/gpl-2.0

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

#12

Post by ajross »

Brian_K_White wrote: post #7
ajross wrote: post #5

Earlier quoted context omitted.

> “In violation of GPL” is a stretch. The originally envisioned distribution method, in fact, was "Send FSF a blank 9-track tape and they'll fill it and mail it back". Nor, obviously, does anything prevent someone who downloads this from Drive from mirroring it on GitHub or wherever. This is arguably bad stewardship of a historically open source project. It's certainly not a license violation.

It's paying a bill in pennies.

It's not even that. Downstream projects host their own mirrors already, this is an annoying hoop to jump through for the maintainers (basically suck down a bunch of tarballs for every release, analogous to grabbing stuff from FTP sites back in the day), but not exactly a terrible hardship compared to the really very significant work of maintaining a large project.

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

#13

Post by cute_boi »

rlpb wrote: post #6
dgellow wrote: post #2

Quoting the first tweet: > 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.

Didn't Google work very hard to avoid any GPL in Android, apart from the kernel? What is in there that is GPL?

I assume Linux.

I am very thankful linux is gpl. Because of GPL these tech giants are forced to release source code.

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

#15

Post by petcat »

dgellow wrote: post #2

Quoting the first tweet: > 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.

> They're in clear violation of the GPLv2 now.

I don't think they are? They could just as easily require requests for the source code to be made through the regular mail instead of a Google form. It's still (maliciously) compliant with the license.

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

#16

Post by HarlequinHair »

gowld wrote: post #11
dgellow wrote: post #2

Quoting the first tweet: > 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.

How slow is "very slow" ? What is "certain source code"? Why is the OP being so coy about describing the problem? Here is the form: https://source.android.com/opensourcerequest This is interesting: > We might charge you a fee to cover the cost of processing. Your request must be sent according to whichever of the following rules applies: > Within three years of the date you received the product from Google that inclu…

> How slow is "very slow?" The answer can be found two replies after: > Initially, Google would usually provide access to the tarballs within a couple hours. Lately, they're often taking weeks to get back to us. They're the ones who chose to use this archaic system instead of pushing Git tags and it's their responsibility to handle requests promptly.

> What is "certain source code"? The OP seems to be GrapheneOS, which heavy patches AOSP. I guess the context is Android source code and its security patches.

> Why is the OP being so coy about describing the problem? Not sure what you mean, I think they are explicit enough. I guess it's clear enough for developers how an upstream update should go. If people depend on big projects like AOSP, devs should be prompt in delivering source code, especially when it is mandatory by license.

Can you give us more details on how/why you think the OP is being coy?

Post reply on HN