<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=utf-8">
<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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@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"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></a></p>
<p class="MsoNormal"><a name="_____replyseparator"></a><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-review [mailto:license-review-bounces@lists.opensource.org]
<b>On Behalf Of </b>Henrik Ingo<br>
<b>>>Sent:</b> Monday, November 5, 2018 7:51 AM<br>
<b>>>To:</b> license-review@lists.opensource.org<br>
<b>>>Subject:</b> Re: [License-review] For Approval: libpng license, version 2.0<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#1F497D">>></span>This list is of course populated with great legal minds as well, but in my experience a lawyer giving your formal legal counsel will trump a mailing list discussion any day.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#1F497D">>></span>None of the above is to imply that I would be opposed to your submission as it stands. I guess my first reaction is that libpng as a library is embedded into larger software applications, so there would
be some value in ending up with a simpler and shorter alternative. So it would be worth looking into the alternatives you mentioned, such as moving the contributors to a separate flat list.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I found this submission very confusing, in part because it seems to be a series of licenses and/or disclaimers sequentially superimposed on other licenses or
disclaimers, each of which appears to indicate that it applies to different versions of a particular piece of software. If, for example, the Boost license is intended to apply to the latest version, why is there a need for reproduction of the license or licenses
used with predecessor versions of the software? If it is for legacy code, that legacy code would already have the license appended to it, so there isn’t a need to instead append the license text itself. If not, how is the user to discern which rights apply
to which parts of the latest version of the software they have received?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="color:#1F497D">I’d also note that the text you submitted has a lot more legal terminology than just a concatenation of the zlib/libpng license (here: https://opensource.org/licenses/Zlib ) and the Boost license (here:</span>
<span style="color:#1F497D">https://opensource.org/licenses/BSL-1.0 ) including a fairly strong trademark statement that neither of those licenses has:<br>
<br>
“</span>The name "libpng" has not been registered by the Copyright owners as a trademark in any jurisdiction. However, because libpng has been distributed and maintained world-wide, continually since 1995, the Copyright owners claim "common-law trademark protection"
in any jurisdiction where common-law trademark is recognized.<span style="color:#1F497D">”<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="color:#1F497D">The effect of that statement on OSD 1 should probably be addressed.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="color:#1F497D">The license, given the manner it is written, also seems to only be applicable to, and may only be used with, a single piece of software given the way it presents authorship statements within the text of the
license, so seems non-reusable.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="color:#1F497D">The UCITA point is an interesting one, but I’m curious if anyone on the list has information on what disclaimer terminology is and is not effective under UCITA.<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>