4 ms·
Android is not an open collaborative project like the Linux kernel or many distributions. Android, is still, however open source in so much as that Google has
by wvenable 16y ago
Android is not an open collaborative project like the Linux kernel or many distributions. Android, is still, however open source in so much as that Google has released the source under a license that permits derivative works. It is however, not Free Software, as it is Apache licensed.
One needs to be careful not to mix terms. Android is "open source" but that's as far as they go. It's not Free Software and the development process is not collaborative.
- nathanb 16y agoLittle hard to be open source when your source is closed and you don't let anyone look at. Android source is released sometime after the product has been out to market. Android is only open to the extent that it benefits Google, not the extent that it benefits the community. I'm not saying that this is the wrong way to go about it...were I a Google exec and responsible to shareholders, I would have difficulty justifying a truly open process. But at this point, "open" has become a bullet point on a product box to attract a certain demographic.
- warfangle 16y agoYou are confusing Open Source software and Free Software. Read the GP again.
- nathanb 16y agoCan Google plausibly claim to be OSI-compliant on Honeycomb when they have released the product without the source? I like to think that I understand the difference between the two, but I have difficulty seeing how "I'll show you the source at some point in the future, when it's convenient for me to do so" is in any meaningful way open source.
- wvenable 16y ago> Can Google plausibly claim to be OSI-compliant on Honeycomb when they have released the product without the source? The GPL requires that sort of thing, most other open source licenses do not. The Apache license covers what you can do with the source when it has been given to you. > I have difficulty seeing how "I'll show you the source at some point in the future, when it's convenient for me to do so" is in any meaningful way open source. Microsoft could release the source code to Windows tomorrow but say you have no right to modify it or distribute the modifications. Just because you've been given the source doesn't mean it's open source. Furthermore, if you haven't been given the source, there isn't anything to say about it. In this case, you are not entitled to the source just because you have the binary.
- bad_user 16y agoThe GPL requires that sort of thing It's a gray area. If you accompany your binary release with a "written offer", you can actually postpone the source release. The GPL doesn't give a deadline either. People are trying to make this a licensing issue, when it definitely it is not. You can always fork Android, and Google cannot sue you for patent infringement (courtesy of the Apache license). The problem then is that the fish doesn't come free anymore -- which is the main gripe of people (i.e. the only valid concern I see for Android is that development is not done in the open). As for the "users cannot do whatever they want with their devices" -- they can always buy alternative devices, or build their own devices (isn't that the purpose of Free Software anyway?). If openness is really what people need, open devices will win because it is a free market (the Nexus S is doing well in my country btw).
- wvenable 16y ago> People are trying to make this a licensing issue, when it definitely it is not. I agree. In fact, that was my original argument. > the only valid concern I see for Android is that development is not done in the open. I don't actually care if the development is not done in the open. What I actually care about is being ability to modify and install alternative versions of the software on my devices. I have had to throw away a lot of perfectly good hardware because the software was old and outdated with no way to update it. I've also had to deal with bugs with no way to fix them. Of course, none of this is Google's problem because they don't make the hardware. > they can always buy alternative devices, or build their own devices (isn't that the purpose of Free Software anyway?). The purpose of Free Software to build hardware? I think you've got something wrong there. As a programmer, I don't build hardware. I build software. > If openness is really what people need, open devices will win No, because most people are not programmers (or highly technical) and therefore have no need or ability to run alternative software. So no, openness will not win out. This appeal to the masses is not a good argument.
- bad_user 16y agoThe purpose of Free Software to build hardware? No, you got it wrong. The purpose of Free Software is to escape from the monopolies created by proprietary software (i.e. only the parent company of such software can provide support and fix it for you); which is not the same with other products, like cars, for which you can always find a local repair-shop. So even if normal people are not developers or hardware builders, they can rely on local businesses that may be cheaper, while also helping the local community. A valid point nonetheless. Search for any of RMS's talks and he'll bring this point up. No, because most people are not programmers I've got dozens of non-programmers as friends. Many of them own iPhones. All of them know about jailbreaking, many of them did it -- some with net-tutorials, some by paying local smarty-pants that unlock phones for a living.
- micampe 16y ago> It is however, not Free Software, as it is Apache licensed The FSF considers the Apache license to be free software (and GPLv3 compatible) http://www.gnu.org/licenses/license-list.html http://www.gnu.org/licenses/license-list.html
- wvenable 16y agoYou are right, FSF considers it a free software license but it's not a copyleft license. Google is not required to give out the code. It's compatible with the GPL because you can re-license Apache code under that license.
- micampe 16y agoI was only replying at your statement that Android is not free software: it is, by the letter of the law, even if it doesn't feel like it at all, in spirit.
- wvenable 16y agoI don't know if my reply came off as hostile, but I am thankful for your correction. I'm quite surprised that the FSF is so forgiving about what they consider a Free Software License. These sorts of Android "shenanigans" seems like exactly the sort of thing they don't like.
- fluidcruft 16y agoThe FSF does not consider the closed software modifications shipped by vendors to be free software. Android is essentially a free-software project with many closed-source forks. The typical Android end user is not running free software (except for the copyleft portions where the vendors have no choice).
- bad_user 16y agoThe typical Android end user is not running free software This is a social problem -- what Open Source licenses do is to allow you to make forks in case you're unhappy with the way the project is being managed. If that's not a reasonable advantage and you still depend on the goodwill of the parent company for future versions -- then you're basically saying that open-source / free-software licenses are useless. Which is not true, as there are examples of famous forks available -- see XFree86 / Xorg; although forks don't happen so often because they take a lot of resources and energy, and there has to be enough incentive for a fork to survive.
- andreyf 16y agoAndroid, is still, however open source in so much as that Google has released the source under a license that permits derivative works. It is however, not Free Software, as it is Apache licensed. What definition of FS are you using? Could you clarify which of the four freedoms [0] Android infringes on? 0. http://www.gnu.org/philosophy/free-sw.html http://www.gnu.org/philosophy/free-sw.html
- bad_user 16y agoI agree that Android development is not in the open; but there are select companies and individuals that participate in its development. On the other hand, terms like "open source" and "free software" have absolutely nothing to do with the development process / collaboration model; they only have to do with end-user or redistribution licenses. Also, the Apache license is stronger than GPL.v2 in the "free software" sense -- it's a lot easier to restrict GPL.v2 software redistribution by means of patents. One needs to be careful not to mix terms. One sure does need to do that.