The format of this document is provided by the incubation committee, we are hosting it on our wiki with the rest of our incubation materials.

{toc}

IncCom Document Number: X (no idea what this is for)

Version: 1.1 (this is the template we are working from)

Status: draft

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.

IncCom : Short form of Incubation Committee

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

Yes

Has an Incubation Mentor been assigned to the project?

Yes, Landon Blake

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?

A direct link to http://geoserver.org/ is used from the main OSGeo.org home page.

This website has long been associated with the GeoServer project.

Is the OSGeo bug tracker being used for the project?

It is not, we make use of the Jira issue tracker hosted at CodeHaus: http://jira.codehaus.org/browse/GEOS

By hosting at CodeHaus was are easily able to transition issues to/from the GeoTools project.

Is the OSGeo mailing list manager being used for the project?

No, we have a long standing SourceForge email list.

Is the OSGeo SVN being used for the project?

No, the world has moved on to git (specifically github in this case https://github.com/geoserver )

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

We make use of SourceForge download services, in part for their replication to download servers around the world: http://sourceforge.net/projects/geoserver/

Is there a functioning user support mechanisms ?

Both a source forge email list is in active use (and to a lesser extent Stack Exchange). We also note a number of international GeoServer email lists are available.

The issue tracker is also considered an user support mechanism.

indicate the available user support mechanisms, and whether they seem to be functioning well .

They seem to be functioning well, we like the idea of using stack exchange to only an answer a question once.

We are increasingly seeing GeoServer bundled by other projects, which is taking some communication load off our support mechanisms.

Are source and binary downloads for the package available?

Always.

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

Yes. The list of members is included in our documentation on the functioning of the psc .

At the time of writing:

• Alessio Fabiani
• Andrea Aime
• Ben Caradoc-Davies
• Chris Holmes (Chair)
• Christian Mueller
• Gabriel Roldan
• Jody Garnett
• Jukka Rahkonen
• Justin Deoliveira
• Phil Scadden
• Simone Giannecchini

The GeoServer project has participation from a number of organisations, the PSC has effective representation/control for the project.

Our PSC representation is balanced from a wide range of organisations and experience (developer and user). We will continue to approach the user-list for direct involvement at this level of the project.

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

Yes, please see the psc page of our developer documentation.

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

The complete list is on our github members page. We have 22 comitters listed, and more developers making contributions via github pull requests.

At the time of writing:

• Andrea Aime (GeoSolutions)
• Jody Garnett (LISAsoft)
• Simone Giannecchini (GeoSolutions)
• David Winslow (OpenGeo)
• Gabriel Roldan (OpeGeo)
• Ian Schneider (OpenGeo)
• Mike Pumphrey (OpenGeo)
• Martin Davis (OpenGeo)
• Niels Charlier
• Rini Angreani (CSIRO)
• Victor Tey (CSIRO)
• Juan Marin
• Frank Gasdorf
• Daniele Romangnoli (GeoSolutions)
• Justin Deolivera (OpenGeo)
• Ben Caradoc-Davis (CSIRO)
• Mark Leslie (LISAsoft)
• Alessio Fabiani (GeoSolutions)
• Tim Schaub (OpenGeo)
• Davide Savazzi
• Emanuele Tajoriol

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

Yes, logo is included on our home page.

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

We have an existing visual web presence.

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

Yes - please see [GeoServer Provenance Review]

Have issues raised in the provenance review been adequately addressed?

Any issues that prevent the release of the GeoServer project have been addressed. The issue tracker is being used to record progress any and all issues raised during review.

The GeoServer Provenance Review page has links to the individual issues.

At the time of writing there were three interesting issues left, none of which prevent the release of the project:

• The download includes states and tasmania sample data obtained prior to the current generation of developers

  • (/) https://github.com/geoserver/geoserver/blob/master/data/release/README.rst now provides correct attribution

• Documentation is not provided under a Documentation License

  • (/) [GSIP 89 Creative Commons with Attribution] is now completed

Are Commiter Responsibilities Guidelines covering legal issues in place?

Code contribution is covered (in depth) by our developers manual (see comitting ).

We have a code contribution agreement (from the wiki) which is now copied over to the developers guide.