|
|
(4 intermediate revisions by one other user not shown) |
Line 1: |
Line 1: |
| === Procedure to request CVS write access ===
| | {{MovedToTrac|PSC/RequestingSVNWriteAccess}} |
| | |
| The [[PSC|GRASS Project Steering Commitee]] is responsible for granting CVS write access to contributors (as defined in [http://mpa.itc.it/markus/grass63progman/rfc/rfc1_psc.html RFC1]).
| |
| | |
| * The requestor has to '''read and accept''' the document [http://mpa.itc.it/markus/grass63progman/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://grass.itc.it/mailman/listinfo/grass-psc subscription] to the mailing list.
| |
| | |
| === Setting up CVS write access ===
| |
| | |
| Once CVS access is granted, the requestor should follow the [http://freegis.org//grass/howto_grass-sshcvs.en.html GRASS-CVS-ssh instructions] to get the write access enabled. The public SSH key should be sent to Bernhard Reiter (email address at page bottom of the GRASS-CVS-ssh instructions, in copy to the GRASS-PSC chair (currently Markus Neteler).
| |
| | |
| Contributions have to follow the [[Working with CVS|code submission guidelines]] (see also SUBMITTING* files in the source code).
| |
| | |
| === Then what? ===
| |
| | |
| Happy hacking :) The requestor should subscribe to the [http://grass.itc.it/mailman/listinfo/grass-commit grass-commit] mailing list which distributes GRASS-CVS commit differences for real-time code review.
| |
| | |
| [[Category: PSC]]
| |
| [[Category:Development]]
| |