incubator-ctakes-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mattmann, Chris A (388J)" <>
Subject Re: licensing question
Date Wed, 01 Aug 2012 17:51:22 GMT
Hey Tim,

In general, the ASF doesn't like to present "surprises" to users downstream. The use of a
parser that is better, and
that users will want to download to provide better accuracy, but that isn't by default included,
is one such example to
me of a surprise that we don't want to have wired into the product.

There is discussion going on right now on the Apache list related
to CloudStack right
now where they are talking about this.

My 2c from a mentor's perspective: stay away from LGPL and try as much as possible to stay
with Category A 
ASF compatible licenses from the legal resolved page. If there is something better that's
LGPL, either rewrite it
here (if possible), or convince the authors of that library to relicense their product (has
worked sometimes in the
past), or think of another creative solution that doesn't involve LGPL :)


On Aug 1, 2012, at 4:01 AM, Miller, Timothy wrote:

> Hi all,
> There was some chatter last week about resources potentially being downloaded via maven
for license compatibility reasons.  Just wondering if that brings about the possibility of
using external libraries that are not apache-licensed that would also be auto-downloaded under
certain maven build commands.  Specifically I was thinking of the GPL-licensed berkeley parser
which I've used to get significantly higher accuracy than the opennlp parser we currently
wrap in our constituency parser module.
> Thanks
> Tim Miller

Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA

View raw message