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

   Hi Kou,
   
   Your understanding and assumptions seem mostly correct to us.
   
   However, we would like to provide a few notes for clarification.
   
   [`mathworks/libmexclass`](https://github.com/mathworks/libmexclass) is 
licensed under the 3-Clause BSD license. This implies that the 
`mathworks/libmexclass` source code and any binary object code that is derived 
directly from this source code can be freely redistributed under the terms of 
the 3-Clause BSD license.
   
   However, when building MATLAB programs that use `mathworks/libmexclass`, 
there is some proprietary MathWorks object code that is linked against / 
compiled into the resulting binaries in order to integrate with the MATLAB MEX 
functionality. MathWorks is explicitly granting the Apache Software Foundation 
the right to distribute any of the MathWorks proprietary object code which is 
required by `mathworks/libmexclass` *and* bundled in the distributed MLTBX 
files under the Apache V2 license. In addition, MathWorks is explicitly 
granting the Apache Software Foundation the right to distribute any of the 
files generated by the MLTBX packaging infrastructure (e.g. files under the 
`metadata/`, `_rels/`, and `_xmlsignatures/` directories), which are included 
in the resulting MLTBX files, under the Apache V2 license.
   
   **To summarize**: our understanding is that *ALL* contents of the 
distributed MLTBX files would be licensed under either, 3-Clause BSD, or Apache 
V2, which should make the MLTBX contents compatible with the ASF 3rd Party 
License Policy.
   
   We hope this clarifies things. Please let us know if you have any other 
questions.
   
   Thank you,
   
   Sarah and Kevin


-- 
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