Open source licences could damage Aust govt software collaboration

By Angus Kidman
14 January 2004 10:10 AM
Tags: kidman, licences, angus, source, open, gpl, code, federal
A shift to open source development models could inadvertently limit the prospects of Australian government agencies sharing locally developed software, a legal expert has warned.

Professor Brian Fitzgerald from the School of Law at Queensland University of Technology told attendees at this week's Linux and Open Source in Government Conference in Adelaide that the impact of GNU General Public Licence (GPL) requirements regarding code sharing remained unclear for government agencies.

Under the licence, developers are required to make source code for any works derived from a GPL-licensed product freely available if that product is distributed to other parties. Some government agencies are reluctant to see code which they have paid to develop released into the public domain, though they are generally happy to share such code with other federal or state agencies.

"As a rule of thumb, distribution amongst government departments is not a distribution [for the purposes of the GPL]," Fitzgerald said. However, he added that since each individual state in Australia has a separate constitutional status to the overall Commonwealth, it was not clear whether code shared between federal and state agencies should be subject to the GPL requirement to make source code freely available.

The federal government is keen to see more collaboration between state and national agencies. In a separate presentation at the conference, NOIE business strategies branch general manager Tony Judge cited the example of the national AusTender site, which is based around code developed for a NSW government agency.

Fitzgerald noted that while the GPL has yet to be legally tested in any jurisdiction, the fact that it relies on concepts such as 'derivative works' which are not defined in Australia's own copyright laws might raise some concerns.

"The GPL is a very unique regulatory structure that has worked very well to this point," Fitzgerald said. "If the Australian government wants to operate within that framework for its open source software, it needs to understand how it operates."

Nic Suzor from the QUT School of Law said developers could sidestep the state/federal issue issues by only releasing source code directly derived from GPL-licensed products, while keeping entirely software in separate packages and thus free from licensing constraints. In this way, code could be shared between federal and state agencies without raising concerns.

Talkback 5 comments

    Incorrect. Software developed ...Anonymous -- 14/01/04

    Incorrect. Software developed to run on linux is not a GPL derived work. Ask the commercial vendors of Linux software that most certainly do not always share their code.

    If a government department wan ...Anonymous -- 14/01/04

    If a government department wants to develop code that is only shared with other government departments it is free to create its own license to this effect. If, however that department wants to take advantage of existing code that has been released under the GPL, then they must pay the "price" that the GPL requests. ie. Derivative software must also be released under the GPL.

    The decision is simple - "is the saving from not having to develop code greater than the 'cost' of having to release the enhancements?"

    Incorrect? John said "Inc ...Anonymous -- 14/01/04

    Incorrect?

    John said "Incorrect. Software developed to run on linux is not a GPL derived work." I cannot see anything in the article that makes such an assertion. Where is it?

    I doubt that any of the softwa ...Anonymous -- 14/01/04

    I doubt that any of the software developed by government agencies would pertain to the core OS or system utilities which are subject to GPL. With correct software architecture, software should be modular and thus any application domain code would rightly be free of GPL constraints. It should be remembered that any application code with a GPL'ed compiler for a GPL'ed database would still be free of GPL constraints.

    Another alternative is to use BSD licensed OS and tools and thus being able to retain ownership of modifications without the disclosure requirement.

    As if departments needed an ex ...Leon Brooks (Linux Australia OCM) -- 15/01/04

    As if departments needed an excuse to not share software! Some departments do, but most of them are as bad for hoarding and not-invented-here syndrome as the most rabid proponent of artificial barriers to exchange.

    Con Zymaris is reporting on the linux-aus list that Brian Fitzgerald is as "flummoxed" as any of us at this interpretation. And see the archives of same for my own interpretation of Gus's itnews.com.au article. http://lists.linux.org.au/archives/linux-aus/2004-January/msg00389.html

Add your opinion

Latest Videos

Sponsored content

Power Centre - Content from our premier sponsors

Blogs

Tags

Back to top

Featured