Massachusetts Finalizes OpenDocument Standard Plan
wellington map writes "The state of Massachusetts has finalized a proposed move to an open, nonproprietary format for office documents, a plan that involves phasing out versions of Microsoft's Office productivity suite deployed in the state's executive branch agencies. Massachusetts expects its agencies to develop phased migration plans away from productivity suites that do not support OpenDocument, with a target implementation date of January 1, 2007. Looks like it's finally cemented after some heated discussions."
Seriously, I like it. I like the fact that govs are looking at the bottom line and trying to streamline operations. Phasing out Microsoft? That would have been unheard of ----- last year.
I am happy to hear the Chew'setts have the brass tacks to pull something like this off and I can't wait to see Microsoft shoot themselves in the foot on this one.
The dangers of knowledge trigger emotional distress in human beings.
While it will take more than days, I think that Microsoft will eventually come around and support OpenDocument. There's no technical reason that they cannot and Microsoft can't afford to let big customers get away. Once large companies and governments realize that they can get along just fine without Microsoft products, it will be even harder to get them back on the crack, so to speak. So I wouldn't be surprised if there are already betas running in Microsoft somewhere that support OpenDocument and they run on the Microsoft Linux Distro too!
Anyway, in the end, the customer is always right. So Microsoft will come around if OpenDocument gets any kind of real traction.
To the making of books there is no end, so let's get started
One of the guys behind KOffice has just posted an open letter refuting a few aspects Alan Yates/Microsoft's criticism of open doc.
By the way, what will happen when the Federal government sends documents to Massachusetts in word format? Would the state send them back?
Suppose M$ suddenly decides to support OpenDocument, gets the state's business and then issues a "security patch", that introduces proprietary extensions as has been in the past?
Well, I can think of an easy answer: to begin to get out of the financial box MS has put most US governments. I can only speak about my own experience working in IT for Multnomah County in Portland, OR, but I know that they were spending millions each year on MS licensing fees, both for OS and Office applications. Sure, it can be expensive to switch IT standards, but it seems to me the more governments rely on open standards and open source software the less they have to spend keeping expensive proprietary software around. As a side note, Oregon at one point was considering a bill that would force local government IT to consider open source when making technology decisions. A move that had MS down there in a jiffy with a team of FUD spreading lawyers who quickly squashed it. As a partial result, Multnomah county is now 100% MS, no NetWare, no Linux, no alternatives allowed. They even fired or demoted those who refused to switch....