By webmink on Feb 24, 2009
Late today (UK time), the British Government issued a bold new strategy for use of open source software - and open standards - in Great Britain. In Open Source, Open Standards and Re-Use, the government's Minister for Digital Engagement (yes, really, and he's on Twitter too) significantly revised the brave but toothless policy of 2004 "that it should seek to use Open Source where it gave the best value for money to the taxpayer in delivering public services". This is fantastic news - the digital tipping point is at hand. (The publication is also progressive in having nominated use of the tag "#ukgovOSS" in comment and coverage so it can be found and aggregated).
Like other fine policies before it, the core of the document asserts that the government
- will actively and fairly consider open source solutions alongside proprietary ones;
- will consider exit and transition costs as well as the total lifetime cost of ownership;
- will pick open source where it doesn't cost more;
- will insist proprietary vendors explain exit, rebid and rebuild costs;
- will expect proprietary licenses to be transferable throughout government;
- will expect public sector solutions to be re-usable
- develop clear and open guidance for ensuring that open source and proprietary products are considered equally (action 1);
- keep and share records of approval and use of open source (action 3)
- support the use of Open Document Format (action 8);
- work to ensure that government information is available in open formats, and it will make this a required standard for government websites (action 8);
- general purpose software developed by or for government will be released on an open source basis (action 9).
This is all to be warmly welcomed and encouraged, and I congratulate the government on this progressive step. The endorsement of ODF is especially welcome, and would have seemed no more than an impossible dream to those of us associated with OpenOffice.org and involved in it at the start of the decade.
I will be very pleased to support and assist in any way that appropriate. In particular, I encourage the CIO Council to consider switching from an assumption of a procurement-driven approach to software acquisition to an adoption-led approach. Doing so does not favour open source; rather, it levels the playing field so that open source solutions can been seen alongside existing approaches. Sadly, if we stick with procurement-driven approaches and try to force-fit open source into them, we will be gamed.