Slashdot Mirror


"Software Choice" Campaigns Against Open Source

Verizon Guy writes: "News.com is reporting that a group called The Initiative for Software Choice, led by the CompTIA, but backed primarily by Microsoft and Intel, is lobbying against Open Source-only laws in for example, the State of California government and the government of Peru. While their goals don't specifically mention open source, they do mention that publicly-funded research should steer clear of licenses such as the GPL. Interesting read."

29 of 398 comments (clear)

  1. Software Choice! HA! by program21 · · Score: 3, Insightful

    Interesting that a group calling itself Software Choice is trying to tell people not to choose certain software.

    --
    This has been a test. Had this been a real emergency, we would have fled in terror and you would not have been informed.
    1. Re:Software Choice! HA! by OSgod · · Score: 5, Insightful

      Interesting that the groups associated with Open Source are attempting to limit a states choice options in software (i.e.: Open Source only laws).

      Let the market rule. Some Open Source products rule. Some stink. Some proprietary products rule. Some stink. A law forbidding you from looking at Open Source products would be "bad". A law prohibiting you from considering non-Open Source products is just as bad if not worse.

  2. No story here... by swordboy · · Score: 4, Insightful

    This isn't a campaign against *open source* but rather a campaign against *open source only laws*. I can fully agree with that. Freedom of choice.

    Stop loading the headlines.

    --

    Life is the leading cause of death in America.
    1. Re:No story here... by taliver · · Score: 3, Insightful

      Open source only laws are the embodiment of fiscal
      responsibility


      Not true. Fiscal responsibilty in government institutions comes from extremely well written specifications and a closed, low bid system with underwriting. Not allowing a closed source shop to compete certainly does not help fiscal responsibility.

      I'm all for open source, but I really don't believe anybody should be strong armed into releasing their code. Remember, freedom of speech should also be freedom not to speak as well.

      --

      I demand a million helicopters and a DOLLAR!

    2. Re:No story here... by Chanc_Gorkon · · Score: 5, Interesting

      If open source costs more in man hours (don't be foolish....you know as well as I it can), retraining and possibly hardware, it could very well mean it could cost more than say sticking with Microsoft or IBM OS/390. Cost is more then just the cost of the software. That said, I do prefer Open Source, but not necessarily because of cost.

      With Open Source, the answer is always out there, usually. It isn't always so when trying to navigate a vendors website. With Open Source,if Red Hat, SuSE or say Debian doesn't have an answer for your problem, someone else usually does!

      I am against Open Source only laws because I want to choose what is best for the situation in question. MySQL is not yet an acceptable replacement for a well done installation of Oracle. Also, when storing massive amounts of info in a database, I want someone to guarantee some sort of stability or performance. I want something others of used (yeah I know, others have used MySQL, but I still would not trust it with a critical database) and has been proven. That's one case. In others, well, I hate to say it, others use microsoft. Granted I know that there are word processors on Linux, but there are certain things you do. You don't want to retrain everyone on a Word Processor....ever. My point, Open Source only laws, while good for Linux and in my opinion a great number of things in the public sector, would prevent you from going to something that may be new and revolutionary. Choice between Open Source and Closed Source products should be maintained. Saying your not being fiscally responsible by not choosing open source is like giving the coffee away for free and having to pay 10 bucks for the cream and sugar. If you can't get all three (ie someone who's already there and isn't going to cost more, who knows Linux and available hardware are the cream and sugar) for free, it ain't worth it.

      --

      Gorkman

  3. Open formats/protocols by Jondor · · Score: 5, Insightful

    While I personaly like and use open source I don't have the illusion that this goes for everybody.
    What I would like the goverments to do is to define open fileformats/protocols and only accept/buy software which supports these formats 100%.

    Ofcourse this also means that ALL govermental communication should use these formats and nothing else. This may not be the end of closed source, but at least it levels the playing field and should brings competition back where it belongs: comparing price and quality.

    --
    Nobody expects the spanish inquisition!
  4. US Government Copyrights by Slak · · Score: 5, Informative
    I've often wondered how US Government agencies (such as the NSA with SELinux) can legally GPL code. According to the US Code Section 17 Chapter 1 Section 105 (http://www4.law.cornell.edu/uscode/17/105.html):


    Copyright protection under this title is not available for any work of the United States Government, but the United States Government is not precluded from receiving and holding copyrights transferred to it by assignment, bequest, or otherwise


    So I'm not sure that these companies don't have a point. I would think this indicates that the government cannot extend GPL code, as the GPL is based on copyright (er, copyleft). Granted, I have but a limited understanding of Copyright Law and the legal basis behind the GPL. I would like to see this issue explained, however.

    I would think that any changes the US Government (or its agencies) made to GPL code would have to fall into the Public Domain. By the same token, if the NSA were to make an UltraSecure Windows OS, then their modifications would not be assignable (as US Government works do not enjoy copyright protection) to Microsoft and would also fall into the Public Domain (just their diffs, not the whole work).

    Obviously, US Code Section 17 Chapter 1 Section 105 does not preclude the government from merely using Open Source (or any form of software, for that matter) without extending it.

    Cheers,
    Slak
    1. Re:US Government Copyrights by Col.+Klink+(retired) · · Score: 4, Insightful

      Government employees can not copyright their work (done for their jobs), but contractors (like Donald Becker when he was at NASA) are not employees but independent agents and they can copyright their work. Similarly, government funded research is not owned by the government but by the researcher.

      --

      -- Don't Tase me, bro!

  5. Steer clear? by Black+Parrot · · Score: 4, Interesting


    > they do mention that publicly-funded research should steer clear of licenses such as the GPL.

    Actually, the GPL is how publicly funded research should be licensed. These people are doing nothing more than lobbying for an entitlement.

    --
    Sheesh, evil *and* a jerk. -- Jade
  6. Bad Idea by deke_2503 · · Score: 4, Interesting
    "'When public funds are used to support software research and development, the innovations that result from this work should be licensed in ways that take into account both the desirability of broadly sharing those advances as well as the desirability of applying those advances to commercialized products,' the group stated."

    Basically, the taxpayers' money should be used to finance "commercialized products" that make money for somebody else...

    "In a recent speech delivered to the Government Leaders' Conference in Seattle, Microsoft chairman Bill Gates likened the concept of open source to anti-capitalism. Warning developing countries against using software based on the GPL, Gates said those who put development time into it are denying themselves the benefits of essential taxes."

    And we all know that anti-capitalism is..communism. I knew those Chinese were onto something with their Linux.
    However, this is not actually true. If a government uses taxes to fund research/development of software, the benefit ti the said government is software--why should it care how it is licensed, as long as it is functional?

  7. not quite so simple by Unordained · · Score: 4, Interesting

    notice that they also asked that research not be put under GPL-like licenses, under the assumption that government-funded research should be resold afterwards ... personally, i don't appreciate giving money to the government, in the form of taxes, and then having to buy back from them what they discovered thanks to my money ...

    i'll agree that laws like this can be bad -- wouldn't want to restrict stuff too much ... but consider their reasons aren't just financial: in the case of Peru, they were very much interested in having the ability to fix code themselves, look through it for spyware, and write their own, based on what they had access to, if necessary. open standards may not be the norm, but when you have full access to the source code ... even non-open standards can become so. (reverse engineering of open-sourced software, mostly because somebody forgot to comment their code?)

    note that they are also trying to promote the idea that open-source = no funds, which is not true. red hat and mandrake (and many others) have shown that open source is not without rewards. note also that the french government is getting their linux from mandrakesoft, which, lest i be mistaken, is a french company ... the argument about taxes is weak in this case: the french government will be getting linux (free) and support (not so free) from mandrake, and they'll collect taxes back from that same company ... promote the creation of tech jobs in france, etc.

    so it's not completely loaded -- it is against open source, partially, under the veil of being pro-choice ...

    1. Re:not quite so simple by sheldon · · Score: 3, Insightful

      personally, i don't appreciate giving money to the government, in the form of taxes, and then having to buy back from them what they discovered thanks to my money ...

      Personally I don't appreciate giving money to the government in the form of taxes so that it can be used to compete against my free market corporation.

      but consider their reasons aren't just financial: in the case of Peru, they were very much interested in having the ability to fix code themselves, look through it for spyware, and write their own

      It's important to note that all of these legitimate goals can be accomplished without the use of the GPL.

      Basically the Open Source community has distorted the argument. If you read the Redhat proposed bill it all sounds very good until you get to the anti-commercial software clauses in Section 3, items e and f which demand that all software must be free as in beer as well as open source.

      so it's not completely loaded -- it is against open source, partially, under the veil of being pro-choice ...

      Similar to how the Redhat proposed bill is anti-commercial software under the veil of being pro-freedom?

  8. Campaigns Against Open Source...? by jukal · · Score: 5, Interesting
    How exactly are they campaigning against open source? To me it says rather - if not very - neutrally that what they want is that open source, semi open source, and closed source and their licensing methods should co-exist. Also, I share their opinion that it would be very stupid to make organisations choose from only what is available under open source.

    I do think that it is a big plus for many (or most) products if it is an open source one. Even if it was true in all cases, some closed source products can still be superior. There are cases and specialist areas in which development under closed source can be done with bigger and better resources, which eventually results in a better product.

    ...and I must say that I prefer open source a lot... and still I think these proposed open source -only laws are utterly stupid.

  9. Open file formats by nuggz · · Score: 5, Interesting

    I think the idea is fully documented file formats that we can edit with alternate applications.

    I don't think we should legislate free software, because quite honestly if MS has the best solution for that task, we SHOULD use it.

    What we should have is that all file formats should be clearly documented and have a non discriminatory royalty free, patent free licence to use in competing products. Then there wouldn't be an arguement.

  10. Places where open-source-only *may* be appropriate by dpilot · · Score: 3, Informative

    (I can't take credit for this, since I read it, but can't remember where, so I can't attribute, either.)

    The problem comes when government at any level distributes information in any electronic form. At that point, the issue isn't really Open Source as much as it is Open Formats and Interchange. For a large part, and IMHO Microsoft is one of the greatest offenders, proprietary software tends to entrench itself with proprietary formats.

    As I view government information available in electronic form, I want the freedom to choose what software to us. If the government publishes in proprietary formats, they have abridged my freedom of choice. In fact, in doing this they meddle in the market, granting certain companies competitive advantages over others, based on their software choice.

    Sticking with Open Formats and Interchange is the only way that the government can avoid forcing choices on citizens. It's the only way they can avoid reducing competition in the marketplace.

    If Microsoft (and other similar software makers) could avoid their desire for proprietary formats, this wouldn't be an issue.

    An Open Source law for government misses the issue, completely. Even so, it may well accomplish the correct end. Still, it would be better to be on target.

    --
    The living have better things to do than to continue hating the dead.
  11. Free help for "Software Choice" by standards · · Score: 5, Insightful

    I love these guys... they're so honest. But their "principles" need some help...:

    "Procure software on its merits, not through categorical preferences"

    Maybe they could say "Please don't judge our product on the license agreement! Our license is designed to maximize our stranglehold on you... and if you disallow our software due to it's license, well, we won't be able to take advantage of you".

    "Promote broad availability of government funded research"

    Perhaps instead they could say "We'd like to package up taxpayer-funded research and sell it back to the tax payers! All for profit! Please don't take that away from us - because we'd hate to have to pay for more research."

    "Promote interoperability through platform-neutral standards"

    Perhaps they could say "Don't place standards on us, because we want to try to monopolize the industry. If the standards are open source, how can we lock in our customers?"

    "Maintain a choice of strong intellectual property protections"

    Maybe it'd be better to say "Don't weaken our intellectual property, because we spent so much money on research! We need to recover our research burden. Of course, much of the research came through tax-payer funded research grants, but we still want it all. After all, we're in it to make as much money as we possibly can, and a legal monopoly is our best approach."

  12. Stalmann told me it wouldn't happen by famazza · · Score: 3, Interesting

    About two year ago, in a FreeSoftware presentation by Richard Stalmann (did I spelled it correct?) I have asked him if he have ever considered the possibility of liberty restricting laws, such as DMCA, affect GPLed softwares, Free Softwares or even any kind of Open Source.

    He told me that this possibily does not exist and that DMCA exists to protect copyrighted material that, in his opinion should, be protected. He told that Free Software is Copylefted and would not have any risk of being affected by such laws.

    Unfortunately he was wrong. In the last year I saw two initiatives trying to ban FreeSoftware from US. I know that he don't have the obligation to preview such things, but it should be better if we have more "gurus" that are able to preview these kind of problems.

    About all these attempts to ban FreeSoftware from US, all I have to say is that I'm really sorry that there's people in the government that can't understand that FreeSoftware is about Freedom and this is one of the base concepts of democracy. Don't US government consider itself democratic?

    --

    -=-=-=-=
    I know life isn't fair, but why can't it ever be un-fair in MY favor!?
    1. Re:Stalmann told me it wouldn't happen by sheldon · · Score: 3, Insightful

      Campaigning against a law which bans commercial software is not at all the same as campaigning against open source.

  13. I'm really gona lose Karma for this but... by SuperCal · · Score: 3, Interesting

    I hate to say this seeing as I just got the automatic +1 score, but hey... what's a little karma among friends.

    I'm kinda glad to see something like this. While I don't think some of these Open Source regulations are as bad as maybe a commercial only regulation, I still think that these are bad policies. I never want my local government to have their hands tied in choosing the most appropriate platform. Many of these laws, even if the legislators don't want to admit it are simply anti M$ laws, but they could hurt other companies as well. Anyway back to the point. I can think of several examples were using commercial solutions would save money over the long run. Basically I think anytime you regulate away choice you are hurting your self. I policy, encouraging Free Software is much more appropriate.

    --
    Business News and Resources: www.usasource.net
  14. Call me a cynic... by Woodie · · Score: 5, Interesting

    OK -

    call me a cynic. But, this whole freedom of choice thing can't be underscored. GPL is great, if you want to put your software under it, feel free to do so. Just don't demand that I do the same. Information doesn't want to be free. Information doesn't _want_ anything. Information just is. People want information for a variety of purposes.

    Unfortunately the US government is somewhat restricted from being a copyright holder, and patent holder for good reason. As if the government doesn't have enough power already, what with laws and everything... Try to imagine if they could be patent holders and copyright holders. What better way to cripple free speech and innovation?

    And all this jazz about China using Linux. They're using you alright. China is not adopting Linux out of any altruistic sense of empowering the people. They are adopting it because it is not controlled by a corporation which is based in a potentially hostile foreign nation. China using Linux isn't about software - it's about politics. "Oh, look - we can get free software & brownie points, while divesting ourselves of foreign interest."

    Sure, Linux may be the next best thing since sliced bread. GPL might be the next best thing too. But keep in mind that some of us still like to buy our loaves of bread whole, and slice them ourselves. Choice is good. Forcing your brand of "freedom" down anyone and everyone's throat == bad.

    I can understand you all wanting the governemt to use OSS systems in building government systems. In fact, I'd lobby for that too. On a business, and social level it makes a lot of sense. But, guess what...? Sometimes OSS isn't always the right choice for the job. Shoehorning the wrong tool into doing the job is a big mistake. Options need to be considered rationally - not religiously. Of course, if you're used to kludges solving your problems - that might be OK.

    Bah!

  15. You have it backwards... by Badanov · · Score: 3, Insightful

    Open source only laws as they apply to government information will insure access to government documents and information regardless of who sells the software. If Microsoft (and that is who we are speaking of) sells a propreitary solution to, as an example, a county government for accessing property records on line, you know for a definitive fact they are going to require their products be on the desktop of anyone who wishes to access this information. (I can see some arguments coming that governments can require MS to allow any browser to access records, but that would entail MS not being able to sell their latest and best technology, and they could conceivably tell a governmental body that it is their way or perhaps a software audit is in order? As it is now in some courts, you MUST have MS Office to access some court records, you do NOT have a CHOICE!) Open source on the other hand, which hold to open standards will only require a browser of ANY kind, or in the case of documents, some accepted standard; there are no backroom deals, no threat that MS nazis will appear at your door demanding to see CDs and licenses, no security headaches, no threats that 'upgrades will force other upgrades, and no being locked into a hostile company's proprietary and ultimately damaging formats. It is simply a means of enforcing a concept of general and free access to government through the internet using open standards, which Open Source adheres to stringently. I guess some folks love of Microsoft products keeps them from understanding the nature of open source software, and makes them see things backwards, and not for what they are. Pity...

    --
    Dawn of the Dead
  16. I don't mind by NorthDude · · Score: 4, Insightful

    If government software are open-sourced or not.
    What I do mind however is if their document format are open or not.
    If they are, it is "easy" to change from one application to another.
    But if you have to reverse-engineer every document-type, it gets harder.
    What really bothers me is the content, not the media.

    --


    I'd rather be sailing...
  17. Here it is... by Corbin+Dallas · · Score: 3, Insightful

    For all you "Open Source Only Laws Are Bad" folks:

    If you buy closed source products, you have NO idea if it has a fatal bug or security exploit, and you are at the company's mercy if you want something fixed. PERIOD.

    I mean, Jesus people, THINK! What if you install the MicroBuss 5000 database software to store Social Security numbers and Drivers Licences, and then suddenly it gets hacked and all the data is compromised? Here's the quote from MicroBuss:

    "Well, we knew about the exploit, but we didn't want to tell anyone until we found a fix for it. It's ready now, just purchase the upgrade to the 6000 series."

    Don't laugh too much, this can really happen. Haven't any of you watched The Net? Granted, much of that was Hollywood, but backdoors are a reality. Is it really worth the risk for a minor economic boost? The answer is NO.

    Of all the places, I didn't think I'd have to post something like this at Slashdot, but after reading the first dozen or so comments, I guess I was wrong.

    --
    Democracy is two wolves and a lamb voting on what to have for lunch. Liberty is a well-armed lamb contesting the vote.
  18. Story at The Register by fatwreckfan · · Score: 3, Interesting
    There was a story at The Register almost a week ago about this.

    Most interestingly is Sincere Choice, created by Bruce Perens and Michael Robertson.

    From their main page:

    We stand for these principles:

    • Open Standards

    • Intercommunication and file formats should follow standards that are sincerely open for all to implement, without royalty fees or discrimination.
    • Choice Through Interoperability

    • No user should be required to use a particular product simply because other users do. Competing products should interoperate with each other through open standards.
    • Competition by Merit

    • Software vendors should compete fairly on the merit of their products, rather than by attempting to lock each other's products out of the market.
      Research Availability
      The people pay for government-funded research, its fruits should be available to all of them equally. We promote Open Source / Free Software licensing as a means of distributing research results fairly.
    • Range of Copyright Policies

    • We support a broad range of copyright policies, from Public Domain through Open Source and Free Software to Proprietary. We support use of the GPL and LGPL licenses when appropriate. We assert that Open Source and Proprietary models can be used together effectively. A number of our companies deploy software under the GPL license and proprietary software in the same product.
    • Freedom to Set Policy

    • Individual users, businesses, and government should all be free to set their own policies regarding what sorts of software they will acquire and use. They should not force their policies upon others.

  19. Shoehorning the wrong tool by mgkimsal2 · · Score: 4, Informative

    "Shoehorning the wrong tool" - this happens OFTEN dealing with MS. Anecdotal case in point:

    The transcription department at the hospital my mother works at transferred everyone over to MS Word a couple years ago, from DOS-based Word Perfect. The reason given was to 'increase productivity'. Well, it only helps the IT productivity, because it's less for them to 'learn' (never mind that they rarely actually help solve a problem anyway, that's another story).

    The point is hundreds of people were trained and very productive in WordPerfect. They didn't WANT to switch to Office/Word, but were forced to. Productivity DROPPED like a rock. All the DOS-based tools (keymap-expanders - "alt-shift-gg" expands to "gyrointestinal gerontology", for example) don't exist for Word, and still haven't appeared on the market.

    By pure line-count per hour based productivity, MANY people in the department fell at least 50%, some by as much as 80%, in terms of productivity.

    This was and still is most definitely the 'wrong tool' for the job, but it's 'company policy' and everyone lives with it. Forcing people in a federal office building to learn OpenOffice after learning Word would be costly, yes, but it would fit the overarching IT vision, if it was articulated to demand open source stuff.

    When the 'wrong tool' for the job is MS, people still seem to go along with it, but when the 'wrong tool' may be open source stuff, suddenly it can't happen?

    1. Re:Shoehorning the wrong tool by puto · · Score: 3, Insightful

      My primary function in IT has been on the medical end. Just about every aspect. And I have used the Nixes and MS products in offices I have managed and was the it director for a small hospital. I have 12 years in this side of industry and have seen it ALL.

      The problems you mention are true but are a little exaggerated.

      1. MS word is a bit of a learning curve if you come from Wordperfect(which in it's day rocked). But all of those items you mentioned that cannot be done with Word, can be. MS is quite big on the Healthcare front. I have implemented key expanders for word since 1995.

      No one know about google at the hospital?

      http://www.google.com/search?hl=en&ie=UTF-8&oe=U TF -8&q=word+key+expanders

      2. A WELL PLANNED ROLLOUT.

      This goes for any software implentation that is in a production enviroment such as a hospital. Have 25 percent of the staff begin to switch at first, have em use it for half a day, but slowly roll it out and ease the new product it. ANY change of software will cause downtime in production. AND all employees when switching from something known to something new create a lotta FUD. They are scared, don't want to learn something new, and in many cases they know the new stuff might bring to light some of their faults. Sounds like the hospital IT staff was a little clueless.

      Then which brings me the the point of TCO and standards.

      Word in the longrun would probably be cheaper than open office and easier to support because people have it at home, can pick up a a dummies book, go to New Horizons, call a friend, many venues for support. And the more widely spread the product on the market, = less calls I get because many people know it and can lean over and help their coworker.

      We do need an open standard for documents. I totally agree. BUT when medical records and forms need to be sent in formats that cannot change and need to print on your printer like I look at them on my screen. Insurance claim forms adhere to a certain standard and if they are 1 millionth of a mm off, then the companies wont take em.

      Then I am going to choose the most widely accepted format, which in this case is Word.

      Word has an 85 percent saturation in the medical industry, and sadly enough I have to go with it but cause it will be around in the long run, TCO. I train em on Word now, the industry supports it, and it will be around.

      Word Perfect has been floundering since the 90s. They actually were going out of business and Novell bought them. I have a CD that says Novells Word Perfect. The widespread use is that it has always been bundled free with systems.

      This is not a Microsoft ad. As an IT director I choose the least painful route and the less costly in the long run. And in the medical industry word fits the bill.

      I use Unix, I like it. I use open office. I use Office, I like em both. Office is a good product

      Puto

      --
      The Revolution Will Not Be Televised
  20. Blammo! Another argument falls to friendly fire by gilroy · · Score: 3, Insightful
    Duh-huh, what? Blockquoth the poster:

    With Open Source, the answer is always out there, usually. It isn't always so when trying to navigate a vendors website. With Open Source,if Red Hat, SuSE or say Debian doesn't have an answer for your problem, someone else usually does!

    You don't think the relative difficulty and obscurity of Microsoft "solutions" should count as a cost? I think it's disingenuous to argue that installation and training are costs but hours lost to dead-end surfing or on hold to tech support are not. Let's not even mention per-incident phone support!
  21. Re:So -- you want the government to set the standa by Shelled · · Score: 3, Insightful

    Right. Without the innovation to break the last proprietary document format with an incompatible, upgrade-forcing new one, how can government possibly continue to operate? XML is "the lowest common denominator" compared to .doc? How, that the unwashed (ie. any citizen) can read it with paying the MS tax?

  22. Governemnt should be transparent... by dh003i · · Score: 4, Insightful

    Thus, the source code for any software it uses should be available.

    The people have the right to know what code the government is using to protect confidential information, criminal records, driving records, manage taxes, etc etc. Closed-source software destroys the possibility of transparency in the government, and denies people that right.

    Furthermore, its OUR tax dollars which are paying for this stuff. Thus, more cost-effective solutions -- hence open source software / free software / public domain software -- should be used by the government.

    Furthermore, the government should not use any standards which lock/force people into using any particular kind of software. That means no proprietary standards (like MS .doc files). Proprietary standards force people into using particular programs (like MS Word). Open Source / Free standards should be used, as they don't lock the people into any particular program. A standard like OpenPGP can be incorporated by anyone into their program, be it the FSF, the OSI, or MS.

    Now, regarding government development of software. In all cases, government-funded projects should produce something which is freely available to the public. That means public domain, GPL, or Open Source Licenses. These licenses (or lack thereof) make the results of government-funded projects available to the public. In regards to the GPL, it requires that you GPL any modifications. But this is a good thing. It is good that the government promote recipricol relationship communities, as the GPL does. This is in the public interest. It is in the public's interest that any software produced or funded or supported by the US Government become public domain, GPL, or covered under any of the OSI certified licenses. It is not in the public's interest that such fall under a proprietary license: that means that citizens pay TWICE for a product. Once to support its development, then again to buy it.

    The simple fact that in 99.99% of cases using Open Source/GPL software saves money should be enough to justify its use. In the few cases where it doesn't, that's b/c its not as good as the proprietary equivalent, but that can easily be fixed by government-funded development.

    Even in the very few (0.01%) of cases where you save money by using proprietary software, that still doesn't justify using it in those cases. Because the public has the right to know what the code is the govenrment is using (as this affects their lives), any code the government uses should be transparent.