GRASS ToDo List: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
This page should help those that are interested in helping with GRASS find a project they can work on. If you decide to work on any of the tasks, please announce it on the | This page should help those that are interested in helping with GRASS find a project they can work on. If you decide to work on any of the tasks, please announce it on the [http://grass.itc.it/mailman/listinfo/grass5 GRASS Developers list] and add a note here on this page. | ||
==Bug reporting== | ==Bug reporting== | ||
When you encounter a problem using GRASS, first read the documentation, then ask on the users list. If the problem seems to be a bug with GRASS and not a usage error, file a bugreport in the | When you encounter a problem using GRASS, first read the documentation, then ask on the users list. If the problem seems to be a bug with GRASS and not a usage error, file a bugreport in the [http://grass.itc.it/bugtracking/bugreport.html GRASS bug tracker]. Please fill in all the fields and be as precise as possible in your error description (for example: do not write "it does not work", but "I get the following error message: xxx"). | ||
==Development== | ==Development== | ||
| Line 9: | Line 9: | ||
With the release of GRASS 5.4 and 6.0, development will focus on 6.1. You can participate in development in the following ways: | With the release of GRASS 5.4 and 6.0, development will focus on 6.1. You can participate in development in the following ways: | ||
* fixing bugs - see the | * fixing bugs - see the [http://intevation.de/rt/webrt?q_sort=age&q_reverse=1&q_queue=grass GRASS bug tracker] | ||
* new ModulePortingList - porting status from 5.3 to 5.7 | * new ModulePortingList - porting status from 5.3 to 5.7 | ||
* implementing new features - check out the | * implementing new features - check out the [http://intevation.de/rt/webrt?q_sort=area&q_reverse=1&q_queue=grass Grass wish list] | ||
==GUI development== | ==GUI development== | ||
Since 5.7 GRASS has one internal GUI, the GIS Manager (d.m), a tcl/tk interface to the GRASS modules. | Since 5.7 GRASS has one internal GUI, the GIS Manager (d.m), a tcl/tk interface to the GRASS modules. | ||
Recent development has been towards the integration of access to GRASS data from general cartographic viewers, such as | Recent development has been towards the integration of access to GRASS data from general cartographic viewers, such as [http://www.qgis.org/ Quantum GIS] (already implemented) and [http://thuban.intevation.org/ Thuban] (on the roadmap?). | ||
So, you can help either with: | So, you can help either with: | ||
* GIS Manager (contact Michael Barton via the | * GIS Manager (contact Michael Barton via the [http://grass.itc.it/mailman/listinfo/grass5 developers list] | ||
* integration of GRASS access into other software (see respective web sites) | * integration of GRASS access into other software (see respective web sites) | ||
| Line 32: | Line 32: | ||
==Translation== | ==Translation== | ||
* check out the | * check out the [http://grass.itc.it/devel/i18n.php GRASS messages translation project (i18N)] if you want to help translating internal GRASS messages | ||
* translate man pages | * translate man pages | ||
* [%ATTACHURL%/grass57-install-run.txt][grass57-install-run.txt] (partially outdated) | * [%ATTACHURL%/grass57-install-run.txt][grass57-install-run.txt] (partially outdated) | ||
Revision as of 12:03, 19 May 2006
This page should help those that are interested in helping with GRASS find a project they can work on. If you decide to work on any of the tasks, please announce it on the GRASS Developers list and add a note here on this page.
Bug reporting
When you encounter a problem using GRASS, first read the documentation, then ask on the users list. If the problem seems to be a bug with GRASS and not a usage error, file a bugreport in the GRASS bug tracker. Please fill in all the fields and be as precise as possible in your error description (for example: do not write "it does not work", but "I get the following error message: xxx").
Development
With the release of GRASS 5.4 and 6.0, development will focus on 6.1. You can participate in development in the following ways:
- fixing bugs - see the GRASS bug tracker
- new ModulePortingList - porting status from 5.3 to 5.7
- implementing new features - check out the Grass wish list
GUI development
Since 5.7 GRASS has one internal GUI, the GIS Manager (d.m), a tcl/tk interface to the GRASS modules. Recent development has been towards the integration of access to GRASS data from general cartographic viewers, such as Quantum GIS (already implemented) and Thuban (on the roadmap?).
So, you can help either with:
- GIS Manager (contact Michael Barton via the developers list
- integration of GRASS access into other software (see respective web sites)
Documentation
- correct and enhance man pages (see ManContribHowTo)
- compile a FAQ (more complete than GrassFAQPage)
- write a beginners tutorial for GRASS 6 (already done in German, currently being translated to english, FDL)
- write HOWTOs on specific tasks
Translation
- check out the GRASS messages translation project (i18N) if you want to help translating internal GRASS messages
- translate man pages
- [%ATTACHURL%/grass57-install-run.txt][grass57-install-run.txt] (partially outdated)