Q: Am I required to have commercial support for OSS? Q: When a DoD contractor is developing a new system/software as a deliverable in a typical DoD contrac

Q: Am I required to have commercial support for OSS? Q: When a DoD contractor is developing a new system/software as a deliverable in a typical DoD contract, is it possible to use existing software licensed using the GNU General Public License (GPL)? Can the DoD used GPL-licensed software? Q: Under what conditions can GPL-licensed software be mixed with proprietary/classified software? Q: Can contractors develop software for the government and then release it under an open source license? Q: Can the government release software under an open source license if it was developed by contractors under government contract? I'm glad these questions were listed and clearly addressed. My experience has been that contractors are terrified of open source, doubly so for projects with copyleft licenses. This FAQ is really comprehensive so hopefully it can give engineers the footing to dissuade fears that project leadership may have and actually force conversations about both using FOSS (instead of homebrewing or overpriced, worse proprietary alternatives) and maybe even allowing projects to contribute to FOSS.