<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:11.0pt;
font-family:"Calibri",sans-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:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle19
{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;
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:12.0pt'>I just saw this thread. I'm sorry for the late response.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'>What is the problem? The libpng license is permissive. It allows you to license your derivative works under any license of your choice, so long as you don't misrepresent it as entirely your own work; you must acknowledge that you created a derivative work; and you must leave the original libpng license in the source code to reflect the original work's availability under that original libpng license.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'>Why do you need a "version 2.0"? You can already do almost anything you need to do to own the future of this program.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'>/Larry<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:.5in'><b>From:</b> License-review <license-review-bounces@lists.opensource.org> <b>On Behalf Of </b>Henrik Ingo<br><b>Sent:</b> Saturday, November 17, 2018 12:07 PM<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></p><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p><div><div><p class=MsoNormal style='margin-left:.5in'>Hi Cosmin<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'><o:p> </o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in'><o:p> </o:p></p><div><div><p class=MsoNormal style='margin-left:.5in'>On Tue, Nov 6, 2018 at 11:02 AM Cosmin Truta <<a href="mailto:ctruta@gmail.com">ctruta@gmail.com</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in'>Thank you for sending me all of that detailed information regarding<br>the legal foundations that I can contact, Henrik. I was not aware of<br>them. I will consider contacting them, in the future.<o:p></o:p></p></blockquote><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>You're welcome. They're a great resource for projects like yours.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in'>> If you modify libpng you may insert additional notices immediately<br>> following this sentence.<br><br>Henrik Ingo wrote:<br>> [...] it would be worth looking into the alternatives you<br>> mentioned, such as moving the contributors to a separate flat list.<br><br>Since the lists of previous contributing authors have been integrated<br>into the past libpng license text, I'm not touching those. But<br>besides that, all contributors, past, present and future, will be<br>mentioned in a separate flat list from now on.<br><br><a href="https://gist.github.com/ctruta/5e276eb83213f9d66bf61539156830c5#file-authors-md" target="_blank">https://gist.github.com/ctruta/5e276eb83213f9d66bf61539156830c5#file-authors-md</a><o:p></o:p></p></blockquote><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>My logic was that if you could go back with a proposal drafted by a respected open source legal expert, it may be more persuasive. But maybe not. I fully understand that as the major contributor to the project is no longer alive, it's not easy to negotiate with his last stated opinion on the matter. Even if his estate might be legally empowered to have such a dialogue, it might not be the right thing to do. Even then, my suggestion was that talking to a real lawyer wouldn't hurt (in this respect, as well as in general).<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in'>> Getting this sort of support from SFLC or SFC is a good suggestion,<br>> but acceptance by those groups tends to take a long time. Finding<br>> other pro-bono help might be appropriate.<br><br>I have already been asked, by eagerly-awaiting users, when will the<br>new ready-to-ship fixes and improvements come out officially as<br>libpng 1.6.36. My response to them was "after the OSI review".<br>(I understood that OSI recommends to only ship software with the new<br>license *after* the review.)<br><br>I'm not saying this to mean that I absolutely must skip a legal<br>review. But if a lengthy review over a lengthy period of time is<br>something that I could avoid, and if I could just go on the beaten<br>path of existing practice instead, then I'd like to do exactly that.<br><br>The ownership of libpng has been passed on from Guy Eric Schalnat and<br>Group 42, Inc., to Andreas Dilger, and then to Glenn Randers-Pehrson,<br>with no legal issues in the process. I hope I can succeed Glenn, in a<br>similar manner, just as well.<o:p></o:p></p></blockquote><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>As a developer myself, I fully understand.<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'>I think a silver lining here is that if the patches to the to-be-released version are all done by yourself, you would not be doing anything irrevocable by doing a release with what you have, and then seeking legal advice on the topic of how to craft the new "last version" of libpng license. For example, you could just do a new release without touching the LICENSE file at all. (But note that this may not be compliant with the old licenses, which forbid publishing changes without clearly attributing changes to the new author.) Even here, it's in *your own interest* to have a lawyer involved to protect yourself, but I don't see any lasting harm to the community and your users if you wanted to go ahead and do a release quickly without waiting for legal advice.<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'>Hope this helps. Not much more someone like me can say here.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><p class=MsoNormal style='margin-left:.5in'>henrik<br clear=all><o:p></o:p></p></div><p class=MsoNormal style='margin-left:.5in'>-- <o:p></o:p></p><div><p class=MsoNormal style='margin-left:.5in'><a href="mailto:henrik.ingo@avoinelama.fi" target="_blank">henrik.ingo@avoinelama.fi</a><br>+358-40-5697354 skype: henrik.ingo irc: hingo<br><a href="http://www.openlife.cc" target="_blank">www.openlife.cc</a><br><br>My LinkedIn profile: <a href="http://fi.linkedin.com/pub/henrik-ingo/3/232/8a7" target="_blank">http://fi.linkedin.com/pub/henrik-ingo/3/232/8a7</a><o:p></o:p></p></div></div></div></body></html>