UK Govt Warned: Don't Buy GPL 806
JPMH writes "ZDNet is reporting that a UK IT industry body backed by Microsoft, IBM, Intel, BAE Systems and other high-tech heavyweights has urged the UK government not to commission open-source software, and particularly not software covered by the General Public License. According to Intellect, which lobbies for about 1,000 UK IT companies, the requirement of open-source licences for software funded by the government could have a negative impact on competition for contracts, the quality of the resulting software and even the confidentiality of government departments. In particular, Intellect recommends that the government drop the GNU General Public License (GPL), the licence upon which the GNU/Linux operating system is based, from its list of acceptable default licences for government-funded software, and steer clear of the GPL generally."
Re:Hard to buy (Score:5, Informative)
Re:IBM too? (Score:2, Informative)
Open Source itself isn't a bad thing, it's the viral nature of the GPL that lots of companies don't like. They like to be able to give a little and still release a "Enterprise" or "Enahnced" version that's closed up tight.
Re:Microsoft, IBM, Intel, BAE Systems (Score:2, Informative)
BAE SYSTEMS make commercial and military equipment for the UK govenment.
Check your facts!
Sounds about right (Score:3, Informative)
Yet another well-formed opinion from those who would save us from ourselves, our own prosperity and our own happiness as a society.
It just amazes me that there are still people who listen to these self-important, avaricious cry-babies who have somehow gotten it into their minds that profits from their current business models (without regard for their viability) are an inalienable right.
Re:I'm confused! (Score:2, Informative)
Re:Well, of course. GPL is severely restrictive. (Score:5, Informative)
Don't be (Score:3, Informative)
Off-the-shelf software is becoming a commodity, where you can get your basic OS/office pack from Linux. IBM wants to capitalize on those special use systems that OSS will never make because not enough people are interested in making. Government software may definately be one of them, I'm not talking about your average secretary office pack but real custom made stuff, or at least obscure enough you won't find any decent OSS alternative on Linux, or any alternative at all.
Kjella
Re:Hard to buy (Score:3, Informative)
Re:understandable (from they 're point of view) .. (Score:3, Informative)
Anyway - all pro-Open Source talk from the EU IMHO is just a lot of nice words and no action while at the same time they really don't understand what they're talking about and give more and more away to big multinationals...
Unfortunately I've only got a link about the news in dutch, but there's a petition to cut this crap over here [eurolinux.org]. If you agree with what it states, please sign it.
ZDNet is not reporting accurately (Score:5, Informative)
The ZDNet article misinterprets many things Intellect suggest:
1. Intellect does not suggest OSS licenses are all bad. Only GNU GPL could be problematic for the Government uses (ZDNet's title is so misleading)
2. The "GPL not suitable for secretive government bodies" is also overblown. The Intellect just suggests that if the Government wants to maintain confidential codes, they can't do it under GPL.
All in all it's fair to recommend the Government not going for 1 type of development model/license by default. The only question I have on the Intellect's analysis is that they suggested that businesses can't get back value of their IP under GPL. As far as I understand, GPL does not require distributing their software free (as in beer), nor giving up the right of redistribution (so I can't distribute a piece of GPL software in which the copywrite holder does not grant me the redistribution rights.) In that sense, GPL won't hinder commercial interest in software development as suggested in Intellect's paper, and the whole analysis could falls apart. But I'm not sure I'm correct on the GPL, better have someone more familiar with GPL to point it out.
Grammar Fairy sez: It's a good day to learn! (Score:2, Informative)
These two words, it's and its, are one of the trickiest in the English language. Here's a little mnemonic that may help:
Posessive "its" doesn't posess an apostrophe.
Using this little phrase, you can tell that your usage above is a contraction (it is less likely...), and hence should read:
"...with GPL software it's less likely
Magic Grammar Dust for you:
This is complete B.S. (Score:3, Informative)
If a piece of Governement funded software were to be subject to a restrictive license, such as the GNU GPL, commercial companies would often not see a benefit in entering tinto such an agreement because:
1) There is a limited amount of money that could be made from the original development because of the limited opportunity for further revenue.
2) They may not want to make public and available for free use any of their IPR that is employed in the development.
Feh. If in today's economy you've got someone balking at developing FOSS, then you can just find someone else. There are plenty of software companies who are hungry for work. They're not worried about future profits, because they're trying to stay in business today.
This is just B.S. cooked up by our "betters" in the IT industry to try to keep their pockets lined with taxpayer cash.
Re:Nothing Holy about Professional Programmers (Score:1, Informative)
This is not a joke. This is real. Both the open and closed source packages are large professional segments of operating systems.
Re:GPL license is political (Score:3, Informative)
I just had a quick look at the GPL. I didn't see any assertions that 'all published software should be free.'
It did say something to the effect that, if you want to publish software, you can protect yourself and make sure someone else doesn't profit from your effort by making it 'free.'
Commercial software licenses and BSD licenses also contain political messages, if implied. Isn't it nice to have choice.
Re:Hard to buy (Score:5, Informative)
If you commision GPL code from another party you could limit their rights by contract (you haven't distributed the code to them under the GPL, they have distributed it to you).
If you bring someone in as a contractor to do work for hire on the code then you may not have "distributed" the code outside of your organisation - so they might not have rights to it under GPL.
If you want another organisation to work on the code you have to distribute it to them under GPL, which would seem to mean that you can't place further restrictions (like NDA, classified etc.) on them that would prevent them distributing the code further.
GPL doesn't prevent you keeping things secret. It does prevent you doing a limited distribution and requiring the recipients to keep things secret. Unfortunately that is exactly what most military stuff needs - "secret" classification doesn't mean you can't tell anyone, it means you can't tell anyone who hasn't got the right clearance (which means they can't tell...).
Re:Its a bitch (Score:3, Informative)
Look at the NHS - a £6 billion budget for a nationwide system to unify hospitals. £6 billion!? The institution employs 250,000... even giving everybody a machine at £400 each you're talking little more than £100 million. Networking... decent servers and software... where the hell do they spend £6 billion? On outsourcing it to probably 13 or 14 different operators.
Software probably, its not like Microsoft HealthService 2003 ships as part of office.
Integrating 100's of information sources and making them securely/reliably available to all the others can't have been cheap.
Unifying hospitals is a bit more than actually wireing them together, in fact thats barely the start.
Alex