Why Government Software Should Be Open-Source Bulgaria just did something revolutionary, and just a tiny bit crazy; they’ve signed in a few new laws concerning software used by their government that, among other things, stipulate that all government software must be open-source, and must be developed and maintained in public repositories. The new laws are not independent, but instead stand as amendments to their Electronic Governance Act. The law also talks about free and public APIs, easy multi-ecosystem implementation, and a number of other things all targeted at making government software as open, transparent and friendly as possible. The reasons for choosing to go with a strict policy against the use of closed-source software are many and varied, running the gamut from cost to ease of implementation, but in the end, they all have a common thread; they essentially boil down to some sort of benefit for the citizens at large. Open-source software is generally cheaper and easier to obtain than the closed-source variety, in most cases being completely free. This means that the government department looking for software does not have to use some of their budget on it. In turn, this means less taxpayer money is being used, and taxes may end up being just a hair lower as a result. Other benefits though also are: 1. Governments can easily find software from other governments that already work in an government environment. 2. Any financial investment spent on support or training, can be spent 100% locally in that country. 3. The software can be adapted to other languages or other local needs. 4. No lock-in to an ever increasing annual license fee (usually a foreign one). 5. Local startup businesses can either provide paid support to their government, or could freely use the software in running their own businesses (in-house use or selling a support service to other businesses). 6. Generally it can… http://bit.ly/29FBP3Z
Comments