-1 (binding)
The incorporation of bad licensing has the potential to limit where Rya can be
deployed. I would like to see following addressed:
https://issues.apache.org/jira/browse/RYA-372 Replace org.json:json library
with a compatibly licensed alternative
I vote to make benchmarks optional.
Sent from my iPhone
> On Sep 14, 2017, at 3:03 PM, Josh Elser wrote:
>
> By the letter of the law, you don't have to resolve license conflicts until
> you graduate from the Incubator.
>
> However, the process of identifying bad
​Here is my completed analysis of our third party licenses.
Result: We have two Licenses not allowed for Apache projects. See the
bottom.
The question is, is this a blocker for the release? Can we make a Jira
task to fix for the next version? One of them: JSON, just switched to
category X