Difference between revisions of "PostGIS Incubation Status"

From OSGeo
Jump to navigation Jump to search
(→‎Community Functioning: added references and links)
Line 36: Line 36:
 
: indicate members and whether it has effective control.
 
: indicate members and whether it has effective control.
 
* The member list available at http://postgis.refractions.net/docs/ch01.html
 
* The member list available at http://postgis.refractions.net/docs/ch01.html
* PSC is in [http://postgis.refractions.net/pipermail/postgis-devel/2009-November/007189.html control of development / QA] and appoints [http://postgis.refractions.net/pipermail/postgis-devel/2010-January/008321.html committer].
+
* PSC is in [http://postgis.org/pipermail/postgis-devel/2009-November/007189.html control of development / QA] and appoints [http://postgis.org/pipermail/postgis-devel/2010-January/008321.html committer].
  
 
; Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines, etc.  
 
; Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines, etc.  
Line 44: Line 44:
 
: Indicate number and some organizations involved.
 
: Indicate number and some organizations involved.
 
* [http://postgis.org/docs/ch01.html#credits List of contributors]
 
* [http://postgis.org/docs/ch01.html#credits List of contributors]
* There are developers from at least four companies (Refractions, OpenGeo, CadCorp, Arrival 3D) plus several free lance developers
+
* There are developers from at least four companies (Refractions, OpenGeo, Sirius, Paragon Corporation, CadCorp, Oslandia) plus several free lance developers
  
 
== Foundation Membership ==
 
== Foundation Membership ==

Revision as of 05:19, 22 February 2011

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?
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?
If not, why?
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 ?
If not, why?

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)
Has a Project Steering Committee been formed, and given control of the project?
yes
indicate members and whether it has effective control.
Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines, etc.
yes/no - provide pointers to various related documents.
How many active developers are there? Are they from multiple organizations?
Indicate number and some organizations involved.
  • List of contributors
  • There are developers from at least four 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?
If not, indicate what is planned. (note: currently an OSGeo web style has not bee established)

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.