Version 6 (modified by neteler, 15 years ago) ( diff )

link to DownloadSource

(Power) Users

Subscribe to the mailing list and answer questions where you have gained some knowledge (and everybody knows something!).

Contribute to the wiki, improving documentation, providing examples, etc.


Using the Ticket system is the best way to submit code contributions. See for example #33.

Code quality: Check Your code according to GRASS "BestPractise" guide list.

What else: see development collection (to be moved here)

Procedure to request GRASS-SVN write access

The GRASS Project Steering Commitee is responsible for granting SVN write access to contributors (as defined in RFC1).

Setting up the new SVN write access

Once SVN access is granted, the requestor needs to obtain an "osgeo_id" at If s/he already have an "osgeo_id" but forgot it, it can be searched at The GRASS-PSC chair (currently Markus Neteler) and other developers can add this "osgeo_id" to the OSGeo LDAP authentication system.

Contributions have to follow the BestPractise rules (see also SUBMITTING* files in the source code).

Then what?

Get the source code and Happy hacking :) The requester should subscribe to the grass-commit mailing list which distributes GRASS-SVN commit differences for real-time code review.

Note: See TracWiki for help on using the wiki.