Software Choice Group Tells DOD Not to Use Open Source
ducomputergeek writes "A group calling themselves the Initiative for Software Choice, backed by Microsoft and others, is recommending that the DOD drop plans for further adoption of Open Source software. This comes after MITRE, a defense contractor, published a report stating that not only does the Department of Defense use opensource, but is recommend on using it more. The article is at News.com and you can read it here."
You can be paid to have them, or you can have them due to some deeply held beliefs with religious fervor, or you can arrive at your opinion through a process of reasoning.
On the other hand, reasoning that it's better to move to an open source product just because said OS product is currently attacked less, is fallacious.
Seriously, how can a group called "Initiative for Software Choice" that's backed by major players against open source (see Microsoft) be open and objective in this?
My good sig is in the laundry
My company does quite a bit of work for the big defense contractors, we're involved in many big programs. These contractors are constantly asking us for Linux based software (SDKs APIs etc.) and especially for their embedded devices. These guys want to stop laying huge license fees to WindRiver for their vxWorks software... and want to spend the $$ elsewhere. Good on them I say. However I will insert the obligatory M$ comment: I'm shocked (not!) that MS would push their own agenda blah blah blah... ;-)
"Content's a bitch."
FUD: You have to open up all your code if you use GPL code in your software.
Fact: You have to open up all your code if you use GPL code in your software and then distribute it!
I don't think the DoD distributes very much of the software it writes, so why should it care if it uses GPL code? It shouldn't care! But let the FUD fly!
Look at the tomato! Isn't it sad? He can't dance! Poor tomato!
It's a pitty to see Intel's name as one of the companies opposing OSS. Strangely they reach out at one side and then at the other side they slap you in the face. It is not that Intel should choose sides.
I can understand fully that it is in Intels best interest to have support from both camps but this is really something they should watch out for. It may well be that more OSS developers and users will buy the products of their competitors if these kind of things become normal practice for them.
Of course they're worried. If their corporate customers start saying "Hey, if the DoD is using it, it must be good and secure enough for us too!"
Oh and the GPL doesn't really stop the DoD at all, as you only have to release source code to those you provide with a binary. Unless DoD starts handing out binaries to others, they can keep every change to themselves (but I imagine they'd rather stay with the main branch than running their own solo run, but they are one of the few who could).
OSS is no magic cure against bugs though, and QA is important. In my experience bugs show up faster & get fixed faster in OSS, so in the short run you have more *known* bugs than commercial software, even if there aren't really any more bugs in it. In the long run though, if enough people use it and find bugs, it is more stable and bugfree.
Kjella
Live today, because you never know what tomorrow brings
you can have them due to some deeply held beliefs with religious fervor, or you can arrive at your opinion through a process of reasoning.
It's my experience that people first tend to form their opinions based on deeply held beliefs (or otherwise) and later use reasoning to give justification to their beliefs. It is extremely rare for someone to start without preconceptions and use reasoning to develop an objective opinion. It is even rarer for someone to start with a deeply held belief and change their mind based on reasoning.
For example, do most people who share files have liberal views on intellectual property because it justifies swapping copyrighted files, or do most people who swap copyrighted files do so because it validates their predeveloped liberal views on intellectual property?
Toronto-area transit rider? Rate your ride.
A group comprised completely of proprietary software vendors is recommending the use of proprietary software.
In the end, it is up to those who want their government to "choose" other software to let their voices be heard. This will work as long as politicians listen to the populace they supposedly represent, instead of listening with their wallets to companies from other states.
Of course, it may be that both the People and the "Software Choice" group of mega-corps both favor the use of proprietary software in government. My vote happens to be that our tax money which buys the software that runs our infrastructure should not be used to place our infrastructure under the control of a proprietary software vendor.
MORTAR COMBAT!
Even if the government only considered open source software, that does not exclude Microsoft from participation. Microsoft would be free to produce software which meets the requirements set, basically set there to ensure that software running our vital infrastructure, paid for by our taxes, does not place our government at the behest and mercy of a software company.
One way to ensure that safety is through the use of open source software. There are undoubtedly other ways, such as Microsoft could provide source licenses only to the government for software the government buys, etc.
However one of the main factors into considering open source software is the rising cost of software licenses. Since our tax money is used to buy this software, I for one would prefer we don't have to pay year after year for what amounts to yearly abandonware.
MORTAR COMBAT!
If you read the actual article recommendation the /. summary is simply incorrect. The recommendation was:
a) The choice of open source vs. closed source be made on a project by project basis and not be a matter of policy. In particular the DoD should not adobt a preferential policy favoring open source over closed source when possible,
b) While BSD licenses are OK using GPL licenses violate congressional norms (in particular they make commercial software impossible)
In addition things not mentioned in the summary
a) DoD is far and away the largest user of open source in the government
b) Security issues are ambigious with regard open source vs. closed source
c) A great deal of open source software violates all sorts of other government regulations and the government would end up having to bring these systems into compliance.
Yes the comments were hostile to open source particularly GPL they certainly where nowhere near the summary though.