| 18 | | 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]). |
| 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. |
| | 18 | * '''Main GRASS-SVN repository:''' |
| | 19 | * 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]). |
| | 20 | * 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). |
| | 21 | * 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). |
| | 22 | * '''GRASS-Addons-SVN repository:''' |
| | 23 | * Individual GRASS developers with write access can grant SVN write access to contributors. |
| | 24 | * 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 | * 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). |
