Publicly funded software: who owns it and how it is licensed

Public funding, government ownership and public access are different attributes of software. Research can be publicly funded while an institution retains rights in an invention. Code written in official federal duties can have a different copyright status from code supplied by a contractor. An open-source license then answers another question: which activities are permitted, and what conditions apply when the code is shared or changed?

These distinctions are important because a funding source alone does not describe all the rights in a program. Patent rules concern inventions, copyright concerns protected expression, and licenses provide permissions under relevant rights. The software intellectual-property page explains those categories. The rules discussed here show why the route from public expenditure to available code can take different forms.

Federally funded inventions and Bayh–Dole

Wikipedia’s account of the Bayh–Dole Act describes the U.S. legislation adopted in 1980 as permitting contractors to retain ownership of inventions arising from federally funded research. Its account specifies nonprofit organizations and small-business contractors, timely disclosure and an election to retain ownership of an invention they acquired. This concerns patent rights in inventions; it is not a general declaration that all publicly funded software belongs to its developer or to the public.

The statute's stated objectives are set out in the policy provision published by Cornell’s Legal Information Institute. They include using the patent system to promote use of federally supported inventions, participation by small businesses, collaboration with universities and other nonprofits, commercialization and public availability. The provision also seeks sufficient government rights to meet government needs and protect the public against nonuse or unreasonable use.

That combination makes the policy more specific than a choice between exclusive ownership and unrestricted access. The Wikipedia account describes disclosure duties, government rights and conditions on retaining title. The statute's policy combines use of inventions and commercial development with protection of public interests. These are stated aims and legal arrangements, rather than evidence that a particular licensing outcome always achieved them.

Government works and contractor works

The federal copyright provision on U.S. Government works states a general rule that copyright protection under that title is unavailable for a work of the United States Government. It also permits the government to receive and hold copyrights transferred to it. The text includes specific provisions for certain covered works, so the general rule and the statute's scope remain distinct from a claim about every item in government possession.

Wikipedia’s explanation of federal-government copyright status defines government works by reference to preparation by an officer or employee as part of official duties. It distinguishes those works from otherwise protected material published by the government, including contractor and grantee material. It also distinguishes the domestic federal rule from treatment abroad and from the separate rules governing subnational governments.

A publicly funded project therefore cannot be described as public domain solely because an agency paid for it or distributed it. The circumstances of creation and the rights held in its components matter. Funding an invention, employing a programmer and commissioning code from an outside institution can involve different legal relationships. The federal sources make those boundaries relevant to any description of ownership.

Public domain and open-source conditions

Wikipedia’s public-domain software article describes software outside exclusive ownership rights and distinguishes it from software shared under a copyright license. It also notes that the procedures and limits for relinquishing rights vary by jurisdiction. Public domain is therefore a rights status, while an open-source license is a set of permissions and conditions applied to protected code.

For code that remains copyrighted, the licensing choice can concern what happens to distributed changes. Wikipedia’s GPL explanation describes copyleft conditions requiring source for recipients of distributed derivatives under the same or equivalent terms. It expressly distinguishes that requirement from a duty to publish every change to the public. The condition concerns distribution, not simply making a modification for internal use.

Wikipedia’s permissive-license overview identifies BSD and Apache among permissive families and contrasts their limited conditions with copyleft. It explains that derivatives of permissively licensed software can be distributed under proprietary terms. These approaches establish different downstream permissions and obligations. Their descriptions do not establish which one offers the greatest benefit for every publicly funded project.

A public body's own license

The European Union Public Licence article describes a free-software license written and approved by the European Commission. It identifies a copyleft model developed with the copyright law of EU member states and compatibility with other free-software licenses in mind. It was initially intended for software developed within a public program, while its generic scope also allowed use by other developers.

The EUPL example distinguishes government-developed code from code without copyright protection. A public authority can distribute software through a license that retains legal conditions. Broad availability can consequently arise through licensing, rather than only through a public-domain status. The license-definitions page describes the differences among the main families.

Publication as a development policy

GOV.UK’s guidance on publishing code sets out reasons for openness, including documentation, maintainability and opportunities for others to suggest improvements. It also records circumstances in which code can remain closed, including keys, credentials and unreleased policy. Publishing code and protecting restricted information are thus separate parts of the policy it describes.

As a government-developed example, Wikipedia’s VistA article identifies the U.S. Department of Veterans Affairs system as public-domain software available through the Freedom of Information Act. Its data-exchange context is covered on the page on VistA and software interoperability. The example illustrates a particular release status; it does not assign that status to all government software.