Wikipedia:Guide to requests for tools

From Wikipedia, the free encyclopedia

This is the guide on the Request for tools process. It is the suggested requirements before a candidate should consider applying and should by no means deter an editor from applying. The point of modules is to make it easier for trusted editors to do their work. Some editors focus primarily on one area. Rather being discouraged due to lack of work in other areas and being unable to receive the tools they would be trusted using, editors could be granted a single module. In the long run it would make it easier for other editors to evaluate a candidate if they started with using a module. If the candidate didn't abuse their module, the community is more likely going to trust the editor with full administrator rights. In a way Request for tools is a sort of stepping stone before request for adminship. Module editors are not required to run a RFA, unless they want all three modules. The whole point of the Administrator tools is to make maintenance tasks easier. If an editor doesn't want full administrator rights, why force them.

Overview[edit]

Unlike request for adminship there are specific things other editors are looking for. Some of the criteria for one module are much different than the criteria for another module.

Suggested criteria[edit]

Patroller[edit]

Editors who wish to apply for Patroller are the users who will likely fall under the most scrutiny. This is because of the editor's ability to block other users with the Patroller user right. The block tool is intended to help anti-vadalism fighters block users who continue to vandalize or create inappropriate pages after a final warning. The block tool should only be used by Patrollers to block after final warnings. There is a potential threat that the tool could be abused and used to inappropriately block editors. Inappropriate use of the tool will result in removal of the tool by a Bureaucrat or by community consensus. Suggested editor standards before applying:

  1. A clear understanding of Wikipedia's core policies
  2. Strong work in the field of anti-vandalism. (at least 500 5000 reverts and 500 5000 warns. A minimum of 8 months of active anti-vandalism work with few mistakes.)
  3. Appropriately filed at least 25 reports to Administrator intervention against vandalism

Protector[edit]

This right gives editors the technical ability to move pages over redirects as well as moving subpages. In addition to moving protectors may also change protection levels of page. This right would be particularly useful for content builders, page movers, and template builders as templates are often full protected and only editors with Administrator or Protectors. As with Patroller, abuse of the tool will result in a Bureaucrat removing it. It may also be removed by community consensus. Suggested editor standard before applying:

  1. A clear understanding of Wikipedia's core policies
  2. Editor is actively helping in the area of content building (Created at least 20 non-stub articles?)
  3. Editor is active in Wikipedia:Requested Moves or active in template creation/improvement (at least 150 appropriate page moves or 20 template building edits?)

Purger[edit]

This right gives editors the technical ability to delete and undelete pages from public view (Only Purgers, Administrators, Bureaucrats, and Oversighters can see deleted pages). Because of the nature of undelete and being able to see deleted pages this right would require a high level of trust in the editor. The editor would also need to be active in helping building and identifying community consensus. Like Patroller and Protector, abuse of this tool will result in removal by a Bureaucrat or by community consensus. Suggested editor standard before applying:

  1. A clear understanding of Wikipedia's core policies
  2. Actively works in Wikipedia:Articles for Deletion. (Performed at least 10 non-admin closures?)
  3. Actively works in New Page Patrol. (At least 50 appropriate CSD tagging and marking at least 300 pages as patrolled?)