This page is currently inactive and is retained for historical reference. Either the page is no longer relevant or consensus on its purpose has become unclear. To revive discussion, seek broader input via a forum such as the village pump.

I cannot stress this enough: Please be bold and add new scoring criteria yourself if you think of any. I don't touch all admin areas, so I can't know how big of a score everything should get.

As a way to help deal with the backlogs, I (User:Grandmasterka) would like to propose an informal admin backlog contest. This was inspired by this discussion on WT:RFA, with deletion stats for each admin, and something similar to this was proposed for the future when the backlogs became large for days or weeks at a time (see NoSeptember's final comment in the above-linked discussion.) This may be that time.

The admin backlog contest would take place during an agreed-upon week, or perhaps start and end each consecutive week. The weekly winner would be recognized with a wikicertificate and be acknowledged in the Wikipedia Signpost. The totals could be entirely self-reported, or it could be overseen by an admin who would recuse themselves from the contest, and the contest could focus on all areas, or a different area each week.

Scoring for the admin backlog contest could be as follows (work in progress:)

Deletions

• 1 point for non-image speedy deletions, or proper removal of a speedy tag.
• 3 points for image speedy deletions, or proper removal of a speedy tag (images must be removed from any articles they are in!)
• 3 points for every XfD closure.
• 5 points for deletion of an image in a fair use backlog.
• 5 points for deletion of copyright violations.
• 7 points for resolving an image in a fair use backlog without deleting it, including adding a sufficient fair use rationale to an image that was up for deletion.
• −25 points for non-speedy deletions that are later overturned as a result of a deletion review or other discussion/complaint.
• −50 points for speedy deletions that are later overturned as a result of a deletion review or other discussion/complaint.

Blocking

• 1 point for each sockpuppet whack-a-mole block.
• 2 points for each block on WP:AIV or WP:UAA.
• 3 points for closing a WP:3RR report.
• 10 points for properly resolved WP:SSP reports.
• −20 points for blocks that are later overturned after community discussion on one of the noticeboards.
• 1 point for taking administrative action in response to an WP:AN/I or WP:AN thread of any other kind. (i.e. blocking for legal threats reported on AN/I, etc. note: only counts for administrative actions that would show up in an administrator log. )
• 1 point for declining an unblock request after investigating the situation.
• 5 points for granting an unblock request after consultation with the blocking admin or on WP:ANI.

Backlogs

• 3 points for closing a WP:3O report.
• 1 point for removing an invalid WP:AIV entry ONLY IF: either the automated template, or a personalized message explaining why is left on the reporter's talk page.
• 1 point for prod'ing autobiographical vanispamcruftisement, or striking a valid article from AlexBot's list
• 1 point for each user warning issued.
• −5 points if issuing admin retracts
• −10 points if warning is retracted by community consensus
• 2 points for each "last warning" issued.
• −5 points if issuing admin retracts
• −10 points if warning is retracted by community consensus
• 2 points for speedily deleting blatant advertising
• 3 points for opening an WP:AfD

Conflict of Interest Noticeboard

• 5 points for resolving a COI report

Protections

• 2 points for closing a WP:RPP report.
• 2 points for adding an interwiki or making a typo fix as the result of a CAT:PER request.
• 3 points for making a wording change to a protected template or system message as the result of a CAT:PER request.
• 5 points for making a content change in response to a CAT:PER request; 3 points for correctly declining a CAT:PER request.
• −20 points if such a change is later reverted.
• 8 points for making a technical change to a high-risk template or system message in response to a CAT:PER request.
• −30 points if the change has to be reverted because it breaks the template in question.
• −80 points if the change has to be reverted because it breaks the system message and messes up the site.

Other

• 3 points for creating an account for another user who can't.
• 3 points for declining an inappropriate WP:ACC request.
• 1 point for other administrative action that is not listed here.

• Automatic disqualification for being involuntarily desysopped during the contest.
• Automatic disqualification for being a subject of an arbitration committee case regarding one's use of the admin tools.
• Disqualification for newbie-biting or gaming the system as a result of this contest. Please tell newbies who visit your talk page about Wikipedia's applicable policies and WP:DRV, if necessary, and be honest with yourself if you deleted something that was obviously worth keeping and someone complains. Remember, this is only a game as a means of lessening Wikipedia's backlogs, and should not trump any of Wikipedia's policies and guidelines.
• Any scoring penalties for reversions obviously do not apply to self-reverts.

Please feel free to discuss on the talk page, or be bold and add new scoring criteria, or adjust the existing scores if you feel they are unfair.

I hope this will at least spark discussion (or more importantly action) on ways to tame the growing backlogs, separate from the ongoing discussion over WP:RFA reform.

• Category:Administrative backlog
• Category:Wikipedia backlog