Flight to the GPL(v3)

It's an astute assessment by Pieter at FFII, in the aftermath of Neelie Kroes' capitulation to Microsoft ...

So, Microsoft has decided to bleed the GPL economy dry by:

  1. Fragmenting the Linux economy by making patent deals with Linux vendors - TurboLinux, Xandros, and of course, Novell.
  2. Starting a proxy-troll patent attack on Red Hat, the leading Linux distributor (it has also attacked Novell but that is probably so that it can ride to Novell's defense). Red Hat refused to make a deal, now it will pay the price.
  3. Splitting the open source community away from the free software community, by re-branding itself as an "open source" firm.
  4. Announcing that it wants to buy open source firms. Money is the greatest divider ever.
  5. Bringing open source projects into its franchise, where they will get protection from Microsoft's patents, in return for using Microsoft's open source licenses.

It's a desperate scheme, because it's guaranteed to backfire in the worst possible way, and surely Microsoft cannot be naive enough to think it'll work.

Here is how Microsoft's plan to kill the GPLv3 is going to backfire.

  1. It's going to bring large numbers of people into the "no software patents" camp. Up to now, it's not been clear to most people just how damaging the EPO's practice of allowing software patents has been. The FFII has been saying for a while, "software patents trump anti-trust" but few have understood, until now.
  2. It's going to end the license wars. Microsoft have set the stage for a mass migration to, not away from, the GPLv3. Why? Because open source projects that get too close to the beast will shrivel and die like grapes on hot coals.
  3. It's going to focus the wrath of an entire community against Microsoft. For the last decade or so, Redmond have not really messed with the FOSS world and the FOSS world has mostly ignored Redmond, apart from a lot of taunting and name-calling. Now, that has changed.

The future of open source and free software will look like this: first, Microsoft will pump money into its franchiseware economy and get very little back. Second, IBM will do the same with its own franchiseware economy (the Apache Foundation) and get a lot more back, because IBM actually understand how this works. Last, all remaining projects will move to the GPL, with a few exceptions. And it's that economy, the one based on formal copyleft licenses, and backed by increasing determination to litigate and defend against litigation, that will prevail.

Novell's Lose-Lose Situation

GPL version 3 paints Novell into a corner in it's "patent & interoperability" deal with Microsoft. (I'm assuming the GNU tools are early to upgrade their license from GPLv2 to GPLv3 and that the Linux kernel will certainly upgrade in time.)

The effects upon Novell's position of the terms of GPLv3 are quite simple to understand: Novell can either 1) elect itself out of the Linux business to protect its deal with Microsoft (something of a non sequitur); or 2) stay in the Linux business and thereby spread immunity from potential patent infringements to any customer who uses Novell's or any new GPLv3 versions of Linux.

