Who's Behind the Google-Linux License Ruckus?

jfruhlinger writes "Yesterday, news broke that Android might have a Linux copyright problem, which would be big trouble for Google, already locked in an IP struggle with Oracle over the mobile platform. Blogger Brian Proffitt looks deeper into the alleged violations. He notes that, while it's possible that Google's on shaky ground, the motivations behind the news release are murky: the lawyer who outlined the violation is an ex-Microsoft hand, and the news was widely propagated by gadfly Florian Mueller, who's tangled with Google over patent issues in the past. Moreover, the alleged violations are in header files, and it's not clear that those are copyrightable; if they are, no actual copyright holders have come forward to complain."

Comments

And Bionic is different from glibc how?

[tbird20d]

This whole thing just makes me angry, because it ignores legal standards that have applied to Linux and been accepted by all parties, for years. If Naughton's legal analysis is correct, and use of the Linux header files causes the GPL to apply to the utilizing work, then glibc is in more danger than Bionic is. glibc is LGPL, not GPL, and has been using "full" Linux kernel headers for years. How could Bionic, using a stripped down subset of the same headers, be subject to the GPL, if glibc is not?

Re:What I'd like to see with the GPL

[tomhudson]

is simply this... when a new version of the GPL comes out and you wish to continue using the GPL, all future licensed software must be released under the new GPL license. GPL 3 is amazing, but too few people are using it.

First, the GPL forbids that sort of restriction.

Second, what if some future version of the GPL contains something that makes it less free?

Third, the GPL v3 has some flaws. Android wouldn't be commercially possible if linux were GPL v3.