Community
Code of Conduct
In support of an inclusive and welcoming community, the pygeoapi code of conduct can always be found at https://github.com/geopython/pygeoapi/blob/master/CODE_OF_CONDUCT.md.
There are numerous ways to interact with the pygeoapi community.
Mailing List
The pygeoapi mailing list enables users and developers to exchange ideas, discuss improvements / issues, and ask questions. To subscribe, visit https://lists.osgeo.org/mailman/listinfo/pygeoapi.
Mailing list archives are available at https://lists.osgeo.org/pipermail/pygeoapi.
GitHub Discussions
pygeoapi also provides GitHub Discussions as a collaborative community space for general questions, ideas, and more.
Chat
pygeoapi provides open communication in real-time, and provides chat via Gitter, Slack, or IRC (note: connecting via either Gitter or Slack or IRC plugs you in to the same chat).
PSC discussions, meetings and user discussion can typically be found in pygeoapi's chat.
Gitter
Gitter provides a web-based instant messaging and chatroom. The pygeoapi Gitter chatroom is public and open to anyone.
Slack
The OSGeo Slack is provided at https://osgeo.slack.com/pygeoapi.
IRC
The pygeoapi IRC can be found at irc://irc.freenode.net#pygeoapi.
For those wishing only to follow repository changes/updates, the pygeoapi-activity IRC can be found at irc://irc.freenode.net#pygeoapi-activity.
The official pygeoapi Twitter handle is at https://twitter.com/pygeoapi.
Mastodon
The official pygeoapi Mastodon handle is at https://noc.social/@pygeoapi.
Stack Overflow
pygeoapi discussions on Stack Overflow can be found with the pygeoapi tag.
Service Providers
pygeoapi service providers (core development, support, training) can be found on the Service Providers page.
Service providers are also listed on the OSGeo Service Provider Directory.
Swag
pygeoapi swag (t-shirts, hoodies, stickers, etc.) are available and can be purchased via the OSGeo Redbubble shop.
GitHub (Wiki, Issues, Code)
The pygeoapi wiki provides an area for supporting information that frequently changes and / or is outside the scope of the formal documentation.
The pygeoapi issue tracker is the place to report bugs or request enhancements. To submit a bug be sure to specify the version you are using, the appropriate component, a description of how to reproduce the bug, as well as what version of Python and platform.
GitHub provides the ability for users to issue pull requests, and is the preferred way to have your contributions added to pygeoapi, although patches and other mechanisms are welcome as well.
All pygeoapi source code is managed on GitHub, which includes the latest (master) and other supported branches.
Security issues
If you encounter a security vulnerability in pygeoapi please report as per our Security Policy
Getting Involved
Users, developers and others are more than welcome! There are plenty of ways to get involved:
- Documentation
- Fixing bugs
- Testing
- Core development (bug fixing, feature implementation, etc.)
See https://github.com/geopython/pygeoapi/blob/master/CONTRIBUTING.md for more information on contributing.