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."
Hard to buy (Score:5, Funny)
Re:Hard to buy (Score:5, Informative)
Re:Hard to buy (Score:3, Insightful)
Re:Hard to buy (Score:3, Insightful)
Most software in use is special purpose.
It actually makes sense for a customer to want his program to be gpled, he is not dependant on the original supplier for later upgrades.
(Although usually the original supplier is the best place to go for such things as they have the best knowledge of both the product and your setup).
Jeroen
Re:Hard to buy (Score:3, Interesting)
You can charge for writting it.
Most software in use is special purpose.
It actually makes sense for a customer to want his program to be gpled, he is not dependant on the original supplier for later upgrades.
This has nothing to do with open source. I write special purpose software exclusively. My clients buy the source - they are not dependant on my company to make changes (although they can hire us to do so). GPLing it just means that our company can just take the source and give it away - in most al
Re:Hard to buy (Score:4, Funny)
Re:Hard to buy (Score:3, Insightful)
just my 2 eurocents.
Re:Hard to buy (Score:5, Insightful)
Re:Hard to buy (Score:3, Funny)
Re:Hard to buy (Score:5, Interesting)
Put it this way: the BSA just wrote a European law. Still think the government are working for us?
Re:Hard to buy (Score:3, Informative)
Re:Hard to buy (Score:3, Interesting)
True, but AFAIK, it's perfectly legal for one of the developers to take some of that code home. That can be a very bad thing.
Re:Hard to buy (Score:3, Interesting)
Because some of what government does should be kept secret does not imply that all of what government does should be kept secret.
But what's absolutely foolish is that they seem to be saying that BSD s
Re:Hard to buy (Score:5, Insightful)
Wich doesn't exclude the usage of GPL'ed software. GPL only says that you should allow anyone that got binaries from you to get the source code as well. Meaning that your government actually get the code of the guidence systems. That government is then 'allowed' to share that code with whoever they choose, but they are not forced to do so in any way. So there is nothing in OSS that prevents anyone from keeping things secret...
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...).
I'm confused! (Score:5, Funny)
What should I do??
Re:I'm confused! (Score:5, Funny)
July, so this is good news. But the day of the week is odd, so we're
supposed to only bash Microsoft and SCO. But the 1 of the digits in the day matches 2 digits
year, so we only especially entrench ourselfs against critisism the GPL. But it was
posted AFTER 18:00, so this is good news.
Got it?
Re:I'm confused! (Score:3, Funny)
Re:I'm confused! (Score:5, Funny)
Homer: That's bad.
Homer: But it comes with a free frogurt!
Homer: That's good.
Shopkeeper: The frogurt is also cursed.
Homer: That's bad!
Shopkeeper: But it comes with a free choice of toppings!
Homer: That's good!
Shopkeeper: The toppings contain sodium benzoate.
[Homer looks puzzled.]
Shopkeeper: That's bad.
Homer: Can I go now?
Re:I'm confused! (Score:5, Funny)
Homer: You had me at comfort.
Re:I'm confused! (Score:5, Funny)
Re:I'm confused! (Score:4, Insightful)
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 eno
Re:I'm confused! (Score:4, Insightful)
You should improve your reading comprehension; there is no indication in this article that IBM endorses this action, or even knows about it. They just happen to be a member of the organization that does, one of over 1000 members.
big surprise.. (Score:5, Insightful)
That's pretty weird (Score:4, Interesting)
Re:That's pretty weird (Score:5, Insightful)
I would even go as far as to suspect that IBM's Linux services division would be upset at this.
From IBM's own mouth, they make over 80% of their revenues on custom integrations and support, which means that GPL software is a good choice from their perspective. Proprietary software wouldn't make them much more money.
Re:That's pretty weird (Score:5, Insightful)
I don't think IBM or any of the other old-UNIX-gone-Linux vendors especially prefer Linux. They sell it because customers demand it.
If they had their druthers, they'd still be locking folks into AIX, OS/2, or other solutions they can control. There's a huge benefit to customers making purchasing decisions based on insurmountable need for more of your product, rather than price shopping whenever a cheap new commodity box might lighten a load.
They'd also be quite happy if the software wasn't getting faster instead of slower. It used to be a given that the new versions of your software with new features you need would run slower than the last version, mandating extra hardware upgrades.
Re:That's pretty weird (Score:3, Interesting)
Whose side is IBM on? (Score:3, Funny)
What gives??
Good Sense (Score:5, Insightful)
The government is there to hand out taxpayer money to corporations.
It's so obvious.
Re:Good Sense (Score:5, Insightful)
It's so obvious."
Parent is modded as funny, but it's actually fact.
The Public Private Partnership, championed by the New Labour government, was all about (in it's propaganda blurb) the private sector getting the profits, because it was taking the risks.
In practice, however, they take the profits, and the taxpayer bails out the compaies concerned when things go wrong - the private sector gains and the public sector takes all the risk.
The government does hand out taxpayer's money to corporations.
It's not obvious, though, it's bleedin' blatant.
That's like Ronald McDonald... (Score:3, Funny)
DUH.
Re:That's like Ronald McDonald... (Score:5, Insightful)
"It'll cost more in the end, you don't have the freedom to choose from a menu, plus no Happy Meals!"
Re:That's like Ronald McDonald... (Score:5, Funny)
Its a bitch (Score:5, Insightful)
interesting times indeed
IBM (Score:3, Interesting)
Re:IBM (Score:3, Insightful)
So what else is new? In the OS/2 days, there was an internal segment of IBM that loved OS/2 and promoted OS/2 while at the same time another segment of IBM was doing almost everything in their power to destroy OS/2. Schizophrenia at IBM is not unheard of.
understandable (from they 're point of view) ... (Score:5, Interesting)
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
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 whi
Re:understandable (from they 're point of view) .. (Score:3, Interesting)
True, but by the same token, a lot of people do get it.
I'm the lead developer of LISSARD [lissard.org], an open-source school administration system. I am having discussions with someone in the U.K. who is very interested in free software, and in particular, using LISSARD in several of the schools he represents.
As I understand it, some U.K. courts have recently ordered thei
In other news ... (Score:5, Funny)
And apparently the UKG is supposed to overlook... (Score:5, Insightful)
"Don't buy GPL" (Score:3, Insightful)
* Don't send a gift to Linus
* Never buy a beer from the OSI guys
* [your 'I misunderstood the topic,too'-line here]
Before you get upset about this... (Score:3, Insightful)
From the list above, you can see that some of the most popular open-source technologies are not GPL. "Recommending against the GPL" does not mean "Recommending against open source."
Just something to keep in mind...
Re:Before you get upset about this... (Score:3, Insightful)
Perhaps not. But if you would have read the article, or heck, even the summary you would have seen this little gem:
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.
Re:Don't be stupid (Score:3, Insightful)
The GPL does no such thing. It does not prohibit dual licensing. These companies are perfectly free to offer to buy the rights to incorporate the code under another license directly from the copyright holders.
Now why should the government, in other words *you*, via your tax dollars, be financing work which proprietary software v
NEWS FLASH: Fox warns against locking henhouse (Score:5, Funny)
Simple equation (Score:5, Funny)
Lets see: 3 mentions in 4 pages. MS probabilty factor - 75%.
Greater probability (Score:3, Funny)
They're more inclined to listen to South Africa (Score:3, Insightful)
The Commonwealth looks like it's verging towards a common strategy.
"The OEE and the DTI are considering establishing open-source licence terms as the default for government-funded software"
This sounds like it's swinging the pendulum even further than South African plans.
"When the Government decides to develop software using a restrictive licensing base, such as the GNU GPL, (it) should be aware that this would prevent it from deriving commercial gain
Which would be bad because we all know how much of our software we buy from the British government.
Corporations pay taxes too... (Score:5, Interesting)
I don't believe a closed source license is a good one at all, but likewise I don't think the GPL is the best idea either. Either putting it directly into the public domain, or using a BSD style license is the best solution, IMHO.
NOTE: This is for discussions of software being *developed* with government dollars, not when bidding is going on to use existing software for a contract, which is a whole different issue. But when development is done with everyone's dollars, it should be open for use by all.
Re:Corporations pay taxes too... (Score:5, Insightful)
They are not losing anything but the ability to fuck over the citizenry with proprietary lock in schemes and dodgy data formats. How the hell is that in the public interest?
There is a weird proposition here, that because a business says they would like govt to give them code they can lock up, they should get it. The point is that no corp would have that code without the govt forcing them to fund it via tax. Why, exactly, are they deserving of the right to take from the commons and not give back?
Re:Corporations pay taxes too... (Score:3, Insightful)
I agree absolutely, which is why the government should create software under a BSD license.
"There is a weird proposition here, that because a business says they would like govt to give them code they can lock up, they should get it."
Whose locking up anything?
Under the BSD license the code is FOREVER free. The only thing locked up is the extra contributions added to it, which is their work and
Re:Corporations pay taxes too... (Score:5, Insightful)
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.
Re:Corporations pay taxes too... (Score:4, Insightful)
You can do whatever the hell you want with it, except prevent others from doing the same.
I guess it also really irks you that you can't set up a toll booth at the entrance to a public park, eh?
Intel? (Score:3, Insightful)
Government Business (Score:4, Insightful)
Call me old fashioned (and having said that I know I'm going to get at least one post that says "You're old fashioned"), but I thought governments were about internal order, external defense and maintenance of currency. Even being relatively liberal they should still only be concerned with generally looking after their citizens, not creating software.
After all, the British govt. providing the NHS really limits its ability to make money by running private hospitals. And if they didn't provide all those policemen they could make a fortune as a private security firm!
Cheers, Paul
Interoperability not in TCO (Score:3, Insightful)
It might make MS stuff look better in the short term, but I think we need to send emails etc. to the makers of theres TCO analysis and demand it be included. Why would the cost of interoperability be any less than say education of system Operators.
Once the component is included it is much easier to have a sober debate on the long term cost of "lock-in"
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.
Nobody seems to have pointed this out yet... (Score:5, Insightful)
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.
Re:Nobody seems to have pointed this out yet... (Score:5, Funny)
Re:Nobody seems to have pointed this out yet... (Score:5, Funny)
GPL license is political (Score:4, Insightful)
Unlike BSD, the GPL carries a political message in it, and the government would have to back all the statements in GPL such as "All published software should be free software", the definition of "free", etc.
For what it's worth, I personally don't think all software should be free, but more importantly, I disagree with the idea of having to distribute a political message with my software.
All the OSS software I wrote has been released under BSD-like terms, and when I use software in my projects, I give preference to BSD-licensed ones.
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.
Interesting (Score:5, Insightful)
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.
How government software works (Score:5, Interesting)
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.
Nothing Holy about Professional Programmers (Score:5, Interesting)
Now the Industry might be spreading some lies around about how open source code is buggy and of lower quality than stuff done by the "professionals" but I think that's a load of crap. Even the worst open source projects I've looked at seem to be only as bad as the average professional code-base. Open source guys tend to code toward the features they need only, but if you paid them to implement features you need, I'm sure they wouldn't have a problem doing that.
As far as the license issue, if I were in charge of a government (or other) agency, I would demand access to the source code of the work I'd commissioned. I would even consider releasing that code to the world, if not under the GPL license at least under a BSD one. Big IT companies might fear that because if their code made it out into the world, they would have commit seppku from the embarassment of the code quality or having some wise-ass kid releasing a much-improved version.
dead wrong (Score:5, Insightful)
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.
When you only have a hammer... (Score:3, Insightful)
Businesses are geared to think only in terms of how profitable a certain action can be, and are incorrectly projecting that necessity-for-profit onto others. Intellect appears to be trying to equate their perception of a reduced commercial value of GPL'd software to a reduced societal value of GPL'd software. And while the former is an unproven assertion at best, the latter is downright wrong.
Should we abandon the creation of roads where the cost of building a new highway exceeds the revenue of the resulting taxes? What about housing for the poor? Surely we're not "deriving commercial gain" out of those projects?
Seems to me this is yet another case where commercial organizations need to be reminded by the public that they exist only at the pleasure of the populace, and by their grace. When a commercial organization (or other entity) begins to promote it's own interests over the advancement of the society as a whole, that society is correct in recognising such an organization as hostile.
The GPL and predatory monopolies (Score:5, Insightful)
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.
Write your MP (Score:3, Interesting)
Now is the time to write your MP. Write him a _polite_ letter (snail mail is best in this case), in which you explain to him that GPL is good, esp. for government funded software. Read the comments in this thread, to get some arguments.
The most important thing is that you stress that this is important to you. Important decisions win votes.
Re:Write your MP (Score:3, Interesting)
Now is the time to write your MP.
That would be write to your MP, Yank. Fax [faxyourmp.co.uk] is best actually (in my experience).
I find this sort of rabid Linux/GPL/open source zealotry particularly irritating. As far as I'm concerned (as a UK tax payer) I want the government using the correct tool for the job required, using cost as the primary deciding factor. I'm sure time will tell that a UNIX (not necessarily Linux) solution would prove to have a cheaper TCO than an MS Windows platform. Ideally, I t
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.
Something I've wanted to say many times when (Score:5, Interesting)
looks like a job for the European Commission (Score:3, Insightful)
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.
A Critique (Score:3, Interesting)
Read the pdf, what a hodge-podge of unsupported statements. Firstly it is written from the perspective of the "Sponsoring" software companies. As pointed out, it totally ignores the fact that 99% of Government funded in-house code is for internal use. Why? Perhaps because they have specailist needs. How many Defence Departments or Internal Revenue agencies does any nation have.
Suddenly the premise that commercial software houses "do so in order to supply the software on a repeating basis and thereby to generate licensing revenues that allow them to make a profit on their investment" becomes null and void.
Governments do create or sponsor code for distribution to end users or clients, particularly in Health and Internal Revenue. Much of this is distributed free in the interest of eGovernment and reducing costs to the taxpayer. The development platform here is dependant on what the client machines have (usually Win95/98) and they can code it in VB if they are stupid enough. A large segment of the economy is still run on clipper code.
"Such a proposal would inevitably act as a deterrent to commercial involvement in Government sponsored R&D software projects because they would have such a limited opportunity to exploit any commercial gain from any privately owned IPR.." So this reads like they expect to profit from Government funded R&D, I thought this was where stendards otfen arose from due to the long term investment and the free rider effect. Normally, when a company pays you to write code they own the IP and I fail to see why this should not be the case with the application of public money. This effect was again raised yesterday by Hans Reiser. US style Corporate Welfare is perhaps not that appealing to the rest of the world.
Some other points;
Lack of adequate competition in the bid process.....
What they are really saying is that "we want to be protected from competition". Especially from small independant development firms that may be able to deliver on a more cost effective manner and with much less overhead. That would be worse that government bodies buying the development tools and coding it themselves.
Software that would not include leading edge developments.......
Like corporates and Governments implementing JAVA and web services and not waiting for .NET
This doesn't mean "we have established products and would like you to help protect the monopoly positions we have created by lack of interoperability
Very basic software which would only provide minimally useful solutions.....
Ah yeah, like "Hello, Microsoft. We are thinking of standardising on WinServer2003 if you could add...".
Confidentiality issues....
Well dont release the code. And if you do, don't copy any privacy law protected personal data into it.
And finally "For the reasons discussed the setting of a default position for use of restrictive licences such as the GPL, brings with it some commercial disadvantages that may in some cases outweigh the benefits." Read any MS EULA.
I would be interested to see the role IBM really has in this as it smacks of biting the hand, Linux and JAVA seem to be a large factor in the slowing down in the death of the mainframe.
I hope I haven't taken any quotes out of context, but they really need to be speaking to someone like Richard Alston in Australia.
Reminds me... (Score:3, Interesting)
Re:Well, of course. GPL is severely restrictive. (Score:3, Interesting)
Re:Well, of course. GPL is severely restrictive. (Score:3)
Frankly anything government funded should be either BSD or public domain at least in countries with extortionate taxation like UK. The taxpayer has payed for it 100 times. He should be entitled to use it as he sees fit.
So no closed source, royalty shit either. I have pa
Tell them that... (Score:3, Funny)
Re:Well, of course. GPL is severely restrictive. (Score:5, Funny)
Re:Well, of course. GPL is severely restrictive. (Score:5, Insightful)
In this case, the GPL is exactly the same as the BSD license.
It's only when the user stops being a user and starts being a distributer that the rules change. The GPL does not allow people to stand on the shoulders of giants without a return in contribution.
It's not users (or "beleaguered UK taxpayers") but profiteers that are under additional restriction.
Re:Well, of course. GPL is severely restrictive. (Score:5, Informative)
Re:Grammar Fairy sez: It's a good day to learn! (Score:3, Funny)
Re:Well, of course. GPL is severely restrictive. (Score:5, Insightful)
Why should they? Your tax payer dollars pay for your city park, yet you aren't free to set up a business in your city park; in fact, what you can do in your city park is quite restricted. And the purpose of those rules is so that everybody can enjoy the city park.
It's quite analogous with the GPL: tax payer dollars pay for the software, and the GPL ensures that the software remains there to be enjoyed by everybody.
Likewise, the fact that tax payer dollars pay for software development doesn't mean that anybody should be able to use that software for whatever they please.
Keep in mind that the same kind of people who make this argument against the GPL now had not trouble making the argument a few years ago that governments should pay for software development in the private sector and then leave ownership of that software with the companies that developed it.
Re:Well, of course. GPL is severely restrictive. (Score:3, Insightful)
Not what the government has purchased with tax dollars but what the government has developed with tax dollars.
Re:Well, of course. GPL is severely restrictive. (Score:3, Interesting)
The GPL and FreeBSD licenses are restrictive to users in almost the same way. They can use software under both licences free (once they obtained it), make changes and let everyone copy it. Only difference is that the BSD license asks to leave the advertisement intact and the GPL to provide source code.
But then you are already on a developing level. The only difference between the licenses is on this level.
Re:Well, of course. GPL is severely restrictive. (Score:3, Interesting)
However a simple copyight notice or note in some help files is different.
BSD is alot more friendly in this regard. MS for example rarely even mentions the university of california qoute. Linux does not either unless you view the source.
BSD is deffinetly more corporate friendly. This is why Apple chose that instead of Linux when designing MacOSX. Their lawyers rightfully were worried that the FSF might su
Re:IBM too? (Score:4, Interesting)
-t
Re:IBM too? (Score:5, Insightful)
Re:IBM too? (Score:5, Insightful)
We need to view corporate relationships with a lot more cynicism than we currently do. The corporation views you as a resource, much like a desk or a computer monitor and will treat you as such. You can't hope they won't turn on you -- you have to expect them to. It's not a matter of "if," it's a matter of "when."
I'm sorry if I come across a bit strongly here, but it's something that very few people in the community actually understand. I think we all want to believe, in our hearts, that companies are made up of people and people are inherently good. Well I'm here to tell you that companies are made up of people and people inherently suck!
Re:IBM too? (Score:5, Funny)
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.
Re:With any luck... (Score:3, Funny)
you have to remember that lobbying groups in Parliament are 10 a penny.
You must have gotten quite a deal. Over here, they're a dime a dozen.
Negative impact. (Score:5, Insightful)
Yeah, it's a bitch when a company can't slap a widget onto government funded software and then sell it back. You can see how the GPL might drive bid prices, aka government costs, down. As for quality, it's hard to see how someone can go wrong with GPL'd software.
GPL-lovers are very quick to cry for censure of any company suspected of violating the license.
Hey, that's the way copyright works. Big dumb companies set it up so they can screw you and me. Too bad when it gets used in a way they did not expect. Various programmers are quick to cry foul when they see work they wanted to stay free and are giving away, used by some big dumb company in an abusive manner. You don't think those same big dumb companies hesitate to set their well funded leagal department on individual programmers if they catch a wiff of anything they might lay claim to? Just look at SCO trying to extort the entire world of Unix. Nothing like that can ever come out of free software. Get back in your hole, troll.
Re:Negative impact. (Score:5, Interesting)
They're already way ahead of you. Check out this passage from the license agreement for the open source computational fluid dynamics software called "ISAAC" (can be found here [sourceforge.net]):
NO SALE TO U.S. GOVERNMENT
11. The PROGRAM, and/or any modified version thereof, shall not, in any manner, be offered for sale to the U.S. Government, without the written consent of the U.S. Government. The U.S. Government shall not pay a second time for the PROGRAM or any enhanced/modified version therof. The PROGRAM may be used in contract with the U.S. Government, but no charge may be made for its use. If the PROGRAM is modified using or enhanced using U.S. Government funds, the Government will be provided the complete source code of that modified/enhanced version and the intellectual property rights of the resulting modification/enhancement shall be controlled by such funding agreement.
In other words, the government already paid for it once, and they'll be damned if they're gonna pay for it again. I'm quite sure that this passage was a requirement of their federal research grant.
Public domain is the way to go (Score:5, Insightful)
There is no reason why publically funded IP should be copyrighted by a corporate entity.
I could understand BSD if it was only partially government funded, but for anything paid for by the taxpayers... PD is it.
Re:BSD is the way to go (Score:5, Insightful)
Yes. But how is that any different from any other software license?
Even closed source code is open to legal trouble. Perhaps even more so?
Re:BSD is the way to go (Score:3, Interesting)
Unless you create software, you never have any quarrel with the GPL. If you do make software, you'd better be sure you have a valid licence to use that code because by default copyright law you have no rights whatsoever.
Stealing GPL'd code is the corporate version of copying MP3s. Damn easy, and very little chance of getting caught. The reason you see so much flak about