GeoTools Project Status

Basics

 * Has the project been approved for incubation by the OSGeo board?
 * Yes


 * Has an Incubation committee member been assigned as Mentor?
 * Yes, Frank Warmerdam was the assigned mentor, later replaced by  Cameron Shorter.

Infrastructure Transition
Note, for each of the following it isn't necessary to move to foundation infrastructure, but if you aren't a reason should be provided.


 * Has the projectname.osgeo.org domain been populated with the projects web presence?
 * We are not willing to move away from Confluence, how may I update this page with a good link?
 * However, a web server may be of interest for hosting static HTML pages automatically generated like Maven reports and Javadoc.


 * Is the OSGeo bug tracker being used for the project?
 * No it is not, once again we have an existing bug tracker Jira which allows for collaboration with several other projects


 * Is the OSGeo mailing list manager being used for the project?
 * Existing mailing list and archives are hosted by SF, any chance we grab archives?


 * Is the OSGeo SVN or CVS system being used for the project?
 * Not at this time, moving to SVN would be of interest.


 * Are binary and source downloads available from the OSGeo download area?
 * Not yet, but this also would be of interest.

Community Functioning

 * Is there a functioning user support mechanisms (ie. mailing list)?
 * There is a active developers list and user list (http://docs.codehaus.org/display/GEOTOOLS/Mailing+Lists) weekly IRC chats (http://docs.codehaus.org/display/GEOT/3.1+Internet+Relay+Chat)


 * Are source and binary downloads for the package available?
 * Yes and we also have a javadoc (ie api) download see http://docs.codehaus.org/display/GEOTOOLS/Downloads


 * Has a Project Steering Committee been formed, and given control of the project?
 * Project has an exisiting Project Management Comittee see http://docs.codehaus.org/display/GEOT/4+Roles+and+Responsibilities


 * Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines, etc.
 * The project is well document here http://docs.codehaus.org/display/GEOT/Home


 * How many active developers are there? Are they from multiple organizations?
 * There are around 10 developers working on geotools as part of their day job, the expanded list goes up to around 30 with commit access. The important part is the number of responsible module maintainers. While the project is made up of individuals (who happen to work for organizations such as Penn State University, Refractions Reserach, The Open Planning Project, IBM, Oracle, Google others...)

Foundation Membership

 * Have project documents been updated to reflect membership in the foundation, and the relationship of the project to the foundation?
 * The home page has, but the formal developers guide will be updated as part of the incubation process (especially with respect to any changes in project procedures).


 * Has an effort been made to brand the project web site with OSGeo foundation web styling and branding marks?
 * We will have the same look and feel but are concerned with some of the limitations

Code Copyright Review

 * Has a Code Provenance Review document been prepared for the project?
 * Jody Garnett has gone through each module and produced a review.txt file listing issues for the Module Maintainers to consider. The GeoTools Provenance Review page contains links to this information.


 * Have issues raised in the provenance review been adequately addressed?
 * The most serious issues have been addressed: we have removed ArcSDE support from the build pending the creation of stub jars, Frank has helped address the concern of EPSG derrived data products, and we have had discussion on the intergration of public domain code with our LGPL license requirements.
 * We have two remaining issues of note, use of WKB in PostGIS, and the creation of the sub jar so we can resume ArcSDE support.