Final Federal Source Code policy includes pilot program requiring federal agencies to publicly release 20% of their code, which will be housed on Code.gov
Aaron Boyd / Federal Times :
Context & Ripple Effects
This finalizes the arc that began with the White House's draft open source policy in March 2016, which proposed making federally developed or funded software shareable across agencies. The final version adds the concrete enforcement mechanism the draft lacked: a pilot requiring agencies to publicly release at least 20% of their new code.
The release also pre-builds the infrastructure for compliance — months before launch, Code.gov is already positioned as the showcase, and it goes live that November housing nearly fifty repositories from ten federal agencies. The policy sits in tension with reporting that the US government has separately demanded source code from tech firms through FISA orders and sealed civil cases.
First-order effects
- Federal agencies must inventory new custom code and designate a fifth of it for public release on Code.gov, creating an immediate compliance workload for agency CIOs and program offices.
- Contractors and vendors building software for the government now write under the assumption that a meaningful share of that work product may become publicly reusable rather than proprietary.
Second-order effects
- Agencies can reuse each other's released code instead of paying vendors to rebuild similar systems, shifting procurement value toward integration and maintenance rather than original development.
- Vendors bidding on federal contracts face pricing pressure as previously billable custom builds become shared government assets, pushing differentiation toward services and support.
Third-order effects
- If the pilot holds, 'open by default' hardens into the norm for government-produced software and data — a trajectory confirmed when Trump signs the OPEN Government Data Act mandating machine-readable public data defaults.
- The same government that mandates releasing its own code simultaneously acquires private firms' source code through secret orders, setting up a structural asymmetry between what the state publishes and what it compels.
The trend: Governments are moving from ad hoc openness toward codified default-release policies for publicly funded software and data, with dedicated platforms like Code.gov turning mandates into standing infrastructure.