IBM joins the OpenOffice.org

To the collective cheer of “It’s about time”, IBM is now officially supporting the OpenOffice.org project. From the press release:

The OpenOffice.org community today announced that IBM will be joining the community to collaborate on the development of OpenOffice.org software. IBM will be making initial code contributions that it has been developing as part of its Lotus Notes product, including accessibility enhancements, and will be making ongoing contributions to the feature richness and code quality of OpenOffice.org. Besides working with the community on the free productivity suite’s software, IBM will also leverage OpenOffice.org technology in its products.

“In the seven years since Sun founded the project, OpenOffice.org has fueled and filled the need for document data and productivity tools that are open and free. Open source software and ODF are having a profound impact around the world, with numerous communities and organizations coming together to support these initiatives and governments, and corporations and schools standardizing on the software. We look forward to working with IBM and the other members of OpenOffice.org to ensure that this momentum continues. We invite others to join us in the community and participate in building the future as OpenOffice.org and ODF continue to gain popularity across the planet,” said Rich Green, Executive Vice President, Software at Sun Microsystems, Inc.

The accessibility gains here are huge for OpenOffice.org, as it means a foot in the door to some Government procurements that were not previously possible or would have previously run into issues. Stephe also points out the significance of Redflag Chinese 2000 Software’s participation in the press release, along with the potential ODF and UOF harmonization that may occur.

IBM almost certainly would have done this much sooner if Sun wasn’t the primary OO.o backer, but it needed to happen. Andy points out that the recent OOXML setback did impact the IBM decision to do this now. The question is, is this too late. I don’t think so. While it would have been great for ODF adoption if this would have happened earlier, I think we are still at a crossroads right now. OOXML approval is an uncertainty and the market is more open than it has been in a long time. Microsoft has overshot from a functionality standpoint and the emphasis is moving toward other items like Open Standards anyway. An opportunity this large only comes around once in a generation, as John McCreesh, the OpenOffice Marketing Project Lead, sums up well in the press release:

“This is great news for the tens of millions of users of OpenOffice.org and the thousands of individual members of the project”, said John McCreesh, OpenOffice.org Marketing Project Lead. “We welcome IBM’s contributions to further enhancing the OpenOffice.org product. But equally important is IBM’s future commitment to package and distribute new works that leverage OpenOffice.org technology supporting the ISO ODF standard. ODF is a once in a generation opportunity for the IT industry to unify round a standard, and deliver lasting benefit to users of desktop technology.”

For the record, that opportunity is about $15B annually. It’s easy to see why IBM and SUN were able to put their differences aside on this one. Carpe diem!

–jeremy

Microsoft kills its 'Get the Facts' anti-Linux site

A little late on this one, but Microsoft has replaced its Get the Facts site with one that is ostensibly less biased.

“The goal of the site is to offer more in-depth information and customer-to-customer opinions about many of the issues IT administrators face,” a company spokeswoman said. “It turns out people wanted 3rd party validation in addition to people’s experiences making OS purchasing decisions so in addition to customer case studies, research reports that compare platforms the site will also offer guidance around best practices, web casts, etc.”

Who would have thought people wouldn’t fully trust what a company said about their own products without “3rd party validation”. I don’t find it too interesting that the site was pulled down. After all, the Get the Facts campaign had been debunked and derided to the point that is was certainly doing more harm than good. I do find it interesting, however, that the new Windows Server “Compare” site doesn’t really compare “Linux” with Windows. What is does is compare “Red Hat Enterprise Linux” with Windows. This could be taken two ways. 1) Red Hat Enterprise Linux is the only real competition in the eyes of Microsoft. 2) Microsoft is specifically targeting Red Hat as a result of it not signing a deal similar to the one Novell signed. I’ll let you be the judge.

While on the topic of the Novell deal, it looks like the Microsoft and Novell Open Interoperability Lab is now open. The Microsoft marketing team really does like to stick the word Open anywhere is can. At 2,500 square feet (or 50 x 50) there doesn’t seem to be much room for engineers, especially when you consider the room also has 80+ servers and a SAN.

–jeremy

Kudos to AMD – ATI GPU Specs Released

Kudos to AMD for following through on an earlier promise to release GPU specs. The specs are now publicly available, without the need for an NDA. The RV630 Register Reference Guide and M56 Register Reference Guide represent almost 900 pages of 2D specs. 3D specs and specs for other chips should be coming soon. Awesome. We’ll see if this has any impact on sales for ATI cards. It will be interesting to watch the Linux driver mature and also see what, if any, impact this has on whether nVidia will release any specs.

–jeremy

Microsoft Fails to Gain Approval for OOXML

