search

hobama / dkpro-wsd

Automatically exported from code.google.com/p/dkpro-wsd
0 stars 0 forks source link

Licence review and documentation #4

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Licences for all project dependencies (including both code and data) need to be 
reviewed.  Code which includes or links to copylefted dependencies may need to 
be split out into a separate project.  All third-party code and data remaining 
in the project needs to be documented in a README which lists the contributors 
and licences.

Original issue reported on code.google.com by tristan.miller@nothingisreal.com on 11 Jul 2013 at 10:38

GoogleCodeExporter commented 9 years ago

Original comment by tristan.miller@nothingisreal.com on 11 Jul 2013 at 10:56

GoogleCodeExporter commented 9 years ago

Original comment by tristan.miller@nothingisreal.com on 11 Jul 2013 at 10:59

GoogleCodeExporter commented 9 years ago 
All licences for libraries we directly depend upon have been reviewed.  Results:

Guava: Apache
Jung: BSD
Log4j: Apache
DKPro Core: Apache
DKPro Lab: Apache
JWPL: LGPL
DKPro Similarity: Apache
Jaxen: Permissive 
http://svn.jaxen.codehaus.org/browse/jaxen/trunk/jaxen/LICENSE.txt?r=1128
Dom4J: Permissive BSD-style 
http://dom4j.sourceforge.net/dom4j-1.6.1/license.html
Apache Commons: Apache
UBY-LMF: ASL
extJWNL: BSD-style http://extjwnl.sourceforge.net/license.txt
JDOM: Permissive apache-style

TreeTagger: proprietary
stanfordnlp: GPL
TWSI: GPL

We need to remove the dependencies on the last three libraries, or else split 
DKPro WSD into separate products based on the licence.  See Issue 18 and Issue 
12.  The rest of the libraries have Apache-compatible licences.

With respect to source code and data, I checked over all the third-party 
material I committed.  (I found one case where the license was incompatible, 
and then removed or rewrote the code.)  Nico and Daniel, could you do the same 
for any code and data you've committed?

Original comment by tristan.miller@nothingisreal.com on 12 Jul 2013 at 3:58

GoogleCodeExporter commented 9 years ago

Original comment by tristan.miller@nothingisreal.com on 12 Jul 2013 at 4:00

GoogleCodeExporter commented 9 years ago

Original comment by tristan.miller@nothingisreal.com on 12 Jul 2013 at 4:04

GoogleCodeExporter commented 9 years ago

Original comment by tristan.miller@nothingisreal.com on 12 Jul 2013 at 4:10

GoogleCodeExporter commented 9 years ago

Original comment by tristan.miller@nothingisreal.com on 12 Jul 2013 at 4:17

GoogleCodeExporter commented 9 years ago 
I added the IMS and TWSI disambiguation methods. Both are GPL.

Original comment by daniel.b...@sap.com on 15 Jul 2013 at 8:41

GoogleCodeExporter commented 9 years ago 
Further libraries used in DKPro WSD GPL:

IMS: GPL
WEKA: GPL
LibSVM: Permissive BSD-style http://www.csie.ntu.edu.tw/~cjlin/libsvm/COPYRIGHT
OpenNLP: Apache
JWNL: Permissive BSD-style
Liblinear: Permissive BSD-style 
http://www.csie.ntu.edu.tw/~cjlin/liblinear/COPYRIGHT

As per the Maven Standard Directory Layout 
https://maven.apache.org/guides/introduction/introduction-to-the-standard-direct
ory-layout.html every Maven module in our project should have a LICENSE.txt 
explaining the project license, and possibly a README.txt file with further 
information.

Original comment by tristan.miller@nothingisreal.com on 18 Jul 2013 at 12:57

GoogleCodeExporter commented 9 years ago 
Added the Apache Rat plugin to the POM; added licence headers to all Java 
source files; added a copy of the GPL to all GPL-licensed modules.

Original comment by tristan.miller@nothingisreal.com on 19 Jul 2013 at 1:05

GoogleCodeExporter commented 9 years ago 
The Maven artifacts we distribute don't include third-party libraries, so as I 
understand it we have no obligation to reproduce their licences or credits.  I 
believe we are now in compliance with all licences, and have conspicuously 
marked the conditions of our own licences.

Original comment by tristan.miller@nothingisreal.com on 24 Jul 2013 at 9:00