017 2:51 PM
> > To: license-discuss@opensource.org
> > Subject: Re: [License-discuss] [Non-DoD Source] code.mil update
> >
> > On Wed, Mar 8, 2017 at 7:03 AM Christopher Sean Morrison <brl...@mac.com
> < Caution-mailto:brl...@mac.com > > wrote:
> >
&g
> -Original Message-
> From: License-discuss [mailto:license-discuss-boun...@opensource.org] On
> Behalf Of Luis Villa
> Sent: Wednesday, March 08, 2017 2:51 PM
> To: license-discuss@opensource.org
> Subject: Re: [License-discuss] [Non-DoD Source] code.mil update
>
On Wed, Mar 8, 2017 at 7:03 AM Christopher Sean Morrison
wrote:
>
> > On Mar 8, 2017, at 9:32 AM, Karan, Cem F CIV USARMY RDECOM ARL (US) <
> cem.f.karan@mail.mil> wrote:
> >
> > You might want to re-read what they posted; the license applies only to
> those
> > portions of
> -Original Message-
> From: License-discuss [mailto:license-discuss-boun...@opensource.org] On
> Behalf Of Christopher Sean Morrison
> Sent: Wednesday, March 08, 2017 10:03 AM
> To: license-discuss@opensource.org
> Subject: Re: [License-discuss] [Non-DoD Sourc
> On Mar 8, 2017, at 9:32 AM, Karan, Cem F CIV USARMY RDECOM ARL (US)
> wrote:
>
> 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
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
6 matches
Mail list logo