There are so many posts flying around about this that it’s been difficult to keep up (and I’m still digesting a lot of it), but the bottom line is that the OOXML is not an ISO standard. Well, at least not yet. A bit oddly, Microsoft has spun this in a positive way with their “Strong Global Support for Open XML as It Enters Final Phase of ISO Standards Process” press release. The reality is that this is just the beginning. Things now move to the next step, which should get really interesting. Microsoft is pulling out all the stops on this one. Andy Updegrove, who is not only extremely knowledgeable on the subject buy also extremely balanced in his observations, went as fas as to say:

As someone who has spent a great part of my life working to support open standards over the past 20 years, I have to say that this is the most egregious, and far-reaching, example of playing the system to the advantage of a single company that I have ever seen. Breathtaking, in fact. That’s assuming, of course, that I am right in supposing that all of these newbie countries vote “yes.”

I guess we’ll just have to wait and see a few more days to learn whether that assumption is true. Want to place your bets?

Looking at other sources, allegations range from ballot stuffing to nearly straight up coercion and bribery. That should be an indication of just how important this is to Microsoft and just how important it should be to you. It’s fascinating to see one part of Microsoft make what appears to be a sincere effort to join the Open Source community and then see another part act like this. I’ll be doing some additional reading/research and will certainly have more to say on the topic. For now, here’s some good additional reading for you:

Once More unto the Breach
Once More unto the Breach
consortiuminfo.org
consortiuminfo.org
consortiuminfo.org
All about Microsoft

–jeremy

Lenovo X61 – Update

A quick update to this post. As of Tribe 5, both audio and wifi work flawlessly in the default configuration. With the manual installation of ThinkFinger for the biometric thumb scanner, absolutely everything on the machine is working as expected. I’m really liking the form factor of this laptop, it’s going to be great for conferences and travel.

–jeremy

LinuxWorld UK Postponed

(via Dave) It looks like LinuxWorld UK has been postponed:

It is with regret that we must announce that LinuxWorld Conference & Expo 2007 has been postponed until spring 2008.

We have reached this decision following feedback from potential sponsors and exhibitors who feel that the event is too close to the Linux Kernel Summit. By delaying the show, we will be able to ensure that the content and programme are a true reflection of the needs of the Linux and Open Source communities.

We hope to be in touch shortly with new dates.

I was really looking forward to going to London in October, so am a bit disappointed by the news. Citing crossover with the Linux Kernel Summit does seem a bit odd, as Dave points out. I’m seeing if I can get any additional information now.

–jeremy

Why Microsoft fears Open Source more than other proprietary vendors do

It does seem as if Microsoft fears Open Source more than companies that are just as proprietary as Microsoft is. Matt has a potential explanation:

Now look at Oracle, SAP, IBM, etc. You won’t find a single other company making a concerted effort to fight open source. Not a one. Larry Ellison (Oracle) says open source is not something to be feared, but rather something “to be explained.” They clearly see open source as something to work with, and sometimes something to work through, but not something to destroy.

Sure, these and other proprietary-software companies occasionally dip into mudslinging against open source, but they don’t regularly buy analysts, set up anti-open source sites, rattle patent sabres, and generally insist on making a fetish out of open source’s demise.

Just Microsoft. Why?

I think it has a lot to do with how Microsoft chooses to make money. Microsoft, more than any other vendor listed (and many others that could be, like Autodesk, HP, Sybase, Salesforce.com, etc.), sells packaged software.

It relies, more than most companies, on a big, upfront license fee. At most vendors, such license fees barely pay for the cost of selling the product, causing them to rely on ongoing maintenance fees for their profits. So, whereas Oracle’s revenue stream looks not hugely dissimilar from an open-source revenue stream, Microsoft’s looks vastly different.

In short, Microsoft’s business and revenue model is threatened by open source much more than most proprietary software businesses.

When you look at current industry trends, both Open Source and closed source companies are relying more and more on maintenance and subscription revenues and less on pure licensing revenue. This means you have to provide continual value to your clients, or revenue starts to disappear. To me, that seems like how it should be. Matt continues:

Microsoft’s “house” is built on sand. The very factors that drove its success – easy-to-use, low-cost, integration between components – are the same things driving open source into the enterprise. Except that instead of lower cost, open source is free. Instead of integration of various components within the Microsoft-only ecosystem, open source’s open standards and open source code makes integration between disparate components – owned by different companies and communities – much easier than in the traditional proprietary world. And new open-source applications, operating systems, and middleware are heavily focused on customer value – including ease-of-use – which is challenging Microsoft on that front, as well.

Microsoft showed the way to beat the incumbent proprietary vendors, and its strategies are now being used against it by the open-source world. Except that this time, there’s one more huge value that Microsoft can never provide:

Freedom. Freedom from lock-in. Freedom to integrate and tweak and fiddle to make software work for the customer, because the vendors are no longer selling software. They’re selling service to make that software sing for the customer.

