Woot!!!

I’ve been trying to get the commands and organizations within DoD to embrace open-source for years! At times it feels like an impossible battle… THEY WON’T EVEN LET US USE FIREFOX!!! I have IE6 and MS Office 2003 at work.

The media totes Intellipedia being a huge improvement within the government – which it has been – but the paradigms are still the same… stovepipes! Just this week, the command I am contracted to announced another blog within the confines of the organizations firewall. We’re not even sharing efficiently with our counterparts within DoD.

Please excuse the venting of a frustrated collaboration consultant and social software evangelist. Is there any hope?!?

While I can certainly see the large benefits of switching to open source platforms, there are problems involved with switching. Microsoft gives governments extensive enterprise licensing deals when they use Windows along with Office along with Outlook along with …

There is considerable re-training time to consider when moving Administrative Assistants and even less technically-inclined employees to a new software system. Also, products delivered by Microsoft systems are more readily accepted by the general public. This is not to say that the long term cost benefits of open source aren’t viable, I’m just playing Devil’s Advocate.

[...] no-bid Microsoft contractshttp://blogs.zdnet.com/open-source/?p=2835Public policy and open sourcehttp://www.wikinomics.com/blog/index.php/2008/08/28/forcing-governments-to-use-open-source/Forcing Governments to use Open [...]

Will,

I find it hard not to agree with everything you said in your post. It is frustrating, to say the least, that open source was not even considered an option. It scares me that the people make decisions on our behalf, or just making decisions in general, are not considering all of their options.

Cost aside, you hit the nail on the head with your comment about customized versions of the software. I have been a Linux user and open source advocate for a few years now and it is unbelievably easy for a technology-savvy person to customize software packages that can be deployed on any platform. It is important to take Shaun’s comment on retraining seriously as this is probably the biggest problem in making the switch, but informing employees of the benefits is step one.

In order to induce change, rewarding departments for switching to open source could be a useful avenue. Keep in mind that open source does not mean no cost as there will be training and installation costs, but as time moves forward the benefits will far outweigh the money paid out. I look forward to seeing what action, across government organizations, occurs due to this suit.

Great writeup Will!