This page is semi-protected against editing.

Commons:Administrators

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search

Shortcuts: COM:A • COM:ADMIN • COM:SYSOP

This page explains the role of administrators (sometimes called admins or sysops) on Wikimedia Commons. Note that details of the role, and the way in which administrators are appointed, may differ from other sites.

If you want to request administrator help, please post at Administrators' noticeboard.

There are currently 186 administrators on Commons.

What is an administrator?

Administrators as of February 2024
Listing by: LanguageDateActivity [+/−]

Number of Admins: 186

  1. -revi, ko, en-3
  2. 1234qwer1234qwer4, ru, de-4, en-3
  3. 1Veertje, nl, en-4, de-1, fr-1
  4. 32X, de, en-2, hsb-1, ru-1
  5. 99of9, en (bureaucrat)
  6. A.Savin, ru, de-4, en-2
  7. Abzeronow, en, fr-1
  8. Achim55, de, en-3, nds-3, la-2
  9. AFBorchert, de, en-3
  10. Ahonc, uk, ru-4, en-2, de-1
  11. Aka, de, en-3
  12. Alno, fr, en-3, es-2, pt-1
  13. Андрей Романенко, ru, en-3, uk-3, be-2, fr-2, lv-2
  14. Ankry, pl, en-2, ru-1
  15. AnRo0002, de, en-2, fr-2, es-1
  16. Anthere, fr, en-3
  17. AntiCompositeNumber, en, fr-2 (steward)
  18. Aude, en, ar-2, de-2, es-3
  19. Benoît Prieur, fr, en-3, pt-2, es-1, it-1, hy-1
  20. Billinghurst, en
  21. Blackcat, it, en-3, fr
  22. BrightRaven, fr, en-3, nl-2, es-2, zh-1
  23. Butko, ru, uk-2, en-1
  24. Captain-tucker, en
  25. Christian Ferrer, fr, en-2, es-2
  26. Ciell, nl, en-2, de-1
  27. Common Good, en
  28. CptViraj, gu, hi-4, en-3
  29. Cromium, en, de-1, fr-1
  30. Cybularny, pl, en-2, es-1, de-1
  31. Czar, en
  32. DaB., de, en-1
  33. DarwIn, pt, en-3, es-2, fr-2, gl-2, ca-1, it-1, oc-1
  34. Davepape, en
  35. De728631, de, en-5
  36. DerHexer, de, en-3, grc-3, la-3, es-1 (steward)
  37. Dharmadhyaksha, mr, en-3, hi-3
  38. DMacks, en
  39. Didym, de, en-2, fr-2
  40. Dyolf77, ar, fr-5, en-2, it-1, es-1
  41. D-Kuru, de, en-2, it-1
  42. Ebrahim, fa, en-3
  43. Elcobbola en, de (checkuser)
  44. Ellin Beltz, en (bureaucrat)
  45. Ellywa, nl, en-2, de-1, fr-1
  46. Emha, de, bar, en-3, fr-1
  47. Érico, pt, en-2, es-1
  48. EugeneZelenko, ru, be, en-2, bg-1, pl-1 (bureaucrat)
  49. Explicit, en, es, ko-2
  50. Ezarate, es-3, en-1
  51. Fitindia, en-3, hi-2, mr-2
  52. FunkMonk, da, en-4, no-3, fo-2, sv-2, de-1, es-1
  53. Gbawden, en-3, af-1
  54. Geagea, he, ka-3, en-3, ru-1
  55. Geni, en
  56. George Chernilevsky, ru, uk-3, de-2, en-2, bg-1, la-1, be-1, fr-1
  57. Gestumblindi, als, de, en-3
  58. Gnangarra, en, nys-1
  59. GPSLeo, de, en-2
  60. GreenMeansGo, en
  61. Grin, hu, en-3, de-1
  62. Hekerui, de, en-4
  63. Herbythyme, en, fr-2, es-1, it-1
  64. Hesperian, en
  65. Holly Cheng, en, ja-2
  66. Huntster, en
  67. Indeedous, de, en-3, fr-2
  68. Infrogmation, en, es-1
  69. IronGargoyle, en, de-1
  70. Jameslwoodward, en, fr-1 (bureaucrat, checkuser)
  71. Jaqen, it, en-2
  72. Jarekt, pl, en
  73. JarrahTree, en, id-1
  74. Jcornelius, de, lt-2, la-2, en-2, pt-2, fr-1
  75. Jdforrester, en
  76. Jean-Frédéric, fr, en-4, es-1
  77. Jianhui67, en, zh-4, ja-2, ms-1
  78. Jmabel, en, es-3, ro-2, de-1, ca-1, it-1, pt-1, fr-1
  79. Joergens.mi, de, en-3
  80. JoKalliauer, de, en-3
  81. Jon Kolbert, en, fr-4, de-2 (steward)
  82. Josve05a, sv, en-3
  83. Julo, pl, en-2, de-1, ru-1
  84. Jusjih, zh, en-3, fr-2, ko-1
  85. Kadı, tr, en-5, fr-2, az-2
  86. Kaldari, en
  87. Kallerna, fi, en-3, sv-2, de-1
  88. King of Hearts, en, zh-3, es-2, ja-1
  89. Klemen Kocjancic, sl, en-3, de-2, hr-1, bs-1
  90. Krd, de, en-3 (bureaucrat, checkuser)
  91. Krinkle, nl, en-3, de-2
  92. Kritzolina, de, en-3, fr-2, it-1
  93. Leit, de, en-3, fr-1
  94. Léna, fr, en-3, es-1
  95. Leyo, gsw, de, en-3, fr-3, es-1, la-1
  96. Lofty abyss, en, mt, it-2
  97. Lymantria, nl, en-3, de-2, fy-2, fr-1, zea-1
  98. Magog the Ogre, en, es-2
  99. Mahagaja, en, de-4, fr-2, ga-2, la-2, cy-1
  100. Maire, pl, en-4, es-2, fr-2, de-2, ru-1
  101. Marcus Cyron, de, en-2
  102. Masur, pl, en-3, de-1
  103. Materialscientist, en-4, ru-4, nl-3, fr-1, es-1
  104. MB-one, de, en-3, fr-1, pt-1
  105. MBisanz, en
  106. Mdaniels5757, en, es-1
  107. MGA73, da, en-3, de-2, no-1, sv-1
  108. Mhhossein, fa, en-3, ar-1
  109. Micheletb, fr, en-3, it-1, es-1
  110. Mike Peel, en, pt-2, fr-1
  111. Minorax, en, zh (oversighter)
  112. Missvain, en
  113. Mitchazenia, en, es-2
  114. Miya, ja, en-2
  115. Moheen, bn, as-1, bpy-1, en-3, hi-1, hif-1
  116. Morgankevinj, en
  117. MPF, en, da-2, de-1, fr-1
  118. Multichill, nl, en-3, de-1, fr-1
  119. Mys 721tx, zh, en-3
  120. Nagy, de, en-3, fr-2, es-1, sv-1
  121. NahidSultan, bn, en-3, bpy-1
  122. Natuur12, nl, en-3, de-1
  123. notafish, fr, en-4, de-3, es-2, it-2
  124. odder, pl, en-4, de-2 (bureaucrat, oversighter)
  125. Otourly, fr, en-2, it-1
  126. P199, en, nl, fr-2, tl-2, de-1
  127. Pi.1415926535, en, es-2
  128. Platonides, es, en-2, fr-1
  129. Poco a poco, es, de-4, en-3, fr-2, it-2, pl-2, pt-1
  130. Podzemnik, cs, en-2
  131. Polarlys, de, en-2, fr-1, no-1
  132. Pyb, fr, en-2
  133. Pymouss, fr, en-3, de-2, it-2, he-1
  134. Racconish, fr, en-4
  135. Ragesoss, en, de-1, fr-1
  136. Ra'ike, de, en-2
  137. Rama, fr, en-3, de-2, la-2, es-1, it-1, ja-1 (oversighter)
  138. Rastrojo, es, en-3, fr-2, eo-1
  139. Raymond, de, en-3, nl-1 (oversighter)
  140. Red-tailed hawk, en, es-4, pt-2, ug-1
  141. Regasterios, hu, en-1
  142. Rehman, en, si-1
  143. Reinhard Kraasch, de, en-3
  144. Rimshot, de, en-4, fr-2, it-1
  145. Romaine, nl, en-3, de-2, af-1, fr-1
  146. Rosenzweig, de, en-3, fr-1, la-1
  147. Royalbroil, en, es-1
  148. RP88, en, de-1
  149. Rubin16, ru, tt, en-4
  150. Rudolphous, nl, en-3, de-2
  151. Ruthven, it, fr, en-4, es-4, nap-4, ca-2, de-1
  152. Sanandros, als, de, en-3, fr-1
  153. Satdeep Gill, pa, en-5, hi-5, es-3, fr-2, fa-1
  154. Shizhao, zh, en-1, ru-1
  155. Spiritia, bg, en-3, ru-2, mk-2, de-1
  156. Sreejithk2000, ml, en-3, hi-3, ta-1, kn-1
  157. Steinsplitter, bar, de-4, it-3, en-1
  158. Stifle, en, ga, fr-2, de-1
  159. Storkk, en, fr-3, de-2, eo-2
  160. Strakhov, es, en-2
  161. TadejM, sl, en-3, de-2, fr-2
  162. Taivo, et, en-3, ru-3, de-1
  163. Tarawneh, en, ar, de-1
  164. Teles, pt, en-3, es-2
  165. Themightyquill, en, fr-2, de-1, hu-1
  166. TheAafi, ks, ur-5, en-3, hi-2, ar-1
  167. The Squirrel Conspiracy, en
  168. Thibaut120094, fr, en-2, ja-1
  169. Thuresson, sv, en-3, no-2
  170. Trijnstel, nl, en-4, de-1, fr-1 (checkuser)
  171. Tulsi, ne, mai, en-3, hi-2, hif-2, bh-1
  172. Túrelio, de, en-3, es-1
  173. VIGNERON, fr, de-2, en-2, zh-1
  174. Wdwd, de, en-2
  175. Well-Informed Optimist, ru, uk-4, en-3
  176. Wikitanvir, bn, en-3, de-2, as-2, bpy-1
  177. Wutsje, fy, nl, en-3, de-2, fr-1
  178. Yann, fr, en-4, hi-2, gu-1
  179. Yasu, ja, en-2, de-1
  180. Ymblanter, ru, en-3, de-2, fr-2, nl-2, it-1, es-1
  181. Yuval CT, he, en-3
  182. Zzyzx11, en, es-1, fr-1
  183. علاء, ar, en-4, he-1, es-1 (steward)
  184. Abuse filter, (automated account)
  185. CommonsDelinker, (bot) see request
  186. KrinkleBot, (bot) see request

