MapFish Incubation Status
IncCom Document Number: X
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
- Has the project been approved for incubation by the OSGeo board?
- Has an Incubation Mentor been assigned to the project?
- Gary Sherman as been assigned as mentor.
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?
There is "http://www.osgeo.org/mapfish" The official URL is mapfish.org and there is a direct link from OsGeo-website to this site.
- Is the OSGeo bug tracker being used for the project?
- If not, why?
No, in the moment trac on the MapFish site is used. So if migration were a future need, the technical issues should be minimal.
- Is the OSGeo mailing list manager (http://lists.osgeo.org/) being used for the project?
- If not, why?
- Is the OSGeo SVN being used for the project?
- If not, why?
No, but MapFish does use Subversion, so if migration were a future need, the technical issues should be minimal.
- Are binary and source downloads available from http://download.osgeo.org ?
- If not, why?
Yes, download and also svn-read access is provided via the MapFish-Website. MapFish packages are distributed through a so-called Python Package Index. We don't provide binaries, so we don't think http://download.osgeo.org would be appropriate.
- 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] 259 members (Oct. 2010) [MapFish-Dev] 103 members (Oct. 2010)
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 about 13 active developers, all from Camptocamp. [access] is open to everybody wanting
- 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)
Not yet. We will wait for an OSGeo web style to be established before using this style. [I googled around to find any information about this style, I do not know the exact status, but as it is still in the template, I guess this is still the status]
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.