Google's Honeycomb Source Code Release Is On Ice
itwbennett writes "'Ice Cream Sandwich', that is. Apparently it's source code delay week, as Google joins Apple in delaying the release of source code for open source licensed software. Except, unlike Apple, which promptly released the LGPL WebKit code in question Monday afternoon, Google stated yesterday that it will not release the source code for Android 3.0 (Honeycomb) until after the release of the next version of Android (Ice Cream Sandwich). This is not necessarily news, since Google said last month that source code would be held for an indeterminate time and released when it was ready. It's just that now 'indeterminate' has an actual date: post-launch of Ice Cream Sandwich. The question, says blogger Brian Proffitt, is: 'How the heck can they do this, given that Honeycomb is licensed under the Apache Software License v2?'"
This story has been covered here before... earlier today.
You must be new around here.
Maybe I'm missing something but this looks like a dup in less than 24 hours. That's impressive, even by slashdot standards...
http://linux.slashdot.org/story/11/05/11/0041250/Android-Honeycomb-Will-Not-Be-Open-Sourced
It is rare to find an article that attempts to analyze legal issues on OSS licenses that is even more horrifying than the worst comments from people pretending to be lawyers on Slashdot.
I don't tend to complain about article quality on slashdot, but this one is pretty extreme. The whole article is basically some random dude making himself look like an idiot by being clueless about OSS licenses and then pretends to be a lawyer. At least on Slashdot, people do know OSI approved licenses do not require source to be provided with the binary.
AND, as others have already noticed, it's a dupe!
Don't quote me on this.
Or because the Apache license is a BSD style license that allows for this.
Unstable Apps: Our Android Apps Don't Suck
This seems like more of the same anti-Google FUD that we've been bombarded with recently. It is a classic political tactic called "attack your opponent's strength". One of the reasons Android has taken off like gangbusters is because it really truly is open source while iOS and WP-7 are certainly not. So the game being played is to stir up a ruckus about Android not being open. The same tactic was used recently when people's hair caught on fire because Google had the ability to nuke malware apps. The story was not "hey, Android is open and safe", the story was that Google was being evil.
I'm currently working on a GPLv2 (for historical reasons) project intended to be part of a Linux distro. Guess what? I don't release the source code until it is ready for alpha and beta testing. Releasing it before basic functionality is in place simply wastes everybody's time and energy. I see absolutely nothing wrong with Google dealing the release of their software until they think it is the best time to release it. If Google released early instead then many of the people bitching and moaning now would have been bitching and moaning about Google releasing code before it was ready.
These unscrupulous tactics have been around for a long time. I'm not surprised that they are being used in this context but I am a little saddened that people seem to keep falling for the same old malarkey.
We don't see the world as it is, we see it as we are.
-- Anais Nin
Thanks, now we have nothing on-topic left to discuss. I suggest we devote the rest of this thread to discussions of ponies. I like them stewed, how about you?
- None can love freedom heartily, but good men; the rest love not freedom, but license. -- John Milton
The Apache License is a free software license authored by the Apache Software Foundation (ASF). The Apache License requires preservation of the copyright notice and disclaimer, but it is not a copyleft license — it allows use of the source code for the development of proprietary software as well as free and open source software.
Apache License (emphasis mine)