Changes between Version 11 and Version 12 of HowToContribute


Ignore:
Timestamp:
May 2, 2008, 4:58:52 AM (14 years ago)
Author:
neteler
Comment:

clarify SVN write access

Legend:

Unmodified
Added
Removed
Modified
  • HowToContribute

    v11 v12  
    1818=== Procedure to request GRASS-SVN write access ===
    1919
    20  * '''Main GRASS-SVN repository:'''
    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]).
     20To avoid security and code quality issues, a procedure has been established to control and grant GRASS-SVN write access. In general, write access must be requested and is not automatically assigned. Any code submission must be compliant with the GRASS submission rules.
     21
     22 * Write access to the '''Main GRASS-SVN repository:'''
     23   * 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]).
    2224      * 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).
    24  * '''GRASS-Addons-SVN repository:'''
    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.
     25      * 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 PSC mailing list. After a period of evaluation, SVN write access may be granted and is set up in the OSGeo authentication system (see below).
     26 * Write access to the '''GRASS-Addons-SVN repository:'''
     27   * [http://trac.osgeo.org/grass/browser/grass/trunk/AUTHORS GRASS developers] with write access can grant SVN write access to contributors (you may contact an active developer, see grass-dev mailing list archive). The selected developer is a sort of "sponsor/mentor" for the requester. Procedure:
    2628      * 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).
    27       * 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).
     29      * The request has to be send to a GRASS developer or the GRASS-PSC chair, stating that RFC2 was read and accepted. After a period of evaluation, SVN write access may be granted and is set up in the OSGeo authentication system (see below).
    2830
    2931=== Setting up the new SVN write access ===
     
    3133Once SVN access is granted, the requester needs to obtain an "osgeo_id" at http://www.osgeo.org/osgeo_userid
    3234If 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
    33 The GRASS-PSC chair (currently Markus Neteler) and other developers can add this "osgeo_id" to the OSGeo LDAP authentication system.
     35The GRASS-PSC chair (currently Markus Neteler) and other developers can add this "osgeo_id" to the list of enabled accounts in the OSGeo LDAP authentication system.
    3436
    3537Contributions have to follow the [wiki:BestPractise] rules (see also SUBMITTING* files in the source code).