Page History

...

• Log into Bugzilla and look for bugs that you can fix. Fix it, and attach a patch (from latest SVN) to the bug report. See also UsingBugzilla.
  

Bug Tidying

• Wiki Markup

  There are many bugs that just need either a couple votes and a commit, or to be closed. Find a bug, read through all the comments, and provide a concise summary of what needs to be done with it. If a patch is attached, make sure the summary starts with "\[review\]". For commits to stable (3.3.x as of May 2011), three "+1" votes are required from committers. Anything that was committed to trunk before the last time it was branched (3.3.x was branched in January 21 2010) should probably be closed. With 514 open bugs over 2 years old as of May 2011, we can use all the help cleaning up we can get. \\

Reduce Resources

• Submit code to speed something up without breaking anything. Minimum is probably about a 1% speed-up in overall check speed.
  
• AutoWhitelist needs AutoWhitelistExpiry bug 3082 and bayes_seen databases need to have automatic expiry.
  

...