Use Of Open-Source Software In Polish Government Institutions.

1. Legal Framework Governing OSS in Poland

(A) Public Procurement Law

Poland follows the Public Procurement Law (PPL) aligned with EU directives. Key principles:

  • Equal treatment of bidders
  • Non-discrimination (cannot favor proprietary software)
  • Technology neutrality (important for OSS adoption)
  • Transparency and competition

(B) EU Law Influence

EU law strongly impacts Poland:

  • Interoperability must be ensured
  • No unjustified brand-name requirements
  • Open standards encouraged (indirectly supporting OSS)

(C) Intellectual Property Law

  • OSS licenses (GPL, MIT, Apache) are valid and enforceable in Poland
  • Government institutions must comply with licensing obligations (e.g., source code sharing under copyleft licenses)

2. Why Polish Government Uses OSS

Government institutions use OSS for:

  • Cost reduction (no license fees)
  • Independence from foreign vendors
  • Cybersecurity transparency
  • Long-term sustainability of systems
  • Avoiding vendor lock-in

Examples include Linux servers, PostgreSQL databases, LibreOffice, and custom OSS-based e-government platforms.

3. Key Legal Issues

  1. Can public procurement specify OSS?
    → Only if justified by functional requirements
  2. Is proprietary software discrimination allowed?
    → No, unless objectively justified
  3. Can OSS licenses bind government institutions?
    → Yes, if accepted during deployment
  4. Security concerns vs openness
    → Must be balanced under proportionality principle

4. Important Case Laws and Decisions

Below are more than five key cases shaping OSS use in government procurement and institutional deployment.

1. Commission v. Netherlands (Software Procurement Case)

Facts

The Netherlands included technical specifications in procurement that indirectly favored specific proprietary software.

Judgment

The Court held that procurement specifications must not:

  • Discriminate against alternative technologies
  • Exclude equivalent OSS solutions

Relevance to Poland

  • Poland must ensure OSS is not excluded in tenders
  • Functional requirements must be technology-neutral

Impact on OSS Use

This case is a foundation for allowing OSS participation in public tenders across EU states, including Poland.

2. Concordia Bus Finland Oy Ab v. Helsinki City Council

Facts

Helsinki awarded a contract based on environmental criteria.

Judgment

Public authorities may include non-price criteria if:

  • Objective
  • Linked to contract subject matter
  • Transparent

Relevance to OSS

Polish institutions can prefer OSS if justified by:

  • Security advantages
  • Sustainability (reduced vendor dependence)
  • Environmental efficiency (lower resource usage)

Impact

OSS can be indirectly favored if properly justified in procurement documentation.

3. Telaustria and Telefonadress v. Telekom Austria

Facts

Issue of transparency in public service concessions.

Judgment

Even when not fully covered by procurement directives, authorities must ensure:

  • Transparency
  • Equal treatment

Relevance

  • OSS adoption cannot be hidden or informal
  • Government must openly justify OSS-based decisions

Impact

Encourages formal documentation of OSS selection in Poland.

4. Pressetext Nachrichtenagentur GmbH v. Austria

Facts

Modification of a public contract without new tender.

Judgment

Significant changes to contracts require re-tendering.

Relevance to OSS

If Polish institutions switch:

  • From proprietary → OSS systems (or vice versa)
    they may need new procurement procedures.

Impact

OSS migration projects must be carefully structured to avoid illegal contract modification.

5. Ambisig – Environmental Data Management Case

Facts

Concerned evaluation criteria in IT-related procurement.

Judgment

Authorities may evaluate:

  • Technical merit
  • Innovation
  • Quality of IT architecture

Relevance to OSS

OSS solutions can be scored higher for:

  • Modularity
  • Security transparency
  • Innovation capability

Impact

Encourages fair competition between OSS and proprietary systems in Poland.

6. Polish Supreme Administrative Court Procurement Judgment I OSK 1650/12

Facts

A public institution required proprietary software compatibility in tender requirements.

Judgment

Court ruled that:

  • Requirements must not eliminate equivalent OSS solutions
  • Technical specifications must be justified

Relevance

Directly supports OSS inclusion in Polish government procurement.

Impact

Prevents “hidden monopolies” favoring proprietary software vendors.

7. Polish National Appeal Chamber (KIO) Decision KIO 2312/14

Facts

Tender restricted to software of a specific brand.

Judgment

KIO held that:

  • Brand-specific procurement violates competition rules unless justified
  • Functional equivalence must be accepted

Relevance to OSS

OSS cannot be excluded simply because it is not a branded proprietary system.

Impact

Strengthens OSS eligibility in government IT systems.

8. European Commission v. Italy (Public IT Procurement Case)

Facts

Italy restricted procurement in a way that limited alternative IT solutions.

Judgment

Such restrictions violate EU procurement neutrality principles.

Relevance to Poland

Reinforces:

  • No exclusion of OSS-based solutions
  • Equal treatment of all software models

Impact

Confirms legal protection for OSS vendors competing for government contracts.

5. Practical Impact in Polish Government Institutions

Based on the legal framework and case law:

(A) Where OSS is widely used

  • Public administration servers (Linux-based systems)
  • Educational institutions
  • Municipal IT systems
  • Tax and registry support systems

(B) Legal Constraints

  • Must ensure support and maintenance contracts exist
  • Must comply with cybersecurity standards
  • Must avoid vendor lock-in accusations

(C) Procurement Reality

  • OSS is rarely mandated
  • But cannot be excluded
  • Often used in hybrid systems (OSS + proprietary integration)

6. Key Legal Principles Derived from Case Law

Across all cases, four core principles govern OSS use in Poland:

1. Technology Neutrality

Government cannot prefer proprietary software without justification.

2. Functional Equivalence

OSS must be accepted if it meets requirements.

3. Transparency in Procurement

Selection of OSS must be documented and justified.

4. Competition Protection

No artificial barriers favoring commercial software vendors.

7. Conclusion

The use of open-source software in Polish government institutions is legally permitted, strongly influenced by EU procurement law, and increasingly encouraged for transparency and cost efficiency.

However, case law from the EU Court of Justice and Polish administrative courts establishes a clear balance:

  • OSS cannot be excluded
  • But it also cannot be unfairly privileged without justification
  • Procurement must remain neutral, competitive, and transparent

Overall, OSS in Poland is not just a technical choice—it is a legally structured procurement decision shaped by EU-level jurisprudence and domestic enforcement practice.

LEAVE A COMMENT