MapFish Incubation Status

= Document Status =

IncCom Document Number: X

Version: 1.2

Status: final 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.

= Template =

General

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


 * Has an Incubation Mentor been assigned to the project?
 * Gary Sherman has been assigned as mentor.

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?
 * If not why, and has the project page got a prominent link to the real home?

We do not use the "mapfish.osgeo.org" domain, but we have http://www.osgeo.org/mapfish. The main website for MapFish is http://mapfish.org, which is clearly referenced from http://www.osgeo.org/mapfish.


 * Is the OSGeo bug tracker being used for the project?
 * If not, why?

No, we do not use the OSGeo bug tracker. We have trac.mapfish.org, which is known and used. Also, we're planning to use Github, to benefit from the power and flexibility of Git and Github. We will use Github primarily for the hosting of the MapFish code, but we're considering using its bug/issue tracker as well.


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

No. Currently we have a running infrastructure in place with people already registered, but we could migrate to OSGeo if necessary.


 * Is the OSGeo SVN being used for the project?
 * If not, why?

No. As mentioned above, we're seriously considering moving the MapFish code to Github.


 * Are binary and source downloads available from http://download.osgeo.org ?
 * If not, why?

MapFish isn't distributed as a binary. MapFish is a collection of Python packages, which are distributed through dedicated Python package repositories hosted on http://www.mapfish.org. As an example here's the Python package repository for MapFish 2.2: http://www.mapfish.org/downloads/2.2/pkg/

We provide a Python script for installing MapFish. The script is available at http://www.mapfish.org/downloads/, as well as at http://download.osgeo.org/mapfish/.

The source code is distributed through the MapFish SVN repository. It is also available as tarball archives at http://www.mapfish.org/downloads/.

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).

There are two mailing-lists: [MapFish-Users] 276 members (June 2011) [MapFish-Dev] 110 members (June 2011)

There is a good operation on this list with a really fast response time


 * Are source and binary downloads for the package available?
 * yes/no (and any caveats)

Yes, both the sources and binaries are distributed. For installation there is an installation script for download which makes install really easy to everybody. There are also links for direct SVN-checkout and manuals for installing from source.

There are also brief manuals for installing the environment, getting MapFish running with Apache and so on.


 * Has a Project Steering Committee been formed, and given control of the project?
 * yes/no, indicate members and whether it has effective control.

Yes, the PSC was formed in 2009. There are 7 members, 5 were voted by the community and 2 were voted by the PSC afterwards. Members are: Eric Lemoine (Chair) Bruno Binet Yves Moisan Julien-Samuel Lacroix Till Adams David Oesch Cedric Moullet


 * Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines, etc.
 * yes/no - provide pointers to various related documents.

Yes. There is a "MapFish Project Steering Committee Process" outlined on the wiki (http://trac.mapfish.org/trac/mapfish/wiki/Community/PSC/Process). In general the process is based on/derived from the OpenLayers, GDAL and Mapserver OSGeo Projects.


 * How many active developers are there? Are they from multiple organizations?
 * Indicate number and some organizations involved.

There are 11 committers, 8 from Camptocamp, 1 from Swisstopo, 1 from Sourcepole, 1 from Landcare Research. We welcome contributions from others, and are open to grant commit access to other people. http://trac.mapfish.org/trac/mapfish/wiki/Community/HowToContribute

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.

We have added OSGeo logos to the MapFish website and wiki/trac, and affiliates MapFish to OSGeo in the text of the website.


 * 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)

We have added OSGeo logos to the MapFish website and wiki/trac, and affiliates MapFish to OSGeo in the text of the website.

Code Copyright Review

 * Has a Code Provenance Review document been prepared for the project?
 * yes/no - point to review document.

Yes, see https://spreadsheets.google.com/ccc?key=0AvqoHyRAlETPdGt5aG5SMGhOQ0hkSWZ1MllmUzRFVWc&authkey=CPPyj9kE&hl=en&pli=1#gid=0


 * Have issues raised in the provenance review been adequately addressed?
 * indicate outstanding issues.

No 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.

Yes, see https://trac.mapfish.org/trac/mapfish/wiki/Community/CommittersResponsibilitiesGuidelines