Was this achievable in the given time? If so, what was the plan to get there? If not, how should it have been managed?
One specialist said that as many as five million lines of software code may need to be rewritten before the Web site runs properly.
In comparison:
Windows 95 had 15 million lines of code.
Windows 98, 18 million
Windows XP, 35 million
http://www.nytimes.com/2006/03/27/technology/27soft.htmlLuckily for all of us they have about 8 weeks.
We should however demand an audit to be done and the result to be published.
They should have to make the case to keep it closed, not the other way around.
In the case of web code, there's nothing's new and innovative about the software that is unknown by existing developers. There is the potential for exploits but open source can help plug up those holes by allowing the community to assist in the process.
Sure, dumping the supposed "500 million" lines of code all at once would make it hard to review but they could release one compinent at a time over several months/years and vow to release all future code.
On a side note, wouldn't reviewing and repairing govt software be an excellent teaching tool for schools? How proud would a child be to have their code fix be accepted into production?
Perhaps the source code should be audited, if only to figure out what happened to the $600,000,000, but it's not clear that that requires open sourcing the code.
Now, the taxpayers purchased the codebase and the codebase could help states that did not offer a state marketplace create one. So I am very supportive of the idea of making it available to various states. But until the thing is running relatively smoothly, I don't see open sourcing it as doing anything but delaying the rollout and making it less reliable and less secure.
Update: it turns out John Oliver has taken a look at the code: http://www.youtube.com/watch?feature=player_detailpage&v=2Qt...