You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spamassassin.apache.org by Apache Wiki <wi...@apache.org> on 2008/01/17 14:46:14 UTC

[Spamassassin Wiki] Update of "BecomingCommitter" by JustinMason

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 JustinMason:
http://wiki.apache.org/spamassassin/BecomingCommitter

The comment on the change is:
provide more details; move CPAN/freshmeat to committer page

------------------------------------------------------------------------------
  = Things you should do when you become a committer =
  
  This page describes stuff you'd want to do when you become elected a committer -- in other words, when you're given write access to the SpamAssassin codebase.  As described at ProjectRoles, the SpamAssassin project has 3 levels of involvement -- the same as many Apache Software Foundation (ASF) projects.  
- 
- ''(This page is still likely to be under construction.)''
  
  == Set Your SVN Password ==
  
@@ -84, +82 @@

  
  ----
  
- = PMC to-do =
+ = Things the PMC need to do on your behalf =
  
- First, propose a vote to add the person as a committer on the '''private -at- spamassassin.apache.org''' list.  Usually the subject is '''[VOTE] Name''', btw.
+ First, propose a vote to add the person as a committer on the '''private -at- spamassassin.apache.org''' list.  Usually the subject is '''[VOTE] Name''', btw.  You need 3 +1s, allow 72 hours, and your own vote counts as one +1.
  
- Upon a successful vote, send an invite to the person (text below).  If the invitation is accepted, grant the person's Bugzilla account with the 'EditBugs', 'HasCla', and 'Security' group permissions.  This is done by following the "Users" link in Bugzilla, specifying the account by email address, and then granting the permissions from there.
+ Upon a successful vote, send an invite to the person (text below).  If the invitation is accepted, grant the person's Bugzilla account with the 'EditBugs', 'HasCla', and 'Security' group permissions.  This is done by [http://issues.apache.org/SpamAssassin/editusers.cgi following the "Users" link in Bugzilla], specifying the account by email address, clicking on the correct username, scrolling to "Group Access" and ticking the appropriate checkboxes.
  
  Then, ask infra to set up an apache.org account: http://www.apache.org/dev/pmc.html#newcommitter
  
  Once they do this, they'll mail the private list with a mail from root/at/apache noting "Account created: Name (username)".  The PMC chair then needs to check out 
  https://svn.apache.org/repos/asf/infrastructure/trunk/subversion/authorization , edit the "asf-authorization" file, and add the new username to the "committers-X" (where "X" is the first letter of the new committer's username) and "spamassassin" groups.  They now have r/w access to the SVN repositories.
+ 
+ == Given CPAN co-maint status ==
+ 
+ Given your CPAN userid, someone with the karma -- this may be just JMASON -- logs in to the [https://pause.perl.org/pause/authenquery?ACTION=share_perms PAUSE Share Permissions page], and selects '3.1 Make somebody else co-maintainer', filling in your userid.  (This can wait until it's needed, since you probably won't know the committer's CPAN userid right now.)
+ 
+ == Given Freshmeat co-maint status ==
+ 
+ http://freshmeat.net/project-admins/edit/14876/ -- possibly again only jmason can do this. (Again, this can wait until it's needed.)
  
  == Invitation Text ==