FSF and (I believe) OSI both worked with the US DOD / DDS to come up
with one solution to these issues, which is published at
<https://code.mil/>, further described at
<https://github.com/Code-dot-mil/code.mil>:
> Licensing Intent
> The intent is that this software and documentation ("Project") should be
> treated as if it is licensed under the license associated with the
> Project ("License") in the LICENSE.md file. However, because we are part
> of the United States (U.S.) Federal Government, it is not that simple.
> The portions of this Project written by United States (U.S.) Federal
> government employees within the scope of their federal employment are
> ineligible for copyright protection in the U.S.; this is generally
> understood to mean that these portions of the Project are placed in the
> public domain.
> In countries where copyright protection is available (which does not
> include the U.S.), contributions made by U.S. Federal government
> employees are released under the License. Merged contributions from
> private contributors are released under the License.
..so far I know they have released projects under AGPLv3-or-later and
GPLv3-or-later.
-john
--
John Sullivan | Executive Director, Free Software Foundation
GPG Key: A462 6CBA FF37 6039 D2D7 5544 97BA 9CE7 61A0 963B
https://status.fsf.org/johns | https://fsf.org/blogs/RSS
Do you use free software? Donate to join the FSF and support freedom at
<https://my.fsf.org/join>.
_______________________________________________
License-discuss mailing list
License-discuss@lists.opensource.org
http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org
