Post a Comment
I believe that the OIN's arbitrary and constantly changing definition of the "Linux System" is a fundamental problem: http://fosspatents.blogspot.com/2010/06/oins-linux-system-only-cons...
I suggested four possible ways to address the problem (one of those ways consist of multiple measures, so all in all I made like a dozen suggestions).
The Oracle-Google situation proves that there is a problem: http://fosspatents.blogspot.com/2010/08/open-invention-network-oin-...
But this is just one of many symptoms, and the worst thing that could happen is for OIN to turn against open source competitors of its backers, such as against Linux distributions competing with Red Hat/Novell.
The article Florian links to has a significant error, I think. The OIN definition of a Linux system includes a list of packages, and also says that it applies to "any predecessor or successor release". So it would appear that an OIN member can never sue GCC for patent violation, for example, since GCC is defined as a Linux system component (and yes, I can hear RMS gnashing his teeth over that).
Edited 2010-10-07 16:35 UTC
Just to clarify this, one thing is that the definition on the website currently makes a certain statement. But it's another thing that in the actual license agreement, the definition is subject to change at any time:
http://www.openinventionnetwork.com/pat_license_agreement.php
“Linux System” shall, at any time, have the meaning set forth, at that time, on www.openinventionnetwork.com.
So there isn't really any reliability in terms of future versions since they reserve the right to change the definition whenever they want, whichever way they want.
Google designed Android deliberately to be incompatible with anything existing out there -- including common Linux distributions.
For this reason, Android is not covered by OIN. But MeeGo is based on technologies found in common Linux distributions, meaning it's covered by OIN.
Somehow it seems that without actively pursuing this, the participants in current events around Android make MeeGo more and more compelling on handset devices.
You don't get it. Even using the existing set of packages you can create technologies that wouldn't be covered by OIN's license. For instance, you could use Gtk+ to code a slide-to-unlock mechanism for your Gtk+-based phone, you're violating a patent, and could be sued, and OIN won't do a thing to help you - coded in Gtk+ or not - since the patent suit would not focus on Gtk+, but on the functionality created USING Gtk+.
Doesn't matter. MeeGo uses those software packages. OIN affiliates can't sue each other over those.
Eg. Oracle sued Google over Java. If Google used Python, for example, Oracle would be breaching a contract with OIN and could be countersued for that.
Doesn't matter. If those phone-specific technologies are implemented by extending the packages currently covered by OIN (eg. establishing a UMTS connection via NetworkManager or whatever is patented these days), OIN members are relatively save.
Yes, OIN does not cover all patents but at least gives its adopters more safety. Additionally Intel and Nokia said they help defend all MeeGo adopters who get sued by someone else and since Nokia is a major mobile player and grants royalty-free patent licenses via (L)GPL and Apache licenses, that gives additional safety for adopters.
Really I am sorry. Tell that to nokia. One of nokia phones at one point run standard off the repo debian.
There is no need for a divide between phones and desktop. MeeGo is not more research along this path. Power management developments from Meego and its past forms are appearing in all distributions.
There are areas that OIN does not cover. But like Java existing rules were already in place that should be followed unless you want doom.
For this reason, Android is not covered by OIN. But MeeGo is based on technologies found in common Linux distributions, meaning it's covered by OIN.
Somehow it seems that without actively pursuing this, the participants in current events around Android make MeeGo more and more compelling on handset devices.
That's a Nokia talking point. It's both a false and meaningless claim. Of course it's Linux. It uses the Linux kernel, GNU userland, and it uses Java technology on top of it. Java isn't Linux, but neither is QT.
MeeGo is doing the same approach. Linux is meant to be customized to whatever you'd like, from megarouters to phones to servers to desktops.
That's a Nokia talking point. It's both a false and meaningless claim. Of course it's Linux. It uses the Linux kernel, GNU userland, and it uses Java technology on top of it. Java isn't Linux, but neither is QT.
That's not entirely correct, it does use the Linux kernel, but that's it. It does not use the usual GNU userland, it has its own which pretty much is the bare minimum needed to bootstrap Dalvik and let the APIs interface with the kernel.
That's a Nokia talking point. It's both a false and meaningless claim. Of course it's Linux. It uses the Linux kernel, GNU userland, and it uses Java technology on top of it. Java isn't Linux, but neither is QT.
That's not entirely correct, it does use the Linux kernel, but that's it. It does not use the usual GNU userland, it has its own which pretty much is the bare minimum needed to bootstrap Dalvik and let the APIs interface with the kernel. "
So how does that make it not-Linux? How does MeeGo differ in ways that "make it Linux".



