Incubation Committee

The project incubation committee is responsible for overseeing the incubation process for new projects entering the foundation. The incubation committee provides resources to assist new projects to reach full membership, and makes recommendations to the board when they feel projects have completed incubation.

About the Incubation Committee
The OSGeo Incubation Committee is an open source advocacy and outreach activity welcoming projects and development teams to our foundation.

The committee is responsible for:


 * 1) OSGeo project website review
 * 2) * Reviewing applications to list projects on the OSGeo website
 * 3) * Preparing and recommend criteria and review process for projects to be listed on the OSGeo website
 * 4) Community project program
 * 5) * Reviewing community project applications and recommending projects to the board to be accepted as community projects
 * 6) * Reporting on the status of projects in the community project program to the board periodically (via Chair)
 * 7) * Preparing and recommending community project process and criteria to the board.
 * 8) * See OSGeo_Community_Projects for more information
 * 9) OSGeo Incubation process
 * 10) * Reviewing applications for incubation and making recommendations to the board on projects that should be admitted into incubation.
 * 11) * Appointing mentors for incubation projects.
 * 12) * Reviewing progress of projects against incubation requirements, and recommending projects for full project status to the board, when deemed appropriate.
 * 13) * Reporting on the status of projects in incubation and the incubation process to the board periodically (via Chair).
 * 14) * Preparing and recommending incubation process and criteria to the board.

The OSGeo incubation committee is not responsible for graduated OSGeo Projects. Graduated OSGeo projects are recognized as a committee who report directly to the board via their project officer.

Supporting project teams
If you would like your software project to listed on the website, or apply to become an OSGeo Community project, please send a description of your project to the OSGeo Incubation Committee Mailing List.

We look forward to helping you!

Financial support
The incubation process establishes a project as a full fledged OSGeo committee, with a project project officer, with direct access to OSGeo treasurer, and reporting to the board during annual general meeting.

While Community projects are not recognized as an independent committee, the OSGeo board maintains an "OSGeo Community" initiative with budget to support your activities. Attend one of the OSGeo board monthly meetings, or ask on the board mailing list, if your project has an activity that can benefit from financial support.

For more information see osgeo_financial_guidence.pdf

Step 1: Add OSGeo Website Project Page
To be listed on the OSGeo website:


 * 1) Be geospatial
 * 2) * Confirm by checking README or project description
 * 3) Have a free license or open source license
 * 4) * The license must be OSI approved
 * 5) Welcome participation and new contributors.
 * 6) * We look for a clear contribution policy

If you have questions about the above, or would like guidance on setting up your open source project, please reach out to us.

Here is an example email request (mailing list sign up required):


 * to: incubator@lists.osgeo.org
 * subject: water topology api
 * message:
 * Incubation committee:
 * I would like to ask permission to to list my project "water topology api" on the OSGeo website in order to share my work with more people!
 * The project is built on PostGIS topology providing a REST API to help with watershed analysis and maintenance.
 * The repository is located here: https://gitlab.host.net/watertopo/ released using GPL license.
 * My OSGeo userid is "atlantis" and I will need permission to create a project page.
 * Thanks!
 * The project is built on PostGIS topology providing a REST API to help with watershed analysis and maintenance.
 * The repository is located here: https://gitlab.host.net/watertopo/ released using GPL license.
 * My OSGeo userid is "atlantis" and I will need permission to create a project page.
 * Thanks!
 * My OSGeo userid is "atlantis" and I will need permission to create a project page.
 * Thanks!
 * Thanks!
 * Thanks!

Step 2: Join Community Projects Program
Projects applying to the *OSGeo Community* program are asked to:


 * 1) Be geospatial
 * 2) * Confirm by checking README or project description
 * 3) * project page on the osgeo website
 * 4) * We ask projects have some user documentation, for example an OSGeo Live quickstart
 * 5) Have a free license or an open source license.
 * 6) * The license must be OSI approved
 * 7) * We ask that the project team check the file headers and double check the license has been appropriately applied
 * 8) Welcome participation and new contributors.
 * 9) * We look for a clear contribution policy
 * 10) * We ask that the project demonstrate collaboration, perhaps with a history of bug report or pull requests
 * 11) * Projects are required to have a code of conduct

