Red Hat CEO Says He Talked Patents with Microsoft III

A quick final follow up on this post (for those of you who still have a little doubt). From eWeek:

Microsoft and Red Hat are no closer to a deal involving intellectual property cooperation, Microsoft has confirmed.

“Red Hat and Microsoft have previously had conversations about interoperability, but none of our recent conversations have included discussions about intellectual property cooperation,” Horacio Gutierrez, Microsoft’s vice president of intellectual property and licensing, told eWEEK.

This effectively puts to rest—for now—the speculation that the rival operating system vendors might actually be talking about a deal that includes some kind of intellectual property provision and/or patent covenant.

Enterprise customers, however, have a great deal of interest in seeing the two companies work together because of their investments in both sets of technologies. Bob Muglia, Microsoft’s senior vice president for server and tools, admitted that interoperability and support for major Linux distributions have come up repeatedly at the company’s Interoperability Executive Customer Council.

“Our message [from customers] was really very simple: ‘Go and talk to Red Hat because we very much would like to [work with both systems],'” he said.

Both companies say they hear their customers, but remain camped on opposite sides of the argument.

Paul Cormier, Red Hat’s executive vice president of engineering, told eWEEK that the company is still willing to work with the Redmond, Wash., software maker on the interoperability front, but that it wants to limit those talks to pure interoperability between Windows and Red Hat Linux, with the goal of solving real customer problems.

But Microsoft’s official position is that interoperability and intellectual property are not completely separate issues and have to be considered together.

Gutierrez emphasized that Microsoft remains “open to exploring a deeper collaboration with Red Hat that includes intellectual property cooperation for the benefit of our mutual customers.”

But while Microsoft is committed to building bridges with the open-source community, “collaboration on interoperability and intellectual property are important foundations for those bridges,” Gutierrez said.

That approach will not work for Red Hat; Cormier’s position has been, “I want to talk to the folks at Microsoft about our two operating systems and how we can work together to solve real customer problems without attaching any unrelated strings, such as intellectual property.”

Cormier also ruled out any possibility of Red Hat doing a deal with Microsoft like the controversial patent agreement and covenant not to sue that Microsoft penned with Novell last year, especially after viewing the limited information that is publicly available on that deal.

That’s a pretty definitive answer. Whether Microsoft will concede and work with Red Hat on interoperability without the IP strings remain to be seen. It’s clear that Microsoft customers want this, however. Kudos to Red Hat for holding their ground.

–jeremy

IBM Pledges Free Access to Patents Involved in Implementing 150+ Software Standards

From the press release:

IBM (NYSE: IBM) today announced that it is granting universal and perpetual access to certain intellectual property that might be necessary to implement more than 150 standards designed to make software interoperable.

One likely result of the pledge to commercial and open source communities is that it will be easier for more computing devices and software to be compatible with one another. The move, which IBM believes is the largest of its kind, is also designed to spur industry innovation, while discouraging litigation.

The software specifications and protocols involved in the pledge underpin industry standards, such as those reflected in Web Services: programming, transactions and data exchanged on the Internet and Web. These are typically under, or moving toward, stewardship by standards groups such as the World Wide Web Consortium and OASIS.

“IBM is sending a message that innovation and industry growth happens in an open, collaborative atmosphere,” said Bob Sutor, IBM’s Vice President of Open Source and Standards. “Users will adopt new technologies if they know that they can find those technologies in a variety of interchangeable, compatible products from competing vendors. We think customers will like this added assurance for the open standards upon which they have come to depend.”

IBM’s commitment not only applies to the distributors, developers or manufacturers that are implementing the specifications involved, but also extends to their users or customers. It is valid as long as adopters are not suing any party — not just IBM — over necessary patented technology needed to implement the standards.

Matthew Aslett puts it well:

I’ve just taken a first look at IBM’s promise not to assert its patents involved in implementing 150 software standards and it appears to be a work of art in its simplicity.

Here’s how the pledge works:

Just get on with developing interoperability based on these standards – don’t even bother coming to us to get a license, you don’t need one.

But if you assert patent claims against IBM, or any one else for that matter, relating to these standards, you better make sure you’ve got the lawyers ready.

Compare the elegant simplicity of this approach with trying to pick and choose which partners to collaborate with based on complex and divisive patent covenants.

Of course, IBM didn’t do this out of pure altruism. Surely they think they can compete more effectively on a level playing field. Opening up in this way will help bring parity to that field. The 3rd party inclusion is also a great way to battle things like the recent Microsoft patent FUD. It’s a reminder of mutually assured destruction. Hopefully others such as Sun and HP, who could benefit in similar ways as IBM, will join the fray. Despite the business implications of a decision like this, it’s impressive how a company as big as IBM (and with the history of IBM) is able to see the big picture like this. They saw the light far earlier than many. You can find additional coverage by Bob Sutor here. A big thanks is due IBM for this one.

