Last week provided a significant boost to open source software in the form of survey results suggesting that such technologies have now become a norm in the business world. Now, in what’s perhaps an even bigger blow to proprietary vendors, none other than the Department of Defense has weighed in with its own support for open technology.
Noting software’s central importance in the way “the warfighter conducts missions” today, the document notes that “DoD must have software that is easily adaptable to changing mission needs and can be evolved rapidly and delivered quickly at lower costs to meet mission requirements in a timely manner.”
And that’s just software, wait until open-source hardware is thought of in the same way…
Have an amazing project to share? The Electronics Show and Tell is every Wednesday at 7:30pm ET! To join, head over to YouTube and check out the show’s live chat and our Discord!
Python for Microcontrollers – Adafruit Daily — Python on Microcontrollers Newsletter: A New Arduino MicroPython Package Manager, How-Tos and Much More! #CircuitPython #Python #micropython @ThePSF @Raspberry_Pi
EYE on NPI – Adafruit Daily — EYE on NPI Maxim’s Himalaya uSLIC Step-Down Power Module #EyeOnNPI @maximintegrated @digikey
As a DoD employee, I can say this isn’t new by any means. But the reasons for going open source is mainly for security. DoD has requirements that source be inspected before the software is approved for use. The proprietary vendors aren’t always too willing to hand over there entire source code base. The second main reason is DoD engineers don’t like getting tied to a vendor for updates and support.
This is just the most current version of this document. The earliest version I can find dates back to 2006 and is a roadway for future use. http://www.acq.osd.mil/jctd/articles/otdroadmapfinal.pdf
As a DoD employee, I can say this isn’t new by any means. But the reasons for going open source is mainly for security. DoD has requirements that source be inspected before the software is approved for use. The proprietary vendors aren’t always too willing to hand over there entire source code base. The second main reason is DoD engineers don’t like getting tied to a vendor for updates and support.