PostGIS Incubation Status

General

 * Has the project been approved for incubation by the OSGeo board?
 * Yes, see: http://wiki.osgeo.org/wiki/Board_Meeting_2009-08-06#Minutes


 * Has an Incubation Mentor been assigned to the project?
 * Arnulf Christl 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?

Ideally we would like postgis.osgeo.org to be an A record to the postgis.org existing domain. This would provide DNS redundancy sould a domain expire etc. We are very content with our existing home page hosting assuming Refractions is happy to continue providing this. postgis.org and postgis.refractions.net are already well established that we feel changing to another primary name will confuse people.


 * Is the OSGeo bug tracker being used for the project?
 * Yes http://trac.osgeo.org/postgis


 * Is the OSGeo mailing list manager (http://lists.osgeo.org/) being used for the project?
 * No, but it is on our management todo (I think though can't find the ticket at the moment)


 * Is the OSGeo SVN being used for the project?
 * Yes http://svn.osgeo.org/postgis


 * Are binary and source downloads available from http://download.osgeo.org ?
 * No, Source downloads and windows binaries are available on http://www.postgis.org/download/ site.
 * The subversion tar balls and documentation are autogenerated by our build bot.
 * This is where people are familiar with getting them and we see no reason to change that.

Community Functioning

 * Is there a functioning user support mechanisms (ie. mailing list)?
 * Yes, there is a web site describing the support mechanisms (http://www.postgis.org/support/) and mailing lists for code users, developers and code repository commits.


 * Are source and binary downloads for the package available?
 * yes/no (and any caveats) - Yes via http://www.postgis.org/download/ (source tar balls, experimental builds for windows, and RTM builds for windows are available). Binaries of the latest RTM releases of PostGIS

are also carried by various Linux distros and PostgreSQL Enterprisedb Stack Builder for Windows. Mac OS binaries are available via stack builder and independent packagers.


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


 * The member list available at http://postgis.org/documentation/manual-svn/ch01.html#psc
 * PSC is in control of development / QA and appoints committer.


 * 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 on contributor guidelines. We are still working on our project procedures

PostGIS developer wiki defines contributor guidelines in the Patch submission section
 * How many active developers are there?
 * 12-20 at any one time (these include patch submitters) but generally 10-12 constant programmers who have commit access.


 * Are they from multiple organizations? Yes
 * Indicate number and some organizations involved - Each developer with commit access is currently from a different company
 * or a free lance developers

(~ 8-10 are from companies and 2-4 are free lance developers)
 * List of contributors
 * There are developers from several companies (Refractions, OpenGeo, Sirius, Paragon Corporation, CadCorp, Oslandia) plus several free lance developers

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.


 * Has an effort been made to brand the project web site with OSGeo foundation web styling and branding marks?
 * No, but it is on our task agenda and we are still figuring out what is expected. http://trac.osgeo.org/postgis/ticket/843

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 - http://trac.osgeo.org/postgis/wiki/DevWikiComitGuidelines still in draft and not yet adopted by PSC, and accepted by all commiters.