–jeremy

Comes vs Microsoft Petition Shows How Microsoft Blocked Linux Sales

Some people wonder why OEM Linux preloads like this didn’t happen sooner. Don’t forget that a couple companies did make small attempts, but were smacked down (PDF warning) by Microsoft:

Microsoft’s Predatory Response to GNU/Linux

142. GNU/Linux is an “open source” operating system that runs on Intel-compatible PCs. Microsoft has targeted the competing operating system by pressuring Intel, as well as various major OEMs such as Dell and Compaq, to boycott Linux. In late 2000, for instance, Microsoft executive Joachim Kempin described his plan of retaliation and coercion to shut down competition from Linux: “I am thinking of hitting the OEM harder than in the past with anti-Linux actions” and will “further try to restrict source code deliveries where possible and be less
gracious when interpreting agreements – again without being obvious about it,” continuing “this will be a delicate dance.”

143. LindowsOS (now known as Linspire), which is developed and marketed by Lindows.eom, Inc., is an Intel-compatible PC operating system based on Linux and which competes directly with Microsoft on the. PC desktop. On information and belief, Microsoft interfered with Lindows.com, Inc.’s ability to distribute its product through the OEM channel. Microsoft also initiated a lawsuit against Lindows.com, Inc. that adversely affected
Lindows.com, Inc.’s ability to exist, obtain; funding and conduct business.

Microsoft’s Anticompetltive Agreements With OEMs To Foreclose Competition

144. Microsoft Chairman and former CEO, Bill Gates, reportedly summarized the effects of the DOJ’s 1995 consent decree–which banned “per processor” licenses, among other exclusionary licensing terms as “nothing.” Microsoft was able to devise other restrictive OEM agreements to foreclose competition in the OEM channel, notwithstanding the consent decree

145. A “per system” license was the practical equivalent of the “per processor” license. Under the “per system” license, the OEM had to pay royalties to Microsoft for every computer of a particular “model” or “system” that it shipped–again, as with the “per processor” contracts, regardless of whether the PC contained Microsoft’s operating system. Microsoft defined “system” and “model” so broadly in its contracts that virtually all of an OEM’s production was subject to Microsoft’s “double tax” if the OEM wanted to give the consumer a choice of operating systems. Microsoft did not agree to give up its “per system” licenses in the 1995 consent decree, even though the Department of Justice warned the federal district court that “per system licenses, if not properly fenced in, could be used by Microsoft to accomplish anticompetitive ends similar to ’per processor’ licenses”–and in fact were.

146. Another way that Microsoft found to circumvent the federal court’s 1995 injunction forbidding its use of “minimum commitment/per processor” licenses was what Microsoft calls its “Market Development Agreements” (“MDAs”). Microsoft contrived the MDA as a device to evade the Court’s decree prohibiting Microsoft from requiring OEMs to adhere to “minimum commitments.” As Steve Ballmer (Microsoft’s current CEO) acknowledged: “We have always given better prices to customers who work with us to make the market. Those used to take the form of commits [i.e., minimum commitments] which we do not do anymore as a result of the [federal court’s] decree but we still believe in rewarding people who help us create demand. Hence the iMDA.” Under the MDAs, Microsoft granted large discriminatory price concessions to those OEMs that would agree to market and promote Microsofl’s Windows to the exclusion of any rival operating system. These discounts were calibrated so as to force the OEM to sell most of its computers with a Microsoft operating system in order to obtain the lowest price.

147. Because the OEM market is so competitive and profit margins are so thin, every OEM had to get the lowest price it could :from Microsoft in order to survive. In March 2002, a Gateway marketing executive (Anthony Fama) testified before Judge Kollar-Kotelly in State of New York et al. v. Microsoft, Case No. 98-1233 (CKK), about how Microsoft used its MDA program in order to force OEMs to market Microsot~’s operating system exclusively: “Given the substantial nature of these discounts, participation in the MDA, as a practical matter, is not optional. In other words, not receiving :these discounts would put Gateway at a substantial competitive disadvantage, and Gateway has communicated that self-evident proposition to Microsoft.” Microsoft also used its MDAs to lock OEMs in and competitors out by offering a discriminatory price to the OEM in a later year provided (a) the OEM reached Microsoft’s imposed goal of Windows sales over competitive sales in the prior year and (b) renewed its exclusionary contract with Microsoft for ,the later year. This placed the OEM on a perpetual treadmill, eliminating competition indefinitely. Microsoft continued these exclusionary terms at least past April 2002.

