Introduction
About the Source Code Policy
The President is committed to a 21st Century digital government – one that is designed to improve the lives of Americans and spur innovation with the best that technology has to offer. From helping students and families make more informed decisions about college selection to modernizing our country’s immigration system to opening up thousands of data sets and collections for Americans to leverage, this work has reimagined how government services and resources should be provided to the public.
The Federal Source Code Policy is designed to support reuse and public access to custom-developed Federal source code. It requires new custom-developed source code developed specifically by or for the Federal Government to be made available for sharing and re-use across all Federal agencies. It also includes an Open Source Pilot Program that requires agencies to release at least 20% of new custom-developed Federal source code to the public.
By making source code available for sharing and re-use across Federal agencies, we can avoid duplicative custom software purchases and promote innovation and collaboration across Federal agencies. By opening more of our code to the brightest minds inside and outside of government, we can enable them to work together to ensure that the code is reliable and effective in furthering our national objectives. And we can do all of this while remaining consistent with the Federal Government’s long-standing policy of technology neutrality, through which we seek to ensure that Federal investments in IT are merit-based, improve the performance of our government, and create value for the American people.
How we'll get there
This section of code.gov is designed to help agencies understand what is required by the policy and provide advice on how best to get there. Whether you're a developer, a Chief Information Officer, or an acquisition officer, this guide is for you. Use it to better understand exactly what is required and how to maximize the benefits your agency will realize from implementation of the policy.
Most importantly, unlike the policy itself, the content here is going to evolve and expand quickly. Check back often for new and improved articles. But better still, please consider this site yours. Use the open source repository for this site to ask questions by opening issues and suggest changes to the content using an Issue or Pull Request. If something is confusing or you have a question that isn't addressed, let's fix that together.
On a final but important note, agencies should always treat the content here as purely advisory and rely primarily on the text of the policy itself to satisfy their obligations.