<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.emailquote, li.emailquote, div.emailquote
{mso-style-name:emailquote;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:1.0pt;
border:none;
padding:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle20
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:black;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal style='margin-left:.5in'><a name="_MailEndCompose"><span style='font-family:"Calibri",sans-serif'>Nigel Tzeng wrote:<o:p></o:p></span></a></p><p class=MsoNormal style='margin-left:.5in'><span style='mso-bookmark:_MailEndCompose'><span style='font-family:"Calibri",sans-serif'>> </span></span><span style='mso-bookmark:_MailEndCompose'>If DOSA explicitly defines the licensing authority I would prefer it be stated as any DOD approved open source license.<o:p></o:p></span></p><p class=MsoNormal><span style='mso-bookmark:_MailEndCompose'><span style='font-family:"Calibri",sans-serif'><o:p> </o:p></span></span></p><p class=MsoNormal><span style='mso-bookmark:_MailEndCompose'><span style='font-family:"Calibri",sans-serif'>Isn't that already true for every software distributor, including the U.S. government? Every distributor controls its own licensing strategies. Even Google asserts that authority for itself, refusing AGPL software. I have no problem with that level of independence. That is (perhaps unfortunately) why there are so many FOSS licenses.<o:p></o:p></span></span></p><p class=MsoNormal><span style='mso-bookmark:_MailEndCompose'><span style='font-family:"Calibri",sans-serif'><o:p> </o:p></span></span></p><p class=MsoNormal><span style='mso-bookmark:_MailEndCompose'><span style='font-family:"Calibri",sans-serif'>But the concern is <i>yet another FOSS license</i> for the U.S. Army Research Laboratory.<o:p></o:p></span></span></p><p class=MsoNormal><span style='mso-bookmark:_MailEndCompose'><span style='font-family:"Calibri",sans-serif'><o:p> </o:p></span></span></p><p class=MsoNormal><span style='mso-bookmark:_MailEndCompose'><span style='font-family:"Calibri",sans-serif'>A proposed solution, however, is that the U.S. government will distribute software under CC0. I don't care if that is sensible. I don't care if that is odd. I do care that CC0 be an OSI-approved license, regardless of its flaws.<o:p></o:p></span></span></p><p class=MsoNormal><span style='mso-bookmark:_MailEndCompose'><span style='font-family:"Calibri",sans-serif'><o:p> </o:p></span></span></p><p class=MsoNormal><span style='mso-bookmark:_MailEndCompose'><span style='font-family:"Calibri",sans-serif'>That will reaffirm the authority in our community of the <u>OSI-approved</u> open source license list, regardless of the elegance of that solution for DOSA.<o:p></o:p></span></span></p><p class=MsoNormal><span style='mso-bookmark:_MailEndCompose'><span style='font-family:"Calibri",sans-serif'><o:p> </o:p></span></span></p><p class=MsoNormal><span style='mso-bookmark:_MailEndCompose'><span style='font-family:"Calibri",sans-serif'>/Larry<o:p></o:p></span></span></p><p class=MsoNormal><span style='mso-bookmark:_MailEndCompose'><span style='font-family:"Calibri",sans-serif'><o:p> </o:p></span></span></p><p class=MsoNormal><span style='mso-bookmark:_MailEndCompose'><span style='font-family:"Calibri",sans-serif'><o:p> </o:p></span></span></p><span style='mso-bookmark:_MailEndCompose'></span><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='margin-left:.5in'><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> License-discuss [mailto:license-discuss-bounces@opensource.org] <b>On Behalf Of </b>Tzeng, Nigel H.<br><b>Sent:</b> Wednesday, March 1, 2017 9:23 AM<br><b>To:</b> license-discuss@opensource.org<br><b>Subject:</b> Re: [License-discuss] Possible alternative was: Re: U.S. Army Research Laboratory Open Source License (ARL OSL) Version 0.4.1<o:p></o:p></span></p></div></div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p><div><p class=MsoNormal style='margin-left:.5in'>OSI approval is not explicitly required under DOSA. It just says open source license. <o:p></o:p></p><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>If DOSA explicitly defines the licensing authority I would prefer it be stated as any DOD approved open source license.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>That would insure that any projects we develop for sponsors and released as open source will be under a license that has been reviewed and accepted by DOD legal from both from a security as well as compliance standpoint.<o:p></o:p></p></div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:5.0pt 0in 0in 0in'><div><p class=MsoNormal style='margin-left:.5in'><b><span style='font-size:10.5pt'>From: </span></b><span style='font-size:10.5pt'>Jim Wright <<a href="mailto:jwright@commsoft.com">jwright@commsoft.com</a>><o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><b><span style='font-size:10.5pt'>Date: </span></b><span style='font-size:10.5pt'>Wednesday, Mar 01, 2017, 11:53 AM<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><b><span style='font-size:10.5pt'>To: </span></b><span style='font-size:10.5pt'><a href="mailto:license-discuss@opensource.org">license-discuss@opensource.org</a> <<a href="mailto:license-discuss@opensource.org">license-discuss@opensource.org</a>><o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><b><span style='font-size:10.5pt'>Subject: </span></b><span style='font-size:10.5pt'>Re: [License-discuss] Possible alternative was: Re: U.S. Army Research Laboratory Open Source License (ARL OSL) Version 0.4.1<o:p></o:p></span></p></div></div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>Certainly the approach code.mil spells out to contributions seems ok without having to address the license issue at all, but these questions seem orthogonal to me. Cem seems to be trying to ensure that all open source projects operating using this process are under an OSI approved license, which appears to require them to pick one (or several) FOSS licenses to actually apply. CC0 doesn’t work for that 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 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 <<a href="mailto:fontana@sharpeleven.org">fontana@sharpeleven.org</a>> 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><a href="mailto:License-discuss@opensource.org">License-discuss@opensource.org</a><br><a href="https://lists.opensource.org/cgi-bin/mailman/listinfo/license-discuss">https://lists.opensource.org/cgi-bin/mailman/listinfo/license-discuss</a><o:p></o:p></span></p></div></div></body></html>