Summary
Makes federal agencies share the computer code they create so other agencies can use it, which helps save time and money.
What problem does this solve?
Government agencies often build similar software from scratch, wasting taxpayer money and time because they do not share their work. This law requires agencies to share their custom-made computer code in central locations, allowing other government groups to reuse it.
Who does this affect?
- Federal government agencies
- Government software contractors
- Federal employees in technology roles
What does this law do?
Requires sharing of custom government code
Directs all federal agencies to store their custom-made software code in at least one public or private storage location, called a repository, so it can be accessed by other federal employees.
Makes code information publicly discoverable
Requires agencies to make the metadata, or the basic information about their custom code, available to the public. This helps others find and understand the software that has been created.
Establishes exemptions for sensitive code
Excludes classified or national security-related source code from the sharing requirements. Agency leaders can also exempt code if sharing it would create a privacy risk or is forbidden by another law.
Updates government purchasing rules
Ensures that when the government pays a contractor to develop software, it gets the rights to share, use, and change the code across all agencies.
Creates new agency policies and reports
Requires each agency's Chief Information Officer to develop a policy for sharing code. Also requires an annual government-wide report on how the law is being followed.
What is the real world impact?
•
Creates potential for widespread security risks
Sharing code across the government could mean that a security mistake in one program gets copied into many others. If a hacker finds that mistake, they could potentially attack multiple government systems at once.
•
Promotes efficiency and saves taxpayer money
Stops agencies from paying to create the same software over and over again. By sharing and reusing code, the government can develop new tools faster and at a lower cost, making better use of tax dollars.
When does this start?
This law sets several deadlines for agencies and officials to put its rules into action over the next two years.
Agency policy development
Within 180 days, each agency's Chief Information Officer must create a new policy for sharing custom-developed code.
Code sharing begins
Within 210 days, agencies must start storing their custom code in repositories and making its metadata publicly accessible.
Update to purchasing regulations
Within one year, the Federal Acquisition Regulation must be updated to include the new rules on software reuse rights.
First annual report published
Within one year, the Office of Electronic Government must publish its first annual report on how agencies are following the law.