OSGeo provides code of conduct guidance, many projects selecting contribution covenant).

OSGeo Community Projects can take part in the incubation committee for guidance on open source use, setting up project governance, promoting the project, and building the project community. We look forward to working with you. For sensitive topics (patents, copyright, trademarks, and license) you wish to attend a video meeting.

Here is an example email request (mailing list sign up required):


 * to: incubator@lists.osgeo.org
 * subject: water topology community project application
 * message:
 * Incubation committee:
 * The Water Topology project would like to apply to join the OSGeo community program. We recently re-branded to just "water topology" to reflect client libraries being include in our project. The project provides web services built on PostGIS topology to help with watershed analysis and maintenance.
 * The osgeo project page is available here: https://osgeo.org/projects/watertopology and our user guide is located at https://watertopo.gitlab.host.net/.
 * The repository remains at https://gitlab.host.net/watertopo/ with GPL license, contribution policy and code of conduct. We have checked our source code to ensure GPL license has been correctly applied. Our issue tracker is active, and we have received a number of merge-requests.
 * Thank you for your consideration and we look forward to your questions!
 * The Water Topology project would like to apply to join the OSGeo community program. We recently re-branded to just "water topology" to reflect client libraries being include in our project. The project provides web services built on PostGIS topology to help with watershed analysis and maintenance.
 * The osgeo project page is available here: https://osgeo.org/projects/watertopology and our user guide is located at https://watertopo.gitlab.host.net/.
 * The repository remains at https://gitlab.host.net/watertopo/ with GPL license, contribution policy and code of conduct. We have checked our source code to ensure GPL license has been correctly applied. Our issue tracker is active, and we have received a number of merge-requests.
 * Thank you for your consideration and we look forward to your questions!
 * The repository remains at https://gitlab.host.net/watertopo/ with GPL license, contribution policy and code of conduct. We have checked our source code to ensure GPL license has been correctly applied. Our issue tracker is active, and we have received a number of merge-requests.
 * Thank you for your consideration and we look forward to your questions!
 * Thank you for your consideration and we look forward to your questions!

Step 3: Incubation process and Graduation
The *OSGeo Project* designation is intended to recognize established projects with a diverse community of developers and users with a proven track record.

To be recognized as an *OSGeo Project* a project team applies for the OSGeo incubation program. Successful projects are teamed up with an experienced open source mentor to help answer questions, obtain legal council, and help guide work on transparency and community development as required.

Although incubation is a lot of work, this is opportunity for project teams to grow and improve and be publicly recognized for their accomplishment.

To be recognized as an *OSGeo Project* we ask that project teams excel in each of areas mentioned above, see graduation checklist or the comparison table on this page for more detail.

The OSGeo incubation process takes place in three stages:


 * 1) Initial Application
 * 2) Application request
 * 3) Mentor volunteer
 * 4) Incubator
 * 5) Project Status: project details, and a few resourcing questions for the system admin committee (see Project Status Template).
 * 6) Provenance Review: project team check to ensure the project is open source and has permission to distribute its source code.
 * 7) Project team and mentor work on graduation checklist priorities
 * 8) Graduation
 * 9) Mentor recommends project for graduation with motion to the incubation committee
 * 10) Committee chair informs the OSGeo board, who appoints the project team as a newly formed OSGeo committee

Incubation
The following projects are currently in OSGeo incubation. The links provided are used to track the progress of incubation projects and are used by the developer team (and OSGeo mentor). In many cases the links will take you to a project specific wiki or website in order to be closer to their target community.

When projects have completed the graduation checklist their mentor will recommend them to the Incubation committee for graduation.

IstSOS
IstSOS: http://wiki.osgeo.org/wiki/IstSOS
 * 1) IstSOS Provenance Review
 * 2) IstSOS Incubation Status
 * 3) Mentor: Jeff McKenna

Opticks
Opticks: http://opticks.org
 * 1) Opticks Incubation Status
 * 2) no provenance review provided
 * 3) Opticks Incubation Checklist
 * 4) Mentor: Mark Lucas

