Difference between revisions of "GeoTools Provenance Review"
| Line 8: | Line 8: | ||
=== Actions === | === Actions === | ||
| + | The following actions have been taken in response to issues raised during the iccubation process. | ||
| + | |||
==== Turning Off Downloads ==== | ==== Turning Off Downloads ==== | ||
After a public email on the GeoServer list, we have chosen to turn off historical downloads of the geotools platform, and produced a new download that does not contain ArcSDE support. | After a public email on the GeoServer list, we have chosen to turn off historical downloads of the geotools platform, and produced a new download that does not contain ArcSDE support. | ||
| − | We may choose to turn historical downloads on again, or issue a patch for each stable branch, depending on community needs. | + | We may choose to turn historical downloads on again, or issue a patch for each stable branch, depending on community needs and involvement. |
| + | |||
| + | ==== Contact EPSG Provideers ==== | ||
| + | |||
| + | Frank was kind enough to contact the prociders of the EPSG dataset and inform them of our difficulties in delivering the content verbatium for databases such as HSQL. | ||
| + | |||
| + | ==== Multi License code ==== | ||
| + | |||
| + | Some code has been donated to the the project under a range of conditions, we have chosen to include the appropriate information in a series of LICENSE.TXT files included with each binary. | ||
| + | |||
| + | We will review these files to discuss any specific needs that must be addressed in client application code, or included documentation: | ||
| + | - The Developers Guide will credit each license | ||
| + | - The Developers Guide will be packaged and included with each release | ||
| + | - An About class will be created, and make a vailable a list of licenses, allowing client applications the ability to pop up a Swing Dialog as needed, or make use of their own presentation layer (say J2EE or SWT application. | ||
== Review == | == Review == | ||
Revision as of 03:56, 7 August 2006
Nothing to see here - why? Because the work is being done on a module by module basis, and the results posted to the geotools wiki. We will post results here as they are made available.
You can find status, including IP status, from this page here:
A couple of modules have already encountered issues, mostly those working with propiatary systems such as ArcSDE or Oracle where our ability to distribute jars and drivers is in question.
Actions
The following actions have been taken in response to issues raised during the iccubation process.
Turning Off Downloads
After a public email on the GeoServer list, we have chosen to turn off historical downloads of the geotools platform, and produced a new download that does not contain ArcSDE support.
We may choose to turn historical downloads on again, or issue a patch for each stable branch, depending on community needs and involvement.
Contact EPSG Provideers
Frank was kind enough to contact the prociders of the EPSG dataset and inform them of our difficulties in delivering the content verbatium for databases such as HSQL.
Multi License code
Some code has been donated to the the project under a range of conditions, we have chosen to include the appropriate information in a series of LICENSE.TXT files included with each binary.
We will review these files to discuss any specific needs that must be addressed in client application code, or included documentation: - The Developers Guide will credit each license - The Developers Guide will be packaged and included with each release - An About class will be created, and make a vailable a list of licenses, allowing client applications the ability to pop up a Swing Dialog as needed, or make use of their own presentation layer (say J2EE or SWT application.
Review
Developers Guide
Updated project header with the following changes:
- 2002-2005 changed to 2002-2006
- Geotools2 changed to GeoTools
Link to Developers Guide page modifed: [Coding Conventions]
Module API
org.geotools.catalog
Provides a catalog capable of managing resources and their associated connections.
- All files required their header to be updated.
org.geotools.data
Data access api providing a common interface to several file formats and data sources.
- All files required their header updated