Message-ID: <337937558.26187.1394302808515.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_26186_1071525900.1394302808515" ------=_Part_26186_1071525900.1394302808515 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This page gathers up the provenance review performed from 2006-2= 008 on the geotools library.
This work was undertaken as an OSGeo incubation requirement.
The review process has being int= egrated into the community development practice, as a step in making module= s supported. A review.apt file (in Apache's Almost Plain Text format) now i= s provided for each module and is considered part of the source code. Initi= al 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 out= standing issues blocking distribution under the LGPL. All source code files= were examined for their headers and mixed headers or conflicts in copyrigh= t were flagged. All data files or other files (such as icon images) were as= sessed 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= .
The following issues apply to all modules:
See further below for the status of the various JIRA tasks which have be= en filed. Several of them have already been closed.
These modules are built on top of the geotools library and add additiona= l analysis and functionality around the abstractions captured by the core l= ibrary.
These files are used as teaching aids. We are considering releasing them= as public domain to aliviate any initial adotpion concerns. They are all a= vailable under a public domain license.
These extensions and plug-ins work with the GeoTools library, but do not= yet meet their QA and Provenance Review checks. While this is mostly to pr= event duplication of development effort, the unsupported modules that have = completed a provenance review can be distributed for feedback.
These are internal to the library and not distributed.
Experiments and Summer of Code projects sometimes take place in an exper= imental spike directory.
We are not intersted in distributing this code; but we have found a coup= le issues anyways:
The main issue tracking the rest is: JIRA GEOT-1873 = , these are all shown below.
All issues should have been filed under the admin component <= /a>.
The following actions have been taken in response to issues raised durin= g the incubation process.
After a public email on the GeoServer list, we have chosen to turn off h= istorical downloads of the geotools platform, and produced a new download t= hat does not contain ArcSDE support.
We may choose to turn historical downloads on again, or issue a patch fo= r each stable branch, depending on community needs and involvement.
Frank was kind enough to contact the providers of the EPSG dataset and i= nform them of our difficulties in delivering the content verbatium for data= bases such as HSQL.
Some code has been donated to the the project under a range of condition= s, we have chosen to include the appropriate information in a series of LIC= ENSE.TXT files included with each binary.
We will review these files to discuss any specific needs that must be ad= dressed in client application code, or included documentation: