ZOO-Project Incubation Status

= Document Status =

IncCom Document Number: X

Version: 0.1

Status: draft

= Purpose =

The project representative and mentor will use this template to inform the IncCom of the project status on a periodic basis. The state of the project, as reported using this template, will be the initial indication that a project is reaching graduation.

= Terms and Definitions =

= Template =

General

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


 * Has an Incubation Mentor been assigned to the project?
 * Frank Warmerdam

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?
 * no, but we can set up a stub page pointing to the project site on short terms


 * If not why, and has the project page got a prominent link to the real home?
 * there is an established web presence (ZOO-Project website) actively maintained by project members


 * Is the OSGeo bug tracker being used for the project?
 * If not, why?
 * We do not use the OSGeo bug tracker cause we already got one in place based on the same Trac technology and available at : http://zoo-project.org/trac . Note that some specific modules are required to get the web site functionning.


 * Is the OSGeo mailing list manager (http://lists.osgeo.org/) being used for the project?
 * If not, why?
 * Yes we migrated the zoo-discuss and zoo-psc mailing lists from Osaka City University (OCU) server to OSGeo one.


 * Is the OSGeo SVN being used for the project?
 * If not, why?
 * We do not use the OSGeo SVN because we already got one in place using the same technology and gracefully hosted at OCU.


 * Are binary and source downloads available from http://download.osgeo.org ?
 * no, but filed a ticket to add ZOO-Project as an external link on the OSGeo download page.


 * If not, why?

Community Functioning

 * Is there a functioning user support mechanisms (ie. mailing list)?
 * indicate the available user support mechanisms, and whether they seem to be functioning well (are getting used and get answers).
 * ticket system, mailing lists (zoo-discuss, zoo-psc)


 * Are source and binary downloads for the package available?
 * Yes the source code is available for the package. By now, one package is provided but it is possible that, in future, the source code may be splited in smalled packages (ZOO-Kernel, ZOO-Services and ZOO-API). There is no plan for binary distribution except for the WIN32 platform.


 * Has a Project Steering Committee been formed, and given control of the project?
 * Yes a Project Steering Committee has been formed and have effective control on the project.


 * Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines, etc.
 * There is a contributor guidelines here and for PSC decisions there is the Project Steering Committee Guidelines here.


 * How many active developers are there? Are they from multiple organizations?
 * contributions come from GeoLabs SARL, Fundazione Edmund Mach, 3LIZ SARL, Cartogenic SARL and further more.

Foundation Membership

 * Have project documents been updated to reflect membership in the foundation, and the relationship of the project to the foundation?
 * Mention to current incubation status can be done in short terms, the "OSGeo Project In Incubation" logo was added to the web site.


 * Has an effort been made to brand the project web site with OSGeo foundation web styling and branding marks?
 * There was always a link with OSGeo (including branding such as logos) as the ZOO-Project's initial goal was to become a "standardized bus" on top of OSGeo softwares so reference to OSGeo was there from the begining. note that the OSGeo Project in Incubation was added when we was accepted by the board to enter in incubation process. Nevertheless, there was no adaptation by applying a non-existing style (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, the Code Provenance Review is here.


 * Have issues raised in the provenance review been adequately addressed?
 * Some issue about the mixture between BSD and MIT-X11 was found long time ago in ZOO-API and addressed.


 * Are Commiter Responsibilities Guidelines covering legal issues in place?
 * Yes, we used the GDAL Project RFC 3 as a base document to create our own, which is available here. On the way for adoption and agreement ..