Open Code in Public Procurement
mpawlo writes: "I wrote something on public procurement and open code that you might want to share with your readers. In my opinion, it is time that public bodies and governments look over their public procurement policies to warrant competition. I don't think free software or open source should be the only choice when it comes to public computer programs, but as of today, public bodies all over the world designs their requirements in a way that rules out all Free Software and Open Source alternatives already at the drawing table. May the best computer program and license win! That's the only way to get an effective allocation of public money when it comes to public computer programs. Maybe a good topic for discussion among Slashdotters?"
At my university (Nebraska-Lincoln) we are currently facing budget cuts to the tune of something like 8.3 million dollars. Now, the university has a contract with Microsoft to for about a few million a year to supply all computers on campus with windows/office.
When somebody suggested not renewing the contract (Thereby saving a few mil) and instead switching over as much of campus as possible to Linux they where laughed out the door by the ITS people. They said, among other things:
1.)Cost too much to implement (retraining users, etc)
2.)Would be too hard to support
3.)Wouldn't provide students with the knowledge of computers to succeed in the real world I.E. Microsoft software is used by 99% of the business world and having everything run linux would simply not be effective in teaching students how to use 'real world' applications.
Where they right? I don't think so. But instead of cancelling the contract they are now cutting faculty raises, a number of teaching centers, and some extra programs.
Before we go and change how gov'ts contract software we must realize just how damm impossible it is to get them to get past microsoft's FUD.
IMHO, this idea is both reasonable and constructive. It's certainly not the radical pseudo-communism the purveyors of FUD will inevitably make it out to be.
... risks none of the dangers of strategic behavior that closed code, or controlled networks, do. If open code is used strategically, then the resource to counter that strategic action are always available. Innovators can rely upon the promise of open code in their innovations. They need not worry that what they develop will be swallowed by the platform they develop for.
Personally, I like the way Lessig put it in _The Future of Ideas_ when he argued that the government should encourage the development of open code.
"Open code
This encouragement should not be coercive. There's no reason to ban or punish proprietary providers. People should be free to develop code however they wish.
But a government has its own interests, and closing its resources to others is not one of them. If the federal government develops a system to handle welfare claims, what reason does it have for hiding the code for that system from the states? Why not let the states take that code and build upon it? And if the states, then so, too, with the universities. In each case, the aim should be to expand the reach of these powerful and valuable resources, not to contract and hoard them when to value to the hoarding exists." The Future of Ideas, p.249