Oskari
Oskari: http://oskari.org/
 * 1) Oskari Incubation Application
 * 2) Oskari Incubation Status
 * 3) Oskari Graduation Checklist
 * 4) Mentor: Arnulf Christl

TEAM Engine
TEAM Engine: http://teamengine.sourceforge.net
 * 1) Incubation Application from 2012
 * 2) TEAM Engine Incubation Checklist
 * 3) Mentor: Jody Garnett

pgRouting
pgRouting: https://pgrouting.org/
 * Mentor: Angelos_Tzotsos
 * Incubation Application:
 * trac
 * mail
 * Incubator Motion to enter Incubation
 * Board Motion to accept pgRouting to incubation
 * Project Status
 * Project Graduation Checklist
 * Issues tagged for OSGeo incubation (label=OSGeo incubation)
 * Graduation: None at this stage

Graduated
The following status and provenance documents are for historical purposes, and are no longer actively maintained.


 * Community Mapbuilder: Community Mapbuilder Incubation Progress | Community Mapbuilder Provenance Review (Entered 2006-02-04, Graduated 2006-07-14, Mentor: Steve Lime)
 * deegree: deegree Incubation Status | deegree Provenance Review (Entered: 2008-06-09, Graduated 2010-02-04, Mentor: Jody Garnett)
 * FDO: FDO Incubation Status | FDO Provenance Review (Entered 2007-03-06, Graduated 2008-02-08, Mentor: Daniel Morissette)
 * GEOS: GEOS Incubation Status | GEOS Provenance Review (Entered 2007-11-02, Graduated 2012-04-28, Mentor: Frank Warmerdam)
 * GDAL/OGR: GDAL Incubation Progress | GDAL Provenance Review (Entered 2006-02-04, Graduated 2008-02-08, Mentor: Paul Spencer)
 * Geomajas: GeoMajas Incubation Status | GeoMajas Provenance Review (Entered 2010-03-04, Graduated 2010-11-22, Mentor: Paul Spencer)
 * GeoNetwork: GeoNetwork Incubation Status | GeoNetwork Provenance Review (Entered 2006-11-10, Graduated 2008-06-21, Mentor: Jody Garnett)
 * GeoNode: GeoNode Incubation Status GeoNode Provenance Review GeoNode Incubation Checklist (Entered 2015-08-13, Graduated 2016-11-09, Mentor: David Bitner)
 * GeoMOOSE: GeoMoose Incubation Status | GeoMoose Provenance Review | GeoMoose Incubation Checklist (Entered 2011-12-08, Graduated 2013-04-19, Mentor: Jody Garnett)
 * GeoTools: GeoTools Incubation Progress | GeoTools Provenance Review (Entered 2006-02-27, Graduated 2008-07-18, Mentor: Cameron Shorter)
 * GeoServer: Incubation Questionnaire | Incubation Status | Provenance Review | Incubation Checklist | Geoserver Mentor Notes (Entered 2009-11-05, Graduated 2013-03-15, Mentor: Landon Blake)
 * gvSIG: gvSIG Incubation Status | gvSIG Provenance Review | gvSIG Incubation Checklist (Entered 2007-09-07, Graduated 2015-11-26, Mentor: Dimitris Kotzinos)
 * GRASS: GRASS Incubation Progress | GRASS Provenance Review (Entered 2006-02-27, Graduated 2008-02-08, Mentor: Norman Vine and Arnulf Christl)
 * Mapbender: Mapbender Incubation Progress | Mapbender Provenance Review (Entered 2006-02-04, Graduated 2006-07-15, Mentor: Paul Spencer)
 * MapFish: MapFish Incubation Status | MapFish Provenance Review (Entered 2009-11-09, Graduated 2011-09-01, Mentor: Gary Sherman)
 * MapGuide Open: MapGuide Incubation Status | MapGuide Provenance Review (Entered 2006-02-04, Graduated 2007-03-02, Mentor: Daniel Morissette)
 * MapServer: MapServer incubation status | MapServer Provenance Review (Entered 2006-02-04, Graduated 2008-12-16, Mentor: Chris Holmes)
 * Marble: Marble Incubation Status | Marble Code Provenance Review | Marble Graduation Checklist (Entered 2012-10-12, Graduated 2013-10-17, Mentor: Arnulf Christl)
 * OpenLayers: OpenLayers Incubation Status | OpenLayers Provenance Review (Entered 2006-11-10, Graduated 2007-11-16, Mentor: Howard Butler)
 * Orfeo ToolBox (OTB): OTB Project Incubation Status | OTB Code Provenance Review (Entered 2009-10-26, Graduated 2017-07-20, Mentor: Landon Blake)
 * OSGeoLive: Graduation Checklist (Entered 2017-10-05, Graduated 2018-04-14, Mentor: Jody Garnett)
 * PostGIS: PostGIS Incubation Status | PostGIS Provenance Review (Entered 2009-08-06, Graduated 2012-06-07, Mentor: Arnulf Christl)
 * PROJ: Incubation Application | PROJ Graduation Checklist (Entered 2019-05-04, Graduated 2019-11-26, Mentor: Michael Smith )
 * pycsw: Incubation Status | Graduation Checklist | Provenance Review (Entered 2013-03-30, Graduated 2015-03-05, Mentor: Jeff McKenna)
 * pygeoapi: Incubation Status | Graduation Checklist | Provenance Review (Entered 2021-11-03, Graduated 2022-08-21, Mentor: Michael Smith)
 * PyWPS: Incubation Status | Graduation Checklist | Provenance Review (Entered 2009-02-27, Graduated 2018-04-11, Mentor: Tom Kralidis)
 * OSSIM: OSSIM incubation status | OSSIM Provenance Review (Entered 2006-02-27, Graduated 2009-06-02, Mentor: Richard Gould)
 * QGIS: QGIS Incubation Status | QGIS Provenance Review (Entered 2007-03-02, Graduated 2008-03-14, Mentor: Bob Bray)

