Measuring Openness In Open Source Projects 65
suy writes "Several open source projects exist under a variety of licenses, and we qualify them as free/open source depending on the license under which the final product is released. But there are other considerations, like the existence of a public roadmap, participation in the decision making, or access to the latest source code to make contributions. Vision Mobile has published a report that compares and measures the openness of several open source projects: Android, Eclipse, Linux, MeeGo, Mozilla, Qt, Symbian (till the existence of the Foundation) and WebKit. Eclipse and Linux scored the highest and Android the lowest."
A related article about the report asks whether open source needs corporate backing to truly succeed.
Openness (Score:4, Interesting)
Eclipse and Linux scored the highest and Android the lowest.
It's no really a wonder Android scored the lowest. Google isn't truly a open source company, they only give out source when it suits them and even then they regain most control of it with no discussion or decisions with other non-google developers. Most of their products are also either so crippled (Chronium) or limited by other means (Android and HW makers drivers) that they're practically unusable for real use or development.
One of the strongest selling point of open source is that you can make a little change or fix yourself if you feel the need to. Since Chronium isn't truly the source code of Chrome you have to give up lots of other things if you want to make that change. For making a small change it would probably be better to disassembly Chrome and make the change in ASM. Android is basically useless to you if you want to make a change since you cannot run it on your phone. It's nice and all that they provide code (even with stripped parts), but there is no practical use for it. Besides, most of their products are closed source just like their competitors. There's a really insightful and interesting post here [slashdot.org] about Google's practices.
Re:Openness (Score:4, Insightful)
Yep, and yet somehow people still scream about how open Android is and how locked down iOS is.
Re: (Score:2)
Maybe because I have source for android and can compile it and modify it all I like. Where is that for iOS?
Re: (Score:2, Insightful)
What good is that if you can't contribute back, you can't change the direction of the project, you can't put it on your device, and you can't well... us it.
Re: (Score:2)
I do have it on my device, so there goes that argument. I do use it, daily. And I could contribute back or fork it which would also change the direction to whatever I want.
Deal with it, a closed product is just not the same as an open one.
Re: (Score:2)
I do have it on my device, so there goes that argument.
Oh, so you illegally copied the closed source drivers needed to make it work with any phones then?
And I could contribute back
How? What's the process for getting your patch accepted by google?
Deal with it, a closed product is just not the same as an open one.
I'm not attempting to assert that iOS is open, I'm asserting that android is closed ;)
Re: (Score:2)
How? What's the process for getting your patch accepted by google?
http://source.android.com/source/submit-patches.html [android.com]
Re: (Score:2, Insightful)
That's not for submitting a patch to android, that's for submitting to ASOP, not the same thing.
Re: (Score:2)
What does ASOP stand for again?
Re: (Score:3, Informative)
Android Open Source Project – A related project to android, but not android.
Re: (Score:2)
In this case, it apparently means:
Android Source Open Program.
Re: (Score:2)
And do you imagine patches might move upstream?
Are you an idiot or just a troll?
Re: (Score:2)
You asked how to submit a patch to Android. That's how. It may have to go into the AOSP first, but that's the method to need to go through to get your patch on everybody's phone.
Is it an indirect route? Sure. Is it setup to ensure someone doesn't submit a patch and get it past one line of verification and inject malicious code into the Android package given out by Google? Sure.
You asked how to get a patch to Android. That's your path.
Re: (Score:2)
You can build Android from source and install it on your phone provided you have working drivers, which you can usually port from the stock rom for your phone.
The CM guys build their roms from AOSP and add extra features and support for more devices.
AOSP is the heart of Android and patches eventually trickle down to the manufacturer's roms.
Re: (Score:2)
Not all phones need closed drivers, and those that do come with a copy of them. Retaining the software that came with the device is legal.
Android is open. It may be less FREE than I would like but open it sure is.
Re: (Score:1)
There actually are relatively few closed pieces necessary to make something like Nexus S go. For the most part they're firmware, not actual "drivers", though the opengl libraries fall into a middle ground -- the SGX kernel driver is GPLv2, the userspace opengl libraries are closed. We've been working with vendors to make the closed pieces available under a license that allows them to be included in builds and distributed non-commercially (commercial distributors tend to be OEMs which have direct relations
Re: (Score:2)
you can't put it on your device
Says who? There are some devices which are locked down, but many more which you can easily put your own kernel on there.
Re: (Score:1)
That's really useful... How about getting any drivers for them?
Re: (Score:3, Insightful)
That gets you the open source parts of the device... who ever said the drivers were open source? Note, in 99.9% of cases, the drivers *aren't* open source.
Re: (Score:2)
When you buy the phone, you buy licenses to use the software on it. Including drivers. If you copy the Google apps and drivers off your phone before wiping it out, you still own the license to use those drivers on that device. You put on a new ROM and put those files back in... in some cases, the files are downloaded with the ROM but only used on devices where the device used them before and is therefore licensed to use them.
Re: (Score:2)
Re: (Score:1)
It isn't just the OS that makes the system open or closed; how easily you can do other things is very important. Apple has a much more tightly locked down application environment. Getting an app into the iOS Appstore is much tougher than getting it into the Android Marketplace, and installing unapproved apps is much easier under Android. From a user standpoint, having access to outside apps by setting a single checkbox contributes more to real openness than being able to replace the OS.
Re: (Score:2)
And your point about Android is somewhat defeated since the only two Google-sponsored phones in existence are unlockable. I mean, shit, the Nexus S recently had a promotion where it was free with contract.
you failed to notice - his point is mindfuckingly invalid because he sees only america. in almost all other parts of the world, this android-locked in situation is nonexistent. people buy android phones where i live, and do whatever they want with them. this also is so in europe.
Re:Openness (Score:5, Interesting)
Android is basically useless to you if you want to make a change since you cannot run it on your phone.
Tell that to the masses of people that have ditched the vendor supplied version of android for customized versions.. it is actually pretty darn common amongst young people. Even non-geeks, all it takes is seeing one extra feature they like to convince and having a half hour of spare time.
Re: (Score:2)
Yes, but tell me how do they use Stock android with no drivers and no google apps? That's a lot to give up on.
Now, they cheat because they "illegally" get Google apps and drivers in binary form. Equivalent to hacking iOS.
The source code helps, but it is not enough for getting the OS on your phone.
Re: (Score:1)
I'm not going to take your word that the drivers aren't available, because of the 3 Motorola Android phones I've owned (2 of them were locked down), all of them have 100% GPL open-source drivers with no userspace components.
And the Market app is the single critical Google app... but there are dozens of alternatives to it. Amazon's app store is side-loadable for instance.
TL;DR: experiment with Android for once or stfu. I never talk about the iPhone because I don't fucking own one.
Some important applications are Market-exclusive (Score:2)
And the Market app is the single critical Google app... but there are dozens of alternatives to it.
Even if I have Soc.io, SlideME, Amazon, and AppsLib installed, that won't help me get to my bank. Chase's banking app is exclusive to Android Market.
Re: (Score:2)
Not to mention that Google's Market is far better than the rest of them, mainly because it has the most of all of them.
Re: (Score:3)
So complain to Chase. Besides you can just use their website.
Scanning paper checks is app-exclusive (Score:2)
Besides you can just use their website.
I occasionally receive a paper check as payment, and I haven't been able to find a way to scan paper checks for deposit using Chase's web site. I don't think HTML5 even provides any way for a web site to request access to a scanner or camera attached to a PC.
Re: (Score:2)
Find me an Android phone that provides a fully functioning GPU including OpenGL without using a single binary blob to do it...
Even the Nexus S (supposedly the most open of the android handsets) has a binary userspace blob for the GPU, a binary userspace blob for WiFi/bluetooth/GPS, a binary userspace blob for the NFC support and a binary userspace blob for the cell modem.
Re: (Score:3)
Most of their products are also either so crippled (Chronium) or limited by other means (Android and HW makers drivers) that they're practically unusable for real use or development.
Really. What about all the third-party manufacturers making Android devices without a license from Google (Archos comes to mind, although in retrospect they might have a license... point is they don't need one)? Or how about CyanogenMod or other modifications for Android based on the OSS part? Lots of people use them, and they work on lots of phones. That is precisely the advantage of OSS that you claim Google doesn't allow. And what "stripped parts"? According to Wikipedia [wikimedia.org], the entire Android OS made by G
Re:Openness (Score:4, Informative)
Do not confusion Android with AOSP. They are two separate versions. Android is commercially licensed (+GPL2 Linux), while AOSP is Apache with GPL2 for the Linux kernel. And getting Android does take money - you have to be in the OHA (so there is a licensing fee, but it's relatively small and it's not per-unit, but an annual one).
Periodically, Google pushes code from Android into AOSP.
OHA members get access to the latest versions of the Android code before release, but they also have to agree to conditions to use that code, conditions not present in AOSP, such as support for 18 months (no more release and forget - Google's demanding 18 months of support and updates), less fancy dressings and customizations, and unlockable bootloaders.
OHA members do this so they can also license (separately) "with Google" because Android phones are relatively useless without the Market app because there are few alternate sources that have a comprehensive selection of apps. (Hell, most "free" apps rarely put up an apk for download - just a QR code to grab it through the marketplace).
And Archos is also a member of the OHA now - they have to be in roder to release a 3.x tablet. Only OHA members have access to Honeycomb source, and while there are hacked versions of Honeycomb around, I wouldn't trust them in a production product. Though, whether or not Archos abides by their open-bootloader thing, that's another issue. Historically Archos devices auto-lock to the hard drive (so you can't replace it), and have signed bootloaders and kernel, which also check for signed user spaces. Archos Androids were "open" in they could run apps, any roots and jailbreaks lasted until the next reboot.
AOSP may be open source, but it's more like "let's just dump what we have" moreso than a true open-source project - the stuff goes from Android -> AOSP typically.
Re: (Score:2)
Re:Openness (Score:5, Insightful)
Honeycomb, of course, isn't OSS ATM, but again, they have good reasons for that.
There really isn't a good reason. If your code is good enough to sell on a device, it's good enough to be opened.
A lot of Android fanboys do logical loops explaining that Android is truly open, and some parts of it are, but a lot of it isn't. Accept it.
Re: (Score:2)
Most of their products are also either so crippled (Chronium) or limited by other means (Android and HW makers drivers) that they're practically unusable for real use or development.
Last I saw, you could easily take the Android Open Source Project and put it on an embedded computing device of your designing. Whether or not you actually have the resources to do so is no concern of theirs, and really doesn't have any bearing on it's openness.
Re: (Score:2)
More to the point, I want to prove something so I will use my judgement to balance the weights of different methodologies and different degrees and come up with the conclusion that matches my opinion.
I want to state that Windows is the best Software out there... I will weigh the fact that it has the most off the self software as very important and the rest as not important and do some research comparing off the shelf software count and boom I prove my point.
But wait... I want Linux to be the best OS out th
Open Source has nothing to do with openness (Score:1)
It is a license. Free Software and Open Source both are derived from a simple idea, the code is free to reuse and distribute. The religiousity of the community is derived only from the community itself. Would it be nice if those projects were more community driven? Sure. Does it make them any less "Open" or "Free", no.
Re:Open Source has nothing to do with openness (Score:5, Insightful)
Uhhh, no... "Open Source" is not a license – it's an idea. There are many licenses that are written with the idea in mind. The idea is *everything* to do with openness.
While open governance is good it is not the point. (Score:3)
While the fact that an open source project has open governance is good if you want to continue using the main codebase, the most important factor by far is the right to fork if needed.
It is the ability to take the code, change it and post your version that really will eventually force the "right" things in any open source product that many enough people care about.
Any "open governance" can be stopped at any point, but once given code is out in open source it is "safe" provided enough people care.
Re: (Score:2)
the most important factor by far is the right to fork if needed.
That depends on whether it's easier to convince mainline to take your patch than to verify that your patch still works with each new version of mainline.
Comparison with Open-By-Rule? (Score:1)
How does the Open Governance Index compare with the Open-By-Rule benchmark [webmink.com]?
Corporate Backing? It helps. (Score:2)
FTS:
A related article about the report asks whether open source needs corporate backing to truly succeed.
No, it doesn't need it, but it definitely helps to have someone with deep pockets willing to financially support your project. Meaning that people can work on the project as part of their full time job, instead of having to do something else with most of their time to be able to afford food and shelter.
Report methodology and licenses (Score:2)
The report gives freedom points for various things to determine openness. But what they consider open is up to debate. Android gets 4 points for having a mostly Apache license, which the report considers the "most open". Linux only gets 2 openness points because it is released under the GPL, and the report considers the GPL to only be worthy of half of the points that the Apache license deserves. This methodology is of course, debatable.
But more importantly (Score:2)
what unit is it measured in?
I propose the Stallman, with 10 Stallman being as open as can be, and 0 Stallman being NSA-like transparency.
Re: (Score:2)
I propose the Stallman, with 10 Stallman being as open as can be, and 0 Stallman being NSA-like transparency.
How about naming it after someone who does not violate the GPL?