Difference between revisions of "MapFish Incubation Status"

From OSGeo
Jump to: navigation, search
(Community Functioning)
m
 
(26 intermediate revisions by 5 users not shown)
Line 1: Line 1:
 +
'''Mapfish is a graduated project of the OSGeo Foundation. This page and the page history document the process. '''
 +
 
= Document Status =
 
= Document Status =
  
 
'''IncCom Document Number''': X
 
'''IncCom Document Number''': X
  
'''Version''': 1.1
+
'''Version''': 1.2
  
'''Status''': draft
+
'''Status''': final draft
  
 
= Purpose =
 
= 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.
 
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 =
 
 
; IncCom : definition
 
  
 
= Template =
 
= Template =
Line 23: Line 21:
  
 
; Has an Incubation Mentor been assigned to the project?  
 
; Has an Incubation Mentor been assigned to the project?  
: Gary Sherman as been assigned as mentor.
+
: Gary Sherman has been assigned as mentor.
  
 
== Infrastructure Transition ==
 
== Infrastructure Transition ==
Line 31: Line 29:
 
; Has the projectname.osgeo.org domain been populated with the projects web presence?  
 
; 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?
 
: If not why, and has the project page got a prominent link to the real home?
 
+
 
     There is "http://www.osgeo.org/mapfish"
+
     We do not use the "mapfish.osgeo.org" domain, but we have http://www.osgeo.org/mapfish.
 
      
 
      
     The official URL is mapfish.org and there is a direct link from OsGeo-website to this site.  
+
     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?   
 
; Is the OSGeo bug tracker being used for the project?   
 
: If not, why?
 
: 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.     
+
     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?
 
; Is the OSGeo mailing list manager (http://lists.osgeo.org/) being used for the project?
 
: If not, why?
 
: If not, why?
  
     No. (s.a.)
+
     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?
 
; Is the OSGeo SVN being used for the project?
 
: If not, why?
 
: If not, why?
  
     No, but MapFish does use Subversion, so if migration were a future need, the technical issues should be minimal.  
+
     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 ?
 
; Are binary and source downloads available from http://download.osgeo.org ?
 
: If not, why?
 
: 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
+
     MapFish isn't distributed as a binary. MapFish is a collection of Python packages, which are distributed through
     Index. We don't provide binaries, so we don't think
+
    dedicated Python package repositories hosted on http://www.mapfish.org. As an example here's the Python package
     http://download.osgeo.org would be appropriate.
+
     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 ==
 
== Community Functioning ==
Line 67: Line 70:
  
 
   There are two mailing-lists:
 
   There are two mailing-lists:
     [MapFish-Users] 259 members (Oct. 2010)
+
     [MapFish-Users] 276 members (June 2011)
     [MapFish-Dev] 103 members (Oct. 2010)
+
     [MapFish-Dev] 110 members (June 2011)
  
 
     There is a good operation on this list with a really fast response time
 
     There is a good operation on this list with a really fast response time
Line 98: Line 101:
  
 
     Yes. There is a "MapFish Project Steering Committee Process" outlined on the wiki (http://trac.mapfish.org/trac/mapfish/wiki/Community/PSC/Process).
 
     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.
+
     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?
 
; How many active developers are there?  Are they from multiple organizations?
 
: Indicate number and some organizations involved.
 
: Indicate number and some organizations involved.
  
     There are about 13 active developers, all from Camptocamp. [[http://trac.mapfish.org/trac/mapfish/wiki/Community/HowToContribute||SVN access]] is open to everybody wanting
+
     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 ==
 
== Foundation Membership ==
Line 110: Line 115:
 
: If not, indicate when this will occur.
 
: If not, indicate when this will occur.
  
open
+
    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?  
 
; 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'')
 
: 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.
+
     We have added OSGeo logos to the MapFish website and wiki/trac, and affiliates MapFish to OSGeo in the text of the website.
    [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 ==
 
== Code Copyright Review ==
Line 124: Line 127:
 
: yes/no - point to review document.  
 
: yes/no - point to review document.  
  
open
+
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?
 
; Have issues raised in the provenance review been adequately addressed?
 
: indicate outstanding issues.
 
: indicate outstanding issues.
  
open
+
No outstanding issues.
  
 
; Are [[Commiter Responsibilities Guidelines]] covering legal issues in place?
 
; 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/no - point to the guidelines and indicate if it is adopted by PSC, and accepted by all commiters.
  
open
+
Yes, see https://trac.mapfish.org/trac/mapfish/wiki/Community/CommittersResponsibilitiesGuidelines
  
 
[[Category:Incubation]]
 
[[Category:Incubation]]

Latest revision as of 06:40, 2 December 2011

Mapfish is a graduated project of the OSGeo Foundation. This page and the page history document the process.

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