Requesting SVN write access: Difference between revisions
Jump to navigation
Jump to search
m (Requesting CVS write access moved to Requesting SVN write access: new repo) |
(updated to new rules (this page should go into trac)) |
||
| Line 1: | Line 1: | ||
=== Procedure to request | === Procedure to request SVN write access === | ||
The [[PSC|GRASS Project Steering Commitee]] is responsible for granting | The [[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]). | ||
* The requestor has to '''read and | * 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). | ||
* The request has to be send to the GRASS-PSC mailing list, stating that RFC2 was read and accepted. This requires [http:// | * 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. | ||
=== Setting up | === Setting up SVN write access === | ||
Once | Once SVN access is granted, the requestor needs to obtain an "osgeo_id" at http://www.osgeo.org/osgeo_userid | ||
If 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 | |||
The GRASS-PSC chair (currently Markus Neteler) and other developers can add this "osgeo_id" to the OSGeo LDAP authentication system. | |||
Contributions have to follow the [[Working with CVS|code submission guidelines]] (see also SUBMITTING* files in the source code). | Contributions have to follow the [[Working with CVS|code submission guidelines]] (see also SUBMITTING* files in the source code). | ||
| Line 15: | Line 17: | ||
=== Then what? === | === Then what? === | ||
Happy hacking :) The requestor should subscribe to the [http:// | Happy 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. | ||
[[Category: PSC]] | [[Category: PSC]] | ||
[[Category:Development]] | [[Category:Development]] | ||
Revision as of 08:46, 6 February 2008
Procedure to request SVN write access
The GRASS Project Steering Commitee is responsible for granting SVN write access to contributors (as defined in RFC1).
- The requestor has to read and abide by the document Legal aspects of code contributions (RFC2).
- The request has to be send to the GRASS-PSC mailing list, stating that RFC2 was read and accepted. This requires subscription to the mailing list.
Setting up SVN write access
Once SVN access is granted, the requestor needs to obtain an "osgeo_id" at http://www.osgeo.org/osgeo_userid If 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 The GRASS-PSC chair (currently Markus Neteler) and other developers can add this "osgeo_id" to the OSGeo LDAP authentication system.
Contributions have to follow the code submission guidelines (see also SUBMITTING* files in the source code).
Then what?
Happy hacking :) The requestor should subscribe to the grass-commit mailing list which distributes GRASS-SVN commit differences for real-time code review.