148. One method for encouraging competition in the operating systems market would have been the sale by OEMs of “naked machines” (i.e., computers that are sold without a predetermined suite of software forced upon the consumer). “Naked machines” would allow consumers to choose their computer’s software configuration from an array of competitive software products, either for preinstallation by the OEM or installation by the end user. Microsoft sought and obtained the agreement of the OEMs to refrain from selling “naked machines.” Instead, OEMs universally agree to “bundle” Microsoft applications and operating systems with their computer hardware, effectively depriving consumers of any competitive choices. These restrictive agreements exited before 2000 but, in 2000, Microsoft ratcheted the restriction up so that OEMs are forced to forfeit all discounts otherwise earned if they ship any “naked machines” to consumers. This heightened restriction, which (on information and belief) continues to the present, prohibits PC users and PC retailers from buying and installing lower priced or better quality operating systems of their choice.

It’s great to see that the grip on the industry is no longer as tight and companies are a bit more free to do what they feel is in the best interest of themselves and their customers. We’ve got a long way to go, but we’re making steady progress.

–jeremy

Update on ODF and Massachusetts

As Andy points out, “Silence means consent”. If this is a topic that is important to you (and it should be), I’d also encourage to take a few minutes and make your opinion known.

A few days ago, I posted my comments to the Mass. ITD on whether or not it should include OOXML in its list of approved standards. I also urged anyone with an opinion on this issue to send their own comments to the ITD at this address: standards@state.ma.us. Now, Pamela Jones, who has contributed hugely to the ODF effort in the past, has just posted a long and informative entry at Groklaw, pointing her readers to various resources that they may wish to consult in preparing their own comments, as well as ideas on the various areas upon which comments may be relevant. PJ has done her usual great job on this, and I’d encourage you to read her entry to see how her observations strike you.

It’s particularly important for you to consider doing so, because I learned from a reporter today that only about 50 comments have been filed with the ITD so far. With only 8 days to comment left, this compares very poorly to the over 150 comments that were received by the ITD in 2005. I have no idea what percentage of these comments are pro OOXML and what percentage urge the ITD to stick only with ODF, but given the small number in total, it could easily be disproportionate in one direction or the other, especially if a concerted effort has been made by one constituency or the other to influence the outcome.

Regular readers will know that I think that this is an important issue. Right now, the default decision in the ITD’s new version of the Enterprise Technical Reference Model is to include OOXML. In my last post, I paraphrased one slogan from the activist 1960’s that helped to shape a lot of who I am today. I’d like to now offer another catchphrase from those braver and more involved times, this time a chant from the many protest rallies that punctuated the antiwar movement: “Silence means consent.”

That slogan is particularly apt now, because the fewer the comments the ITD receives, the more certain will be the result. After all, if people no longer care, why should the ITD stick its neck out? The past immediate experiences of both Peter Quinn and Louis Gutierrez have made the consequences all to obvious. These people aren’t paid combat pay to be controversial – they’re just supposed to keep the IT structure effective for our benefit. If we want them to do more than just do what they’re told by vendors, we owe it to them to back them up.

–jeremy

OpenMoko

While the iPhone has been getting all the press, something seriously interesting has been happening in the Open Source mobile space. OpenMoko devices are becoming available. From a Wired Blog:

After seemingly endless delays, the OpenMoko phone is here. The first version of the NEO 1973 mobile phone, which carries the Linux kernel inside and is not locked to a specific network, is available for purchase from OpenMoko.com. It’s not as jaw-droppingly pretty as the iPhone, but it shares a design philosophy — no buttons, just a screen — and it’s ready to be loaded with any number of open-source software applications. (Though, according to Gadget Lab, so is the iPhone).

The base version of the NEO sells for $300. It has a 2.8″ VGA touch screen, a micro SD card slot, a USB port and 2.5G GSM quad band capability.

Keep in mind that this unit (the GTA01) was pushed out early so developers could begin writing device drivers, custom GUIs and some cool apps for the phone. The next revision (GTA02), which will be available starting at $450 in October, will be ready for the mass market. It will have wi-fi, 3-D motion sensors and added graphics accelerators. So this phone isn’t exactly an iPhone killer — the next one will be a contender. AptUsTech has a nice comparison of the NEO 1973 and the iPhone.