If 186 is not the last number on this list, there may be an error or there are some users assigned temporarily.

Technical

Administrators are users with the technical ability on Wikimedia Commons to:

  • delete and undelete images and other uploaded files, and to view and restore deleted versions
  • delete and undelete pages, and to view and restore deleted revisions
  • protect and unprotect pages, and to edit admin-protected pages
  • block and unblock users, individual IP addresses and IP address ranges
  • edit less-restricted interface messages (see also Commons:Interface administrators)
  • rename files
  • add and remove user groups
  • configure Upload Wizard campaigns
  • delete and undelete specific log entries and revisions of pages
  • import pages from other wikis
  • merge the history of pages
  • modify abuse filters
  • not create redirects from source pages when moving pages
  • override the spoofing checks and title or username blacklist
  • send a message to multiple users at once (massmessage)
  • use higher limits in API queries

These are collectively known as the admin tools.

Community role

Administrators are experienced and trusted members of the Commons community who have taken on additional maintenance work and have been entrusted with the admin tools by public consensus/vote. Different admins have different areas of interest and expertise, but typical admin tasks include determining and closing deletion requests, deleting copyright violations, undeleting files where necessary, protecting Commons against vandalism, and working on templates and other protected pages. Of course, some of these tasks can be done by non-admins as well.

