[Spamassassin Wiki] Update of "BecomingCommitter" by DuncanFindlay

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Spamassassin Wiki" for change notification.

The following page has been changed by DuncanFindlay:
http://wiki.apache.org/spamassassin/BecomingCommitter

------------------------------------------------------------------------------
  
  == Set Your Password ==
  
- Generally, you should have sent in your desired password in 'htpasswd' format with the account request (I think that's the current idea).
- 
- The alternative is that, when your account is created, the ASF infrastructure person will have sent you a password for cvs.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:
+ When your account is created, the ASF infrastructure person will have sent you a password for the Apache servers.  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
@@ -24, +22 @@

  
  == Writable SVN checkout ==
  
- When a contributor becomes 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:
+ 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:
  
  {{{
    svn checkout https://svn.apache.org/repos/asf/spamassassin/trunk
@@ -39, +37 @@

  
  Changes to the SVN tree can now be checked in directly using {{{svn commit}}}.
  
- The first time a file is checked in using {{{svn commit}}}, the committer will be prompted for their username and password.  This will then be cached for all further commits.
+ The first time a file is checked in using {{{svn commit}}}, you will be prompted for your username and password.  This will then be cached for all further commits.
  
- You should first commit a change adding themselves to the CREDITS file.  If you want to do additional test commits, something like adding a single newline to the end of an inoffensive file in a subdirectory, or removing it again, would do the trick.
+ You should first commit a change adding yourself to the CREDITS file.  If you want to do additional test commits, you can try something like adding a single newline to the end of an inoffensive file in a subdirectory, and removing it again; that should do the trick.
  
  The first time you commit something your commit message needs to be moderated through, so don't be surprised if it doesn't show up for awhile.
  
@@ -70, +68 @@

  
  You should subscribe to the security list by sending a subscription request to '''security-subscribe -at- spamassassin.apache.org'''.
  
- The PMC members should grant their Bugzilla account 'EditBugs' status.  I'm not sure how this is done, but Theo knows ;)
+ The PMC members should grant your Bugzilla account with the 'EditBugs' permission (if you don't already have it).  This is done by following the "Users" link in Bugzilla and granting the EditBugs status.
  
  = More Details =