kevingurney commented on PR #38660:
URL: https://github.com/apache/arrow/pull/38660#issuecomment-2007665315

   Hi Kou,
   
   > If "I" not the Apache Software Foundation creates a MLTBX file, the MLTBX 
file includes proprietary object code and it's "not" licensed under the 
Apache-2.0. Right? (I'm not sure whether this is a problem or not.)
   
   If we are understanding your question correctly, there are two points we 
think are worth noting:
   
   1. If "I" (not the Apache Software Foundation and not on behalf of the 
Apache Software Foundation) receieve/download the MLTBX file that the Apache 
Software Foundation is planning to distribute via the official ASF release 
channels (i.e. the MLTBX file for the MATLAB bindings), then the terms of the 
Apache V2 / 3-Clause BSD licenses apply (i.e. "I" can use/modify/redistribute 
any of the contents of the MLTBX file under the terms of the Apache V2 / 
3-Clause BSD licenses).
   
   2. If "I" (not the Apache Software Foundation and not on behalf of the 
Apache Software Foundation):
   2.1 create a *separate* MLTBX file or
   2.2 receive/download a MLTBX file that does originate from the Apache 
Software Foundation's official release channels and
   2.3 the MLTBX file bundles MathWorks proprietary bits
   2.4 then those proprietary bits would still be under a MathWorks proprietary 
license.
   
   **In Summary**: Generally speaking, MathWorks proprietary bits inside of a 
MLTBX file are under a MathWorks proprietary license. However, MathWorks is 
granting the Apache Software Foundation the right to distribute the proprietary 
bits (e.g. the object code required by `mathworks/libmexclass`) inside of the 
MLTBX file for the Arrow bindings via its official release channels under the 
Apache V2 license.
   
   We hope that clarifies things! Thanks!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to