Requesting SVN write access: Difference between revisions
Jump to navigation
Jump to search
(extended) |
(grass-commit) |
||
| Line 12: | Line 12: | ||
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). | ||
=== 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: PSC]] | ||
Revision as of 12:17, 23 June 2007
Procedure to request CVS write access
The GRASS Project Steering Commitee is responsible for granting CVS write access to contributors (as defined in RFC1).
- The requestor has to read and accept 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 CVS write access
Once CVS access is granted, the requestor should follow the 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 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-CVS commit differences for real-time code review.