Hi Ian, Thank you for sharing your input on this.
> This appears to be a custom-written license. Is that correct? Yes, that is correct. This is a custom written license. > If not, can you provide some explanation of why this license should be > considered to meet the criteria for Category B? We want to make sure we provide a thorough response to this question. So, we would like to first consult with a few colleagues at MathWorks. Our sincere apologies for the delay. We hope to get back to the community quickly on this. Best, Sarah and Kevin ________________________________ From: Ian Cook <ianmc...@apache.org> Sent: Thursday, January 18, 2024 3:22 PM To: sgilm...@mathworks.com.invalid <sgilm...@mathworks.com.invalid> Cc: dev <dev@arrow.apache.org>; Kevin Gurney <kgur...@mathworks.com> Subject: Re: [DISCUSS][MATLAB] Proposed "Category B" License for Bundling MATLAB MEX Build Artifacts in Official Arrow Release Hi Sarah, Thanks for pursuing this. The ASF 3rd Party License Policy lists a number of standard, off-the-shelf licenses that are compatible with Category B, but the policy does not include any provision for custom-written licenses. This appears to be a custom-written license. Is that correct? Is this custom-written license based on one of the listed Category B licenses? If so, can you tell us which one? If not, can you provide some explanation of why this license should be considered to meet the criteria for Category B? Thank you, Ian On Wed, Jan 17, 2024 at 12:08 PM Sarah Gilmore <sgilm...@mathworks.com.invalid> wrote: > > Hi Everyone, > > Kevin Gurney and I have been working on integrating the MATLAB Arrow bindings > with the project's release processes in this pull request [1]. While working > on integrating with the release tooling, we realized that we need to ensure > that the licenses of any MEX artifacts [2] bundled with the released MLTBX > [3] file are compatible with the ASF 3rd Party License Policy [4]. > > After several rounds of discussion with some colleagues at MathWorks, we came > up with a license [5] that is intended to meet the requirements for inclusion > as a "Category B" [6] license according to the ASF 3rd Party License Policy. > > Our goal is to make sure we are doing the right thing here, so, as per Kou's > suggestion [7], we wanted to share the proposed license [5] with the broader > Arrow development community. We understand this may need further input from > ASF Legal as well. > > Please let us know what we can do to help move this forward. We sincerely > appreciate everyone's support as we navigate these licensing requirements. > > [1] > https://github.com/apache/arrow/pull/38660<https://github.com/apache/arrow/pull/38660> > [2] https://www.mathworks.com/help/matlab/call-mex-functions.html > [3] https://www.mathworks.com/help/matlab/creating-help.html?s_tid=CRUX_lftnav > [4] > https://www.apache.org/legal/resolved.html<https://www.apache.org/legal/resolved.html> > [5] > https://github.com/apache/arrow/files/13955180/license.txt<https://github.com/apache/arrow/files/13955180/license.txt> > [6] > https://www.apache.org/legal/resolved.html#category-b<https://www.apache.org/legal/resolved.html#category-b> > [7] > https://github.com/apache/arrow/pull/38660#discussion_r1454804607<https://github.com/apache/arrow/pull/38660#discussion_r1454804607> > > Best, > > Sarah Gilmore >
