In support of an inclusive and welcoming community, the PyWPS code of conduct can always be found at https://github.com/geopython/pywps/blob/develop/CODE_OF_CONDUCT.md.
The pywps-dev mailing list enables users and developers to exchange ideas, discuss improvements / issues, and ask questions. To subscribe, visit http://lists.osgeo.org/mailman/listinfo/pywps-dev.
Mailing list archives are available at http://lists.osgeo.org/pipermail/pywps-dev. The mailing list is also available/searchable via the OSGeo Nabble forum.
PyWPS exists as a Google+ community. Join us there for news, discussion, and more.
PyWPS has Twitter account. You can also use #pywps hashtag for tweets associated with PyWPS topic.
Most of the developers are available via IRC channels #grass
and #geopython
on Freenode.
The PyWPS wiki provides an area for supporting information that frequently changes and / or is outside the scope of the formal documentation.
PyWPS’ 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 PyWPS, although patches and other mechanisms are welcome as well.
All PyWPS source code is managed on GitHub, which includes the latest (master) and other supported branches.
If you are offering professional support for PyWPS, feel free to contact us and we will ad your name here:
OpenGeoLabs is private company (limited company), registered in Czech republic. We are focused on workshops and development around open source software for geospatial (FOSS4G), especially GRASS GIS, PyWPS, web mapping and generic GeoPython topics. | Website | Email | |
Your logo | detailed info of your company or yourself |
PyWPS service providers (core development, support, training) can also be found on the OSGeo Service Provider Directory.