UK executive knocks back Govt projects that don't consider FOSS
theregister.co.uk
theregister.co.uk
In fact, if I was really cynical (which I am when it comes to how HMG spends our money) I might wonder if the use of open-source software might be pushed by consulting companies as an opportunity to increase their share of spend, rather than decreasing actual project costs.
This is the first time I've heard someone suggesting that it might be an opportunity to increase their share of spend, but ... you have a good point. However, it's not automatic that reduced software costs result in higher consulting fees. The government might have more money in general to spend on projects, but that's a good thing for everyone.
Ive been using mysql for 10+ years and the documentation on security still hurts my brain to look at - and AWS is even worse one of my developer colleges was unable to decipher how to log onto one of our aws systems even though he had the AWS login - the documentaion is confusing poorly written and in some key places just wrong!
The main difference is that open-source docs are usually lacking in general, while closed-source docs are there in large quantities (if someone figured out auto-generation, there's hundreds of pages) but still don't tell you anything important. The only part that changes is that someone was forced by contract to produce something - but it doesn't need to be usable.
I think these days I actually prefer to just look at the code to see what's going on rather than hope that on page 2xx I'll find something useful. Only the first source will never lie.
Proprietary companies also want to increase their share of spend. Unless open source companies charge more, what does it matter?
So by forcing them to consider FOSS this is the government's attempt to put it right. If they just told people that FOSS was now acceptable, people in some parts of HMG would still use closed source software in case the wind changes again.
What's bad is that departments appear to be excessively pressured into open source, which is not a good idea. It's important to go for the best tool for the job and the things you can manage the most effectively, which might not always be open source.
That wasn't the impression I got from the article:
“We believe open source isn't properly considered when we are doing IT. Our objective is not to have a target for open source in government – a year on year increase. Our objective is to best explore the opportunities out there. Sometimes that might be open source. At the moment, we believe we are missing out on the opportunities.”
Based on that quote, it sounds like they are taking a surprisingly well considered approach. Is this not the case in some departments?
But governments are a special case because they are using involuntarily-given public money and have a mandate to represent all citizens' interests and contribute to the public good.
Funneling public money to corporations in the form of contracts is a great nexus of corruption. The duty of a government is to the people, not to prop up (say) Microsoft, which provides services but also manipulates the market.
Any government which can build billions of dollars of military hardware annually can fix up or devise open source software. And then there is publicly usable software rather than JUST the perpetuation of a private company's strategy for claiming public money.