Details
-
Task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
Before we make a release we must make sure all our code is either
a) Original works of IKS contributors that was donated to stanbol via the STANBOL-2 code grant.
b) Original works of Apache committers and contributors
c) Forked code for which we have an explicit license that allows the fork (but why fork it in stanbol? should be discussed)
We also need to check that all our dependencies (as reported by mvn dependency:tree and/or mvn site) are compatible with http://apache.org/legal/resolved.html
Attachments
Issue Links
- blocks
-
STANBOL-270 Release Stanbol 0.9
- Closed
- depends upon
-
STANBOL-20 Use commons-codec for Base64 functionality
- Closed
-
STANBOL-21 DOMUtils class has nuclear clause license
- Closed
-
STANBOL-22 Code copied from geonames, why?
- Closed
-
STANBOL-24 Remove LGPL OWL API dependency
- Closed
-
STANBOL-4 Check stanbol code for "restricted cryptography"
- Closed
- is blocked by
-
STANBOL-39 Rename the KReS java package
- Closed
-
STANBOL-40 Rename the fise java package
- Closed
- requires
-
STANBOL-38 Rename the rick java package
- Closed