1. Introduction: OSS in Government Obligations

Open-Source Software (OSS) is software distributed with licenses that allow users to use, modify, and redistribute the code, subject to certain conditions (e.g., attribution, sharing modifications, copyleft obligations).

When governments adopt OSS, they incur legal obligations similar to contractual and copyright duties, such as:

• Compliance with license terms (GPL, MIT, Apache, AGPL, etc.)
• Source code disclosure obligations (in copyleft licenses)
• Attribution requirements
• Restrictions on proprietary redistribution
• Ensuring downstream compliance in government procurement contracts

Government obligations arise in two ways:

(A) Direct Use

Government departments using OSS must comply with license terms.

(B) Procurement Contracts

When governments outsource software development, contracts often require vendors to comply with OSS licensing.

2. Legal Nature of OSS Obligations

Courts worldwide have consistently held that:

• OSS licenses are legally enforceable copyright licenses
• Violation of license terms = copyright infringement
• Governments or contractors cannot treat OSS as “free of obligations”

This principle is central in public sector software procurement.

3. Case Laws on OSS Enforcement and Government/Institutional Obligations

Case 1: Jacobsen v. Katzer (2008, USA)

Principle:

Open-source Artistic License is legally enforceable under copyright law

Facts:

• Developer Jacobsen released software under an open-source Artistic License
• Defendant used the code but violated attribution and notice requirements

Held:

• Court ruled OSS license terms are conditions, not mere contractual covenants
• Breach leads to copyright infringement

Significance for Government:

If a government agency uses OSS, it must comply strictly with license conditions or risk infringement liability.

Case 2: Wallace v. IBM (2006, USA Seventh Circuit)

Principle:

GPL (General Public License) does not violate antitrust laws and is legally valid

Facts:

• Plaintiff challenged GPL claiming it restricted competition
• IBM used GPL software in its ecosystem

Held:

• Court upheld validity of GPL licensing model
• Confirmed OSS licensing is lawful and enforceable

Government relevance:

Governments cannot refuse OSS obligations on grounds of “anti-competitive licensing”.

Case 3: Software Freedom Conservancy v. Vizio (2021–2022, USA)

Principle:

OSS compliance obligations can be enforced through litigation

Facts:

• Vizio used GPL/LGPL licensed software in smart TVs
• Alleged failure to provide source code and proper compliance

Held:

• Case allowed to proceed; court accepted enforceability of OSS claims

Government relevance:

Government contractors using OSS in public procurement systems can be sued for non-compliance.

Case 4: Welte v. Sitecom (2004–2006, Germany)

Principle:

GPL license violations constitute copyright infringement

Facts:

• Company distributed firmware using GPL-licensed Linux code
• Failed to release source code as required

Held:

• German court enforced GPL obligations
• Injunction granted against distributor

Government relevance:

European governments procuring embedded systems must ensure vendors comply with GPL obligations.

Case 5: Versata Software v. Ameriprise (2014, USA arbitration)

Principle:

Violation of open-source licensing can result in commercial damages

Facts:

• Software included GPL components without proper compliance
• Contract dispute escalated to arbitration

Held:

• Court recognized OSS compliance failure as breach impacting contractual rights

Government relevance:

Government procurement contracts can impose financial penalties for OSS violations by vendors.

Case 6: Cisco Systems GPL Litigation (Various settlements, USA)

Principle:

Large corporations must comply with OSS obligations or settle legal claims

Facts:

• Cisco used GPL software in networking devices
• Alleged failure to provide full source code and notices

Outcome:

• Multiple settlements and compliance agreements with FSF-related enforcement bodies

Government relevance:

Governments using Cisco or similar vendors must ensure OSS compliance audits in procurement.

Case 7: Neo4j / ONgDB Litigation (EU/US influence, ongoing disputes)

Principle:

“Open-source branding” and license obligations are legally enforceable representations

Facts:

• Forked database software disputes over AGPL compliance and licensing terms

Held/Position:

• Courts increasingly treat OSS compliance as enforceable legal obligation, not marketing language

Government relevance:

Public procurement must avoid “open-source washing” (mislabeling proprietary software as OSS).

Case 8: Sony / Linux-based PlayStation Litigation (GPL enforcement context)

Principle:

Embedded systems using GPL must disclose source code

Facts:

• Linux kernel (GPL) used in embedded/consumer systems
• Allegations of non-compliance in distribution

Outcome:

• Settlements and compliance obligations enforced in practice

Government relevance:

Government defense, telecom, and embedded systems must ensure compliance in critical infrastructure procurement.

4. Key Legal Principles Derived from Case Laws

From the above cases, courts consistently establish:

1. OSS licenses are enforceable law

They are not informal agreements.

2. Violation = copyright infringement

Not just breach of contract.

3. Source code disclosure is mandatory under copyleft licenses

Especially GPL/AGPL.

4. Governments and contractors are equally bound

No immunity for public bodies or procurement agencies.

5. Compliance must be ensured in procurement chains

Governments must audit vendors.

5. Government Obligations in Practice

When governments adopt OSS, obligations typically include:

(A) Legal Compliance

• Follow license terms strictly
• Maintain attribution notices
• Provide source code (if required)

(B) Procurement Requirements

• Include OSS compliance clauses in contracts
• Require vendor disclosure of OSS components

(C) Transparency Requirements

• Encourage reuse of public-funded code (public money → public code principle)

(D) Risk Management

• Avoid license incompatibility in mixed software systems
• Conduct OSS audits

6. Conclusion

Open-source software in government systems is not “free of legal obligations.” Courts globally—from the United States to Germany—have confirmed that OSS licenses are binding, enforceable legal instruments.

The key takeaway from all major case law is:

Governments may freely use open-source software, but they must fully comply with its legal conditions—or face infringement liability.