Difference between revisions of "PostGIS Incubation Status"

From OSGeo
Jump to navigation Jump to search
m
 
(30 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 +
''PostGIS has [http://wiki.osgeo.org/wiki/Board_Meeting_2012-06-07 graduated from incubation] on 2012-06-07. ''
 +
 
== General ==
 
== General ==
 
; Has the project been approved for incubation by the OSGeo board?
 
; Has the project been approved for incubation by the OSGeo board?
 
: Yes, see: http://wiki.osgeo.org/wiki/Board_Meeting_2009-08-06#Minutes
 
: Yes, see: http://wiki.osgeo.org/wiki/Board_Meeting_2009-08-06#Minutes
  
; Has an Incubation Mentor been assigned to the project?  
+
; Has the project been graduated from incubation by the OSGeo board ?
: [[Arnulf Christl]] has been assigned as mentor.
+
: Yes, see: http://wiki.osgeo.org/wiki/Board_Meeting_2012-06-07
 +
 
 +
; Who is the primary contact for the project?
 +
: '''Paul Ramsey''' has been assigned as Project Administrator
 +
 
 +
; Who was the Incubation Mentor of the project?  
 +
: [[Arnulf Christl]] was assigned to mentor the project
 +
 
  
 
== Infrastructure Transition ==
 
== Infrastructure Transition ==
Line 10: Line 19:
  
 
; 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?''
: Ideally we would like postgis.osgeo.org to be an A record to the postgis.org existing domain.
+
: Ideally we would like postgis.osgeo.org to be an A record to the postgis.org existing domain. This would provide DNS redundancy should a domain expire etc. See [http://trac.osgeo.org/osgeo/ticket/839 ticket]
: This would provide DNS redundancy should a domain expire etc.
 
 
: We are very content with our existing home page hosting assuming Refractions is happy to continue providing this.
 
: We are very content with our existing home page hosting assuming Refractions is happy to continue providing this.
 
: http://postgis.org and http://postgis.refractions.net are already well established that we feel changing to another primary name will confuse people.
 
: http://postgis.org and http://postgis.refractions.net are already well established that we feel changing to another primary name will confuse people.
Line 28: Line 36:
 
: No, Source downloads and windows binaries are available on http://www.postgis.org/download/ site.
 
: 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.
 
: 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.
+
: This is where people are familiar with getting them and we see no reason to change that. We would however request that
 +
: a link to the http://www.postgis.org/download/ page be added to the http://download.osgeo.org page.  I think that would
 +
: achieve the intent of the letter. See [http://trac.osgeo.org/osgeo/ticket/835 Ticket closed, done.]
  
 
== Community Functioning ==
 
== Community Functioning ==
Line 35: Line 45:
  
 
; Are source and binary downloads for the package available?  
 
; 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
+
: 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.
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?
 
; Has a Project Steering Committee been formed, and given control of the project?
: yes
+
: Yes. The member list available at http://www.postgis.org/documentation/manual-svn/postgis_introduction.html#psc
: indicate members and whether it has effective control.
+
: Here are some example mails from the PostGIS-devel mailing list showing that the PSC is in [http://postgis.org/pipermail/postgis-devel/2009-November/007189.html control of development / QA] and [http://postgis.org/pipermail/postgis-devel/2010-January/008321.html appoints committers].
* The member list available at http://postgis.org/documentation/manual-svn/ch01.html#psc
 
* 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.  
: yes/no - provide pointers to various related documents. Yes on contributor guidelines.  We are still working on our project procedures
+
: An [http://trac.osgeo.org/postgis/wiki/RFC/RFC-1 RFC-1] has been drafted to more formally define the PSC and it's functions and [http://postgis.refractions.net/pipermail/postgis-devel/2012-May/020503.html ratified]
[http://trac.osgeo.org/postgis/wiki/DevWikiMain PostGIS developer wiki] defines contributor guidelines in the Patch submission section
+
: Contributor guidelines are loosely described on the [http://trac.osgeo.org/postgis/wiki/DevWikiMain PostGIS developer wiki] in the Patch submission section,
 +
: More complete  [http://trac.osgeo.org/postgis/wiki/DevWikiComitGuidelines Committer Guidelines] have been drafted as RFC-5 and [http://postgis.refractions.net/pipermail/postgis-devel/2012-May/020503.html ratified].
 +
 
 
; How many active developers are there?   
 
; 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.
 
: 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
+
; Are they from multiple organizations?
: Indicate number and some organizations involved - Each developer with commit access is currently from a different company
+
: Yes, there are developers from several companies (Refractions, OpenGeo, Sirius, Paragon Corporation, CadCorp, Oslandia, University of Laval, UC Davis, Deimos Space) plus several free lance developers
: or a free lance developers
+
: (~ 8-10 are from companies and 2-4 are free lance developers)
(~ 8-10 are from companies and 2-4 are free lance developers)
+
: [http://www.postgis.org/documentation/manual-svn/postgis_introduction.html#credits List of contributors]
: [http://postgis.org/docs/ch01.html#credits List of contributors]
 
: There are developers from several companies (Refractions, OpenGeo, Sirius, Paragon Corporation, CadCorp, Oslandia) plus several free lance developers
 
  
 
== Foundation Membership ==
 
== Foundation Membership ==
Line 68: Line 74:
  
 
; Has a [[Code Provenance Review]] document been prepared for the project?
 
; Has a [[Code Provenance Review]] document been prepared for the project?
: A [[http://trac.osgeo.org/postgis/wiki/DevWikiProvenanceReview Code Provenance Review document]] is currently being prepared.
+
: The [[PostGIS Provenance Review]] document was finalized in November 2011.
  
 
; Have issues raised in the provenance review been adequately addressed?
 
; Have issues raised in the provenance review been adequately addressed?
: indicate outstanding issues.
+
: Yes.
  
; Are [[Commiter Responsibilities Guidelines]] covering legal issues in place?
+
; Are [[Committer Responsibilities Guidelines]] covering legal issues in place?
: Yes - [http://trac.osgeo.org/postgis/wiki/DevWikiComitGuidelines http://trac.osgeo.org/postgis/wiki/DevWikiComitGuidelines] still in draft and not yet adopted by PSC, and accepted by all commiters.
+
: Yes - [http://trac.osgeo.org/postgis/wiki/DevWikiComitGuidelines Committer Guidelines] still in draft but [http://www.postgis.org/pipermail/postgis-devel/2011-May/thread.html#12845 accepted by existing committers and PSC members] as of version 1.00000006
  
 
[[Category:Incubation]]
 
[[Category:Incubation]]

Latest revision as of 05:32, 20 November 2013

PostGIS has graduated from incubation on 2012-06-07.

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 the project been graduated from incubation by the OSGeo board ?
Yes, see: http://wiki.osgeo.org/wiki/Board_Meeting_2012-06-07
Who is the primary contact for the project?
Paul Ramsey has been assigned as Project Administrator
Who was the Incubation Mentor of the project?
Arnulf Christl was assigned to mentor the project


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 should a domain expire etc. See ticket
We are very content with our existing home page hosting assuming Refractions is happy to continue providing this.
http://postgis.org and http://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. We would however request that
a link to the http://www.postgis.org/download/ page be added to the http://download.osgeo.org page. I think that would
achieve the intent of the letter. See Ticket closed, done.

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 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. The member list available at http://www.postgis.org/documentation/manual-svn/postgis_introduction.html#psc
Here are some example mails from the PostGIS-devel mailing list showing that the PSC is in control of development / QA and appoints committers.
Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines, etc.
An RFC-1 has been drafted to more formally define the PSC and it's functions and ratified
Contributor guidelines are loosely described on the PostGIS developer wiki in the Patch submission section,
More complete Committer Guidelines have been drafted as RFC-5 and ratified.
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, there are developers from several companies (Refractions, OpenGeo, Sirius, Paragon Corporation, CadCorp, Oslandia, University of Laval, UC Davis, Deimos Space) plus several free lance developers
(~ 8-10 are from companies and 2-4 are free lance developers)
List of contributors

Foundation Membership

Have project documents been updated to reflect membership in the foundation, and the relationship of the project to the foundation?
Yes. The generated and on-line docs have "OSGeo Project" logos, as does the main wiki page.
Has an effort been made to brand the project web site with OSGeo foundation web styling and branding marks?
Yes, an "OSGeo Project" logo has been added to the postgis.org site header, as well as to the main wiki page.

Code Copyright Review

Has a Code Provenance Review document been prepared for the project?
The PostGIS Provenance Review document was finalized in November 2011.
Have issues raised in the provenance review been adequately addressed?
Yes.
Are Committer Responsibilities Guidelines covering legal issues in place?
Yes - Committer Guidelines still in draft but accepted by existing committers and PSC members as of version 1.00000006