PeterSymonds (talk | contribs) →{{green|Active clerks}}: Seddon, full clerk |
→SPI team: -2 removed due to inactivity, non-progression |
||
Line 63: | Line 63: | ||
;Non-admins |
;Non-admins |
||
<!-- Alphabetically, please. --> |
<!-- Alphabetically, please. --> |
||
:*{{User6b|Bsadowski1}} (Trainee) - MuZemike |
|||
:*{{User6b|Elockid}} (Trainee) - NuclearWarfare |
:*{{User6b|Elockid}} (Trainee) - NuclearWarfare |
||
:*{{user6b|GrooveDog}} (Trainee) - PeterSymonds |
|||
:*{{User6b|Nathan}} |
:*{{User6b|Nathan}} |
||
:*{{User6b|Spitfire}} (Trainee) - NuclearWarfare |
:*{{User6b|Spitfire}} (Trainee) - NuclearWarfare |
Revision as of 23:45, 3 March 2010
- For the clerking co-ordination page, see the Clerks' Noticeboard.
The role of clerks is (together with CheckUsers) to be the users responsible in the first instance for day to day running of the WP:SPI functions, and management of SPI and its case sub-pages.
Clerks
Clerks are selected by full CheckUser clerks and must gain consensus among those. A clerk must first have been a clerk trainee and have been recommended by a current clerk to Checkusers.
Checkuser clerks will be called upon to ensure the smooth operation of the SPI page, and they will be responsible for:
- Flagging requests for checkuser attention, either independently or by request from other users;
- Assistance with housekeeping tasks, including archiving, merging and formatting of cases;
- Ensuring that proper evidence is provided for checkuser requests, and requesting such evidence when it is not provided;
- Assisting with non-private, operational aspects of cases, as needed;
Any user will be able to request checkuser, and clerks will endorse those requests or refer them back to traditional means (Suspected sockpuppet investigations) for resolution. In either case, the request will be categorized and available, and a checkuser request need not be endorsed in order to be run; clerks only flag these requests for attention or do not. Ultimate discretion remains solely with the checkusers.
While clerks will not be dealing with any private or sensitive information, the checkusers must be able to trust the knowledge and judgment of users flagging requests for their attention, and should not be made to feel that they must continually check over their work.
- Clerks should be users who are in good standing within the community, and are experienced with Wikipedia. Clerks should have a good working knowledge of Wikipedia policy, especially in the area of sockpuppets and the situations where checkuser is important. Clerks are asked to keep this page and its talk page on their watchlist to be kept informed of procedural changes and requests from the checkusers.
- Clerks who persistently make problematic comments on requests or otherwise violate decorum may be asked by the checkusers to cease contributing here. Be aware that this position is rather dull and carries no particular prestige; status-seeking will not be looked upon kindly.
Trainee clerks
Anyone may request to become a trainee clerk. Users in good standing may ask any current clerk (who will serve as the trainee's coach) to be a trainee clerk, and will simply be accepted due to supply and demand. Trainee clerks may exercise all of the above, except:
- Posting of formal SPI/CU notices other than as agreed;
- "Coach" a trainee.
Admin patrollers
Any administrator is free and welcome to patrol SPI but not perform "clerk" actions (endorsing CU requests, archiving, redirecting, etc.). A clerk will follow up by tagging blocked accounts and archiving cases.
A few last notes
- Clerks (whether or not administrators) have no special authority beyond that which the user usually has. However, users disrupting SPI against clerk requests are likely to be blocked, as they are hampering the maintenance of the page as an easy-to-use, organised resource.
- Clerks are in position to ensure the smooth operation of the SPI process and should strive to be as helpful as possible.
- What small authority clerks have ends with the SPI process; it is not a status symbol, and nor does it grant the clerk immunity with regard to consensus or other policies.
- Clerks have no access to private information.
- Clerks' actions can be overturned by the community, and by any CheckUser.
- Administrators are not by default clerks, and must request clerkship via the usual means.
SPI team
The following users are currently providing assistance. They are listed here for ease of contact and coordination with the checkusers. Note, all checkusers are also considered clerks.
Last updated: 03:58, 14 January 2010 (UTC).
Active clerks
- Admins
-
- Amorymeltzer (talk · · contribs · count · logs · email) (Trainee) - MuZemike
- Jake Wartenberg (talk · · contribs · count · logs · email)
- JamieS93 (talk · · contribs · count · logs · email) (Trainee) - PeterSymonds
- Juliancolton (talk · · contribs · count · logs · email) (Trainee) - PeterSymonds
- MuZemike (talk · · contribs · count · logs · email)
- NJA (talk · · contribs · count · logs · email) (Trainee) - NuclearWarfare
- NuclearWarfare (talk · · contribs · count · logs · email)
- OhanaUnited (talk · · contribs · count · logs · email)
- PeterSymonds (talk · · contribs · count · logs · email)
- Seddon (talk · · contribs · count · logs · email)
- Tiptoety (talk · · contribs · count · logs · email)
- Non-admins
Away
Clerks who are on a period of temporary absence from clerking.
IRC channel
There is a public IRC channel #wikipedia-en-spi (direct link) for co-ordination among clerks and other users. If you have a question for the clerks feel free to ask it there.
Historical note
Prior to the present clerking system being implemented, a team of appointed clerks performed these functions. A table of editors who served as clerks under the old system is kept for historical interests at Wikipedia:Requests for checkuser/Clerks/Table. The current system is now similar, but is not built in with a command structure.