It would never be implemented that way. At most it'd be "by default, software developed with government funding is released as open source software". Specialt

It would never be implemented that way. At most it'd be "by default, software developed with government funding is released as open source software". Specialty weapon systems would quickly request and get an exemption. But the reality is that even in weapon systems there's lots of "boring code" that would make sense to have as open source software. A lot of it involves "move bits from A to B", "calculate this matrix", and so on that are not really special (you can find the basic algorithms publicly) - but having a way to share the costs with others who need it would be valuable. You can find the US Department of Defense (DoD) OSS FAQ here: https://dodcio.defense.gov/open-source-software-faq/ https://dodcio.defense.gov/open-source-software-faq/ Here's the US DoD OSS policy (2009): https://dodcio.defense.gov/portals/0/documents/foss/2009oss.pdf https://dodcio.defense.gov/portals/0/documents/foss/2009oss.... The DoD policy does not require release by default as open source software (OSS), but there IS a short discussion of when it's okay to release software as OSS when it's funded by the Department of Defense (DoD) - and it's quite open-ended.