The initial projects to go through the incubation process helped define what is required. The above pages tracked the progress (and capture the experience) of these projects.

Withdrawn
The following projects did not complete incubation:


 * rasdaman: :  rasdaman Incubation Status  | Code Provenance | Incubation Checklist (Mentor Bruce Bannerman )
 * MetaCRS: ::  MetaCRS Incubation Status (Mentor: Daniel Morissette)

Committee Operation
The incubation committee operates within the OSGeo committee guidelines, operating in a close working relationship with the OSGeo board as reflected in our responsibilities above.


 * Voting members: Voting members are maintained on this page as outlined below. This committee is volunteer based with committee member ship driven by email request to be added or removed. Inactive members (see below) are removed as needed to preserve committee function.
 * Project mentors: Have volunteered to represent our organization at a personal level as a guest on the projects email list and meetings. Project mentors are responsible for recommending when a project is ready for graduation based on this first hand experience. For more information see mentor guidelines.
 * Committee chair: Committee chair appointed by motion, result forward to the board for approval and recognition as an officer of the foundation. Committee chair is responsible for operation of the committee.
 * Communication: This committee operates on the incubator mailing list. With the occasional breakout IRC meeting, hangout, or phone call to explore specific issues.
 * Decision making: Decision making is performed by email motion. Motions are held open for a two week period. Each motion requires a 50% quorum within the two week period. Voting consists of +1 (approval), +0 (slight agreement), -0 (slight disagreement), -1 (against). The committee chair is responsible for replying to the email thread with voting results and motion resolution.
 * Email motions should be clearly worded and have a subject line “Motion:”.
 * Motions are held open for a two week period to give everyone a chance to respond, this accounts for volunteers that are only available on weekends.
 * At discretion of the chair a motion may be held open longer than two weeks.
 * If a motion does not gather a 50% response within a two week period we may need to revisit our active member list – removing members that have not voted within the last year.
 * Voting +0 and -0 are a good way to reach quorum for volunteers that have not had a chance to follow the discussion.
 * There is no veto in the incubation committee, but we tend to respect -1 votes and withdraw motions that are divisive. It is noted that when reviewing graduation checklists -1 votes tend to track outstanding issues that are then addressed within the voting period.
 * Independence: Our mandate is focused on providing to the OSGeo board as outlined above.

