Microsoft made major concessions Thursday that should make it easier for open-source software to dovetail with or even replace Microsoft products, but a major caveat means the company's legal threats remain alive and well.
Microsoft. Among other things, the company said it will share communication protocols that govern how Microsoft software products communicate; pledged not to sue open-source programmers for developing software that uses those interfaces; and launched an Open Source Interoperability Initiative to improve how well open-source software works with its own.
Although programmers now are apparently free to reproduce the software, Microsoft's generosity ends when the software crosses the threshold from project to commercial product.
"Microsoft is providing a covenant not to sue open-source developers for development or noncommercial distribution of implementations of these protocols," the company said. "Companies that engage in commercial distribution of these protocol implementations will be able to obtain a patent license from Microsoft, as will enterprises that obtain these implementations from a distributor that does not have such a patent license."
In other words, Microsoft hasn't backed down from its insistence that its intellectual property isn't free for the taking, an assertion made most clearly in 2007 when Chief Executive Steve Ballmer said Linux and other open-source projects violate 235 Microsoft patents.
"The promise not to sue is only for 'noncommercial' open source, which is a bit meaningless," said Jeremy Allison, a founder of the open-source Samba project that lets Linux servers substitute for Windows file and print servers by emulating the required Microsoft communication protocols.
The Thursday move suggests two forms of patent agreements. First is one in the mold of the controversial Microsoft partnership with Novell from 2006 and various other smaller Linux companies afterward. The second is an agreement directly with customers that use open-source software such as Red Hat's Linux, aswhen he said, "People (who) use Red Hat, at least with respect to our intellectual property, in a sense have an obligation to eventually to compensate us."
It's not likely Microsoft opened up its specifications and made its pledges Thursday out of the goodness of its heart. As the open-source movement and its free-software predecessor have matured over more than two decades, Microsoft has found it necessary to make accommodations.
First, the open-source programming philosophy outdid Microsoft in an area where it previously had been a leader, fostering communities of developers. Second, there have been years of antitrust litigation, first by the United States and more recently from the European Union, that called on Microsoft to share. The third, and perhaps strongest reason, is that open-source software has become a powerful force in the software industry and customer sites--and even at Yahoo, the Internet company Microsoft is trying to acquire for $44.6 billion in part because of its engineering expertise.
The Samba case illustrates the pressures on Microsoft. In December,, a move that came shortly after the European Union required Microsoft to share interoperability information with open-source projects.
Sharing protocols, while it makes it easier for others to interoperate or clone Microsoft products, also could serve to entrench Microsoft's products by making its in-house protocols into de facto industry standards.
Take OOXML, the office document format Microsoft is trying to standardize as an alternative to the ODF that was spawned from the OpenOffice.org software, an open-source rival to Microsoft Office. "The approval of OOXML, for instance, is seen as crucial by Microsoft as a means of maintaining its Office market share," The 451 Group, an analyst firm, said in a statement Thursday.
And as ZDnet blogger Mary Jo Foley noted, the ISO standards group is meeting in Geneva next week to vote on whether OOXML should be awarded official standard status.