...

(This page is still likely to be under construction.)

Set Your SVN Password

In theory, when the account request was made to the infrastructure group, it would have included the output from htpasswd -ns username and that would have your initial SVN password setup. If there is a problem with this however, you will need to run svnpasswd.

When your account is created, thean ASF infrastructure personvolunteer will havesend sent you a password for the Apache servers login server (currently minotaur.apache.org).  This allows you to log in using SSH to set your SVN password, as described \[http://www.apache.org/dev/version-control.html#https-svn here\].  Here's a quick summary of what to do:

  ssh -l MYUSERNAME svn.apache.org
  Password: [THATPASSWORDYOURPASSWORD]
  svnpasswd

And enter your desired SVN password twice to set it.

...

When you become a committer, you should check out the svn repository using the HTTPS url instead of the HTTP one, so that you have read/write access to the repo. To check out from scratch, assuming that you're using the standard svn commandline client:

  svn checkout https://svn.apache.org/repos/asf/spamassassin/trunk

...

  cd /path/to/checkedout/tree
  svn switch https--relocate http://svn.apache.org/repos/asf/spamassassin/trunk https://

Changes to the SVN tree can now be checked in directly using svn commit.

...

The PMC members should grant your Bugzilla account with the 'EditBugs' permission , 'HasCla', and 'securitySecurity' group membership permissions (if you don't already have them). This is done by following the "Users" link in Bugzilla, specifying the account by email address, and then granting the EditBugs status and adding the user to the security grouppermissions from there.

More Details

Be sure to read \[http://www.apache.org/foundation/how-it-works.html how-it-works.html\] -- there's lots of useful stuff about ASF processes there.

...