Changes between Version 3 and Version 4 of HowToContribute


Ignore:
Timestamp:
Mar 26, 2008, 7:58:17 AM (14 years ago)
Author:
neteler
Comment:

extended

Legend:

Unmodified
Added
Removed
Modified
  • HowToContribute

    v3 v4  
    1 == Developers ==
    2 
    3 Using the Ticket system is the best way to submit code contributions. See for example #33.
    4 Check Your code according to GRASS "BestPractise" guide list.
    5 
    6 == Users ==
     1== (Power) Users ==
    72
    83Subscribe 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!).
    94
    105Contribute to the wiki, improving documentation, providing examples, etc.
     6
     7
     8== Developers ==
     9
     10Using the Ticket system is the best way to submit code contributions. See for example #33.
     11
     12'''Code quality:''' Check Your code according to GRASS "BestPractise" guide list.
     13
     14What else: see [http://grass.gdf-hannover.de/wiki/Development development collection] (to be moved here)
     15
     16=== Procedure to request GRASS-SVN write access ===
     17
     18The [http://grass.gdf-hannover.de/wiki/PSC GRASS Project Steering Commitee] is responsible for granting SVN write access to contributors (as defined in [http://download.osgeo.org/grass/grass6_progman/rfc/rfc1_psc.html RFC1]).
     19 * The requestor has to '''read and abide by''' the document [http://download.osgeo.org/grass/grass6_progman/rfc/rfc2_psc.html Legal aspects of code contributions] (RFC2).
     20 * The request has to be send to the GRASS-PSC mailing list, stating that RFC2 was read and accepted. This requires [http://lists.osgeo.org/mailman/listinfo/grass-psc subscription] to the mailing list.
     21
     22=== Setting up the new SVN write access ===
     23
     24Once SVN access is granted, the requestor needs to obtain an "osgeo_id" at http://www.osgeo.org/osgeo_userid
     25If s/he already have an "osgeo_id" but forgot it, it can be searched at http://www.osgeo.org/cgi-bin/ldap_web_search.py
     26The GRASS-PSC chair (currently Markus Neteler) and other developers can add this "osgeo_id" to the OSGeo LDAP authentication system.
     27
     28Contributions have to follow the [wiki:BestPractise] rules (see also SUBMITTING* files in the source code).
     29
     30=== Then what? ===
     31
     32Happy hacking :) The requestor should subscribe to the [http://lists.osgeo.org/mailman/listinfo/grass-commit grass-commit] mailing list which distributes GRASS-SVN commit differences for real-time code review.
     33