Slashdot Mirror
UK Government Breaks Open Source Promises
judgecorp writes "The UK government has promised to favour open source systems in its procurement (and made those promises repeatedly). However, freedom of information requests have shown it is doing nothing of the sort. It is giving contracts to the same large suppliers as before."
Sadly, this is not that surprising. We are talking about the Government of the United Kingdom, or Her Majesty's Government as it is officially known. If you were a queen (who in the 21st century still won't enter the House of Commons and only talk with the House of Lords) then who would you rather listen to: him or him? We in the open-source movement have a problem with image. The sad truth is that the very people thanks to whom that movement was started don't really care about they appearance, the arguments that would get to the Upper Class. They think that just because they are Right - which they are, no doubt about that - everyone will automatically recognize that and make decision based on what would be the best for the humanity. Sadly we live in the world of politicians, lobbies, parties, Kings and Queens. We have to recognize that and work on our appearance if we ever want to go main stream.
The commitment was for open STANDARDS, not open source. Open Standards are also a good thing, but they are not the same as open source.
Andrew Oakley - www.aoakley.com
First up: Any government department that's got a significant investment in IT can't just go out and replace, say, Microsoft Office with LibreOffice overnight. There's a huge amount of testing to do, and when you hit upon things like Access databases and Excel spreadsheets that have become an entire department's IT system, it's very tempting to say "Stuff it. We'll stick with Office."
It's even more tempting when the F/OSS firm says "Yes, we can replace all those things - it'll cost £X hundred thousand, mind." The cost of a migration to a newer version of Office isn't seen by the higher-ups for the exact same reason that these databases and spreadsheets were able to become so widespread without anyone noticing - the people that maintain them won't make a big song and dance, they'll simply quietly beaver away tweaking their database so it works in the Latest Greatest Version. The cost of that isn't seen.
Second up: Something that a lot of people in IT don't realise unless/until they start their own business. Marketing something with any degree of success is remarkably hard - and it's as much an art as it is a science. At first, "make it free of charge" (or even "Make it remarkably cheap") sounds like an absolute corker of a strategy. How can anyone fail to sell a product when the cost is zero? Hell, you could probably throw up a website and have the world beating a path to your door inside a few days!
It doesn't work like that. If you're buying a product of any significance, the choice of product probably comes more from the salesman than from the product itself. As soon as you start saying things like "the software is free, but you'd have to pay for consulting to make it all work together" - you've got two huge problems. "The software is free" is the classic "sounds too good to be true" offer that will usually be regarded with extreme suspicion - and as soon as you say just one thing that makes your prospect suspicious of you, that's it. You've lost their trust and you won't get it back again. If you've ever watched Dragons' Den (I believe the US equivalent is called "Shark Tank"), you'll have seen exactly this happen.
The second problem is the "you'd have to pay for consulting" bit. The IT consulting industry doesn't exactly have a spotless reputation; anyone who's been in industry for any length of time can tell you all about the consultant they brought in at great expense who over-promised and under-delivered. At least with a COTS package there's the possibility of being able to evaluate it for some time before going ahead, that's greatly reduced when you're paying for one-off work.