Home opinion-and-analysis Open Sauce Android: not-so-open open source

Author's Opinion

The views in this column are those of the author and do not necessarily reflect the views of iTWire.

Have your say and comment below.

The Bionic library is released under the 3-clause BSD licence while Dalvik, the virtual machine that Android uses, is again under the Apache licence.

Google does a parallel development process between the "mainline" Linux releases, and its own Linux kernel tree. "There are some features that have been developed for Android that have been ported back to the mainline Linux development process," says Neugebauer. "I believe a project has been recently started to try and merge most of Google's custom developments back to mainline."

This has been a point of contention between Google and the main Linux kernel development team due to differences in the way the teams wanted to make Android features part of the mainline kernel; it now appears that it will take four to five years for the two projects to come back to a common kernel.

Hence the only thing common to Android and any Linux distribution is the kernel.

The Android development takes place in a closed environment and source is released only when a release is complete. One cannot gain access to source while the development process is ongoing. There is no indication of when a release will be made. Google calls the tune and to hell with all models of open source development.

Neugebauer, however, points out that in the 1980s, the Free Software Foundation followed a similar model. "They released final releases with few intermediates, in exactly the same way that closed source products did at the time. The difference was that they provided the source code. Sure, it's a less common method of releasing code, but it's definitely not unusual," he says.

There are business reasons behind the mix of licences. The Apache licence allows Google to let others take the code and do what they want with it without the strictures which the GPL places on a piece of software. And the BSD licence is open slather - you can take code and lock it away after modifying it to your heart's content and nobody need be any the wiser.

In the case of Android 3, Google suddenly decided that it wasn't going to make any source available for the userspace bits. The kernel source was published. And that was that.

There is no guarantee that an Android device can continue to be upgraded as new versions of the OS emerge. Some devices are just cut off and if one wants to run a later version, one has to just fork out for a new device. For example, the Nexus One ran 2.1 and could be upgraded up to 2.3. And there the story ended.

FREE - SYDNEY & MELBOURNE BUSINESS INTELLIGENCE EVENTS

The Holy Grail of the Business Intelligence (BI) industry – pervasive deployments and widespread end-user adoption – has remained an illusive dream for years. Until now!

REGISTER & SECURE YOU PLACE / BRING A FRIEND

Melbourne - venue Captain Melville’s CBD 2:30 – 6:00pm, Tuesday 28th April

Sydney - venue Redoak CBD 2:30 – 6:00pm, Thursday 30th April

DON'T MISS OUT - MELBOURNE REGISTER NOW!

DON'T MISS OUT - SYDNEY REGISTER NOW!

FREE WHITEPAPER - RISKS OF MOVING DATABASES TO VMWARE

VMware changed the rules about the server resources required to keep a database responding

It's now more difficult for DBAs to see interaction between the database and server resources

This whitepaper highlights the key differences between performance management between physical and virtual servers, and maps out the five most common trouble spots when moving production databases to VMware

1. Innacurate metrics
2. Dynamic resource allocation
3. No control over Host Resources
4. Limited DBA visibility
5. Mutual ignorance

Don't move your database to VMware before learning about these potential risks, download this FREE Whitepaper now!

DOWNLOAD!

Sam Varghese

website statistics

A professional journalist with decades of experience, Sam for nine years used DOS and then Windows, which led him to start experimenting with GNU/Linux in 1998. Since then he has written widely about the use of both free and open source software, and the people behind the code. His personal blog is titled Irregular Expression.

Connect