I’m going to try to hold out for the GTA02, but we’ll see if I make it. Bottom line is, I am getting one of these. I’ll probably keep the iPhone also, even if it’s just as a wi-fi enabled iPod. Which phone I’ll use on a day to day basis remains to be seen, but the more I use the iPhone the more its closed architecture is a limiting factor. If rumors of a pending firmware upgrade prove true and it does in fact allow real 3rd party apps things could change quickly. In that case I may just carry around two phones :) If you’re interested in the GTA01 you can find more details here.

–jeremy

Microsoft Statement About GPLv3 II

To answer a question I posed in a previous post about how Novell was going to handle the fact that Microsoft does not want to be a party to the GPLv3 (from the Novell PR Blog):

Shortly after the GPLv3 license was released, Microsoft issued a statement in which they expressed their view that Microsoft is not a party to the GPLv3 and it is therefore not applicable to them. Yesterday, they also articulated that, “to avoid any doubt or legal debate on this issue, Microsoft has decided that the Novell support certificates that we distribute to customers will not entitle the recipient to receive from Novell, or any other party, any subscription for support and updates that includes the receipt of any code licensed under GPLv3.”

Microsoft’s current position, taken unilaterally, is intended to eliminate any perceived ambiguity about the applicability of GPLv3 to Microsoft. Nonetheless and independent of Microsoft’s position, we would like to make clear our commitment to our customers that Novell will continue to distribute SUSE Linux Enterprise Server with its full set of functionality and features, including those components that are licensed under GPLv3.

For those customers who will obtain their Linux via a certificate from Microsoft, Novell will provide them with a regular SUSE Linux Enterprise Server subscription, regardless of the terms of the certificate provided by Microsoft. Customers who have already received SUSE Linux Enterprise certificates from Microsoft are not affected in any way by this, since their certificates were fully delivered and redeemed prior to the publication of the GPLv3. Novell will continue to put the needs of our customers first and ensure that they can take advantage of the latest version of SUSE Linux Enterprise to run their business.

Novell and Microsoft plan to continue our technical collaboration efforts which include our joint development work on virtualization, standards-based systems management, identity interoperability and document format translators. Regarding the applicability of the covenants not to sue in the Novell-Microsoft agreement and their applicability in a GPLv3 world, our respective customers will continue to have the benefit of those provisions. For Novell customers, all Novell products are covered by the Microsoft covenant not to sue, independent of their channel of distribution, including both server and desktop and whether they are licensed under GPLv2 or GPLv3.

Whether things end up playing out that simply remains to be seen. It should also be noted that just because Microsoft doesn’t want to be party to the GPLv3 doesn’t necessarily make it so. I’m not a lawyer and won’t venture a guess as to if certificate distribution binds them legally. The issue is getting plenty of coverage, though, if you’re interested. It does strike me as odd how much ambiguity the huge Microsoft legal team continues to leave, but if that’s intentional or accidental I’m not sure. I also surprised how short sighted and unimaginative Microsoft continues to be. I guess it’s all part of protecting the cash cows. Stephe sums it up nicely:

“The (July 5) Microsoft statement seems a bit premature and over reaching,” Walli said. “Stating outright that they aren’t a party to it, means they’ve cut themselves off from using it in some future circumstance where it might be genuinely business beneficial. They would need to unmake this statement. By saying they can’t envision such a situation arising shows a lack of imagination, and makes them as religious on the issue as (Free Software Foundation founder Richard) Stallman. They remain ‘committed to working with the open source community’ without actually wanting to participate in it.”

–jeremy

Feature upgrade release to the Internet Tablet OS 2007 edition

With all the iPhone hype, it’s easy for other gadgets to fall out of mind. The N800 is still a very cool device, however, and does quite a bit that the iPhone just doesn’t do (and never will). Oh, and it’s a mostly open platform. The latest firmware has just been released and contains some really nice features:

* Skype client support
* Adobe Flash 9 browser plug-in
* Up to 8GB memory card support
* better touch screen sensitiveness
* better battery life
* New pre-installed content
* Tableteer applet
* and more! (there’s a comprehensive roundup here)

It’s great to see that Nokia continues to add features and improve the device. The N800 is hands down one of the most useful (and slickest) devices I’ve ever owned. Hopefully I’ll get a chance to upgrade the firmware today. Previous upgrades have gone very smooth and it’s great that there is an official Linux installer.

–jeremy

Microsoft Statement About GPLv3

A quick follow up on my previous GPLv3 coverage. Here’s the official Microsoft statement:

Microsoft is not a party to the GPLv3 license and none of its actions are to be misinterpreted as accepting status as a contracting party of GPLv3 or assuming any legal obligations under such license.