Administrators are expected to understand the goals of this project, and be prepared to work constructively with others towards those ends. Administrators should also understand and follow Commons' policies, and where appropriate, respect community consensus.

Apart from roles which require use of the admin tools, administrators have no special editorial authority by virtue of their position, and in discussions and public votes their contributions are treated in the same way as any ordinary editor. Some admins may become more influential, not due to their position as such, but from the personal trust they may have gained from the community.

Suggestions for administrators

Please read Commons:Guide to adminship.

Removal of administrator rights

Under the de-admin policy, administrator rights may be revoked due to inactivity or misuse of sysop tools. In a de-admin request, normal standards for determining consensus in an RfA do not apply. Instead, "majority consensus" should be used, whereby any consensus to demote of higher than 50% is sufficient to remove the admin.

Apply to become an administrator

All intending administrators must go through this process and submit themselves to RFA, including all ex-administrators who are seeking to return to their previous role.

First, go to Commons:Administrators/Howto and read the information there. Then come back here and make your request in the section below.

  • If someone else nominated you, please accept the nomination by stating "I accept" or something similar, and signing below the nomination itself. The subpage will still need to be transcluded by you or your nominator.


Use the box below, replacing Username with your username:

Voting

Any registered user may vote here although those who have few or no previous edits may not be fully counted. It is preferable you give reasons for both Support and Oppose votes as this will help the closing bureaucrat in their decision. Greater weight is given to an argument, with supporting evidence if needed, than to a simple vote.

