Google copyright purge leaves Android developers exposed
Could be forced to hand over source code
Steps to Take Before Choosing a Business Continuity Partner
Google's attempt to purge copyright from header files has put mobile developers at risk of being forced to reveal their own source code, according to legal experts.
This time it's not patents or Android's reinterpretation of Java that's causing problems, but the Linux code that compiles down into Android itself.
Google publishes that code under the Apache licence, but derives it from Linux source protected by the General Public Licence version 2 (GPLv2) claiming to remove all copyrighted components before changing the licence. Only it seems that Google's idea of what constitutes copyrighted content isn't quite the same as that defined by US courts.
At issue are the header files in the Linux kernel - a list of APIs and macros that are used during compilation. These fall under the GPLv2 which states that any work derived from them must also be published under the GPLv2, but Google uses scripts to take out all the comments and extraneous odds and sods, then claims that this removes the copyright. That enables Google to publish the resulting code under the (less open) Apache licence as though it were an original work.
In his advice (pdf) Edward Naughton, of legal firm Brown Rudnick, highlights cases which have come before the US courts and established that copyright can exist on an API thanks to its innovative structure and design, which would seem to give the lie to Google's claims.
Even if Google is proved right things are not well as the search giant will have blazed a path that others could follow, potentially creating software of all sorts derived from open source projects but without being bound by open source rules.
Naughton's advice builds on work from Raymond Nimmer who first pointed out Google's innovative approach to copyright interpretation. The advice takes that further, as Naughton explains in his Huffington Post article on the subject, going on to analyse the Bionic package, 750 files that Google derived from Linux kernel header files published under the GPLv2.
The problem for developers is that the GPLv2 applies itself to any application that makes use of covered code, which could arguably apply to any native Android application as the kernel headers are so universally applied.
That could see developers forced to reveal their source code to all and sundry, and permit its reuse, which would certainly be a challenge for the Android community. That's a worst case scenario, but the breach in copyright could leave companies exposed to litigation, which is what Naughton is advising against. ®
COMMENTS
RE: Aaaarrgh
Actually, there isn't a problem writing a licence - the GPL is well understood (by those that don't have an agenda against it).
I find Google's approach *interesting*, and I can't help but think they've mad a whole pile of pain for themselves when they finally lose in court.
But as for the bit about applications developers having to reveal their code. **WHAT** ? Because the kernel and it's headers are under GPL doesn't mean that applications will have to be under GPL. That's one of the oldest bits if FUD thrown at free software and completely bogus. Now if the developer actually links some GPL code into their application then it would apply, but not just by writing an application that runs on that kernel.
What we want?
What do you mean "what we want"? Clearly the reasoning behind GPL'ing the Linux kernel makes sense and is for many the reason people commit code into Linux?
The whole idea of Linux is to keep ALL the derived code open, if companies were planning to do it with Android then though luck, welcome to the GPL ecosystem. Linksys, Tivo and others learnt how it works already.
If Google didn't like GPL they could have used one of the BSDs.
Removing Copyright
So, let me get this straight
You have a piece of copyrighted work, but if you remove something from it, it ceases to be copyright.
Does that mean I can rip music from CDs, pass them through an audio filter to remove something, say the content above 25KHz, thus removing the copyright and allowing me to distribute the work as my own.
And think of all those TV shows I can sell on - I just cut out the credits and flog them off as my own production.
I like it!
(mine's the one Andrew Crossley won't be chasing any time soon)
IT infrastructure monitoring strategies
Requirements Checklist for Choosing a Cloud Backup and Recovery Service Provider
Data control in the cloud
Cloud based data management
Agentless Backup is Not a Myth
