OSGeo Community Projects

This wiki page is a scratchpad of ideas forming the osgeo community program. To see how these ideas have been realized please see our website page.

= OSGeo support for 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!

About OSGeo Project List
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

About OSGeo Community Projects
We ask that *OSGeo Community* projects go further:


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

To be recognized as an *OSGeo Project* we ask that project teams excel in each of these three aspects, see the graduation checklist for more detail.

How OSGeo Community Projects Are Related To OSGeo Incubation
There are two ways for an open source software project to join OSGeo. The first way is through the regular incubation process. This is best for projects that already have an established community of developers and users. (This community should be diverse. This means that developers should come from more than one organization or group.)

If a project doesn't yet have an active and diverse community, it can join OSGeo as an OSGeo Community Project. OSGeo Community Projects get help from the incubation committee with things like choosing an open source license, setting up project governance, promoting the project, and building the project community).

The same volunteers that help software projects through the OSGeo Incubation Process also help OSGeo Community Projects.

Purpose
The purpose of *OSGeo Community* projects is help foster innovation and include more project teams in the Open Source Geospatial Foundation.

Comparison
As shown below there is some overlap requirements for an OSGeo projects (as defined by the incubation process graduation checklist).

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 a 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

Available branding:

Community Projects
For a complete list please see the osgeo website: menu > projects > community projects.

The following projects were added to the OSGeo Community program from the earlier "osgeo labs" :


 * Geoinformatica
 * GeoWebCache
 * MapProxy
 * pgRouting
 * Portable GIS
 * Postal Address Geo-Coder
 * Proj4php
 * Pronto Raster
 * Virtual Terrain Project
 * Loader

The following projects have now graduated from incubation:
 * pycsw

There is an archive of the old OSGeo Technology Projects page at OSGeo Labs Page Archive.