Promotion normally requires at least 75% in favour, with a minimum of 8 support votes. Votes from unregistered users are not counted. However, the closing bureaucrat has discretion in judging community consensus, and the decision will not necessarily be based on the raw numbers. Bureaucrats may, at their discretion, extend the period of an RfA if they feel that it will be helpful in better determining community consensus.

 Neutral comments are not counted in the vote totals for the purposes of calculating pass/fail percentages. However, such comments are part of the discussion, may persuade others, and contribute to the closing bureaucrat's understanding of community consensus.

Purge the cache Use the edit link below to edit the transcluded page.

Requests for adminship

When complete, pages listed here should be archived to Commons:Administrators/Archive.

  • Please read Commons:Administrators before voting here. Any logged in user may vote although those who have few or no previous edits may not be fully counted.


Bedivere

Vote

Bedivere (talk · contributions · deleted user contributions · recent activity · logs · block log · global contribs · CentralAuth) (Activity: Talk Commons DR)

Scheduled to end: 22:34, 28 February 2024 (UTC)

Hello again! It's been a year since my last request for adminship. I took those comments and votes at heart and have tried my best, with the limited time I have, to contribute more and more to this project. I have been an active participant in Commons for nearly four years, and have contributed especially in regards to copyright issues, participating for example tagging copyvios, in discussions for deletion, and general maintenance tasks. I believe my dedication and commitment to the platform's core principles are unwavering. I have created a more comprehensive local user page (in response to one of the older RFA comments), reflecting my sincere dedication to contributing meaningfully to this community. I am committed to continually educating myself on copyright matters, as I am currently a law student. If entrusted with adminship, I pledge to utilize my skills and experience to address the backlog of deletion requests, combat copyright violations, and provide assistance to fellow users. Additionally, my proficiency in Spanish positions me to better support speakers of that language. I humbly request your support and vote of confidence in this endeavor. I am steadfast in my commitment to learning and growing alongside our community. I appreciate all comments and questions, and I am looking forward to respond to each one! Thanks in advance. Bedivere (talk) 22:34, 21 February 2024 (UTC)Reply[reply]

Votes

Comments

Matrix

Vote

Matrix (talk · contributions · deleted user contributions · recent activity · logs · block log · global contribs · CentralAuth) (Activity: Talk Commons DR)

Scheduled to end: 17:20, 26 February 2024 (UTC)

Hello, I'm Matrix. I would like to request administrator tools to handle copyright violations, deletion requests and to generally tackle the admin backlog. I've been an active member of Commons, having done ~7K edits whilst attaining licence reviewer and filemover and helping with various backlogs such as Category:All media needing categories as of 2017, Category:Media requiring renaming, etc. Feel free to ask questions below. Cheers, —Matrix(!) {user - talk? - contributions} 17:20, 19 February 2024 (UTC)Reply[reply]

Votes