While there have been some claims that Microsoft’s distribution of certificates for Novell support services, under our interoperability collaboration with Novell, constitutes acceptance of the GPLv3 license, we do not believe that such claims have a valid legal basis under contract, intellectual property, or any other law. In fact, we do not believe that Microsoft needs a license under GPL to carry out any aspect of its collaboration with Novell, including its distribution of support certificates, even if Novell chooses to distribute GPLv3 code in the future. Furthermore, Microsoft does not grant any implied or express patent rights under or as a result of GPLv3, and GPLv3 licensors have no authority to represent or bind Microsoft in any way.

At this point in time, in order to avoid any doubt or legal debate on this issue, Microsoft has decided that the Novell support certificates that we distribute to customers will not entitle the recipient to receive from Novell, or any other party, any subscription for support and updates relating to any code licensed under GPLv3. We will closely study the situation and decide whether to expand the scope of the certificates in the future.

It’s obvious why Microsoft wouldn’t want to be a party to the GPLv3, so their official position is not at all surprising. I’m not sure how Novell is going to handle the fact that a certificate that Microsoft gives out does not include support or even updates for GPLv3 software, though.

–jeremy

LQ will be in the .org Pavilion at the San Francisco LinuxWorld Expo

I’m happy to announce that LinuxQuestions.org will be in the .org Pavilion at the upcoming LinuxWorld Conference and Expo in San Francisco. If you’ll be near the Moscone Center between August 7-9, be sure to stop by .org booth 9 and say hello. You can use priority code N0113 to get a Free exhibit hall pass or 20% off a conference pass. See you in San Fran!

Conference Invite (pdf)

–jeremy

Survey: Windows loses ground with developers

From a recent InfoWorld article:

Microsoft’s Windows platform is losing traction as a target for application developers in North America but still is the dominant platform, according to Evans Data survey results being released on Tuesday.
Free IT resource

A survey this spring of more than 400 developers and IT managers in North America found that the number of developers targeting Windows for their applications declined 12 percent from a year ago. Just 64.8 percent targeted the platform as opposed to 74 percent in 2006.

“We attribute [the decline] largely to the increase in developers beginning to target Linux and different Linux [distributions]. Both Novell and Red Hat are the two dominant ones right now,” said John Andrews, the CEO of Evans Data.

The arrival of Windows Vista likely only kept the numbers from being even worse. “I think Vista probably offset some of the decline,” Andrews said.

The share for Windows is expected to drop another 2 percent, to about 63 percent, in the next year, Andrews said.

The targeting of Linux by developers increased by 34 percent to 11.8 percent. It had been 8.8 a year ago, according to the survey. Linux targeting is expected to reach 16 percent over the next year.

Evans views the situation as a battle of Windows versus open source with open source maturing, Andrews said. Windows remains tops, though. “They’re still dominant, there’s no doubt about it,” said Andrews. Use of Windows on the development desktop remains steady.

The survey, featuring developers at enterprises and solution providers like system integrators, covered both client and server application development.

Evans Data said the shift away from Windows began about two years ago and is accelerating. Linux is benefiting as are nontraditional client devices. Evans Data also surveyed developer plans for such platforms as Unix and Mac OS but did not release those numbers.

Now, I dislike “surveys” for a variety of reasons, which I’ve detailed in the past. They’re easy to manipulate, so can often come out saying whatever it us you want them to. That being said, I think in the right context and given the right qualifiers, surveys can be extremely informative. Sure, the linked survey isn’t without issue, so shouldn’t be taken without a grain of salt (only North America for instance, doesn’t seem to take into account people using languages that don’t target a specific platform). But, it comes to a general conclusion that seems congruent with what most people are hearing. As an industry wide trend, developer support for Windows is declining. I think that’s a leading indicator and one I’d be worried of if I were Microsoft. It’s not just Linux that they’re losing to, though. It’s Linux and OS X and the web (a huge one) and platform independent technologies and mobile devices and, well you get the idea. They are fighting a rising tide. I think < 50% of developers targeting Windows will be the watershed moment. Given the current trends, that may only be a few years off.

A quick note on a related topic. I often hear people say that many Open Source applications have surprisingly large download numbers for Windows. From asking around and thinking about this, that’s not surprising at all. I’d say it should be expected, in fact. You see, the adoption of Open Source apps in many companies is a grass roots type adoption. Because of this, coupled with the fact that Windows is still by far the dominant corporate desktop, you’ll get huge numbers of developers downloading various Open Source apps for Windows so they can test them out on their workstations. Once they are comfortable with the product and have a proof of concept, they very often (but of course not always) deploy them on non-Windows infrastructures. Raw numbers alone don’t always tell the whole story. It’s about context.

–jeremy