Slashdot Mirror
UK Govt Warned: Don't Buy GPL
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."
That which is free.
What should I do??
they'd rather sell you their closed source buggy software at over-inflated prices. did you expect "industry leaders" to suggest otherwise?
abcdefghijklmnopqrstuvwxyz
The government is there to hand out taxpayer money to corporations.
It's so obvious.
the major advances in civilization are processes which all but wreck the societies in which they occur - A.N. White
fact is: opensource is changing the IT industry economics and IT providers should adapt or die ...
...
...
... (anyone in it 's sane mind really believes that OSS is inherently bad and insecure ? got tell that to NSA, NASA, ESA, IBM, the City of Munich or google ...)
as usual some people really don 't get it (not a big deal - dynossaurs got extint anyway) and will try all sorts of dirty tricks like this one
I hope as an european netizen and taxpayer that EC watch bodies look very wel at this kind of tricks
Other than that - lots of good publicity for OpenSource
Cheers from Portugal
"Hi, we don't like having to compete with these guys. Could you please help us destroy our competition? If you do this, competition between the existing installations will improve! Really!"
A study commissioned by the fox, today issued a strong warning against putting a lock on the henhouse. "Locks are dangerous things. They can pinch your fingers. They cause changes in behavior that are undesirable."
- For the complete works of Shakespeare: cat
Number of mentions of the word innovations per page is roughtly equivalent to the probability that this report was funded and ghost written by Microsoft.
Lets see: 3 mentions in 4 pages. MS probabilty factor - 75%.
Just because you are a member of a group does not mean you always have to agree with the majority.
I know. I'm an American.
"Provided by the management for your protection."
They clearly either misunderstand the GPL or are blatantly lying. The GPL does not require you to disclose anything unless you distribute the modified version.
Thus the MI-5, CIA,CSIS, Interpol, or whatever can freely develop their own internal software under the GPL, and deploy it throughout their systems. The requirement to include source only applies if they distribute the product. I expect intelligence agencies don't normally distribute sensitive software outside the agency.
You're damn right its tax-payers' dollars we're talking about. Whenever the UK government buys software from Microsoft, IBM, Oracle etcetera, they are essentially converting British Pounds Sterling into US Dollars and sending them off to US-owned companies. At least with GPL software its less likely to be spent improving a foreign economy, as we have as much chance to compete here in the UK, what with having access to the source code of this non-proprietary software.
One of the previous arguments of proprietary vendors is that a governament shouldn't base their decisions on the license of the software, specifically, the GPL. Instead, governament should decide based on the functionalities of the software. For example, Microsoft Office's Word is the best word processor available, so the governament should buy it, since it meets the user's demands.
Now, the table have turned. These UK lobbists are asking to deny a software based on its license, and that it doesn't matter if it is the best tool for the job. As long as it is GPL, it is wrong.
Highly amusing. It only indicates that proprietary vendors are shooting everywhere hoping that one of their arguments convince someone. And that the "feature-rich" argument, after all, isn't working.
Buy a Nintendo DS Lite
At least the KFC kernel is very stable, having been dead for some years now...oh wait, that's colonel!
I,
Am in the unfortunate situation alluded to in the article referenced.
As a sole proprietor I've worked two years on a fairly sophisticated aviation simulation program that has usages in planning new airports and in airspace changes.
I would like to make my project GPLed.
Unfortunately, there are companies much more politically connected than I am that would absolutely love to take the code, go to the government official that they have in their hip pocket and sell it to them.
Sure, the stuff would have my name written all over it, but the government official would probably never ever see the code. All he would know is that some slick sales person sold him on the software and more importantly the big fat maintenance/upgrade contract that goes along with it.
That sort of thing is basically how it works in government contracting. Government guys have zero ethics and will screw you over in a heartbeat.
It's sort of like an ego trip for them. They know they have you (especially if you really want to sell them something) and they will jerk you around bigtime.
So yeah, if you're in a particularly giving mood then GPL is just fine. Just plan on not being able to put gas in your car for the rest of your life if you're gonna deal with government people.
Because there is always somebody who is going to make they government person more happy they you will, even though you might be the "expert".
Having said that, I have made my software's code available with fairly lax licensing terms.
The terms basically state that if you license the code and then try to sell anything based upon it then you owe me a piece of the pie.
If you want to use it for in-house purposes then you are free to use it.
If you don't like the terms then you can develop the code yourself.
Caution: Contents under pressure
There may in some cases be a conflict between the Government's desire to maintain confidentiality and the requirement to disclose the software laid down by a restrictive licence, to the extent that the source code itself discloses attributes about the Government body that are regarded as confidential
Absolutely incorrect.
The GPL does not in any way cover internal distribution. This is not the same as public distribution. Making modifications and keeping them within your company, but not releasing the source, is completely uncovered by the GPL.
In regards to software that the government funds, the government should NEVER fund proprietary software development (except for things which are meant to always be secret, like the US govt's program to predict how radar bounces off of curved surfaces). Public money should not be used to create private information, or proprietary programs, which the public then has to pay for again.
In regards to what software is acceptable for the government, this organization's concerns about the GPL are bogus, and anything they say should be ignored. Irrelevant of the truth, they are going to advocate the use of proprietary software. It benefits them.
The proper course of action is for the government to give strong consideration to FOSS, and if it decides against using FOSS, it should have to publish and explanation of it's decision to the public. In fact, any decisions on what software the government uses should be justified to the public, and the government should be required to consider FOSS, for the very frequent cost advantages of using it. The government has an obligation to tax-payers to consider what is likely to in most cases be a less costly solution.
social sciences can never use experience to verify their statemen
Suppose I am a government funded researcher. To be precise, people and businesses in my country pay their taxes and the government awards me some of this money to fund a new software system. Suppose my system is useful for SMEs to quickly help them to communicate opportunities to do business. It doesn't matter what it does exactly; the key is that there is communication between different organizations and that this is facilitated by my government-funded project. If I GPL this software, everyone in the country gets to use the software. If you're so inclined, you could go into business to try to make money from the software; you could improve the interface, or make it easier to search for partnerships, or whatever. Of course, you must GPL your changes, but you might be the clear leaders in the installation and configuration of this SW, so you could make some money. In any case, whether you can make money or not, the taxpayers do not lose out.
Suppose now that the software is released into the public domain, or even under a BSD licence. Suppose further that half-a-dozen firms spot a market opportunity to improve this project and make a commercial product out of the system. This is fine in principle, but if one of those six firms is Microsoft, we have an immediate problem. MS could decide to integrate the system into MS Outlook; perhaps the system uses email to communicate opportunities. We still have no problem of course, because there are five other competitors, any of whom could come up with a better approach to improving the product. Perhaps some of them will flourish in organizations which do not use Outlook for whatever reason.
However, if MS wishes to, they can simply make a subtle change to the protocol used by their version of the software. Because MS Windows is universal, this new protocol becomes the de facto standard. Of course, even this wouldn't be a problem, so long as MS published their changes to the protocol.
Suppose however that MS declines to publish their changes to the protocol. Our five other competitors are pushed out, and whatever money there is to be made from the software will accrue to Microsoft. For all I know, MS are paying a huge amount of tax, and perhaps they should have the opportunity to make a killing like this. The problem is that all the other taxpayers get to pay twice; they funded the original software with their taxes. And now if they want to get the benefit from the money they "invested" before, they have to pay again, this time to Microsoft. Of course you could argue that MS might have made significant improvements, but I don't think that argument holds, because they wouldn't have to make any useful changes to effectively require taxpayers to pay again for what they have already funded. All Microsoft needs to do is to make some subtle and unimportant and secret change to the communication protocol and they've made an instant market for themselves (or, more accurately, they've damaged another market).
I think that this is the key problem with BSD and public domain licensing for taxpayer-funded software.
Reality is defined by the maddest person in the room
"But when development is done with everyone's dollars, it should be open for use by all."
Absolutely it should be open for use by all. GPL software is absolutely "open for use" by one and all. The GPL even states it has to be. So don't worry, your business can run linux, too.