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

41–50 of 350 posts

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

#41

Post by shevy-java »

jmole wrote: post #4

“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.

Why would it be a "stretch"?

The basic requirement is whether the source code is available - and made available. Are you certain that Google's solution here is ensuring that the source code is easily made available? So many other projects just provide a wget-able link. Why does Google want to make it harder to obtain the source code than those other projects?

> Android has always been more source-open than “open source”.

And what exactly does that mean? I don't know what your words mean here. More source open than open source? Is that a tautology?

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

Is it GPLv2? If so then I fail to see why anyone should get higher rights. Everyone gets the same for GPLv2. That's the whole point. I don't understand your statements here.

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

#42

Post by shevy-java »

leni536 wrote: post #35
simoncion wrote: post #23

Earlier quoted context omitted.

There might be some merit to a claim that Google Drive isn't a medium customarily used for software distribution these days, but, yeah, it's definitely not paying a thousand+ cent bill in pennies, and I'm skeptical that it's a violation of the letter of the GPL. It is definitely a dick move by Google.

While I don't find any requirements on how timely the source distribution must be upon request, one can reasonably say that there must be a line between 1 nanosecond and 1 century.

Courts would most definitely make a distinction here. For instance, one century would mean "refusing to release the source code".

We should test how long it takes Google to release source code upon request. And whether it is 100%. I think we should test whether Google fulfils the GPL here. That's now a challenge.

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

#43

Post by shevy-java »

osmsucks wrote: post #8
spydum wrote: post #3

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

Yeah, I agree. While this is a terrible move IMHO, from my superficial reading of the GPLv2 it doesn't really constitute a violation: the license imposes that the source be distributed to anyone who asks, potentially even charge a fee to cover its distribution costs , but it doesn't require that development happen in the open.

I mean, the only way to test this is to require of Google here to release the source code. And then look at how a court will evaluate it. For instance, what if Google never sends the source code? What if they claim that no request made it in? Though I guess this can be ensured, e. g. via letter that is registered being sent and then looking at Google's response to it.

So right now I think we all probably do not know. Google MIGHT refuse to release the source code, but it could release it - we don't know yet. Someone has to test that.

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

#44

Post by sunshine-o »

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.

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

#45

Post by flotzam »

jmole wrote: post #4

“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.

GrapheneOS is arguing that throwing away the metadata of however many commits and squashing them into a messy tarball is not the "preferred form of the work for making modifications", and that a manual process where you have to fill out a form in order to get a Google Drive link a week later is not "a medium customarily used for software interchange" in current times. Those are quotes from the GPLv2.

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

#47

Post by TheMiddleMan »

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.

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

#48

Post by paxys »

TheMiddleMan wrote: post #47

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.

Doesn’t Apple do the same?

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

#49

Post by knollimar »

shevy-java wrote: post #41
jmole wrote: post #4

“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.

Why would it be a "stretch"? The basic requirement is whether the source code is available - and made available. Are you certain that Google's solution here is ensuring that the source code is easily made available? So many other projects just provide a wget-able link. Why does Google want to make it harder to obtain the source code than those other projects? > Android has always been more source-open than “open sour…

"And what exactly does that mean? I don't know what your words mean here. More source open than open source? Is that a tautology?"

I'm sure this means the source happens to be open rather than following the spirit of open source.

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

#50

Post by compiler-guy »

waisbrot wrote: post #40
r3trohack3r wrote: post #34

Earlier quoted context omitted.

I think it’s nuanced I can see an argument that Google is requiring you to enter into a separate agreement with them (the terms they require you to agree to when using Google Forms) to request access to the GPL licensed source. You do not enter into an agreement with the vendor of the software the postal service uses to sort your mail.

Don't they force you to sign up for a Google account to be able to gate access to a Google Drive file?

No. As long as the sharing permission is “Anyone with the link”, then anyone can download from that link with wget or whatever.

Is that the permission they use? Who knows? But it’s at least possible.

Post reply on HN