U.S. Defense Department Promotes Open Source
An open memo from the U.S. DoD declares that open source software is no worse than traditional software, perhaps even useful.
The DoD needs to take faster steps at increased care and maintenance of its software infrastructure, where open source provides a marked advantage, according to acting DoD chief information officer David M. Wennegren in his recent memo to defense entities. In it he asserts that knowledge gaps and misunderstanding have prevented effective use of open source in the DoD. His "Clarifying Guidance Regarding Open Source Software (OSS)" addresses joint chiefs of staff, the defense secretariat and other decision-makers in IT, acquisitions and related entities, and includes some enlightening material.
The memo recommends taking a good look at open source software to determine which market products can best address a stated task. Wennegren states his case with seven arguments for open source: its (1) broad peer review provides stability and reliability, (2) adaptability to changing conditions, (3) independence from single developer reliance, (4) unrestricted licensing, (5) cost growth mitigation, (6) shared maintenance opportunities and (7) rapid prototyping and experimentation opportunities.
Wennegren's memo goes on to dash some current misconceptions among DoD folks about open source. For example, he clarifies that "many open source licenses permit the user to modify OSS for internal use without being obligated to distribute source code to the public. However, if the user chooses to distribute the modified OSS outside the [DoD], then some OSS licenses (such as the GNU General Public License) do require distribution of the corresponding source code to the recipient of the software." In other words, if further developed open source code is to be used only internally (is classified), the source code need not be distributed externally.
The six-page document dates from October 16, 2009 and is available off the DoD FOSS webpage, which also includes the FAQ and a document from 2003 that Wennegren claims resulted in some misconceptions he wanted to resolve with the current memo. The older document likewise targeted OSS in the DoD, but focused almost entirely on compliance with policies instead of providing clarification.
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters
Support Our Work
Linux Magazine content is made possible with support from readers like you. Please consider contributing when you’ve found an article to be beneficial.

News
-
System76 Releases COSMIC Alpha 7
With scores of bug fixes and a really cool workspaces feature, COSMIC is looking to soon migrate from alpha to beta.
-
OpenMandriva Lx 6.0 Available for Installation
The latest release of OpenMandriva has arrived with a new kernel, an updated Plasma desktop, and a server edition.
-
TrueNAS 25.04 Arrives with Thousands of Changes
One of the most popular Linux-based NAS solutions has rolled out the latest edition, based on Ubuntu 25.04.
-
Fedora 42 Available with Two New Spins
The latest release from the Fedora Project includes the usual updates, a new kernel, an official KDE Plasma spin, and a new System76 spin.
-
So Long, ArcoLinux
The ArcoLinux distribution is the latest Linux distribution to shut down.
-
What Open Source Pros Look for in a Job Role
Learn what professionals in technical and non-technical roles say is most important when seeking a new position.
-
Asahi Linux Runs into Issues with M4 Support
Due to Apple Silicon changes, the Asahi Linux project is at odds with adding support for the M4 chips.
-
Plasma 6.3.4 Now Available
Although not a major release, Plasma 6.3.4 does fix some bugs and offer a subtle change for the Plasma sidebar.
-
Linux Kernel 6.15 First Release Candidate Now Available
Linux Torvalds has announced that the release candidate for the final release of the Linux 6.15 series is now available.
-
Akamai Will Host kernel.org
The organization dedicated to cloud-based solutions has agreed to host kernel.org to deliver long-term stability for the development team.