Open Source (FOSS)
Software whose source code anyone can inspect, use, modify, and share. It’s about freedom and public auditability, not price.
Why NYC should careA handful of NYC agencies already publish code on GitHub on their own initiative. Endorsement would turn that scattered habit into a citywide standard.
Learn more · Wikipedia ↗UN Open Source Principles
Eight commitments adopted by the UN’s Digital and Technology Network in 2025 defining how the UN system approaches software.
Why NYC should careEndorsement is a signature plus a roadmap, not a procurement overhaul — the entry ticket to a global community of practice.
Learn more · unite.un.org ↗OSPO — Open Source Programme Office
A small team that coordinates an institution’s open source strategy: what to use, what to publish, how to contribute, and how to stay secure doing it.
Why NYC should careParis, Munich, and the UN itself run OSPOs. NYC’s Office of Technology & Innovation is the natural home for one.
Learn more · Wikipedia ↗Digital Public Infrastructure (DPI)
The shared digital rails a society runs on — identity, payments, data exchange. Like roads or the power grid, it works best as interoperable public infrastructure, not walled gardens.
Why NYC should carePlatforms like Decidim and X-Road are built by one government and reused by dozens. NYC can join that exchange instead of buying its own silo.
Learn more · Wikipedia ↗Digital Sovereignty
A government’s ability to control its own digital destiny — to run, audit, and change the systems it depends on rather than being locked into any single vendor.
Why NYC should careEvery proprietary contract renewal NYC can’t walk away from is a sovereignty question. Open source is the strongest structural answer.
Learn more · Wikipedia ↗Open Standards & Interoperability
Publicly documented formats and protocols that let systems from different makers work together — the difference between an ecosystem and a lock-in.
Why NYC should careWriting open standards into procurement is the single highest-leverage clause NYC’s buyers control.
Learn more · Wikipedia ↗"Public Money, Public Code"
The principle that software paid for by the public should be available to the public as open source — adopted as policy by cities like Munich.
Why NYC should careA slogan NYC’s civic tech community already believes in; endorsement would make it official posture.
Learn more · FSFE ↗Vendor Lock-in
A dependency on a single vendor’s proprietary products that makes switching to a competitor difficult and costly — created by incompatible data formats, patents, or an ecosystem built to work only with that vendor’s other tools.
Why NYC should careNYC’s three-year, $57 million Microsoft agreement was negotiated by a buyer with no credible exit — a textbook case of the lock-in open source is built to avoid.
Learn more · Wikipedia ↗