contribute

Contribute to Open Source Geospatial

2014 OSGeo code print in Wien

Report a bug or enhancement wish

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.

Some recommendations

  • Check if the bug you found is still present in the current stable release version or, better, in the “master” version before reporting. If you use an older version, please consider to upgrade first.
  • Make sure that the developers have all the information needed to reproduce the bug (e.g. explain how to reproduce the bug using the North Carolina example dataset)
  • Report only a single bug or feature request with each issue
  • Before reporting a bug, please check that it hasn’t been reported already in the GRASS GIS bugtracking system
We recommend to read How to Report Bugs Effectively by Simon Tatham.

Documentation

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.

Translation

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! See below how to join.

Want to join?

Great! Please subscribe to the dedicated mailing list and check the messages translation Wiki page on how we translate on Transifex.

Create an Addon

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.

Contribute to GRASS GIS core

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.

Mirror our website

Please consider to contact us, ideally reporting your already running mirror.

Requirements:

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.

How to set up a mirror site:

The master 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.

Mirror site setup in greater detail:

  • Install the rsync software.
  • Check if you can connect - note the two ‘::’ characters (this command should display a welcome message):
    • rsync -az --port=50026 grass.osgeo.org::grass-website grass-website
  • Define a daily cron-job (in ‘crontab’) for rsync (example):
    • /usr/bin/rsync -az --port=50026 grass.osgeo.org::grass-website /mirror/grass-website
      This will copy/update the GRASS site to your local directory /mirror/grass-website/ which needs to be made available in your web server.
  • Check if the synchronization works the next day(s).
  • Announce the new mirror site for this mirror list to us.

Other opportunities

Google Summer of Code (GSoC)

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.

Google Code-in (GCI)

GCI is an online contest introducing high school students to open source development.

Students can participate with the OSGeo organization and solve tasks for different projects. Tasks might include documentation, design, coding, etc.

Cite GRASS GIS

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.