"Open Source" has made its way into DOD, but DOD is not capitalizing on its greatest values. DOD is currently exploring use of Open Source tools, services, and code but not so much on development philosophies and methodologies. In fact, many in DoD think it is just too hard. Why? Consider this definition of open source software development:

"Open source doesn't just mean access to the source code. The distribution terms of open-source software must comply with the following criteria:

1. Free redistribution

2. Program must include source code and must allow distribution in source code as well as compiled form.

3. License must allow derived works

4. Integrity of the author's source code

5. No discrimination against persons or groups

6. No discriminations against fields of endeavor

7. The rights attached to the program must apply to all whom the program is redistributed

8. License must not restrict other software

9. License must be technology-neutral"¹

This is a departure from DoD acquisition practices. It is generally accepted and encouraged to use proven products of open source, but not to develop DoD products in this manner. The industry proven benefits include reduced cost, opening the aperture of developers contributing to solutions, higher quality from community reviews, and accelerated technology innovation to name a few. DoD has tried in limited ways to open the door by hosting sites like Forge.mil, but that is not enough. This paper will make a case for expanding DoD's use of open source development philosophies and methodologies. It will propose approaches to include changes in how we acquire software that could kick-start a revolutionary approach to efficient software development and rapid technology capability growth.

Meggan Schoenberg

Affiliation

Refine Results

A Plausible Approach to Open Source Development in a Department of Defense (DoD) Environment: Open Technology Development (OTD)