Slashdot Mirror
The Open Source Dilemma for Governments
Sam Hiser writes "Tom Adelstein, open source consultant and Member of the Open Government Interoperability Project ("OGIP") working group, offers another incisive article in which he discusses the costs in the terms of lives and dollars when local governments do not deploy open standards-based software for data sharing. Asks Adelstein, 'Can local governments afford to create redundant applications to meet new Federal standards for first responder alerts, emergency services, law enforcement, broadcasters?' He posits that Open Source collaborative initiatives may provide the only solution for the US if the people want to create a safer environment."
I don't care if the US Senate or House chooses to use MS Office or vi or whatever - as long as the documents they produce are of an open format (text, rtf, XML, whatever), and can be read by us Citizens (and others, why not?) wihtout needing to have a particular piece of software. Same can be said of exchanging data between various levels, types, and branches of government.
Don't blame me, I voted for Kodos
For pure niche apps (patrol car suspect lookups, etc), I would posit that small commercial companies are in the best possible position to provide support and apps, not the FOSS world - after all, where does your teenage A-Patchy Webserver hacker get his hands on the specialty hardware used in patrol cars?
by the UK goverment that they might "look-in" to open source software themselves simply because they know it scares Microsoft, like Germany, who got massive discounts.
/. stories on goverments considering OSS and then stories a few months later about them receiving massive discounts.
A goverment just has to say it's thinking about it to get Microsoft scared and giving out vouchers left right and centre.
Expect to see alot more
--- any post that takes longer than 20 seconds to write, isn't worth writing
1)"Free" is not a good motivator - coming in under budget is not a motivator if they want budget they need to spend budget
2) it's too complex for SLG admins, it's not as easy to pass an open source torch on to your new team mate or underling.
what will motivate Open Sopurce Adoption?
those 400k novell seats and their admins that still run win9x and office 97 need an upgrade very badly. If Novell/SUSe and Ximian can pull off a compelling solution then you will see huga adoptions -- not these onsie twosie deals.
Mod me down if you like but this is a strong emerging market.
Sorry you need to update your version of Microsoft Office to 2003sp3 in order to report a child missing.
When timing is critical a commercial solution can fall flat on it's face.
As seen on Wired: Get a free desktop PC
If we want secure software, it has to be open source.. Granted, at the start the code quality of open source stuff is around equal to closed source stuff but the resources available to check code that is public are far larger than any closed source firm can muster.
Potential resources mean nothing. Open source code that no-one bothers to read isn't going to get better on it's own.
Comment removed based on user account deletion
"So as more people use open source, the bigger target it becomes to hackers."
Care to tell me why that Apache is so much more secure then IIS?
Apache is the most popular web server in the world. But IIS has the most flaws....
There are much worse ways that software can fail. One of the worst is software that looks like it's working, but in fact is not displaying new / updated items -- this leaves the warfighter with the false impression of situational awareness. Another popular failure is software that has time-consuming processing steps that don't have adequate progress indicators -- this leaves the warfighter wondering 'Is it done yet?' when it hangs or fails.
At least with a blue screen or core dump, you know you've got a problem, and you can restart / reboot to resume, with a well known startup time.
We call it art because we have names for the things we understand.
the problem lies not government "per se" but with the management thereof.
The same government that you are railing about is the reason nobody's dying in low speed head-on crashes from getting a steering column rammed through their chest.
The car companies were quoting "market forces" and "nobody will want to pay for collapsible steering columns," and people were pinned to their seats like butterflies to cardboard. Sound familiar? Its the justification of every elite to anything that's going to cut into sl/easy profit.
Management of government by objectives without citizen input into what the objectives are is disastrous.
Remember Clinton's medical plan fiasco that was thrown out, not by elected representatives like the congress, but by HMO lobby groups posing as experts, as being unmanagable.
You didn't get to register so much as a peep for or against or make a suggestion. It was managed right out of your hands.
People are dying because their only sin is being temporarily broke from the last scrape with the health care system.
MSBPodcast.com The opinions expressed here are my own. If you don't like 'em... Think up your own stuff.
"Anyhow, this article is a lot of FUD. I write software for local governments, and at least in this state (which is one of the richest in the US), OSS wouldn't save any money nor eliminate any problems."
That's a strong statement. I'd say that there is more FUD in your post than in the original article. Maybe you forget that a lot of Slashdotters are, or have been government workers too...
'"Code Security" is not a big problem in local government -- as local governments generally only use their digital systems to warehouse and process publically available information. These guys keep paper records going back to the 18th century, and if anything seems out of the ordinary they check the paper.'
I worked at a federal agency that had everything stored on paper too. One day they decided to double check some things and found out the off-site storage facility they had been paying for years had no idea where most of their documents were. Those that could be found were water damaged beyond being readable.
So much for using paper as a back-up mechanism. I think part of the point of the article is that local governments do things on-the-cheap and that if they all shared more of their systems the systems would likely improve for everyone, even the smallest local agencies.
"And if asked, we readily turn over our code to local auditors. Very rarely do we do this. Nobody cares about anything except getting the software to cut down on their workload."
Sam here. But they never ask. Thats the problem. They don't know if contractors are sticking to standard coding practices, they don't know if third party "shareware" components have snuck into their systems (and they have) and they don't get involved with these issues until something breaks, and by then it's probably too late. More eyes on the code solves this too. Worst case, after the same breakage occurs for one local shop, other local shops will at least be aware that there is a problem that needs to be addressed (and most of them will only have to apply the fix, not invent it).
"And that's the biggest problem in this market: accountability. Small companys come in, install software, and then disappear."
Right, small companies like yours, supplying one of a kind mixtures of COTS software and local code. You most likely have a long term contract where you are because you have wired a dependence on your institutional knowledge into your systems. Good for you, not good for taxpayers.
"Can you imagine the accountability headaches associated with asking a "community" to write custom tax logic? "
Again, you seem to have missed the point, which was that there is not all that much variation from one location to another. The types of variation caused by different tax rates etc. should not be buried in code logic anyway, but should be in parameter control files and be alterable at a fairly high level.
"Don't get me wrong...I like the idea of getting more eyes on my code...but I can't imagine injecting community code into a hectic development schedule like we maintain."
Well, from what you have said, it most likely wouldn't be your code getting examined. Most likely in fact you would adapt code written at a larger, richer locality to your needs.
"My boss would surely never go for it. Of course, I don't expect many of the OSS acolytes to agree with me...some people don't seem to understand that the minimum wage people working without possibility of overtime at the county clerk's office don't want to visit the newsgroups for help when they have bugs preventing their license software from printing."
Both you, and your boss probably won't go for it until you see other similar localities going for it successfully. At the federal level almost everyone looks to other agencies for guidance. With no agency in a clear leadership position you end up with the same thing you get in any leaderless organizations, n