(Among the layered ironies here, is that it is more likely that Microsoft is the infringer upon others' patents which may be contained in Linux.)

Holding aside the (greater) problems for Microsoft, the problem for Novell arises from the free-SuSE Linux support vouchers which Microsoft has been spreading around to its customers, making Microsoft a distributor of GPL software. In particular, the problem arises because the vouchers have no expiry date. With no end-date, the vouchers exercised by customers after GPLv3 code comes into use means that Microsoft, as a distributor, becomes subject to the terms of the GPLv3 license and therefore its patent license to Novell gets applied to all users of relevant GPLv3 code, not just Novell's customers.

This, according to the provisions of Sections 10, 11 & 12 (parts given below) of GPLv3, means that after Novell has upgraded the Linux kernel and GNU tools on its own development tree to GPLv3 code, then the resulting product will cause the same patent protections granted to Novell by Microsoft in their deal to be distributed to any "downstream" user of this code and other works derived from it. Thus, all users of Novell's SuSE and other distros of Linux after a certain time will have the same protections & immunities Microsoft attempted to grant only to Novell.

Accordingly, Novell can do one of two things: lose or lose...

In the first scenario, Novell can simply stop distributing Linux (not likely) or elect not to use GPLv3 code in its GNU/Linux-based products. This would mean Novell would have to effectively fork itself away from the Community activities and Community code -- away from GNU/Linux -- to become isolated as a lone steward of, over time, obsolete GPLv2 code. Ostensibly they would choose to do this in order to continue to honor the Microsoft deal, justify the large (company-saving) payment from Microsoft, and continue to "benefit" by being among the few commercial Linux vendors offering patent "protection". This scenario sees Novell removing itself from the Linux business to protect its vig from Microsoft. Yet, in the end, such a move would make Novell an uncompetitive and unattractive Linux partner. (The scenario is unlikely because it doesn't make business sense from Novell's perspective.)

In the second scenario, Novell loses a new uniqueness among Linux distributors it thought it had forged with the desktop Monopolist. Here, the company continues as normal to take down and work on the new GPLv3 code from the Community development trees of GNU/Linux and when any end user installs the resulting Novell product, they are subject to the immunity of the "patent license" granted by Microsoft to Novell customers; this occurs whether the case is an installation of the free voucher versions or of versions purchased from Novell. And here's the rub: the patent protections get automatically extended to all recipients of GPLv3 GNU/Linux code (see Section 11); the new terms nullify the Microsoft-Novell patent detente by spreading the protection to all GNU/Linux users & purveyors.

For Novell, the second scenario looks like the present course (this Novell has confirmed): the company stays in the Linux business, it stays current on GNU/Linux code and the only thing it loses is the uniqueness among Linux vendors as a source of protection against Microsoft's threatened legal lashings-out.

It would be easy to say this was a set-up by the Linux and the Free Software Communities against Microsoft; but it's been clear from triangulation in parallel and orthogonal experiences over time that Novell's senior people did not (do not) understand the GPL much better than Microsoft's. This makes the truth seem stranger than the fiction. But in the end it will be difficult to conclude other than that knowledge will continue to insist upon its freedom (this video is a rousing bit of oratory on June 26, 2007, from the homeland of Adam Smith by the Lawyer of the FSF).

For the curious and the other lawyers, here are the relevant parts of GPLv3, Sections 10, 11 & 12, on which I base my assertions. In particular, note how the license does not permit different terms to be attached by different purveyors to different recipients of the work...

Section 10 - Automatic Licensing of Downstream Recipients (exerpt)

Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License.

Section 11 - Patents (exerpt)

If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it (emphasis added).

Section 12 - No Surrender of Others' Freedoms (exerpt)

If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License.  If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all.

Groklaw has an interpretation and discussion here, MS: Dancing as fast as it can to try to get away from GPLv3, which assumes some prior knowledge.

Microsoft can say it is not subject to the terms of the GPL, but one can say one is not subject to the forces of gravity...

This is likely to become a court case. If Microsoft can satisfy a court that it is not distributing Linux (via the support vouchers), then its present dissociation from Novell and GPLv3 might -- MIGHT -- hold up.

Business is Business

Business is business in the office suite monopoly.

Bob Sutor has an interesting synthesis of Microsoft financials (referring to Tim Bray's comment a year ago)...

"[From 2006 reports]...this 'information worker' segment of the business generated about 26% of the revenue but about 50% of the operating income for Microsoft."

...with the fresh news of Microsoft User-Interface license which excludes GPL software.

Java is Free Software

Sun has accelerated the release of Java under the GPL. This was undoubtedly precipitated by the "SCOvell" situation; but, regardless, Sun is doing the right thing and a good thing for all technology.

There will be a huge volume on this so I'm going to lay back and let better people like Stephen O'Grady and David Berlind do what they do so well -- assess & contextualize.

Tim Bray's post is a definitive source so that's what I'm linking to now.

Open Source, GPL'd Java will be great for Linux, great for Solaris, potentially good for OpenOffice and ODF and, overall, excellent for SOA and system interoperability. Open Source Java will attract a lot more energy from kids, universities and research institutions as well as entrepreneurial hackers.

My blessing!

Stallman's Clarity

Required Reading:

"Keeping Free Software Free"
by Richard Stallman
BusinessWeek Online (March 28, 2006)

This BusinessWeek article is the 2-minute version of what Pamela Jones (Groklaw) kindly posted of the transcription (by Ciaran O'Riordan) of Richard's remarks at a keynote address in Turin, Italy, introducing the GPL v3 and the non-superficial thinking that goes with it.

Above all Stallman is clear.

Like v2 of the GPL (released in 1991), v3 is intended to maintain the spirit of the GNU General Public License -- reinforcing the Four Pillars of Software Freedom -- while bringing it into our post-Post Modern age.

The Four Freedoms are...

1. run the program as you wish;

2. study the source code and change it to do what you wish;

3. make and distribute copies when you wish; and

4. distribute modified versions when you wish

According to RMS, our modern world is rife with treachery, and since I do not represent any particular corporation, any particular group of shareholders, and have no media or technology investments, I have the luxury to find myself in full agreement. Richard's ideas for GPL v3 are on the money and their force & practical portent will have been sharpened by Eben Moglen, Counsel to FSF.

GPL v3 attacks DRM, so-called "Trusted" Computing, copy-protection schemes, patent aggression and ways corporations would use Free Software to interfere with any of the Four Freedoms. The reason the debate is more heated than ever is that the stakes are higher now: more GPL software is being used by corporations and the trend will increase rather than decrease over time.

Open comment on GPL v3 will last the better part of this year. This discussion and the story of OpenDocument adoption are the two most important developments in technology.

Tune in.


Sam Hiser

OFF-WHITEPAPERS

ARTICLES


www.flickr.com
This is a Flickr badge showing public photos from swhiser. Make your own badge here.


Locations of visitors to this page


Google
Search PlexNex

  

View Sam Hiser's profile on LinkedIn

Powered by TypePad