Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

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.

Status

You can find status, including IP status, from this page here:

A couple of modules have already encountered issues, mostly those working with propitiatory systems such as ArcSDE or Oracle where our ability to distribute jars and drivers is in question.

Actions Taken

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

TODO:

  • Include listing of licenses covered by the code base
  • Change release guide to include packaging of the developers guide

Users Guide

The users guide is currently under construction we have outstanding questions about documentation licenses and are waiting for feedback from the iccubation committee.

TODO:

  • Change release guide to include packaging of the users guide

Source Code

The review process is being integrated into the development community, that is taken right into the source code where it can be tracked and versionde along with the code.

The following files were created by Jody Garnett as part of the initial review process which completed on August 7th, 2006. These files are maintained, by the module maintainer associated with the section of code described.
Library

These modules make up the GeoTools library itself, and form a layered architecture covering a range of geospatial activities.

Plug-in

These plug-ins slot into the GeoTools library making additional capabilities and data formats avaiable.

Extentions

These modules are built on top of the geotools library and add additional analysis and functionality around the abstractions captured by the core library.

Demo

These files are used as teaching aids. We are considering releasing them as public domain to aliviate any initial adotpion concerns. They are all available under a public domain license.

Unsupported

These extensions and plug-ins work with the GeoTools library, but do not yet meet their QA and Providence Review checks. While this is mostly to prevent duplication of development effort, the unsupported modules that have completed a providence review can be distributed for feedback.

Spike

These files are not covered by the provenance review as they are experiments, and thus not distributed.
Maven

We have some custom maven plugins to keep our build happy.

  • No labels