Example email: Subject: motion: accept project x as a community project The following motion has been made by Firstname Lastname: Motion to accept project x as an community project. This motion is held open for two weeks closing MONTH DAY, requiring 50% quorum, from the following incubation committee members: * LINE BY LINE BULLETED LIST OF CURRENT MEMBERS

A subsequent email will be sent when the motion is completed, either by the elapsed time period, or by unanimous consent before the closing period.

Committee Members
Volunteers Welcome - if you would like to take part we are always looking for new members, sign up to the email list, and introduce yourself to volunteer.

Current members:


 * Bob (CI-StPaul) Basques
 * Arnulf Christl
 * Jo Cook
 * Jody Garnett (chair)
 * Dimitris Kotzinos
 * Tom Kralidis
 * Steve Lime
 * Daniel Morissette
 * Regina Obe
 * Michael Smith
 * Angelos Tzotsos
 * Frank Warmerdam

Thank you - we ask that volunteers remain active, joining the discussion and voting on the email list. If you are unable to take part please send us an email. As volunteers we understand that life can get in the way of advocacy – you are welcome to rejoin at any time. We will also retire inactive members as needed. Prior members:


 * Bruce Bannerman
 * Landon Blake
 * Robert Bray
 * Howard Butler
 * Chris Holmes
 * Julien-Samuel Lacroix
 * Mark Lucas
 * Judit Mays
 * Jeff McKenna
 * Markus Neteler
 * Markus Schneider
 * Cameron Shorter
 * Paul Spencer
 * Jeroen Ticheler
 * Norman Vine

Documents

 * Official incubator public web page is at: https://www.osgeo.org/about/committees/incubation/ (with members list).
 * OSGeo_Community_Projects
 * Incubation FAQ
 * Official_IncCom_Documents
 * Incubation process docs: https://www.osgeo.org/about/committees/incubation/incubation-process/ (original wiki draft documents)
 * Incubation Badges

Draft or discussion documents
 * Draft Commiter Responsibilities Guidelines
 * Draft 5-star-rating - discussion about more fine incubation procedure
 * OSGeo Distribution and Committer [licenses which can be used as is, or as an example for projects starting off with participatory open source.
 * Geotools Copyright Assignment (pdf, odt) - previous example
 * Project Copyright Assignment - previous example
 * Contributor Agreement and FAQ
 * Incubation Phases proposal

Document Refresh 2014
 * Project Graduation Checklist

References:
 * Project Infrastructure Migration
 * Producing OSS - by Karl Fogel - an excellent primer on running an FOSS project.

Reports:
 * Incubation Committee Report 2012
 * Incubation Committee Report 2011

Trac:
 * Open Incubator Trac Issues
 * Pending Incubation Applications

Meetings and Reports
Meetings are scheduled via Mailing List and take place via IRC at the times specified in the Foundation Calendar.
 * First Meeting - March 13th 2006
 * Second Meeting - March 20th 2006
 * Third Meeting - March 27th 2006
 * Fourth Meeting - April 10th 2006
 * Fifth Meeting - April 24th 2006
 * Sixth Meeting - June 19th 2006
 * Seventh Meeting - August 7th 2006
 * Eighth Meeting - October 30th 2006
 * Nineth Meeting - February 12th 2007
 * Tenth Meeting - June 11th 2007
 * Eleventh Meeting - October 29th 2007
 * Twelfth Meeting - September 8th 2008
 * Thirteenth Meeting - October 29th 2009
 * Fourteenth Meeting - March 1th 2010
 * IncCom Meeting15 - Nov 21 2011
 * IncCom Meeting16 - Jan 17 2012
 * IncCom Meeting17 - March 19 2012
 * IncCom Meeting18 - May 21 2012
 * IncCom Meeting19 - July 23 2012
 * IncCom Meeting20 - Sep 24 2012
 * IncCom Meeting21 - Feb 18 2013
 * IncCom Report22 - 2013 Q2
 * IncCom Report23 - 2013 Q3
 * IncCom Report24 - 2014 Q1
 * Fall 2014 Committee Report for OSGeo Journal