You might want to re-read what they posted; the license applies only to those 
portions of the code that have copyright attached, otherwise it's public 
domain.  The trick is that while US Government (USG) works are ineligible for 
copyright within the US, they may be eligible for copyright outside the US, 
and in those areas the USG works are licensed under the OSI-approved license. 
I'm not sure what it would mean for code that was moved across jurisdictions, 
but I do understand and appreciate the intent of their approach.

Thanks,
Cem Karan

> -----Original Message-----
> From: License-discuss [mailto:license-discuss-boun...@opensource.org] On 
> Behalf Of Christopher Sean Morrison
> Sent: Tuesday, March 07, 2017 9:13 PM
> To: License Discussion Mailing List <license-discuss@opensource.org>
> Subject: [Non-DoD Source] [License-discuss] code.mil update
>
> All active links contained in this email were disabled. Please verify the 
> identity of the sender, and confirm the authenticity of all links
> contained within the message prior to copying and pasting the address to a 
> Web browser.
>
>
> ________________________________
>
>
>
>
> On a rather unrelated note (apologies for the deluge of e-mails today!), the 
> folks behind code.mil have responded to public feedback and
> are proposing significant changes to their approach.
>
> Instead of wrapping an OSI license as before, they now propose to directly 
> utilize an existing copyright-based open source license.  That is,
> they may actually attempt to test the theory postulated by Richard Fontana 
> et al., namely that horrible things might not actually happen
> if the USG slaps a copyright-based license on their works.  Instead of 
> wrapping the license, they use it straight up with an INTENT.md file
> to explain that what's public domain obviously remains as such, and what's 
> not falls under the license.  Details here:
>
>
> Caution-https://github.com/deptofdefense/code.mil#welcome-to-codemil---an-experiment-in-open-source-at-the-department-of-defense
> < 
> Caution-https://github.com/deptofdefense/code.mil#welcome-to-codemil---an-experiment-in-open-source-at-the-department-of-
> defense >

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
License-discuss mailing list
License-discuss@opensource.org
https://lists.opensource.org/cgi-bin/mailman/listinfo/license-discuss

Reply via email to