It’s very true, and somewhat ironic, that some of the strategies used by Microsoft are now being used against it. It shouldn’t be a surprise though – Microsoft does some things very well. The additional freedom from lock-in (and freedom in general) is the part that is going to turn the industry on its head though. For too long people in IT have been shackled. They’re getting a taste of freedom now and once you get that taste it’s painful to go back.

–jeremy

Community Involvement

At LinuxQuestions.org, community feedback is absolutely critical to us. On that note, I’m happy to announce the LQ Project Tools, which will allow us to monitor community feedback, bug reports and feature requests in a much better way than we have in the past. If you have a suggestion on a project you’d like to see us undertake, have found a bug or have a feature suggestion, please let us know. We really do listen.

–jeremy

Are SCO Execs in trouble?

From Mark Webbink:

Some have speculated that it would be worthwhile to now take SCO off the market. Heck, their market cap is now under $10 million. The problem is that paying $10 million to buy SCO would not be the end of it. SCO is still embroiled in the IBM case and the Red Hat case, to say nothing of the on-going claims that Novell has. In addition, when the lights finally flicker out on SCO, look for some shareholder lawsuits based on violation of securities laws. If you go back to the press conferences that SCO repeatedly called back in 2003 and 2004, they never began those press conferences by making the standard disclaimers cautioning investors to take what they were saying with a grain of salt. As a consequence, investors had every right to take what Darl McBride and Chris Sontag were saying in public back then as the gospel truth. Like McBride stating publicly that SCO owned the copyrights to Unix in the spring of 2003 while he was privately corresponding with Novell begging them to transfer the copyrights to SCO.

We have come a long way from that day in 2003 when McBride suggested IBM buy SCO for $500 million.

I’d expect shareholder lawsuits once SCOX runs out of money and it looks like Darl McBride and Chris Sontag might end up getting a little more than they bargained for. It would have been nice to see this case make it all the way through to judgment, but it’s looking less and less likely that SCO will be able to hold out that long.

–jeremy

OSI email group gets catty over Microsoft's Permissive License request

In what should come as no surprise, it looks like the discussion surrounding the Microsoft OSI submissions are getting a little cantankerous. From the article:


Another community member, Donovan Hawkins, doesn’t like the MS-PL’s requirement to keep its code separate from any other code licensed differently. “I can think of cases where I made MAJOR changes to some open-source function to use in a project,” he writes. “What sort of Frankenlicense would apply to that function if I wished to release my changes under GPL but the original was MPL or MSPL? Every other line of code under a different license?”

Things got really interesting when Chris DiBona, longtime OSI member, open source advocate, and open source programs manager for Google, Inc. chimed in:

I would like to ask what might be perceived as a diversion and maybe even a mean spirited one. Does this submission to the OSI mean that Microsoft will:

a) Stop using the market confusing term Shared Source
b) Not place these licenses and the other, clearly non-free , non-osd
licenses in the same place thus muddying the market further.
c) Continue its path of spreading misinformation about the nature of
open source software, especially that licensed under the GPL?
d) Stop threatening with patents and oem pricing manipulation schemes
to deter the use of open source software?

If not, why should the OSI approve of your efforts? That of a company who has called those who use the licenses that OSI purports to defend a communist or a cancer? Why should we see this seeking of approval as anything but yet another attack in the guise of friendliness?

That query got the attention of heretofore silent Bill Hilf, Microsoft’s general manager of platform strategy. “I’m unclear how some of your questions are related to our license submissions, which is what I believe this list and the submission process are designed to facilitate,” Hilf wrote. “You’re questioning things such as Microsoft’s marketing terms, press quotes, where we put licenses on our web site, and how we work with OEMs – none of which I could find at http://opensource.org/docs/osd. If you’d like to discuss this, I’d be happy to – and I have a number of questions for you about Google’s use of and intentions with open source software as well. But this is unrelated to the OSD compliance of a license, so I will do this off-list and preferably face to face or over the phone.”

Mee-ow!

Hilf went on to say that one of the reasons Microsoft coined the term “Shared Source” was “to acknowledge that these licenses had not been approved by the OSI, and some of our Shared Source licenses will not be submitted to the OSI.” But, Hilf wrote, “I’m open to make this more distinguishable on where/how we post the [licenses] on the Web site, if it’s important to the community.”

I’d guess this is going to get even more heated from here. The OSI may end up stuck between a rock and a hard place on this one. On the one side, it’s easy to argue that the entity submitting an entry should not even come into play and that a license should be approved or disapproved solely on its merit. On the other hand, some people reason that approving a license from an entity whom it’s perceived is out to harm Open Source is enabling them to do so, and therefor should not be done. That may be a slippery slope to walk on though. We certainly don’t want Open Source to become “whatever the OSI wants”, but at the same time we do need to trust the OSI to steward the Open Source label in the way they see fit. That is going to get interesting…

You can view the entire discussion here.

–jeremy