Bug reports and feature requests can be submitted as issues in the GRASS GIS bugtracking system. All new submissions in the tracker will be automatically forwarded to the GRASS GIS development mailing list.
Each GRASS GIS module comes with a respective manual page that provides clear and up-to-date documentation including working examples.
There are also several tutorials, courses and wikis contributed by different developers and users. These are a very important tool to learn how to use GRASS GIS, too.
Writing or editing documentation and tutorials is an ideal platform for your first contribution to the project.
The great worldwide interest in GRASS suggests value in translating GRASS messages to languages other than English. The GRASS Development Team is continuously seeking translators.
This is an opportunity to contribute even for non-programmers since messages can be easily translated in a user friendly platform. No programming skills required!
Great! Just sign in into weblate, pick the GRASS GIS project and start translating. The interface is really simple to use and all the changes you make will be automatically sent as a pull request to the GRASS GIS repository. Please also subscribe to the dedicated mailing list and check the translation glossary for agreed terminology in different languages.
Developing your own modules? Great!
Please upload your add-ons to the GRASS GIS Addons repository. In this way, they become available to the community through the extension manager (g.extension or graphical user interface). Here is the full list of existing addons to get inspired.
Further details about how to gain access to our GitHub Addons repository can be found in this document.
The GRASS GIS core consists of the libraries used by GRASS GIS modules and GUI, as well as the code used to develop the Graphic User Interface and the most important modules.
It may be a good idea to send a small posting to the GRASS developers mailing list to announce your activities (maybe someone will join you!). Please read how to write source code before submitting.
We’d also appreciate if you could support us with bug fixing and enhancement wishes.
Please consider to contact us, ideally reporting your already running mirror.
A GRASS mirror site requires around 14 GB space, the space requirements may vary due to the changing presence of precompiled binaries. If you would like to support the GRASS community, do not hesitate to set up your mirror site.
The main site hosted at OSGeo (grass.osgeo.org) can be mirrored with the “rsync” software protocol, allowing to synchronize mirrors automatically overnight. The idea of using “rsync” mirror software is that only changed files are transferred which minimizes the network traffic.
Check if you can connect - note the two ‘::’ characters:
rsync -az --port=50026 grass.osgeo.org::
This command should display the following welcome message:
GRASS GIS Website grass-website GRASS GIS Website
Now generate a mirror folder on your server where to store the GRASS GIS website copy. We assume
Change into this folder and copy the website into the subfolder
rsync -az --port=50026 grass.osgeo.org::grass-website grass-website
Once finished, define a daily cron-job (in ‘crontab’) for rsync (example):
/usr/bin/rsync -az --port=50026 grass.osgeo.org::grass-website /var/www/html/mirror/grass-website
Check if the synchronization works the next day(s).
Announce the new mirror site for this mirror list to us.
Student Grants is a stipend program for students by the GRASS GIS project.
The GRASS GIS project offers a limited number of student grants for projects related to GRASS GIS. These can include actual coding, bug fixing, or documentation and the creation of educational resources.
GSoC is a stipend program for students by Google.
Students are encouraged to propose their own ideas. Otherwise, they can choose from the GRASS GSoC Ideas list. If selected, Google will pay a monthly stipend for 3 months.
If you use GRASS GIS for developing applications, products or for your scientific work, please cite it properly to raise awareness and visibility of the multiple uses of the software.
Have a look at our Google Scholar profile for examples of applications in the most diverse fields.