Community

pycsw is used in government, academia and industry, both as a standalone and embedded component in geospatial data portal applications such as GeoNode and Open Data Catalog.

FAQ

The FAQ provides answers to commonly asked questions about pycsw.

Mailing List

The pycsw-devel mailing list enables users and developers to exchange ideas, discuss improvements / issues, and ask questions. To subscribe, visit http://lists.osgeo.org/mailman/listinfo/pycsw-devel.

Mailing list archives are available at http://lists.osgeo.org/pipermail/pycsw-devel.

IRC

Internet Relay Chat (IRC) allows for real-time communication and group discussion. The pycsw IRC channel can be found at:

• Server: irc.freenode.net
• Channel: #geopython
• Port: 6667

pycsw developers can be found in the IRC channel. Below are some suggested IRC clients:

• Chatzilla (Firefox)
• Colloquy (Mac OS)
• irssi (Terminal-based)

GitHub (Wiki, Issues, Code)

The pycsw wiki provides an area for supporting information that frequently changes and / or is outside the scope of the formal documentation.

pycsw’s 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. For convenience, you can run sbin/pycsw-admin.py -c get_sysprof and copy/paste the output into your bug report.

GitHub provides the ability for users to issue pull requests, and is the preferred way to have your contributions added to pycsw, although patches and other mechanisms are welcome as well. If you are submitting a patch, please add the has-patch label to the ticket (so tickets with patches can be easily filtered). Also read the FAQ before submitting.

All pycsw source code is managed on GitHub, which includes the latest (master) and other supported branches.

Getting Involved

Users, developers and others are more than welcome! There are plenty of ways to get involved:

• Developers (check Development for more info)

• adding new functionality
• fixing issues
• adding unit tests

• Users

• reporting bugs
• testing
• documentation