Switch branches/tags
debian/2.10.0+rc4 debian/2.10.0+rc3 debian/2.10.0+rc2 debian/2.10.0+rc1 debian/2.10.0+rc0 debian/2.8.1+rc0 debian/2.8.0+thefinal0 debian/2.8.0+rc13 debian/2.8.0+rc12 debian/2.8.0+rc11 debian/2.8.0+rc10 debian/2.8.0+rc9 debian/2.8.0+rc8 debian/2.8.0+rc7 debian/2.8.0+rc6 debian/2.8.0+rc5 debian/2.8.0+rc4 debian/2.8.0+rc3 debian/2.8.0+rc2 debian/2.8.0+rc1 debian/2.8.0+rc0 debian/2.7.5+dev20180124154147 debian/2.7.5+dev20180123112419 debian/2.7.4+dev20171114153121 debian/2.7.2+dev20171013181704 debian/2.7.1+dev20171013111656 debian/2.7.0+thefinal0 debian/2.6.3+thefinal0 debian/2.6.2+thefinal0 debian/2.6.1+thefinal0 debian/2.6.0+thefinal0 debian/2.6.0+rc1 debian/2.6.0+beta1 debian/2.6.0+alpha1 debian/2.5.15+thefinal0 debian/2.5.14+thefinal0 debian/2.5.13+thefinal0 debian/2.5.12+thefinal0 debian/2.5.11+thefinal0 debian/2.5.10+thefinal0 debian/2.5.9+thefinal5 debian/2.5.9+thefinal4 debian/2.5.9+thefinal3 debian/2.5.9+thefinal2 debian/2.5.9+thefinal1 debian/2.5.9+thefinal0 debian/2.5.9+dev20170116091118 debian/2.5.7+thefinal0 debian/2.5.6+thefinal0 debian/2.5.5+thefinal0 debian/2.5.4+thefinal0 debian/2.5.3+thefinal0 debian/2.5.2+thefinal0 debian/2.5.1+thefinal0 debian/2.5.0+thefinal0 debian/2.4.1+thefinal1 debian/2.4.0+thefinal0 debian/2.4.0+rc4 debian/2.4.0+rc3 debian/2.4.0+rc2 debian/2.4.0+rc1 debian/2.4.0+dev20141024171719 debian/2.4.0+beta28 debian/2.4.0+beta27 debian/2.4.0+beta26 debian/2.4.0+beta25 debian/2.4.0+beta24 debian/2.4.0+beta23 debian/2.4.0+beta22 debian/2.4.0+beta21 debian/2.4.0+beta20 debian/2.4.0+beta19 debian/2.4.0+beta18 debian/2.4.0+beta17 debian/2.4.0+beta16 debian/2.4.0+beta15 debian/2.4.0+beta14 debian/2.4.0+beta13 debian/2.4.0+beta12 debian/2.4.0+beta11 debian/2.4.0+beta10 debian/2.4.0+beta9 debian/2.4.0+beta8 debian/2.4.0+beta7 debian/2.4.0+beta6 debian/2.4.0+beta5 debian/2.4.0+beta4 debian/2.4.0+beta3 debian/2.4.0+beta2 debian/2.4.0+beta1 debian/2.4.0+alpha38 debian/2.4.0+alpha37 debian/2.4.0+alpha36 debian/2.4.0+alpha35 debian/2.4.0+alpha34 debian/2.4.0+alpha33 debian/2.4.0+alpha32 debian/2.4.0+alpha31 debian/2.4.0+alpha30 debian/2.4.0+alpha29
Nothing to show
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
75 lines (52 sloc) 3.6 KB
.. _contrib:
Contributing to GeoNode
.. warning:: This section is freely adapted from the official `GitHub guides <>`_.
If you are interested in helping us to make GeoNode, there are many ways to do so.
Participate in the Discussion
GeoNode has a mailing list ( where users can ask and answer questions about the software.
There are also IRC chats on Gitter where users ( and developers ( can discuss GeoNode in real time.
Sometimes users also post interesting tips for managing sites running GeoNode.
If you want to help out with GeoNode, one easy way is to sign up for the mailing list and help answer questions.
Report Problems on the Issue Tracking System
Informative bug reports are a key part of the bug fixing process, so if you do run into a problem with GeoNode, please don't hesitate to report it on our bug tracker, available online at
Useful information for bug reports includes:
* What were you doing when the bug occurred?
Does the problem occur every time you do that, or only occasionally?
* What were you expecting to happen?
What happened instead?
* What version of the software are you using?
Please also note any changes from the default configuration.
* If there is a data file involved in the bug (such as a Shapefile that doesn't render properly), please consider including it in the bug report.
Be aware that not all data files are freely distributable.
To help GeoNode address the issue, you can tag the ticket with one or more labels
that you can find on the side column.
Write Documentation
GeoNode's documentation can always use improvement - there are always more questions to be answered.
For managing contributions to the manual, GeoNode uses a process similar to that used for managing the code itself.
The documentation is generated from source files in the `docs/` directory within the GeoNode source repository.
See for more information on the documentation system GeoNode uses.
If you want to learn more about contributing to the documentation, please go ahead to the "`How to contribute to GeoNode's Documentation <>`_".
GeoNode also have some guidelines to help with writing once you are set up "`How to write Documentation <>`_".
Provide Translations
If GeoNode doesn't provide a user interface in your native language, consider contributing a new translation.
To get started here are the instructions "`How to contribute to GeoNode's Translation <>`_".
Write Code
Of course since GeoNode is an open source project which encourages contributions of source code as well.
If you are interested in making small changes, you can find an open ticket on, hack away, and get started on the "`Patch Review Process <>`_".
Further Reading
.. toctree::