On 2017-07-26 02:59, Shawn Wells wrote:
Still reading/learning about the code.mil process, but it looks like it'll really help contributions from the non-US community. This gives US Gov employees/contractors what they need for Public Domain protections, and non-US Gov people can follow an agreed license like MIT/GPL etc. Added bonus: This might also be a way to solve a long-standing gripe about certain vendors using the SSG content without attribution. Philippe: Can you review the code.mil process?
As far as i know, it would be perfect. This should resolve the copyright problem for other countries like France. It's even better if, as you said, it also resolve the problem of vendors using SSG without attribution. However, maybe we can decide of an unified Open-source license to avoid multiplicity of licenses in the same project. We can use BSD-3 (as described in [1], which is clearly permissive), or license such as (L)GPL, which is more restrictive depending on how the community which to protect itself against vendors.
https://github.com/deptofdefense/code.mil [1]
-- Philippe. _______________________________________________ scap-security-guide mailing list -- [email protected] To unsubscribe send an email to [email protected]
