GEOS Incubation Status

General

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

Yes, approved on November 2, 2007

Has an Incubation Mentor been assigned to the project?

Yes, Frank Warmerdam

Infrastructure Transition

Has the projectname.osgeo.org domain been populated with the projects web presence?

The web presence is currently being started here: http://trac.osgeo.org/geos/

Is the OSGeo bug tracker being used for the project?

Yes: http://trac.osgeo.org/geos/

Is the OSGeo mailing list manager (http://lists.osgeo.org/) being used for the project?

Yes: http://lists.osgeo.org/mailman/listinfo/geos-devel

Is the OSGeo SVN being used for the project?

Yes: http://svn.osgeo.org/geos/

Are binary and source downloads available from http://download.osgeo.org ?

If not, why?

Community Functioning

Is there a functioning user support mechanisms (ie. mailing list)?

Yes, http://lists.osgeo.org/mailman/listinfo/geos-devel

Are source and binary downloads for the package available?

Source downloads are available, binaries are not. The SVN repository at http://svn.osgeo.org/geos is publicly readable as well.

Has a Project Steering Committee been formed, and given control of the project?

Yes, see http://trac.osgeo.org/geos/wiki/PSC

Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines, etc.

Yes, see http://trac.osgeo.org/geos/wiki/RFC1 and http://trac.osgeo.org/geos/wiki/RFC2

How many active developers are there? Are they from multiple organizations?

There 2-3 active developers, depending on how you count, from multiple organizations.

Foundation Membership

Have project documents been updated to reflect membership in the foundation, and the relationship of the project to the foundation?

If not, indicate when this will occur.

Has an effort been made to brand the project web site with OSGeo foundation web styling and branding marks?

If not, indicate what is planned. (note: currently an OSGeo web style has not bee established)

Code Copyright Review

Has a Code Provenance Review document been prepared for the project?

yes/no - point to review document.

Have issues raised in the provenance review been adequately addressed?

indicate outstanding issues.

Are Commiter Responsibilities Guidelines covering legal issues in place?

yes/no - point to the guidelines and indicate if it is adopted by PSC, and accepted by all commiters.