Done.
https://issues.apache.org/jira/browse/LEGAL-244
Anthony
> On Apr 6, 2016, at 8:57 AM, Marvin Humphrey wrote:
>
> Hi,
>
> I agree with Justin and Bertrand's analysis, but I would also request
> that you open a LEGAL Jira requesting that the MX4J license be added
Hi,
I agree with Justin and Bertrand's analysis, but I would also request
that you open a LEGAL Jira requesting that the MX4J license be added
to the list of approved licenses.
MX4J is not only similar to Apache 1.1, but also to the PHP license.
http://www.apache.org/legal/resolved#category-a
Thanks for the help!
Anthony
> On Apr 6, 2016, at 4:50 AM, Justin Mclean wrote:
>
> Hi,
>
> INAL but this is what I would do:
> - Add a pointer (i.e. path to the file) and the copyright owner to the full
> text of the license in LICENSE
> - Add the notice “This product
Hi,
INAL but this is what I would do:
- Add a pointer (i.e. path to the file) and the copyright owner to the full
text of the license in LICENSE
- Add the notice “This product includes software developed by the MX4J project
..” mentioned in the MX4J license to the NOTICE file
(i.e. exactly
Hi,
On Wed, Apr 6, 2016 at 4:28 AM, Anthony Baker wrote:
>...The file in question has a license [4]
> that is similar but different to ASF v1.1 [5]
IANAL but my reading of [4] is that the only requirement beyond a
typical MIT-style license is including the "This product
I'm working on clearing an issue [1] found during the review for Geode
1.0.0-incubating.M1 [2] (thanks Justin!). We have a bundled source
dependency on an MX4J file [3]. The file in question has a license [4]
that is similar but different to ASF v1.1 [5].
How should we deal with this license?