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

61–70 of 350 posts

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

#61

Post by bitpush »

shevy-java wrote: post #39

I don't think the real focus is on the tags, but on the delay here via a form as well as human interaction. Worded differently, the simplest way to provide the source code is IMO via a URL that you can just wget. At the least this is done by so many projects out there. Google refusing to do so means Google wants to violate the GPLv2, since their alternatives are inferior. https://distrowatch.com/ has many convenient…

> Google refusing to do so means Google wants to violate the GPLv2

Not an expert in GPL, but does it say that the source code needs to be provided by a url?

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

#62

Post by a-dub »

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.

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

#63

Post by lambda »

paxys wrote: post #48
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?

I specifically use Android because of this, among other requirements, that Apple imposes on software development on their platform.

I do not own general purpose computers that I am not allowed to develop software for without permission. I have always avoided consoles for that reason as well (Steam Machine and other similar platforms would be fine, but I've been avoiding consoles for long enough that it's not something I really look for any more).

I was a major Apple fanboy up until the iPhone. Left the ecosystem after the iPhone and macOS started moving in that direction as well.

I'm going to miss having a smartphone that I can use with my banking and EV apps, but probably for the best to get out of Google's ecosystem. Hoping that GrapheneOS will still allow me to use some of the apps that I like.

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

#65

Post by phire »

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.

Google are absolutely within the letter of the GPL, pedantically so. But maybe not the sprit.

We didn't have git tags when GPL was written in 1989, and while we did have sccs and rcs, (and early versions of cvs) they just weren't that widely used, and generally not used for distribution.

Even when GPL 3.0 was written in 2005-2007, source tarballs were still the primary form of distribution, even though it was starting to become standard to additionally provide anonymous cvs, svn, or one of the brand new distributed systems like git.

But these days git is the primary form of distribution, and source tarballs are noting more an afterthought. Hell, even tags are a bit of an afterthought on many projects. It's basically become the norm to expect an healthy revision history for any open source code.

Based on it's stated goals of "freedom to modify the software you use", IMO if the GPL was written (or updated) today, it would most likely require the distribution of revision history and restrict how much that history can be squashed/rewritten.

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

#66

Post by dminik »

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.

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

#67

Post by shalom1112 »

dminik wrote: post #66

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 a…

[dead]

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

#68

Post by devy »

bitpush wrote: post #61
shevy-java wrote: post #39

I don't think the real focus is on the tags, but on the delay here via a form as well as human interaction. Worded differently, the simplest way to provide the source code is IMO via a URL that you can just wget. At the least this is done by so many projects out there. Google refusing to do so means Google wants to violate the GPLv2, since their alternatives are inferior. https://distrowatch.com/ has many convenient…

> Google refusing to do so means Google wants to violate the GPLv2 Not an expert in GPL, but does it say that the source code needs to be provided by a url?

GPL doesn't require them to publish the source in git. FWIW, Google can be compliant and publish the source in Physical Medium too if they opt too.

Also, the OP did mentioned that Google also squashed the git commit to a single commit for whatever reason.

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

#69

Post by leipert »

jraph wrote: post #26
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.

Open source doesn't imply open to contributions. And you could imagine source available software that's not open source but takes contributions (and this is not theoretical, I've seen this in the wild). (However, that's quite orthogonal to being a dick about making the source code that you must share available)

GitLab is MIT licensed, but also has also parts which are source available but not MIT licensed. Contributions to both are possible.

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

#70

Post by flotzam »

phire wrote: post #65
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.

Google are absolutely within the letter of the GPL, pedantically so. But maybe not the sprit. We didn't have git tags when GPL was written in 1989, and while we did have sccs and rcs, (and early versions of cvs) they just weren't that widely used, and generally not used for distribution. Even when GPL 3.0 was written in 2005-2007, source tarballs were still the primary form of distribution, even though it was startin…

> We didn't have git tags when GPL was written in 1989

The GPLv2 requires "a medium customarily used for software interchange", not "a medium customarily used in 1989 for software interchange". Customs are the customs of the time someone is releasing the work.

Post reply on HN