Compliance first: We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Home / Guidelines / Open data policy guideline 16
Open data policy guideline 16

Open Code: Open Data Policy Guideline 16

Open Code: Open Data Policy Guideline 16

Guideline 16 asks governments to share the code behind their websites, portals and tools and to favor open source solutions, treating software as a public resource alongside data.

Code as a public resource

The software a government pays for to run portals, dashboards and services can be as valuable as the data it publishes. When that code is shared openly, other governments can reuse it, residents can inspect how systems work and local developers can improve it. Guideline 16 asks policies to require code sharing where possible and to prefer open source solutions.

How policies typically phrase it

  • A preference for open source software in procurement, considered alongside proprietary options.
  • Requirements to publish custom code developed with public funds.
  • Definitions of open data broad enough to include source code.
  • Encouragement of partnerships with local developer communities.

Places whose policies adopted it

Only a handful of policies address open code directly. Raleigh's 2012 resolution directed the IT department to create an open systems procurement policy encouraging open source licensing models. Portland's 2009 resolution promoted open source software alongside open data and asked the city to consider it when replacing business systems. Austin's 2013 memo encouraged departments to use open source where possible, and Tulsa's 2015 order defines open data to include source code published online. Denton's 2015 directive was also tagged, though it treats proprietary code as an exclusion.

Common pitfalls

  • Preference without process, so procurement defaults to familiar vendors.
  • Publishing code without documentation or a license, which limits reuse.
  • Ignoring security review before releasing code.

Practical steps for sharing code

Governments that put this guideline into practice usually take a few concrete steps:

  • Publish custom code in a public repository under a recognized open source license.
  • Include documentation explaining what the code does and how to run it.
  • Review code for security issues and embedded credentials before release.
  • Consider open source options in procurement evaluations, alongside total cost of ownership.
  • Contribute improvements back to shared projects rather than maintaining private forks.

Several cities published their open data policies themselves in public code repositories, inviting comment and reuse by other governments. That practice blurs the line between policy and code in a useful way: the policy text becomes a shared, versioned resource that others can adapt, much as they would adapt open source software.

Why this matters for your business data

Most businesses run on commercial software, and that is fine; what matters is whether the data inside it is yours to use. Knowing which tools hold your operational records and how to export them is the first step toward valuing them.

Browse the systems we support on sell my data, or get a bid once you know what you have. We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.

Our compliance promise: We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.

Frequently asked questions

Why include code in an open data policy?

Code paid for with public funds can be reused by other governments and improved by the community. Sharing it also makes public systems more transparent and reduces duplicated spending.

Do open data policies require open source software?

Usually they express a preference rather than a mandate, asking departments to consider open source options in procurement alongside proprietary ones.

How common is this guideline?

Relatively uncommon. Only a small number of policies in the annotated collection were tagged for open code language.

Policies in the index that reflect guideline 16

PlaceAdoptedInstrumentGuidelines
Portland, ORSep 30, 2009Council resolution37810162230
Austin, TXDec 8, 2011Council resolution351627
Raleigh, NCFeb 7, 2012Council resolution381618
Austin, TXAug 26, 2013Administrative memo123457810
Denton, TXFeb 9, 2015Administrative directive357811121618
Tulsa, OKDec 21, 2015Executive order123458910

Sources

  1. Sunlight Foundation, Open Data Policy Guidelines (historical reference)

Updated December 31, 2024.