The strength and success of GRASS relies on the user community. With this in mind, the philosophy of the GRASS Development Team is to encourage users to develop their own unique tools and applications for GRASS. If you develop tools and techniques that you feel would benefit other GRASS users, let us know!

Because GRASS is an open system, anyone may develop applications and programs. However, if you would like your tools to be considered for future GRASS releases, please include the following when you place your files on the ftp server:

• All files in a single .tar file. For example: mycode.tar
• Comment your source code here and there.
• Manual page in nroff/troff format and/or plain ASCII text.
• A brief README file if appropriate.

• Tell others about GRASS. They may use GRASS, distribute and improve it (hopefully they will tell us about it).

• If you are programmer, please assist us in bug-fixing. The latest bug list is available in the experimental source directory. Or you
  get the online GRASS 5 buglist.

  And you can join the GRASS GIS Developers Forum. Read on here, what you can do.

• Perhaps you want to contribute your development(s) to be included in the standard package? You are welcome, too!
  Please contact Markus Neteler, who is coordinating the GRASS 5 development.

• Still developing in GRASS 4.x? Want to include a package? Contact Bruce Byars, who is coordinating the GRASS 4.x development.

• But most important is testing. We are always interested in reports concerning bugs in GRASS. And if you have suggestions to improve a module (maybe the menu or anything else), please talk to us as well.
  You may use our small bug tracking form (additionally to the bug information we need to know which system you are using)

Further programming instructions

Send your GRASS related email