Open means having access.
In the Dept. of Defense we need to ensure/create/enable open access to tax-payer funded technology, period.
Tax-payer funded software development needs to be openly available to all (except for really classified stuff). This means that we will need to figure out the acquisitions mechanisms needed to ensure that the intellectual property is made available to the defense industry and ultimately the tax-payer.
The inclusion of open source software into National Security Systems has jumped the chasm and shown the path. Military OSS products such as Delta3D, BRL-CAD, OSSIM, (and many many more) and of course Open Solaris and RedHat have shown the path for deployment of software systems, now we need to make the institutional default.
Prediction: 18 months from now this will be standard.
Let me know if you want to help.
We agree!
http://fire.nist.gov/fds
How can I help?
-Bryan
i just created an group:
https://www.govloop.com/group/OSSinGov/
add in your tool and invite folks, would be good to get the band together
I thought federal law generally prohibited distributing government software as open source.
An alternative (work-around) is discussed in Federally Funded Software Reuse Optimized Via Open Source Licensing where the author states, “It is in the Government’s interest to encourage authors to copyright software thereby providing a clear lineage and enabling release under open source license.”