When developing GRASS software, you may want to share your development with the GRASS community. There are several ways to probably get your code into the standard GRASS release. Another option is to host the software on your own web page - in this case we can add a link to our "GRASS Add-ons" section. We strongly recommend you follow the coding style described in SUBMITTING files (which you find in the GRASS source code). Optionally, for group based development we can offer access to the GRASS AddOns-SVN repository which we grant to trustable people who agree to the GRASS rules of code contributions (see below):
  • Legal aspects of code contributions (RFC2): these rules have to be accepted to gain SVN write access.
  • C language coding standards: Check your code against the rules defined in the 'SUBMITTING' file (find it in the main directory of the GRASS source code and also SUBMITTING). This ensures a smooth integration into the standard GRASS code base.
  • Shell script coding standards: Check your code against the rules defined in the 'SUBMITTING_SCRIPTS' file (find it in the main directory of the GRASS source code and also SUBMITTING_SCRIPTS). This ensures a smooth integration into the standard GRASS code base and avoids portability problems.
  • Python coding standards: Check your code against the rules defined in the 'SUBMITTING_PYTHON' file (currently developed here).
  • Code submission: Please contact a member of the GRASS Development Team or write to the development mailing list (see above).
    In general, please generate differences to the current SVN instead of sending full files:
    svn diff -x -u [file.c] > grass.diff
    Please submit the patch to GRASS-trac.
  • GRASS Add-on Wiki submission: go here (Add-on code is hosted on your server).
  • GRASS Add-on SVN repository: We maintain a SVN repository for group-wide code development. You can ask the developers for write access, but you have to agree to the Legal aspects of code contributions (RFC2) and the code SUBMITTING standards (see in the SVN repository).

GRASS Quality Control

The development team invests time and efforts to verify the quality of GRASS, be the coding style, be the functionality of the commands:

Development >> Code submission | Last change: 01-Dec-2013