Skip to content

Project Graduation Checklist

Regina Obe edited this page Oct 1, 2024 · 19 revisions

Project Graduation Checklist

Based on the OSGeo Project Graduation Checklist version 2.0.

Overview

This checklist is based on the pgRouting master branch at https://github.com/pgRouting/pgrouting/tree/main)

Incubation Checklist

Open

The project has demonstrated that it has an open, active and healthy user and developer community:

Copyright and License

We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:

Processes

Documentation

Release Procedure

In order to maintain a consistent level of quality, the project should follow defined release and testing processes.

OSGeo Committees and Community

The OSGeo Foundation is made up of a number of committees, projects and local chapters. This section gathers up information these groups have requested from OSGeo projects. These expectations are not mandatory requirements before graduation, but a project should be prepared to address them in order to be considered a good OSGeo citizen.

Board

The OSGeo Board holds ultimate responsibility for all OSGeo activities. The Board requests:

Marketing

Access to OSGeo's Marketing_Committee and associated Marketing Pipeline is one of the key benefits of joining the OSGeo foundation. The Marketing Committee requests:

Projects

  • Projects do not exist in isolation; and are expected to communicate and collaborate on key issues.
    • We communicate with QGIS, PostGIS, PostgreSQL, MobilityDB and many others
    • pgRouting has a plugin with QGIS

SAC

The System Administration Committee is available to help with infrastructure and facilities. Information for this committee is collected as part of the Project Graduation Checklist.

Clone this wiki locally