powdermonkey: DoD memo on Open Source
powdermonkey brings us the welcome news that the US Department of Defense has positively OK'd Open Source software for use in its projects.
Here's the opening statement:
To effectively achieve its missions, the Department of Defense must develop and update its software-based capabilities faster than ever, to anticipate new threats and respond to continuously changing requirements. The use of Open Source Software (OSS) can provide advantages in this regard.
The memo's attachments outline a cogent case for OSS, which all software customers should take to heart. Here's a list of key points:
There are positive aspects of OSS that should be considered when conducting market research on software for DoD use, such as:
- The continuous and broad peer-review enabled by publicly available source code supports software reliability and security efforts through the identification and elimination of defects that might otherwise go unrecognized by a more limited core development team.
- The unrestricted ability to modify software source code enables the Department to respond more rapidly to changing situations, missions, and future threats.
- Reliance on a particular software developer or vendor due to proprietary restrictions may be reduced by the use of OSS, which can be operated and maintained by multiple vendors, thus reducing barriers to entry and exit.
- Open source licenses do not restrict who can use the software or the fields of endeavor in which the software can be used. Therefore, OSS provides a net-centric licensing model that enables rapid provisioning of both known and unanticipated users.
- Since OSS typically does not have a per-seat licensing cost, it can provide a cost advantage in situations where many copies of the software may be required, and can mitigate risk of cost growth due to licensing in situations where the total number of users may not be known in advance.
- By sharing the responsibility for maintenance of OSS with other users, the Department can benefit by reducing the total cost of ownership for software, particularly compared with software for which the Department has sole responsibility for maintenance (e.g., GOTS).
Gives new meaning to "Good enough for government work" :-)
Powdermonkey post
DoD PDF document