This page gathers up the provenance review performed from 2006-2008 on the geotools library.
|Table of Contents|
This work was undertaken as an OSGeo incubation requirement.
- We removed ArcSDE and Oracle support from the library due to difficulties distribution the jars on which this functionality depended. In addition we shut off prior downloads of the library that contained this work. This functionality was restored after "stub jars" were created by hand (these jars are non functional; operating similar to a C header file allowing code to be compiled but not executed).
- Frank has helped address the concern of EPSG derrived data products, and we have had discussion on the integration of public domain code with our LGPL license requirements.
- All headers in the library were assigned to the "GeoTools PMC" - an entity with no legal existence. We arranged to transfer copyright to the OSGeo foundation.
- Remaining issues can be found in our issue tracker under GeoTools License Issues. The majority of these known issues concern checking where test case data originated from.
- http://jira.codehaus.org/browse/GEOT-1896 Credit each license in the user guide
The review process has being integrated into the community development practice, as a step in making modules supported. A review.apt file (in Apache's Almost Plain Text format) now is provided for each module and is considered part of the source code. Initial review was completed by Jody Garnett August 7th, 2006. Adrian Custer has lead the a second review in July, 2008.
For each module you can locate a report - for example:
Modules are considered CLEAN if the origin of all files was confirmed as our own work or appropriated under a suitable license so there were no outstanding issues blocking distribution under the LGPL. All source code files were examined for their headers and mixed headers or conflicts in copyright were flagged. All data files or other files (such as icon images) were assessed to establish our right to redistribute them if they were not our own files. These reports include links to Jira issues raised during the review.
All issues should have been filed under the license admin component .
The following issues have been identified and are recorded in our issue tracker:
The following actions have been taken in response to issues raised during the incubation process.