<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>Cem,
<div><br>
</div>
<div>Thanks. I missed that when skimming before. :). I think your materials are ahead of what I've seen in the DOSA repo.</div>
<div><br>
</div>
<div>One of the concerns I have (not speaking for my organization) are the same ones that prompted the patent changes to Apache for ECL V2.0.
</div>
<div><br>
</div>
<div>Copyright is easy, I and my team wrote our code. Patent are harder because we as developers or even program managers are not always aware of all patents owned or in progress by the far flung parts of a large research organization. As I've stated before,
I don't mind giving away my work. I don't want to accidentally give away someone else's work (patent).
</div>
<div><br>
</div>
<div>ECL is my natural conservative inclination over Apache. Most of what you see under my name approved for open sourcerelease is actually under NOSA.</div>
<div><br>
</div>
<div>Nigel</div>
<div><br>
</div>
<div class="x_gw_quote" style="border-top:#b5c4df 1pt solid; padding-top:6px; font-size:14px">
<div><b>From: </b><span>Karan, Cem F CIV USARMY RDECOM ARL (US) <<a href="mailto:cem.f.karan.civ@mail.mil">cem.f.karan.civ@mail.mil</a>></span></div>
<div><b>Date: </b><span>Wednesday, Mar 01, 2017, 12:40 PM</span></div>
<div><b>To: </b><span>license-discuss@opensource.org <<a href="mailto:license-discuss@opensource.org">license-discuss@opensource.org</a>></span></div>
<div><b>Subject: </b><span>Re: [License-discuss] [Non-DoD Source] Re: Possible alternative was: Re: U.S. Army Research Laboratory Open Source License (ARL OSL) Version 0.4.1</span></div>
</div>
<br>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">That is actually a part of ARL's policy. If you haven't looked at the policy yet, go to
<a href="https://github.com/USArmyResearchLab/ARL-Open-Source-Guidance-and-Instructions">
https://github.com/USArmyResearchLab/ARL-Open-Source-Guidance-and-Instructions</a> and take a look.<br>
<br>
Thanks,<br>
Cem Karan<br>
<br>
> -----Original Message-----<br>
> From: License-discuss [<a href="mailto:license-discuss-bounces@opensource.org">mailto:license-discuss-bounces@opensource.org</a>] On Behalf Of Tzeng, Nigel H.<br>
> Sent: Wednesday, March 01, 2017 12:23 PM<br>
> To: license-discuss@opensource.org<br>
> Subject: [Non-DoD Source] Re: [License-discuss] Possible alternative was: Re: U.S. Army Research Laboratory Open Source License (ARL<br>
> OSL) Version 0.4.1<br>
> <br>
> All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links<br>
> contained within the message prior to copying and pasting the address to a Web browser.<br>
> <br>
> <br>
> ________________________________<br>
> <br>
> <br>
> <br>
> OSI approval is not explicitly required under DOSA. It just says open source license.<br>
> <br>
> If DOSA explicitly defines the licensing authority I would prefer it be stated as any DOD approved open source license.<br>
> <br>
> That would insure that any projects we develop for sponsors and released as open source will be under a license that has been reviewed<br>
> and accepted by DOD legal from both from a security as well as compliance standpoint.<br>
> From: Jim Wright <jwright@commsoft.com < Caution-mailto:jwright@commsoft.com > ><br>
> Date: Wednesday, Mar 01, 2017, 11:53 AM<br>
> To: license-discuss@opensource.org <license-discuss@opensource.org < Caution-mailto:license-discuss@opensource.org > ><br>
> Subject: Re: [License-discuss] Possible alternative was: Re: U.S. Army Research Laboratory Open Source License (ARL OSL) Version 0.4.1<br>
> <br>
> Certainly the approach code.mil spells out to contributions seems ok without having to address the license issue at all, but these questions<br>
> seem orthogonal to me. Cem seems to be trying to ensure that all open source projects operating using this process are under an OSI<br>
> approved license, which appears to require them to pick one (or several) FOSS licenses to actually apply. CC0 doesn’t work for that<br>
> purpose because it’s not OSI approved anyway and also doesn’t have a patent license, but observing this doesn’t solve Cem’s problem of<br>
> how to license this stuff in a way that *is* OSI approved, which I think is what he’s getting at. (Feel free to correct me…)<br>
> <br>
> <br>
> > On Mar 1, 2017, at 8:29 AM, Richard Fontana <fontana@sharpeleven.org> wrote:<br>
> ><br>
> > Well the complication is mainly a response to Cem wanting the OSI to<br>
> > bless his proposed approach. I think however that code.mil has already<br>
> > rejected this sort of idea.<br>
> ><br>
> > I think the code.mil approach is much more elegant without introducing<br>
> > the use of CC0.<br>
> ><br>
> ><br>
> <br>
> _______________________________________________<br>
> License-discuss mailing list<br>
> License-discuss@opensource.org<br>
> Caution-https://lists.opensource.org/cgi-bin/mailman/listinfo/license-discuss < Caution-https://lists.opensource.org/cgi-<br>
> bin/mailman/listinfo/license-discuss ><br>
<br>
</div>
</span></font>
</body>
</html>