Changes between Version 13 and Version 14 of HowToContribute


Ignore:
Timestamp:
May 7, 2008, 6:37:47 AM (16 years ago)
Author:
neteler
Comment:

more text

Legend:

Unmodified
Added
Removed
Modified

  • HowToContribute

    v13 v14  
    11[[TOC]]
     2
     3Contributions to GRASS are most welcome. There are a number of ways that you can contribute to help make GRASS a better GIS system. Perhaps the most important way to contribute is to write high-quality code for solving old and new problems, and to make your code freely available for others to use. But not everybody is able to program. Still you can help!
    24
    35== (Power) Users ==
    46
    5 Subscribe to the [http://lists.osgeo.org/mailman/listinfo/grass-dev mailing list] and answer questions where you have gained some knowledge (and everybody knows something!).
     7'''Documentation:''' If you see manual pages or other documents which are outdated, grammatically incorrect, too short, lacking examples, etc. please don't hesitate to send revised text segments (preferably in HTML) to one of the developers or the related mailing list. Please also contribute to the wiki, improving documentation, providing examples...
    68
    7 Contribute to the wiki, improving documentation, providing examples, write [wiki:HowToProgram source code], fix [http://trac.osgeo.org/grass/query?status=%21closed&type=defect&order=id&desc=1 bugs] etc.
    8 
     9'''GRASS Usage:''' Subscribe to the [http://lists.osgeo.org/mailman/listinfo/grass-dev mailing list] and answer questions where you have gained some knowledge (and everybody knows something!).
    910
    1011== Developers ==
    1112
    12 Using the Ticket system is the best way to submit code contributions. See for example #33.
     13For inspiration, we have a wish-list of [report:1 projects and feature requests]. Just pick a task from the list. It may be a good idea to send a small posting to the [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list] to announce your activities (maybe someone will join you!). Please read [wiki:HowToProgram how to write source code]. We appreciate if you can fix [http://trac.osgeo.org/grass/query?status=%21closed&type=defect&order=id&desc=1 bugs] etc. Using the Ticket system is the best way to submit code contributions if you don't have write access to SVN. See for example #33.
    1314
    14 '''Code quality:''' Check Your code according to GRASS "BestPractise" guide list.
     15'''Code quality:''' Check your code according to GRASS "BestPractise" guide list.
    1516
    1617What else: see [http://grass.gdf-hannover.de/wiki/Development development collection] (to be moved here)