[License-discuss] [Non-DoD Source] Re: [Non-DoD Source] Re: U.S. Army Research Laboratory Open Source License (ARL OSL) 0.4.0

Radcliffe, Mark Mark.Radcliffe at dlapiper.com
Thu Aug 18 18:28:43 UTC 2016


I suggest using the Apache contribution license agreements rather than Apache itself.

-----Original Message-----
From: License-discuss [mailto:license-discuss-bounces at opensource.org] On Behalf Of Richard Fontana
Sent: Thursday, August 18, 2016 8:04 AM
To: license-discuss at opensource.org
Subject: Re: [License-discuss] [Non-DoD Source] Re: [Non-DoD Source] Re: U.S. Army Research Laboratory Open Source License (ARL OSL) 0.4.0

On Thu, Aug 18, 2016 at 02:50:18PM +0000, Karan, Cem F CIV USARMY RDECOM ARL (US) wrote:
> >
> > Even if you were correct in the assertions you've made about ARL 
> > code, why is a new license needed for contributors other than ARL?
> 
> Are you suggesting a dual license scheme, where all copyrighted 
> portions are under Apache 2.0, and all non-copyrighted portions are under the ARL OSL?

No, I'm just suggesting why not adopt a rule that all contributors (other than ARL -- though for the reasons others have stated I think this should also apply to ARL) license contributions under the Apache License 2.0.

As a few have pointed out, all code that is nominally licensed under open source licenses will contain noncopyrighted portions.
_______________________________________________
License-discuss mailing list
License-discuss at opensource.org
https://lists.opensource.org/cgi-bin/mailman/listinfo/license-discuss
Please consider the environment before printing this email.

The information contained in this email may be confidential and/or legally privileged. It has been sent for the sole use of the intended recipient(s). If the reader of this message is not an intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please reply to the sender and destroy all copies of the message. To contact us directly, send to postmaster at dlapiper.com. Thank you.


More information about the License-discuss mailing list