OSGeoIncubation ProjectStatus - geopython/pygeoapi GitHub Wiki

Document Status

Version: 1.2

Purpose

The project representative and mentor will use this template to inform the IncCom of pygeoapi project status on a periodic basis. The state of the pygeoapi project, as reported using this template, will be the initial indication that pygeoapi is reaching graduation.

General

• Has the project been approved for incubation by the OSGeo board?

  Yes

• Has an Incubation Mentor been assigned to the project?

  Yes (Mike Smith - @msmitherdc)

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?

  Yes: https://www.osgeo.org/projects/pygeoapi. A direct link to https://pygeoapi.io is also used from the main osgeo.org home page, via the "Projects -> Community Projects" menu.

• Is the OSGeo bug tracker being used for the project?

  No, issues are hosted on GitHub, which allow reference to / from source code. GitHub bug tracker hosting is common for numerous OSGeo projects (eg. MapServer, OpenLayers, QGIS, pycsw, PyWPS)

• Is the OSGeo mailing list manager (https://lists.osgeo.org) being used for the project?

  Yes (https://lists.osgeo.org/mailman/listinfo/pygeoapi). There are currently 30 registered members. The current primary communication vehicle is Gitter (we also have GitHub discussions and matrix to Slack/IRC).

• Is the OSGeo SVN being used for the project?

  No, pygeoapi uses Git/GitHub (https://github.com/geopython/pygeoapi) for source code management, wiki and issues.

• Are binary and source downloads available from https://download.osgeo.org?

  No, pygeoapi releases are made available on the Python Package Index (PyPI) and GitHub releases

Community Functioning

• Is there a functioning user support mechanisms (ie. mailing list)? indicate the available user support mechanisms, and whether they seem to be functioning well (are getting used and get answers).

  Yes. The Gitter channel is very active. There are also a number of discussions as part of issue tracking and pull requests.

• Are source and binary downloads for the package available?

  Yes. Source is available at https://pygeoapi.io/download. pygeoapi is available on the OSGeo-Live project (https://live.osgeo.org/en/overview/pygeoapi_overview.html), and packages exist for PyPI, Docker, Conda, UbuntuGIS, and FreeBSD.

• Has a Project Steering Committee been formed, and given control of the project?

  Yes. A PSC was formed as part of RFC1 in 2019-10. The PSC is currently 6 members from various projects, organizations and countries.

• Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines, etc.

  Yes, see RFC1

• How many active developers are there? Are they from multiple organizations?

  • Number of active developers: 5 (more or less, over time)
  • Organizations: National Technical University of Athens, GeoBeyond, ISRIC, Just Objects, Meteorological Service of Canada, United States Geological Survey, volunteer contributors

  Over time, months there have been numerous contributors to the project (both core committers and via contributions/pull requests

  • OpenHub: https://www.openhub.net/p/pygeoapi/contributors/summary)
  • GitHub contributors: https://github.com/geopython/pygeoapi/graphs/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 OSGeo Community project logo is visible on the project homepage. Project presentations also identify pygeoapi's OSGeo project status.

• Has an effort been made to brand the project web site with OSGeo foundation web styling and branding marks?

  The website will contain an "OSGeo: Project in Incubation" graphic once accepted for Incubation (bottom right of https://pygeoapi.io)

Code Copyright Review

• Has a Code Provenance Review document been prepared for the project?

  Yes

• Have issues raised in the provenance review been adequately addressed?

  N/A

• Are Committer Responsibilities Guidelines covering legal issues in place?

  No