Welcome to Code.mil

An experiment in open source at the Department of Defense.

The U.S. Department of Defense (DoD) faces unique challenges in open sourcing its code. Unlike most software projects, code written by U.S. Federal government employees typically doesn't have copyright protections under U.S. and some international laws. This can make it hard to attach an open source license to our code, and our team here at Defense Digital Service wants to find a solution. Read about our journey so far on Medium.

If you are a DoD or Military Department employee with a project you want hosted on Code.mil, get the conversation going by submitting your information.

This repository is the open source home for the public-facing web site Code.mil.

Build with us.

The DoD is charged with protecting our citizens and national security. We have an incredibly diverse portfolio spanning from communications, logistics, education, healthcare, and even the next generation of GPS (yes, the GPS!) that supports billions of people across the globe.

We need your help in contributing to our projects to build better products and services for the American people. You can contribute by finding a project, reviewing its contributor guidelines, and submitting an issue or Pull Request!

[!NOTE] Curious about DDS?

If you're curious about Defense Digital Service (DDS), the team behind Code.mil, check us out online at dds.mil. We're always looking for good people to join us!

Make us better.

We've drafted documentation on implementing OSS within the DoD and a guideline for accepting contributions to DoD OSS projects so the DoD can participate in the open source and free software communities, even where we may not have copyright. This lets us harness the depth and breadth of talent in the open source and free software communities to improve our software and make our code available for public use.

We want your help to continue making our open source strategy better. Our philosophy is continuous iteration. We encourage everybody to open an issue (or a pull request!) with your suggestions on how to continue improving.