Changes between Version 10 and Version 11 of HowToContribute


Ignore:
Timestamp:
Apr 30, 2008, 4:58:48 PM (14 years ago)
Author:
neteler
Comment:

links added to easier find a developer; added "sponsor/mentor" for GRASS-Addons-SVN

Legend:

Unmodified
Added
Removed
Modified
  • HowToContribute

    v10 v11  
    1919
    2020 * '''Main GRASS-SVN repository:'''
    21    * In general, the [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]).
    22       * 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).
    23       * 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. If granted, SVN write access is set up (see below).
     21   * In general, the [http://grass.gdf-hannover.de/wiki/PSC GRASS Project Steering Committee] is responsible for granting SVN write access to contributors (as defined in [http://download.osgeo.org/grass/grass6_progman/rfc/rfc1_psc.html RFC1]).
     22      * The requester 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).
     23      * The request has to be send to the GRASS-PSC [http://lists.osgeo.org/mailman/listinfo/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. If granted, SVN write access is set up (see below).
    2424 * '''GRASS-Addons-SVN repository:'''
    25    * Individual GRASS developers with write access can grant SVN write access to contributors.
    26       * 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).
     25   * Individual [http://trac.osgeo.org/grass/browser/grass/trunk/AUTHORS GRASS developers] with write access can grant SVN write access to contributors (maybe select an active developer, see grass-dev mailing list archive). This person is a sort of "sponsor/mentor" for the requester.
     26      * The requester 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).
    2727      * The request has to be send to a GRASS developer or the GRASS-PSC chair, stating that RFC2 was read and accepted. If granted, SVN write access is set up (see below).
    2828
    2929=== Setting up the new SVN write access ===
    3030
    31 Once SVN access is granted, the requestor needs to obtain an "osgeo_id" at http://www.osgeo.org/osgeo_userid
     31Once SVN access is granted, the requester needs to obtain an "osgeo_id" at http://www.osgeo.org/osgeo_userid
    3232If 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
    3333The GRASS-PSC chair (currently Markus Neteler) and other developers can add this "osgeo_id" to the OSGeo LDAP authentication system.