Skip to content

🌐 Open-Source Policy Collection

To support Latin American and Caribbean countries in shaping their strategies for open-source software adoption, Code for Development, the Inter-American Development Bank’s open-source initiative, has created this repository of public policies from governments around the world.

The collection brings together regulations, policy documents, and strategic frameworks from various jurisdictions, serving as a reference for policymakers, technologists, and public officials exploring open-source-first approaches in government.

By organizing these policies according to their purpose and focus, this resource aims to facilitate:

  • 🧠 Policy Learning: Understanding different approaches to open-source governance
  • 🌟 Best Practice Sharing: Highlighting successful implementations that can inspire others
  • 🌐 Global Collaboration: Connecting policymakers working toward similar goals

⚠️ Disclaimer
This repository is provided for informational and reference purposes only.
It does not represent an official position of the Inter-American Development Bank or the Code for Development program.

🧭 Structure

The open-source policies featured in this site are organized in two complementary ways:

By Policy Category:
Policies are grouped by type (e.g., public release of software, reuse, licensing, training) to showcase thematic approaches and implementation patterns. Each category page includes:

  • A short explanation of the policy type
  • A list of official documents or strategies
  • Links to the original sources
  • Policy overviews

By Country:
For users interested in national approaches, the country view presents all documented policies grouped by jurisdiction. This view helps highlight how different countries address multiple aspects of open-source governance in a single place.

πŸ“‚ Policy Categories

πŸ›οΈ Government Software Management

Public Release of State-Owned Software Governments require or incentivize that software developed with public funds be released to the public, unless restricted by legal or security concerns.

Reuse and Transfer of Government Software Encourages the reuse and transfer of software among public institutions to avoid duplication and promote efficiency.

Open Source Sharing Platforms Creation of centralized platforms to host and manage OSS projects developed by or for government entities.

Prioritize Open Source in Procurement Mandates or incentivize that procurement processes prioritize or give preference to open source solutions when technically viable.

Mandatory Contribution Back to Open Source Policies requiring or incentivizing agencies to contribute improvements (upstream) to the open source projects they use or modify.

Open Source Security Measures Defines protocols for securing OSS used in public systems, including dependency audits and vulnerability scans.

Open Standards Requirement Requires that all new government digital systems adopt open standards to ensure interoperability and vendor neutrality.

Licensing Frameworks and Guidelines Provides clear guidance on licensing practices and acceptable OSS licenses for government use.

πŸ“š Capacity Building and Strategy

OSS Training Programs Programs designed to build open-source competencies across public sector teams and civil servants.

OSS in Strategic Planning Documents Mentions and commitments to OSS within high-level digital strategies or sectoral transformation plans.

🌍 Policies by Country

For those interested in exploring open-source policies from a national or regional perspective, this view groups all documented policies by jurisdiction in a single table.
The full list is available in the Complete Country Overview section.

Note: For the European Commission, we have grouped all regional policies under a single entry due to their wide applicability across member states.

🀝 How to Contribute

This list is not exhaustive, and it serves as a living resource that is open to continuous updates as new policies emerge, and additional countries are included. Contributions and suggestions for improvement are welcome to ensure the repository remains relevant and useful for the broader community.

We welcome input from researchers, policymakers, and open-source advocates. You can contribute in two ways:

πŸ“ Option 1– Open a Policy Suggestion

If you know of a policy we should include or you'd like us to review something:

You can let us know:

  • The name and purpose of the policy
  • Which category it belongs to
  • Whether it's new or related to an existing entry
  • Any official documentation or source links

πŸ“₯ Option 2 – Submit a Pull Request

If you're comfortable editing Markdown and GitHub:

  1. Review our contribution guidelines
  2. Fork the repository
  3. Add or edit a policy in the correct category
  4. Submit a pull request

We review all suggestions and aim to include relevant contributions quickly.

πŸ“’ Share Your Experience

In addition to contributing policy documents, we invite governments and organizations to take part in the Global Open-Source Policies & Practices Survey, launched by the Digital Public Goods Alliance Secretariat together with twenty-four partner institutions. By completing the survey, you will help map the global landscape of open-source policies and practices, surface challenges, and highlight promising approaches. Your participation will enrich this repository and support the collective effort to advance open-source-first adoption worldwide

βš–οΈ License

All content in this repository is licensed under:
Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International (CC BY-NC-ND 4.0)

Individual government policy documents retain their original licenses.

πŸ“„ Citation

This work can be cited using:

Dias Emendabili, J. V. A., SΓ‘nchez Romero, L.A., & Kang, D. (2025). Comparative Overview of Open-Source Policies in Government. Inter-American Development Bank, Code for Development Initiative. Available at: https://el-bid.github.io/OSS_policies/

πŸ‘₯ Contributors

This collection was made possible thanks to the collaboration of:

Special thanks to everyone who helped research, organize, and validate the content.