Language Selection

English French German Italian Portuguese Spanish

AU Government to use open source to break lock-ins

Filed under
OSS

IT vendors pushing costly proprietary software lock-ins have been warned that feeding at the $4.2 billion IT trough of the Australian taxpayer is over and a strict and a new procurement diet for vendors will be personally enforced by the Special Minister of State, Senator Eric Abetz.

A copy of "A Guide to Open Source Software" prepared by Australian Government Information Management Office (AGIMO), exclusively obtained by Computerworld, reveals new guidelines that state if an equal or superior open source product adequately fits the government's needs, it will be expected to be objectively considered by public servants alongside proprietary offerings.

Due to be officially released at the Open Computing in Government conference in Canberra next week, the government guide to open source is the most exhaustive analysis and evaluation of open source for use in government to date.

"This is an important document for both the government and for the open source community. For the first time, government agencies will now have access to an explanatory document about open source software," Abetz told Computerworld.

"The aim of this document is to explode some of the myths surrounding open source software and to acknowledge it as a viable option which should be considered when undertaking government software procurement," he added.

The document's forward from Abetz states, "All solutions - open source or proprietary - which can meet an agency's functional specifications should be considered by an agency when it is undertaking software procurement."

The document also cautions that government agencies preparing "requests for tender need to take care to avoid introducing unintentional barriers that may discourage or inhibit open source vendors and resellers from submitting responses".

Specifically, agencies are advised to avoid specifying products by name or mandating that solutions be delivered using a named proprietary or otherwise named solution.

On the licensing front, the guide goes as far as to provide a matrix as to what sort of open source licence is most appropriate for various government uses. This includes not only the development and sharing of open source solutions (presumably applications) by and for the government, but clear guidance that government agencies can "link open source product with internally developed code and distribute beyond the Australian government as a proprietary product".

However, it is on the subject of lock-ins that the open source guide by far delivers the strongest warning yet the government will not tolerate being led by the nose by vendors at taxpayers' expense.

Under the heading "Risk analysis and risk management", the document states: "One high-level risk associated with proprietary software technology (particularly software only available from a single publisher or supplier) is the financial risk of potentially high termination costs. This risk arises for a number of reasons, but the most important issue is the lack of alternative support for the software in question.

"The result is a lock-in scenario where an agency is tied to a particular supplier with little room for negotiation. This stems from the prohibitively high cost of moving away from a particular piece of technology for which there is no functional or interoperable equivalent from an alternative supplier.

"Such scenarios allow the current vendor to increase future product pricing, support cost structures or other contractual terms," the guide states.

It also refers to previous advice from AGIMO that, "...agencies develop a transition / termination strategy during the original procurement process to reduce the risk of future problems for the agency".

Source.

More in Tux Machines

NVIDIA Linux Performance-Per-Dollar: What The RX 480 Will Have To Compete Against

There's a lot of benchmarking going on this weekend at Phoronix in preparation for next week's Radeon RX 480 Linux review. Here are some fresh results on the NVIDIA side showing the current performance-per-dollar data for the NVIDIA Maxwell and Pascal graphics cards for seeing what the RX 480 "Polaris 10" card will be competing against under Linux. Read more

RaspAnd Project Brings Android 6.0 Marshmallow to Raspberry Pi 3, Now with GAAPS

Android-x86 and GNU/Linux developer Arne Exton has informed Softpedia today, June 25, 2016, about the immediate availability of a new build of his RaspAnd distribution for Raspberry Pi single-board computers. RaspAnd Build 160625 is the first to move the Android-x86-based distro to the latest Android 6.0.1 Marshmallow mobile operating system created by Google. And in the good tradition of the RaspAnd project, both Raspberry Pi 3 Model B and Raspberry Pi 2 Model B are supported. Read more

BSD Leftovers

  • FreeBSD 11.0 Alpha 5 Released, Schedule So Far Going On Track
    The fifth alpha release of the huge FreeBSD 11.0 operating system update is now available for testing. FreeBSD 11.0 is bringing updated KMS drivers, Linux binary compatibility layer improvements, UEFI improvements, Bhyve virtualization improvements, and a wide range of other enhancements outlined via the in-progress release notes.
  • DragonFly's HAMMER2 File-System Sees Some Improvements
    The HAMMER2 file-system is going on four years in development by the DragonFlyBSD crew, namely by its founder Matthew Dillon. It's still maturing and taking longer than anticipated, but this is yet another open-source file-system.

Debian GNU/Linux 9 "Stretch" to Ship with GCC 6 by Default, Binutils 2.27

Debian developer Matthias Klose has announced that the new GCC 6 compiler, which will be made the default GCC compiler for the upcoming Debian GNU/Linux 9 "Stretch" operating system, is now available in the Debian Testing repos. Debian users who are currently using Debian Testing can make GCC 6 the default compiler by installing the gcc/g++ packages from experimental. If installing it, they are also urged to help fix reported built failures in Debian Testing and Debian Unstable. Read more