Project Graduation Checklist

NOTE: please edit this in edit mode 'reStructuredText'. This will make things easy to port to the codebase (sphinx) docs in git

Incubation Checklist

Last updated: 2015-02-13

Open

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

1. Open: projects are expected to function in an open and public manner and include:

• [x] Open source license(s),
  • Yes, MIT for code, Attribution 4.0 International (CC BY 4.0) for docs
• [x]Open communication channels,
  • Mailing list http://lists.osgeo.org/mailman/listinfo/pycsw-devel
  • IRC #pycsw (on freenode.net)
  • Google+ Community (https://plus.google.com/communities/104084873011085696113)
• [x] Open decision making process.
  • Yes. A Project Steering Committee has been formed (http://pycsw.org/development/rfc/rfc-1.html). A process for Request for Proposals (RFP) for significant changes to the source code has been articulated and in operation (http://pycsw.org/development/rfc/).

2. Active and healthy community:

• [x] The project should have a community of developers and users who actively collaborate and support each other in a healthy way. Eg. collaboration on project activities such as testing, release and feature development.

  • Release processes are open and documented at https://github.com/geopython/pycsw/wiki/Release-Plans
  • Guidelines for creating a release are documented at https://github.com/geopython/pycsw/wiki/Release-Packaging/
  • Bugs and features on GitHub at https://github.com/geopython/pycsw/issues
  • Discussion in mailing lists both upstream and downstream of pycsw as well as across GitHub https://github.com/search?q=pycsw&type=Issues&utf8=%E2%9C%93

• [x] Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organizations. Eg. The project is resilient enough to sustain loss of a developer or supporting organization, often referred to as having a high bus factor. Decisions are made openly instead of behind closed doors, which empowers all developers to take ownership of the project and facilitates spreading of knowledge between current and future team members.

  • The project has core developers from 4 organizations and other contributors from downstream projects/organizations such as CKAN and GeoNode.

  • Some statistics for the project can be found at https://www.openhub.net/p/pycsw

  • Decisions are made openly via mailing lists/IRC

  • The project powers CSW implementation of numerous high profile activities:

    • data.gov and geoplatform.gov
    • data.noaa.gov
    • numerous deployments in support of US IOOS (http://ioos.noaa.gov)
    • USGS
    • US National Geothermal Data System
    • WMO World Ozone and Ultraviolet Radiation Data Centre

    and receives many contributions/fixes through GitHub.

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:

1. [x] All project source code is available under an Open Source license.

• Yes, MIT

2. [x] Project documentation is available under an open license. Eg. Creative Commons

• Yes, Attribution 4.0 International (CC BY 4.0)

3. [x] The project code, documentation and data has been adequately vetted to assure it is all properly licensed, and a copyright notice included. As per a Provenance Review

• Done. See https://github.com/geopython/pycsw/wiki/pycsw-Provenance-Review. Issues documented at https://github.com/geopython/pycsw/labels/osgeo-incubation

4. [x] The project maintains a list of all copyright holders identified in the Provenance Review Document.

• Done. See https://github.com/geopython/pycsw/wiki/pycsw-Provenance-Review#copyhold

5. [ ] All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived.

• TODO: in progress https://github.com/geopython/pycsw/issues/312

Processes

1. [x] The project has code under configuration management. Eg, subversion, git.

• yes, git

2. [x] The project uses an issue tracker and keeps the status of the issue tracker up to date.

• yes, GitHub

3. [x] The project has documented its management processes. This is typically done within a Developers Guide or Project Management Plan.

• yes, http://docs.pycsw.org/en/latest/contributing.html, release planning https://github.com/geopython/pycsw/wiki/Release-Plans, release packaging management https://github.com/geopython/pycsw/wiki/Release-Packaging
• The project has a suitable open governance policy ensuring decisions are made, documented and adhered to in a public manner. This typically means a Project Management Committee has been established with a process for adding new members. A robust Project Management Committee will typically draw upon developers, users and key stakeholders from multiple organisations as there will be a greater variety of technical visions and the project is more resilient to a sponsor leaving.
• Yes, PSC (http://pycsw.org/community/psc.html) and RFC (http://pycsw.org/development/rfc/) mechanisms exist
• The project uses public communication channels for decision making to maintain transparency. E.g. archived email list(s), archived IRC channel(s), public issue tracker.
• yes, irc, mailing list, GitHub issues. See http://pycsw.org/community/

Documentation

1. The project has user documentation:

• [x] Including sufficient detail to guide a new user through performing the core functionality provided by the application.
  • yes, substantial user documentation, distributed through GitHub (https://github.com/geopython/pycsw/tree/master/docs) and currently hosted through 'Read the Docs' (http://docs.pycsw.org/en/1.10.1/)
  • a wiki also exists (https://github.com/geopython/pycsw/wiki)

2. The project has developer documentation:

• [x] Including checkout and build instructions.
  • yes, checkout and build instructions are outlined with examples: http://docs.pycsw.org/en/1.10.1/installation.html#installing-from-source
• [x] Including commented code, ideally published for developer use. Examples: javadocs for Java applications, or Sphinx documentation for Python applications.
  • yes, code examples are published through the Sphinx documentation framework, allowing visually pleasing code examples (https://github.com/geopython/pycsw/blob/master/docs/profiles.rst)
• [x] Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions.
  • yes, including Coding Guidelines, as well as GitHub Commit Guidelines (http://docs.pycsw.org/en/1.10.1/contributing.html)

Release Procedure

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

1. The project follows a defined release process:

• [x] Which includes execution of the testing process before releasing a stable release.
  • yes, the full release process is documented step-by-step (https://github.com/geopython/pycsw/wiki/Release-Packaging)
  • the second step of the release process is to make sure the source passes all OGC CITE tests (steps to run own tests at https://github.com/geopython/pycsw/wiki/OGC-CITE-Compliance)
  • release plans are documented (https://github.com/geopython/pycsw/wiki/Release-Plans)

2. The project follows a documented testing process.

• [x] Ideally, this includes both automated and manual testing
  • yes, automated testing through travis-ci (http://travis-ci.org/#!/geopython/pycsw) occurs, so that every commit to master must pass
  • manual testing occurs through the OGC-CITE tests
  • integration tests also occur as part of downstream tools like CKAN and GeoNode
  • unit tests exist at https://github.com/geopython/pycsw/tree/master/tester
• [x] Ideally this includes documented conformance to set quality goals, such as reporting Percentage Code Coverage of Unit Tests.
  • yes, as pycsw is the OGC CSW reference implementation, therefore the goal is always 100% OGC compliance.

3. [x] Release and testing processes provide sufficient detail for an experienced programmer to follow.

• yes, as noted above

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:

1. [x] A project provide a Project Officer as a contact point:

• the project officer is Angelos Tzotsos
• The Project Officer should be listed at Officers and Board of Directors and Contacts
• This person is established when the incubation committee recommends the project for graduation
• Your community can change the project officer as needed. Add an agenda item to the next board meeting so they can recognise the change of officer.

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:

1. [x] Marketing artefacts have been created about the project in line with the incubation criteria listed in the OSGeo Marketing Committee's Marketing Artefacts. This lists the documentation requirements for OSGeo-Live. Marketing Artefacts include:

• Application Overview
• Application Quick Start
• Logo
• Graphical Image

2. [x] Ideally, stable version(s) of executable applications are bundled with appropriate distributions. In most cases, this will at least include OSGeo-Live, but may also include DebianGIS, UbuntuGIS, and/or osgeo4w, ms4w, etc.)

• pycsw is part of OSGeo-Live, UbuntuGIS, and DebianGIS, openSUSE Application:Geo, PyPI. See http://pycsw.org/download/

Projects

[x] Projects do not exist in isolation; and are expected to communicate and collaborate on key issues.

As an example the PostGIS release procedure asks that the release be checked with MapServer, GeoServer and others.

• pycsw works with projects such (upstream: Shapely, OWSLib, pyproj; downstream: CKAN, GeoNode, Open Data Catalog)

SAC

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

1. [ ] The following should be set up:

• A http://pycsw.osgeo.org domain name
• not requested: the osgeo.org website should link to pycsw.org

2. [x] A project may optionally request SAC help to make use of:

• OSGeo issue tracker
• OSGeo mailing list
• OSGeo svn
• http://downloads.osgeo.org
• Done. pycsw uses http://download.osgeo.org/pycsw for downloads, http://lists.osgeo.org/pipermail/pycsw-devel for mailing list, and the Projects VM for http://demo.pycsw.org. SCM and issue tracker and wiki via GitHub. Full details are at https://github.com/geopython/pycsw/wiki/Technical-Infrastructure .