Comments

  •  Question You are a license reviewer since April 2023 but you only have 236 patrols logged. And you made some problematic overwrites in the past. What do you say on this? GPSLeo (talk) 18:18, 19 February 2024 (UTC)Reply[reply]
    @GPSLeo: Generally, I've been focused on other maintenance tasks, such as some I've pointed out above (categorisation, importing files to Commons, etc.). When it comes to actually patrolling, I like to focus on quality and not quantity (i.e. making sure that the content is free and not a copyvio, checking scope, etc.) rather than being particularly fast. This explains the large number of redlinks on my patrol log (copyvios).
    Furthermore, I often patrol the File talk namespace, so I usually ensure any comments on the talk page of the file don't go unnoticed by replying, which takes time.
    As for file overwrites, it would be helpful if you pointed out specific overwrites so I can discuss in more detail. Generally I follow Commons:Overwriting_existing_files, and I usually have done acceptable overwrites such as cropping on the subject of an image, adding higher resolution versions or removing watermarks. —Matrix(!) {user - talk? - contributions} 18:42, 19 February 2024 (UTC)Reply[reply]
    On example is your change at File:Peter Rainier by Thomas Hickey.jpg. GPSLeo (talk) 18:47, 19 February 2024 (UTC)Reply[reply]
    @GPSLeo: Looking at Commons:Overwriting existing files#DO overwrite, my rationale at the time was that this would fall under minor and uncontroversial color correction, since it was a higher-res image that was more vibrant. I also doubt whether this would fall under "digital restoration". Looking back, this change would probably fall under the grey area, since it's unclear whether the change in vibrancy was minor or uncontroversial. It is also important to note that I overwrote this image at enwiki, and then imported it to Commons, and enwiki doesn't really have an actual policy on this.
    However, these days I would now err on the side of caution and upload a new file and tag with {{Superseded}}. —Matrix(!) {user - talk? - contributions} 18:59, 19 February 2024 (UTC)Reply[reply]
    IMO this case is fine. It is the same painting, but in higher solution. I don't see the point of creating separate files here, as the first version would not be useful once the new version is uploaded. Now, if the painting were edited in any way, that would be different. Yann (talk) 20:01, 19 February 2024 (UTC)Reply[reply]
    I agree with that. This should not be a problem. Mosbatho (talk) 22:46, 20 February 2024 (UTC)Reply[reply]
    Two other examples are File:Institute of Medical Sciences, Japan.jpg and File:Caboose from Monongahela Railroad no.67 at Railroad Museum of Pennsylvania 115440.jpg where you overwrote with Crop Tool using precise mode. There appear to be more examples of overwrites using precise mode that I could have chosen. Are you aware of the limitations of precise mode? From Hill To Shore (talk) 10:49, 20 February 2024 (UTC)Reply[reply]
    I feel like this is extremely nitpicky. I've been an admin since 2005 and I don't even know what you're referring to. If precise mode is so problematic, then why is it the default choice? COM:CropTool doesn't even elaborate beyond "Note that in many cases an inexact (Lossless mode) is completely sufficient and recommended." holly {chat} 18:09, 20 February 2024 (UTC)Reply[reply]
    I have withdrawn the question on the basis that the guidance page you linked says, "As of September 2020, all cropping is done using lossy mode, even if lossless mode is selected and the tool says that a lossless crop was performed." Precise mode used to be discouraged as it often caused problems with file quality/compression if you left the image with an indivisible number of pixels in a particular direction. However, if both choices are producing the same result, the question is redundant. I don't think "nitpicky" is a fair description of the question though as that implies I was deliberately taking a negative attitude to the candidate. From Hill To Shore (talk) 18:34, 20 February 2024 (UTC)Reply[reply]
    My apologies. I should have said "obscure" instead. holly {chat} 18:50, 20 February 2024 (UTC)Reply[reply]
 Question Here are some common deletion request scenarios. What would be your initial decision (and reasoning) for each one? (Obviously, the final decision might change depending on whatever information is uncovered during the discussion, but let's just stick with your first thought.) Feel free to answer inline. holly {chat} 18:33, 20 February 2024 (UTC)Reply[reply]
  1. Nomination is for a PNG version of a coat of arms file with the rationale "superior SVG version exists now" and all usages of the PNG have been replaced by the SVG. The SVG version cites the PNG version as its source.
    Looking at the superseded image policy, I would firstly assess whether there are any specific significant stylistic differences between the PNG and SVG. If so, I would keep the PNG or defer to the graphics lab to create a faithful reproduction of the SVG. If there is own work involved, I wouldn't delete as it would break the "attribution path" for licences such as GFDL. Otherwise, I would copy the history over using a tool such as fileinfo and then !vote delete. —Matrix(!) {user - talk? - contributions} 20:30, 20 February 2024 (UTC)Reply[reply]
  2. Nominator asks for a courtesy deletion of their own photo because they feel like the quality is not very good. It is currently unused, but it was uploaded 10 years ago, and when you look in the category, there are no other photos that show the same subject.
    Assuming there are no privacy issues with topics such as GDPR, I would reject this argument due to the sheer time of the image being online and lack of other options at the time for the same subject. If appropriate I would prompt the uploader to upload a better quality image. —Matrix(!) {user - talk? - contributions} 20:30, 20 February 2024 (UTC)Reply[reply]
  3. Nomination is for a photo uploaded by the person depicted in the photo and it does not appear to be a selfie or a case where the person used a timer, but is claimed as "own work". When questioned, uploader reveals that his friend took the photo and gave it to him, whereupon he uploaded it.
    I would direct the uploader to COM:VRT, asking his friend to email VRT. If there is no response, or the response does not release a free licence, then I would !vote delete. —Matrix(!) {user - talk? - contributions} 20:30, 20 February 2024 (UTC)Reply[reply]
  4. Nomination is for a photo of an old painting in a museum, clearly PD, but also includes the frame. The photo was downloaded from the museum's website, is properly credited to the museum, and is tagged {{PD-Art|PD-old-70-expired}}, but the source page does not indicate a free license.
    If the painting hasn't been scanned before, and the frame/museum itself is not the source of commentary, it would be easier to simply crop the frame and do some revdel. Policy only allows PD-Art to be used when the image is a faithful reproduction. If the painting has been scanned before I would !vote delete. —Matrix(!) {user - talk? - contributions} 20:30, 20 February 2024 (UTC)Reply[reply]
  5. Nomination is for a company's logo and the file was downloaded from the company's site. The nominator's rationale is "copyright violation".
    This depends on whether the logo passes the threshold of originality in the US as well as the one in the country of origin. For example, the British threshold of originality is extremely low and many British logos have to be deleted due to this. —Matrix(!) {user - talk? - contributions} 20:30, 20 February 2024 (UTC)Reply[reply]
  6. Nomination is for a chart that is used across multiple projects and was created by a Commons user who has since retired, and the data for the chart is cited to what appears to be a reliable source. Nominator claims that the source is obsolete and provides a citation to a source with updated data.
    I would !vote keep, since COM:INUSE overrides claims that the data is unreliable. The uploader can create a new chart with the updated source, and local projects can decide whether to use it or not. —Matrix(!) {user - talk? - contributions} 20:30, 20 February 2024 (UTC)Reply[reply]
  •  Question Your answers here compel me, but I know so little about you. I checked your talk page and while there is nothing really negative, much positive isn't there either. Did you run into some disagreements during your wikipedia career? Were you able to solve them to the satisfaction of the ones involved?Paradise Chronicle (talk) 11:08, 21 February 2024 (UTC)Reply[reply]
    @Paradise Chronicle: My work on Commons has primarily consisted of categorisation, uncontroversial speedy deletion nominations and regular DRs, which means I don't frequently run into major disagreements. However, one example of me starting a discussion on Commons and helping stop an edit war at File:Air Force Ensign of India.svg was at this file talk page, where consensus emerged to not proceed with a file move, and deal with issues locally on the respective projects the file was in use from. As showcased by that example, I always look to starting discussions and building consensus on the talk page when reverts stack on a page. —Matrix(!) {user - talk? - contributions} 18:17, 21 February 2024 (UTC)Reply[reply]
  •  Comment All due respect to @Mateus2019: , but I was not aware admins needed to be special. I guess I should consider resigning as someone who is quite bland and uninteresting. Beside that, I can't run very fast, I'm proper crap at karaoke, a terrible bowler, and while I do look like a painting in an art museum, it's only after some protester threw soup on it.
    My general impression was that admins needed to be a net positive, capable of helping out in a way that wont break the internet, and willing to admit when they were wrong. — Preceding unsigned comment added by GreenMeansGo (talk • contribs) 12:05 21 February 2024 (UTC)

Requests for bureaucratship

When complete, pages listed here should be archived to Commons:Bureaucrats/Archive.

  • Please read Commons:Bureaucrats before posting or voting here. Any logged in user may vote although those who have few or no previous edits may not be fully counted.

No current requests.

Requests for CheckUser rights

When complete, pages listed here should be archived to Commons:Checkusers/Archive.

  • Please read Commons:Checkusers before posting or voting here. Any logged in user may vote although those who have few or no previous edits may not be fully counted.

No current requests.

Requests for Oversight rights

When complete, pages listed here should be archived to Commons:Oversighters/Archive.

  • Please read Commons:Oversighters before voting here. Any logged in user may vote, although those who have few or no previous edits may not be fully counted.

No current requests.

See also