Late last month the US Department of Defence (DoD) published a memorandum on software development [defense.gov] (warning for PDF). It focuses specifically on Open Source Software (OSS), though it misses the fact that OSS can also be commercial in nature.
- A. The Department must follow an "Adopt, Buy, Create" approach to software, preferentially adopting existing government or OSS solutions before buying proprietary offerings, and only creating new non-commercial software when no off-the-shelf solutions are adequate.
- (1) OSS meets the definition of "commercial computer software" and therefore, shall be given equal consideration with proprietary commercial offerings, in accordance with Section 2377 of Title 10, U.S.C. (reference (e)) (see also FAR 2.l0l(b), 12.000, 12.101 (reference (f)); and DFARS 212.212, DFARS 208.74, DFARS 227.7202, and 252.227-7014(a)(l) (reference (g))).
- (2) In accordance with FAR 13.104, (reference (h)) refusal to consider all OSS based solely on software being open source may be contrary to statutory and regulatory preferences for commercial products, and would unnecessarily restrict competition. OSS should be considered to the maximum extent practical.
Across the pond, the EU's Open Source Observatory (OSOR) has an analysis of the memorandum [europa.eu] in the context of DoD Software Modernization Strategy [defense.gov] from earlier this month.
Even back in 1998 M$ proprietary software was deemed a threat [strassmann.com] and the situation has not changed [techrights.org] it is still a threat [medium.com] to safety, reliability, confidentiality, and costs.
Previously:
(2021) More Than Two Decades of Causing Worsening Cybersecurity [soylentnews.org]
(2018) The Battle to Free the Code at the Department of Defense [soylentnews.org]
(2018) Code.mil Serves as Guidepost for Releasing Custom US Government Software as FOSS [soylentnews.org]
(2017) Uncle Sam Needs You... to Debug, Improve Dept of Defense Open-Source Software at Code.Mil [soylentnews.org]