<div dir="ltr">Dear Antonie,<div><br></div><div>> However, there are a few libraries distributed with the Apache v2 license,<br>> and, currently, we are not sure if this is ok to ship them in the<br>> PrestaShop installer. We know that Magento, who uses OSL too, are shipping<br>> Apache v2 libraries, like some from Elastic. So, it might be good. But, our<br>> legal team can't find a clear confirmation that this is possible, and that<br>> it does not represent a compliance failure.<br><br>I am an attorney, but not licensed to practice law in France, so the following does not constitute legal advice. Several licenses have been drafted in the United States of America with the help of US Attorneys, or by US attorneys. Therefore, most of its interpretation is under US Law. Even though that, and despite the differences or similarities between legal systems and legislations, very, unfortunately, these laws and its interpretation are not equal in all countries. Furthermore, in the Open Source Licensing, you may know that opinions differ even within borders, from the copyright holder of the license and the copyright holders of the technology. Thus, it is not an easy task. I think that you have already a response below, but it would be up to your legal department to move forward only with that. An email, even from one of the most knowledge open-source attorney, it could or not be enough for your legal department, most when even the Apache and the OSL Licenses should be reviewed under the French Law. But if the company that you work for put their attorney to talk with an expert, they can solve the local law interpretation issue -if any-.Under that perspective, your Legal depart shall be covered, since it counts with a legal opinion signed by a well-versed attorney. For instance, in my country, Argentina, with have some specialties about how contract (licenses is a contract for us) must be interpreted. And these are regulated in our civil code. Anyway, I just wanted to point out that form the legal practical perspective the best way to approach with an internal legal department is just to provide the name to who they should talk in case they are uncertain about. Thanks, Gustavo. <br><br>> When I read your interview, and other documents about OSL, my feeling is<br>> that the OSL allows to distribute the code with any aggregated software<br>> (e.g dependencies), and does not require to change their license. And that,<br>> of course, only derivative work of the code in OSL must be in OSL. But, I<br>> am not a lawyer, and our legal team is looking for a clear statement. <br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">El vie., 8 nov. 2019 a las 12:53, <<a href="mailto:license-discuss-request@lists.opensource.org">license-discuss-request@lists.opensource.org</a>> escribió:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send License-discuss mailing list submissions to<br>
<a href="mailto:license-discuss@lists.opensource.org" target="_blank">license-discuss@lists.opensource.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org" rel="noreferrer" target="_blank">http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org</a><br>
<br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:license-discuss-request@lists.opensource.org" target="_blank">license-discuss-request@lists.opensource.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:license-discuss-owner@lists.opensource.org" target="_blank">license-discuss-owner@lists.opensource.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of License-discuss digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: OSL, Apache and PrestaShop (Lawrence Rosen)<br>
2. Re: OSL, Apache and PrestaShop (Antoine Thomas)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Fri, 8 Nov 2019 07:36:13 -0800<br>
From: "Lawrence Rosen" <<a href="mailto:lrosen@rosenlaw.com" target="_blank">lrosen@rosenlaw.com</a>><br>
To: "'Antoine Thomas'" <<a href="mailto:antoine.thomas@prestashop.com" target="_blank">antoine.thomas@prestashop.com</a>><br>
Cc: <<a href="mailto:license-discuss@lists.opensource.org" target="_blank">license-discuss@lists.opensource.org</a>>, "Lawrence Rosen"<br>
<<a href="mailto:lrosen@rosenlaw.com" target="_blank">lrosen@rosenlaw.com</a>><br>
Subject: Re: [License-discuss] OSL, Apache and PrestaShop<br>
Message-ID: <003001d5964a$419aada0$c4d008e0$@<a href="http://rosenlaw.com" rel="noreferrer" target="_blank">rosenlaw.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Dear Antoine,<br>
<br>
<br>
<br>
I saw your posting on license-discuss@ and read your email below. You are perfectly right: There is no problem aggregating Apache and OSL code. Both licenses allow it. I stand completely by my earlier blog posting on this topic.<br>
<br>
<br>
<br>
I remain surprised that there was any reluctance even for non-lawyers to confirm that on license-discuss@. Both licenses are perfectly clear that only derivative works of OSL must be released under the OSL, and ASL doesn't care at all. <br>
<br>
<br>
<br>
Best regards, Larry<br>
<br>
<br>
<br>
Lawrence Rosen<br>
<br>
Rosenlaw ( <<a href="http://www.rosenlaw.com/" rel="noreferrer" target="_blank">http://www.rosenlaw.com/</a>> <a href="http://www.rosenlaw.com" rel="noreferrer" target="_blank">www.rosenlaw.com</a>) <br>
<br>
LinkedIn: LawrenceRosen<br>
<br>
3001 King Ranch Rd., Ukiah, CA 95482<br>
<br>
Cell: 707-478-8932 <br>
<br>
This email is licensed under <<a href="https://creativecommons.org/licenses/by/4.0/" rel="noreferrer" target="_blank">https://creativecommons.org/licenses/by/4.0/</a>> CC-BY-4.0. Please copy freely. <br>
<br>
<br>
<br>
From: Antoine Thomas <<a href="mailto:antoine.thomas@prestashop.com" target="_blank">antoine.thomas@prestashop.com</a>> <br>
Sent: Friday, November 8, 2019 4:28 AM<br>
To: <a href="mailto:lrosen@rosenlaw.com" target="_blank">lrosen@rosenlaw.com</a><br>
Subject: OSL, Apache and PrestaShop<br>
<br>
<br>
<br>
Dear Lawrence,<br>
<br>
<br>
<br>
I am contacting you for in the past, you have answered an interview about the OSL and the AFL published on PrestaShop blog (<a href="https://www.prestashop.com/en/blog/interview-lawrence-rosen-author-open-software-licence" rel="noreferrer" target="_blank">https://www.prestashop.com/en/blog/interview-lawrence-rosen-author-open-software-licence</a>)<br>
<br>
<br>
<br>
In this interview, you state that, I quote, "The OSL/AFL licenses intend to eliminate such confusion. These licenses do not affect independently written code at all, no matter how aggregated." And, at PrestaShop, we would need to have a few precisions.<br>
<br>
<br>
<br>
To give you a bit of context, I am currently working for the PrestaShop company, and I do my best to study and improve the maturity of the PrestaShop project, with the support of our legal team, the developers, and other teams. One of the big taks is the legal compliance: this topic is more and more important today, because more and more companies want to use open source software, but they don't want to take risks for their business. So, after a review of the license all the dependencies and sub-dependencies of the project, we found that most are distributed with MIT or BSD. <br>
<br>
<br>
<br>
However, there are a few libraries distributed with the Apache v2 license, and, currently, we are not sure if this is ok to ship them in the PrestaShop installer. We know that Magento, who uses OSL too, are shipping Apache v2 libraries, like some from Elastic. So, it might be good. But, our legal team can't find a clear confirmation that this is possible, and that it does not represent a compliance failure.<br>
<br>
<br>
<br>
When I read your interview, and other documents about OSL, my feeling is that the OSL allows to distribute the code with any aggregated software (e.g dependencies), and does not require to change their license. And that, of course, only derivative work of the code in OSL must be in OSL. But, I am not a lawyer, and our legal team is looking for a clear statement.<br>
<br>
<br>
<br>
That is why, recently, I sent a question about this problem to the OSI mailing list, where the answer was, to make it short: "ask a lawyer". Then, I thought that you were certainly the best person to confirm what is the right way to aggregate libraries in an OSL project, and what are the compatible licenses. And so, in a way, that would also clarify what you told in this old interview.<br>
<br>
<br>
<br>
So, if you could provide some clarification in an answer, or links to already existing resources, that would be a great help for the PrestaShop project and its users.<br>
<br>
<br>
<br>
Of course, if you need more details or information, please let know. I will be available.<br>
<br>
<br>
<br>
Looking forward to hearing from you,<br>
<br>
<br>
<br>
Antoine<br>
<br>
<br>
<br>
<br>
<br>
<<a href="https://www.prestashop.com/?utm_source=signature&utm_medium=e-mail&utm_campaign=emails-signatures" rel="noreferrer" target="_blank">https://www.prestashop.com/?utm_source=signature&utm_medium=e-mail&utm_campaign=emails-signatures</a>> <br>
<br>
Antoine Thomas aka ttoine<br>
<br>
Developer Advocate<br>
<br>
t: +33 (0)6 63 13 79 06<br>
<br>
<mailto:<a href="mailto:antoine.thomas@prestashop.com" target="_blank">antoine.thomas@prestashop.com</a>> <a href="mailto:antoine.thomas@prestashop.com" target="_blank">antoine.thomas@prestashop.com</a><br>
<br>
<br>
<br>
<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/attachments/20191108/85c79bcb/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/attachments/20191108/85c79bcb/attachment-0001.html</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: image001.png<br>
Type: image/png<br>
Size: 1393 bytes<br>
Desc: not available<br>
URL: <<a href="http://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/attachments/20191108/85c79bcb/attachment-0001.png" rel="noreferrer" target="_blank">http://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/attachments/20191108/85c79bcb/attachment-0001.png</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Fri, 8 Nov 2019 16:52:21 +0100<br>
From: Antoine Thomas <<a href="mailto:antoine.thomas@prestashop.com" target="_blank">antoine.thomas@prestashop.com</a>><br>
To: <a href="mailto:lrosen@rosenlaw.com" target="_blank">lrosen@rosenlaw.com</a><br>
Cc: <a href="mailto:license-discuss@lists.opensource.org" target="_blank">license-discuss@lists.opensource.org</a><br>
Subject: Re: [License-discuss] OSL, Apache and PrestaShop<br>
Message-ID:<br>
<CAAJ8xWc-xGYb9oj-_yqeBtLc4u6bd_-V_4Q-jhgVE=<a href="mailto:QBs5RF7Q@mail.gmail.com" target="_blank">QBs5RF7Q@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Dear Larry,<br>
<br>
Thank you very much for your answer. I will forward your email to our legal<br>
team, and add Apache v2 to the list of cleared licenses.<br>
<br>
Have a nice weekend,<br>
<br>
Antoine<br>
<br>
<br>
<br>
[image: PrestaShop]<br>
<<a href="https://www.prestashop.com/?utm_source=signature&utm_medium=e-mail&utm_campaign=emails-signatures" rel="noreferrer" target="_blank">https://www.prestashop.com/?utm_source=signature&utm_medium=e-mail&utm_campaign=emails-signatures</a>><br>
<br>
Antoine Thomas aka ttoine<br>
<br>
Developer Advocate<br>
<br>
t: +33 (0)6 63 13 79 06<br>
<br>
<a href="mailto:antoine.thomas@prestashop.com" target="_blank">antoine.thomas@prestashop.com</a><br>
<br>
<br>
<br>
<br>
On Fri, 8 Nov 2019 at 16:36, Lawrence Rosen <<a href="mailto:lrosen@rosenlaw.com" target="_blank">lrosen@rosenlaw.com</a>> wrote:<br>
<br>
> Dear Antoine,<br>
><br>
><br>
><br>
> I saw your posting on license-discuss@ and read your email below. You are<br>
> perfectly right: There is no problem aggregating Apache and OSL code. Both<br>
> licenses allow it. I stand completely by my earlier blog posting on this<br>
> topic.<br>
><br>
><br>
><br>
> I remain surprised that there was any reluctance even for non-lawyers to<br>
> confirm that on license-discuss@. Both licenses are perfectly clear that<br>
> only *derivative works* of OSL must be released under the OSL, and ASL<br>
> doesn't care at all.<br>
><br>
><br>
><br>
> Best regards, Larry<br>
><br>
><br>
><br>
> Lawrence Rosen<br>
><br>
> Rosenlaw (<a href="http://www.rosenlaw.com" rel="noreferrer" target="_blank">www.rosenlaw.com</a>)<br>
><br>
> LinkedIn: LawrenceRosen<br>
><br>
> 3001 King Ranch Rd., Ukiah, CA 95482<br>
><br>
> Cell: 707-478-8932<br>
><br>
> This email is licensed under CC-BY-4.0<br>
> <<a href="https://creativecommons.org/licenses/by/4.0/" rel="noreferrer" target="_blank">https://creativecommons.org/licenses/by/4.0/</a>>. Please copy freely. [image:<br>
> <a href="https://licensebuttons.net/l/by/4.0/88x31.png" rel="noreferrer" target="_blank">https://licensebuttons.net/l/by/4.0/88x31.png</a>]<br>
><br>
><br>
><br>
> *From:* Antoine Thomas <<a href="mailto:antoine.thomas@prestashop.com" target="_blank">antoine.thomas@prestashop.com</a>><br>
> *Sent:* Friday, November 8, 2019 4:28 AM<br>
> *To:* <a href="mailto:lrosen@rosenlaw.com" target="_blank">lrosen@rosenlaw.com</a><br>
> *Subject:* OSL, Apache and PrestaShop<br>
><br>
><br>
><br>
> Dear Lawrence,<br>
><br>
><br>
><br>
> I am contacting you for in the past, you have answered an interview about<br>
> the OSL and the AFL published on PrestaShop blog (<br>
> <a href="https://www.prestashop.com/en/blog/interview-lawrence-rosen-author-open-software-licence" rel="noreferrer" target="_blank">https://www.prestashop.com/en/blog/interview-lawrence-rosen-author-open-software-licence</a><br>
> )<br>
><br>
><br>
><br>
> In this interview, you state that, I quote, "The OSL/AFL licenses intend<br>
> to eliminate such confusion. These licenses do not affect independently<br>
> written code at all, no matter how aggregated." And, at PrestaShop, we<br>
> would need to have a few precisions.<br>
><br>
><br>
><br>
> To give you a bit of context, I am currently working for the PrestaShop<br>
> company, and I do my best to study and improve the maturity of the<br>
> PrestaShop project, with the support of our legal team, the developers, and<br>
> other teams. One of the big taks is the legal compliance: this topic is<br>
> more and more important today, because more and more companies want to use<br>
> open source software, but they don't want to take risks for their business.<br>
> So, after a review of the license all the dependencies and sub-dependencies<br>
> of the project, we found that most are distributed with MIT or BSD.<br>
><br>
><br>
><br>
> However, there are a few libraries distributed with the Apache v2 license,<br>
> and, currently, we are not sure if this is ok to ship them in the<br>
> PrestaShop installer. We know that Magento, who uses OSL too, are shipping<br>
> Apache v2 libraries, like some from Elastic. So, it might be good. But, our<br>
> legal team can't find a clear confirmation that this is possible, and that<br>
> it does not represent a compliance failure.<br>
><br>
><br>
><br>
> When I read your interview, and other documents about OSL, my feeling is<br>
> that the OSL allows to distribute the code with any aggregated software<br>
> (e.g dependencies), and does not require to change their license. And that,<br>
> of course, only derivative work of the code in OSL must be in OSL. But, I<br>
> am not a lawyer, and our legal team is looking for a clear statement.<br>
><br>
><br>
><br>
> That is why, recently, I sent a question about this problem to the OSI<br>
> mailing list, where the answer was, to make it short: "ask a lawyer". Then,<br>
> I thought that you were certainly the best person to confirm what is the<br>
> right way to aggregate libraries in an OSL project, and what are the<br>
> compatible licenses. And so, in a way, that would also clarify what you<br>
> told in this old interview.<br>
><br>
><br>
><br>
> So, if you could provide some clarification in an answer, or links to<br>
> already existing resources, that would be a great help for the PrestaShop<br>
> project and its users.<br>
><br>
><br>
><br>
> Of course, if you need more details or information, please let know. I<br>
> will be available.<br>
><br>
><br>
><br>
> Looking forward to hearing from you,<br>
><br>
><br>
><br>
> Antoine<br>
><br>
><br>
><br>
> [image: PrestaShop]<br>
> <<a href="https://www.prestashop.com/?utm_source=signature&utm_medium=e-mail&utm_campaign=emails-signatures" rel="noreferrer" target="_blank">https://www.prestashop.com/?utm_source=signature&utm_medium=e-mail&utm_campaign=emails-signatures</a>><br>
><br>
> *Antoine Thomas aka ttoine*<br>
><br>
> Developer Advocate<br>
><br>
> t: +33 (0)6 63 13 79 06<br>
><br>
> <a href="mailto:antoine.thomas@prestashop.com" target="_blank">antoine.thomas@prestashop.com</a><br>
><br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/attachments/20191108/72c9186d/attachment.html" rel="noreferrer" target="_blank">http://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/attachments/20191108/72c9186d/attachment.html</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: image001.png<br>
Type: image/png<br>
Size: 1393 bytes<br>
Desc: not available<br>
URL: <<a href="http://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/attachments/20191108/72c9186d/attachment.png" rel="noreferrer" target="_blank">http://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/attachments/20191108/72c9186d/attachment.png</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
License-discuss mailing list<br>
<a href="mailto:License-discuss@lists.opensource.org" target="_blank">License-discuss@lists.opensource.org</a><br>
<a href="http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org" rel="noreferrer" target="_blank">http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org</a><br>
<br>
<br>
------------------------------<br>
<br>
End of License-discuss Digest, Vol 92, Issue 3<br>
**********************************************<br>
</blockquote></div>