Community Development

The GeoServer team channels of communication. If you are interested in joining the team please contact us!

Mailing List

Email is the primary form of communication for GeoServer developers. Being an open community means that sending email to individual developers is discouraged. Instead all email communication should take place on one of the email lists. If you have a question are chances are someone else has the same question.

If you are not in position to communicate in public please contact one of our commercial support vendors.

Developer List

This list is for developers to discuss topics related to GeoServer development. If you're knee deep in the code it's the place to email. Traffic can be high, as we try to make most all conversations public so people know what's going on.
Do not report security vulnerabilities here. See the "Responsible disclosure" instructions.

  • List archive from SourceForge and signup
  • Alternate archive from nabble
  • After subscribing you can post at

The same OSGeo code of conduct and post guidelines as the user list apply to the developer list.

Developer Manual

The GeoServer Developer Manual describes the project including source code, how to build, software translation, development process, software releasing, and other administrative work.

A Documentation Manual is available with writing guidelines and tips.

GeoServer Meeting

The GeoServer team attend a 1 hour bi-weekly video chat. This is call is primarily for project steering committee to discuss day to day project management issues but all developers who are actively engaged in GeoServer development are welcome. If you wish to attend contact the developer list.

This is a suitable venue for responsible disclosure of security issues.

Monthly Bug Stomp

The GeoServer team has setup a bug stomp to work on GeoServer maintenance activities on the last Friday of each month. If you would like to take part please introduce yourself on the developper list - we look forward to working with you.