Commons:Administrators/Proposed

< Commons:Administrators
Note: it's historical because the changes this page suggested were adopted. If in future another mass rewrite is thought needed, raise the issue at the VP, then if warranted, blank the page and take another pass.
Administrators as of June 2016 [+/−]
Listing by language
Listing by date
Listing by activity

Number of Admins: 245

  1. -revi, ko, en-3 (global renamer)
  2. ~riley, en, fr-1, es-1
  3. 1Veertje, nl, en-4, de-1, fr-1
  4. 32X, de, en-2, hsb-1, ru-1
  5. 99of9, en (bureaucrat, global renamer)
  6. A.Savin, ru, de-4, en-2
  7. Achim55, de, en-3, nds-3, la-2
  8. AFBorchert, de, en-3 (bureaucrat)
  9. Ahonc, uk, ru-4, en-2, de-1 (global renamer)
  10. Aka, de, en-3
  11. Alan, es, eu-3, en-2
  12. Alison, en, ga-3, fr-2, gd-1
  13. Alno, fr, en-3, es-2, pt-1
  14. Alpertron, es, en-3
  15. Amada44, de, en-3, fr-1
  16. Angr, en, de-4, fr-2, ga-2, la-2, cy-1
  17. Ankry, pl, en-2, ru-1
  18. AnRo0002, de, en-2, fr-2, es-1
  19. Anthere, fr, en-3
  20. Aude, en, ar-2, de-2, es-3
  21. Avenue, en, de-1, fr-1, it-1
  22. Avraham, en, he-2 (oversighter, steward)
  23. Axpde, de, en-4, es-1, fr-1, it-1, nl-1
  24. AzaToth, sv, en-4
  25. Badseed, el, en-3, it-1
  26. Barcex, es, en-2, fr-1
  27. Bastique, en, fr-3, es-2, la-2, ga-1
  28. Basvb, nl, en-3, de-2
  29. Benoit Rochon fr, en-4
  30. Beria, pt, en-2, es-2
  31. Billinghurst, en
  32. Blackcat, it, en-3, fr
  33. Blurpeace, en, es-1
  34. BrightRaven, fr, en-3, nl-2, es-2, zh-1
  35. Butko, ru, uk-2, en-1
  36. Cambalachero, es, en-3
  37. Captain-tucker, en
  38. ChrisiPK, de, en-3, fr-1
  39. Christian Ferrer, fr, en-2
  40. Ciell, nl, en-2, de-1
  41. Common Good, en
  42. Cookie, es, en-2
  43. Courcelles, en, es-2, fr-2
  44. Coyau, fr, en-1
  45. Czar, en
  46. DaB., de, en-1
  47. Dantadd, it, pt, en-3, es-3, fr-3, gl-3, ca-2, ro-1, el-1
  48. Darwinius, pt, en-3, es-2, fr-2, gl-2, ca-1, it-1, oc-1
  49. Davepape, en
  50. David Levy, en
  51. De728631, de, en-5
  52. Dereckson, fr, en-3, de-1, nl-1
  53. DerHexer, de, en-3, grc-3, la-3, es-1 (steward)
  54. Dharmadhyaksha, mr, en-3, hi-3
  55. DMacks, en
  56. Didym, de, en-2, fr-2
  57. Dschwen, de, en-3, fr-1 (bureaucrat)
  58. D-Kuru, de, en-2, it-1
  59. Ebrahim, fa
  60. Edgar181, en, de-1, fr-1, es-1
  61. Elcobbola en, de (checkuser)
  62. Eleassar, sl, en-3, de-2, fr-2
  63. Elitre, it, en-3, fr-2
  64. Ellin Beltz, en (bureaucrat)
  65. Elya, de, en-3, uk-2, ru-1
  66. Emha, de, bar, en-3, fr-1
  67. EPO, da, en-3, de-1
  68. Érico, pt, en-2, es-1 (global renamer)
  69. Esby, fr, en-3, de-1
  70. EugeneZelenko, ru, be, en-2, bg-1, pl-1 (bureaucrat)
  71. Ezarate, es-3, en-1
  72. Fanghong, zh, en-2, fr-1
  73. Flominator, de, als, en-3
  74. FunkMonk, da, en-4, no-3, fo-2, sv-2, de-1, es-1
  75. Geagea, he, ka-3, en-3, ru-1
  76. Geni, en
  77. George Chernilevsky, ru, uk-3, de-2, en-2, bg-1, la-1, be-1, fr-1
  78. Gestumblindi, als, de, en-3
  79. Gnangarra, en
  80. Golbez, en, ja-2
  81. Green Giant, en, de-1, fr-1
  82. grin, hu, en-3, de-1
  83. Gruznov, ru, en-1, fr-1
  84. Hedwig in Washington, de, en-4, nds-1
  85. Hekerui, de, en-4
  86. Herbythyme, en, fr-2, es-1, it-1
  87. Hesperian, en
  88. HJ Mitchell, en
  89. Howcheng, en, ja-2
  90. Huntster, en
  91. Hystrix, de, en-1
  92. H-stt, de, en-4, fr-1
  93. Indeedous, de, en-3, fr-2
  94. Infrogmation, en, es-1
  95. Jameslwoodward, en, fr-1 (bureaucrat, checkuser)
  96. January, en
  97. Jaqen, it, en-2
  98. Jarekt, pl, en
  99. JarrahTree, en, id-1
  100. Jastrow, fr, en-3, de-1, it-1
  101. Jcb, nl, en-3, es-3
  102. Jcornelius, de, lt-2, la-2, en-2, pt-2, fr-1
  103. Jdforrester, en
  104. Jean-Frédéric, fr, en-4, es-1
  105. JGHowes, en, fr-2, de-1
  106. Jianhui67, en, zh-3, ms-1 (global renamer)
  107. Jmabel, en, es-3, ro-2, de-1, ca-1, it-1, pt-1, fr-1
  108. Joergens.mi, de, en-3
  109. John Vandenberg, en
  110. Julo, pl, en-2, de-1, ru-1
  111. JuTa, de, en-2, fr-1 (bureaucrat)
  112. Jusjih, zh, en-3, fr-1, ko-1
  113. Kaldari, en
  114. Kallerna, fi, en-3, sv-2, de-1
  115. Kanonkas, no, en-4, nn-3, da-2, sv-2, de-1 (bureaucrat)
  116. Killiondude, en, es-3, ru-1
  117. King of Hearts, en, zh-3, es-2
  118. Klemen Kocjancic, sl, en-3, de-2, hr-1, bs-1
  119. Krd, de, en-3 (bureaucrat, checkuser)
  120. Krinkle, nl, en-3, de-2
  121. Krzysiu, pl, en-2, szl-2
  122. KTo288, en, zh-4
  123. Kwj2772, ko, en-2
  124. Leit, de, en-3, fr-1
  125. Léna, fr, en-3, es-1
  126. Leyo, gsw, de, en-3, fr-3, es-1, la-1
  127. Logan, en, es-3
  128. Lokal Profil, sv, en-4, pt-2, fr-1
  129. LtPowers, en, es-1
  130. Lymantria, nl, de-2, en-2, fy-2, fr-1, zea-1
  131. Magog the Ogre, en, es-2 (checkuser)
  132. Maire, pl, en-4, es-2, fr-2, de-2, ru-1 (global renamer)
  133. Marcus Cyron, de, en-2
  134. Mardetanha fa, az, en-3, tr-2, ar-1 (steward)
  135. Martin H., de, en-2
  136. Masur, pl, en-3, de-1
  137. Matanya, en, he (steward)
  138. Materialscientist, en-4, ru-4, nl-3, fr-1, es-1
  139. Mattbuck, en, fr-1, la-1
  140. Maxim, ru, en-3, fr-2
  141. MBisanz, en (steward)
  142. McZusatz, de, en-3, es-1, la-1 swg-1
  143. Mentifisto, en, mt, it-2 (steward)
  144. MGA73, da, en-3, de-2, sv-1, no-1
  145. MichaelMaggs, en, fr-1 (bureaucrat)
  146. Micheletb, fr, en-3, it-1, es-1
  147. Missvain, en
  148. Mitchazenia, en, es-2
  149. Miya, ja, en-2
  150. Mmxx, fa, en-3
  151. Mono, en
  152. Morgankevinj, en, es-1, la-1
  153. Mormegil, cs, en-2, de-1
  154. M0tty, fr, en-1
  155. MPF, en, da-2, de-1, fr-1
  156. Multichill, nl, en-3, de-1, fr-1
  157. Mys 721tx, zh, en-3 (global renamer)
  158. Nagy, de, en-3, fr-2, es-1, sv-1
  159. NahidSultan, bn, en-3, bpy-1
  160. Natuur12, nl, en-3, de-1
  161. Neozoon, de, en-4, nl-4, fr-2
  162. Nick, en, sco-2, fr-1
  163. Niklem, ru, en-3
  164. Nilfanion, en, fr-1
  165. NordNordWest, de, en-3
  166. notafish, fr, en-4, de-3, es-2, it-2
  167. Nyttend, en, ang-1
  168. odder, pl, en-4, de-2 (bureaucrat, oversighter)
  169. Okki, fr, en-2
  170. Otourly, fr, en-2, it-1
  171. P199, en, nl, fr-2, tl-2, de-1
  172. PierreSelim, fr, en-3, es-1 (oversighter)
  173. Pitke, fi, en-4, sv-2
  174. Platonides, es, en-2, fr-1
  175. Pleclown, fr, en-3
  176. Poco a poco, es, de-4, en-3, fr-2, it-2, pl-2, pt-1
  177. Podzemnik, cs, en-2
  178. Polarlys, de, en-2, fr-1, no-1
  179. Powerek38, pl, en-4, fr-2, es-1, de-1
  180. PumpkinSky, en, de-2
  181. Putnik, ru, en-2
  182. Pyb, fr, en-2
  183. Pymouss, fr, en-3, de-2, it-2, he-1
  184. Ragesoss, en, de-1, fr-1
  185. Ra'ike, de, en-2
  186. Rama, fr, en-3, de-2, la-2, es-1, it-1, ja-1 (oversighter)
  187. Rastrojo, es, en-3, fr-2, eo-1
  188. Raymond, de, en-3, nl-1 (oversighter)
  189. Rehman, en, si-1
  190. Reinhard Kraasch, de, en-3
  191. Revent, en
  192. Rillke, de, en-2, fr-1
  193. Rimshot, de, en-4, fr-2, it-1
  194. Rodhullandemu, en, fr-1, de-1, sv-1
  195. Romaine, nl, en-3, de-2, af-1, fr-1
  196. Ronhjones, en, fr-1
  197. Rosenzweig, de, en-3, fr-1, la-1
  198. Royalbroil, en, es-1
  199. RP88, en, de-1
  200. Rubin16, ru, tt, en-3 (global renamer)
  201. Rudolphous, nl, en-3, de-2
  202. Sanandros, als, de, en-3, fr-1
  203. Sandstein, als, de, en-4, fr-3, it-1
  204. Sealle, ru, en-4, pl-2, sk-2, uk-2
  205. Shizhao, zh, en-1, ru-1
  206. Siebrand, nl, en-3, fr-1, de-1
  207. Sphilbrick, en
  208. Spiritia, bg, en-3, ru-2, mk-2, de-1
  209. Sreejithk2000, ml, en-3, hi-3, ta-1, kn-1
  210. Steinsplitter, bar, de-4, it-3, en-1 (global renamer)
  211. Stifle, en, ga, fr-2, de-1
  212. Storkk, en, fr-3, de-2, eo-2
  213. Tabercil, en
  214. Taivo, et, en-3, ru-3, de-1
  215. Tarawneh, en, ar, de-1
  216. Techman224, en
  217. Teles, pt, en-3, es-2 (steward)
  218. Thibaut120094, fr, en-2, ja-2
  219. Thuresson, sv, en-3, no-2
  220. Tom, en, es-1
  221. Trijnstel, nl, en-4, de-1, fr-1 (checkuser, steward)
  222. tsca, pl, en, da
  223. Túrelio, de, en-3, es-1
  224. VIGNERON, fr, de-2, en-2, zh-1
  225. Waldir, pt, en-3
  226. Wdwd, de, en-2
  227. Whym, ja, en-2
  228. Wikitanvir, bn, en-3, as-2, bpy-1 (steward)
  229. WJBscribe, en, fr-3, de-1 (global renamer)
  230. Wsiegmund, en, fr-1, es-1
  231. Wutsje, fy, nl, en-3, de-2, fr-1
  232. Wuzur, de, en-3
  233. wvk, de, en-4, fa-3, fr-2
  234. Yann, fr, en-3, hi-2, gu-1
  235. Yarl, pl, en-2, de-1, ru-1
  236. Yasu, ja, en-2, de-1
  237. Ymblanter, ru, en-3, de-2, fr-2, nl-2, it-1, es-1
  238. Yuval Y, he, en-3
  239. Zhuyifei1999‎, zh, en-4
  240. Zzyzx11, en, es-1, fr-1
  241. とある白い猫, en, tr, az-3, ja-2, fr-1, nl-1
  242. CommonsDelinker, (bot)
  243. CommonsMaintenanceBot, (bot) see request
  244. GifTagger, (bot) see request
  245. KrinkleBot, (bot) see request

The system currently recognizes 245 administrators. If that is not the last number in the list above, there is an error in the list.

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 Commons:Administrators' noticeboard.

There are currently 245 administrators on Commons.

What is an administrator?Edit

TechnicalEdit

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 the MediaWiki namespace

These are collectively known as the admin tools.

Community roleEdit

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. Of course, some admins are influential, but that derives not from their position as such but from the personal trust they have gained from the community.

How do I become an administrator?Edit

First, consider whether becoming an administrator is the best way for you to contribute to the project. Experience shows that outstanding contributors of content often reduce their contributions because of the maintenance overhead after they become admins, and this is what we want least. So please contribute your best skills and understand that there are many ways of getting community credit besides being an admin. Admin status on Commons is not an honour for outstanding content contributors, but just provides an additional set of tools for people who show that they want to clean up.

Consider whether you actually need the admin tools for the work you would like to do. The community does not hand out the tools to those who do not need or who are not likely to make use of them. So, if you need the tools only for a limited period, or in order to clean up your own contributions, please simply ask an existing admin to help you out.

Admins are expected to remain reasonably active here, and if after appointment you cease to use the tools for an extended period you will automatically lose them under our de-admin policy. You should expect as a admin to make yourself available on Commons to a reasonable extent (a userpage that asks people to leave messages for you on some other project is not considered acceptable practice for an admin).

We do not have any hard and fast rules setting out the minimum period you should have been active on Commons in order to apply for adminship, nor any minimum number of edits. However, the requirement that you be a experienced and trusted member of the Commons community typically means that prior to applying you should have had sufficient breadth and depth of experience here to be able to demonstrate that. If you are an admin or an experienced user on another project, by all means mention that, but bear in mind that off-Commons experience is on its own not normally enough.

Although not mandatory, it is often a good idea to talk to existing admins to get feedback about your experience and approach. You may be able to get another admin to nominate you, although self-nominations are also allowed.

When you request adminship, the community will consider your ability to fill the admin role. Individual Commons contributors may have varying expectations of candidates, and you may wish to review some archived RFAs to get a sense of what people are looking for. As a practical matter, users often want to see a reasonable level of involvement in admin-type activities such as deletion requests, accurately tagging images as copyright violations, new user patrolling, and so on. Users often want to be satisfied that you are an integral member of the Commons community and will look at the way you interact with others, on user talk pages and elsewhere.

The request for adminshipEdit

When you are ready, make sure you have a userpage, enable email in your preferences, then apply, or ask your nominator to apply, using the box below:

Use the box below, replacing username with your username:



Next stepsEdit

  • 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.

The public discussion and voteEdit

Adminship nominations usually remain open for seven days, for votes and comments. The period starts when you posted your nomination (if a self-nom) or when you posted your acceptance (if somebody else nominated you). At the end of that period the nomination will be closed by a bureaucrat who will either grant or decline promotion. The nomination may be left open for more than seven days, or a longer period specified, should a bureaucrat consider that desirable.

As a guideline, promotion normally requires at least 75% in favour, with a minimum of 4 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. Among other things, the closing bureaucrat may take into account the strength of any arguments presented and the experience and knowledge of the commenting users. For example, the comments and votes of users who have zero or few contributions on Commons may at the bureaucrat ‘s discretion be discounted.

If the nomination is successful, the closing bureaucrat will grant the applicant admin rights.

Suggestions for administratorsEdit

Please read Commons:Guide to adminship.

  • Previous requests are listed in the /Archive.

How to make a requestEdit

AdminshipEdit

Use the box below, replacing username with your username:



See: Commons:List of administrators

BureaucratshipEdit

Use the box below, replacing username with your username:



See: Commons:List of bureaucrats

CheckuserEdit

Use the box below, replacing username with your username:



See: Commons:List of checkusers

OversightEdit

Use the box below, replacing username with your username:



See: Commons:List of oversighters


Requests for permission to run a botEdit

Use the box below, replacing botname with your bot's username:



See Commons:Bots/Requests for the whole process.

Next stepsEdit

  • After creating the subpage, you must transclude it on Requests and votes, at the top of the section.
  • If someone else nominated you, rather than you nominating yourself, please "accept" the nomination by stating "I accept" or something similar, and signing below the nomination itself. This puts you on record as accepting, and the timestamp of the acceptance is how we determine when the request started (so we don't close early by mistake). The subpage will still need to be transcluded by you or your nominator.

CandidatesEdit

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

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

Shortcut
COM:VOTE
This project page in other languages:

This is the requests and votes page, a centralized place where you can keep track of ongoing user requests, and where you can comment and leave your vote. Any user is welcome to comment on these requests, and any logged in user is welcome to vote.

When requesting rights that do not need the support of the community (e.g. filemover) please go to Commons:Requests for rights!

How and where to apply for additional user rights on CommonsEdit

How to comment and voteEdit

Any logged-in user is welcome to vote and to comment on the requests below. Votes from unregistered users are not counted, but comments may still be made. If the nomination is successful, a bureaucrat will grant the relevant rights. However, the closing bureaucrat has discretion in judging community consensus, and the decision will not necessarily be based on the raw numbers. Among other things, the closing bureaucrat may take into account the strength of any arguments presented and the experience and knowledge of the commenting users. For example, the comments and votes of users who have zero or few contributions on Commons may at the bureaucrat's discretion be discounted.

It is preferable if you give reasons both for Symbol support vote.svg Support votes or Symbol oppose vote.svg Oppose ones as this will help the closing bureaucrat in their decision. Greater weight is given to argument, with supporting evidence if needed, than to a simple vote.

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

Requests for Oversight rightsEdit

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.

Requests for CheckUser rightsEdit

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 bureaucratshipEdit

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

  • Please read Commons:Bureaucrats 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.

Requests for adminshipEdit

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.

INeverCry (readmin)Edit

Vote

INeverCry (talk · contributions · deleted user contributions · recent activity · logs · block log · global contribs · SULinfo)

Scheduled to end: 04:04, (UTC)

It's been just about a year since my meltdown of last July. What happened was that I became too emotionally involved in my efforts to stop Russavia from socking. I wasn't stable or mellow at the time, and so I ended up doing things that were unacceptable, dramatic, and uncalled for. As some speculated at the time, my actions started with a complete over-reaction to an account that Russavia created called Snitches get stitches. I took this as being directed at me, and I went off the deep end over it. My blocks of Fae and Stemoc were out of line and unacceptable. They were petty revenge blocks without a whole lot of thought behind them. I haven't apologized directly to Fae or Stemoc, thinking they'd rather not see or hear much from me, but I certainly do regret those actions, which were completely undeserved and were very immature of me. My deletions of Russavia sock uploads caused a lot of extra work for my fellow admins as well, and I hope they know that I didn't mean to cause them such a hassle.

If the community is willing to give me a last shot at adminship, I can say without a doubt that there would be no repeat of any of the above. I still remember seeing the de-admin and not knowing if I even wanted to continue editing as INeverCry out of embarrassment. I decided to own my extremely poor decisions and move on without trying to hide under a new account. I'll sink or swim as INC. As for Fae and Stemoc, I would not take any admin action in cases involving them in the future under any circumstances. I spoke to Russavia via email 6+ months ago, and we buried the hatchet. I wouldn't take any admin action where he's concerned either if I'm re-granted adminship by the community. I would also make it a point to continue to avoid my old confrontational behavior as I have for quite a while now.

If the community decides to give me another chance at adminship, my main focus would be on helping to keep the DR backlog down and deleting copyvios. I know now that I really used to overdo it hunting sockpuppets and obsessing on them. My approach would be much more laid back now and I would spend very little time in that area of admin work. I hope the community is willing to forgive me that horrid July night last year and give me a shot at being a Commons admin again, a position of trust that I just didn't realize the full value of in the past. Support or oppose, I thank the community for its consideration. INeverCry 04:04, 21 June 2016 (UTC)

VotesEdit

  • Symbol support vote.svg Support. Congrats for being mature enough to rethink your past mistakes. Most will do wrong, but too few will admit and learn with that. Let's keep with your enthusiasm and amazing contribution that you provenly are capable of.—Teles «Talk to me ˱C L @ S˲» 04:53, 21 June 2016 (UTC)
  • Symbol support vote.svg Support Everyone makes mistakes, only a few learn from it. Seems you did. — regards, Revi 05:14, 21 June 2016 (UTC)
  • Symbol support vote.svg Support Just stay out of drama :) --Zhuyifei1999 (talk) 05:25, 21 June 2016 (UTC)
  • Symbol support vote.svg Support I wish every admin reflected so well on past incidents. Hopefully welcome back. Natuur12 (talk) 07:15, 21 June 2016 (UTC)
  • Symbol support vote.svg Support per above. Yes! Jianhui67 talkcontribs 07:56, 21 June 2016 (UTC)
  • Symbol support vote.svg Support: I had only positive personal communication and seen a lot of useful work. In spite of last year situation was very bad, but I see INeverCry has made the right conclusions now. --sasha (krassotkin) 09:12, 21 June 2016 (UTC)
  • Symbol support vote.svg Support Extremely valuable admin in the past, extremely valuable user in the meantime. But please take more breaks when the drama level increases. Storkk (talk) 10:05, 21 June 2016 (UTC)
  • Symbol support vote.svg Support. -- Geagea (talk) 10:31, 21 June 2016 (UTC)
  • Symbol support vote.svg Support Poco2 10:41, 21 June 2016 (UTC)
  • Symbol support vote.svg Support Christian Ferrer (talk) 11:01, 21 June 2016 (UTC)
  • Symbol support vote.svg Support Rodrigolopes (talk) 11:43, 21 June 2016 (UTC)
  • Symbol support vote.svg Support - Being honest I don't think I'd support anyone at EN who had a meltdown etc etc etc however INC is a valuable editor/admin here and to be fair we all make mistakes which he's admitted, Plus he was always active at DR and keeping the backlogs down which was extremely helpful and I know DR is a painful task, The only thing I would suggest INeverCry is that if things get too much just walk away for a bit, Anyway 100% Support!. –Davey2010Talk 12:31, 21 June 2016 (UTC)
  • Symbol support vote.svg Support I can't wait to see the absence of backlog when INC is back in the saddle again. Backlog? What backlog? Ellin Beltz (talk) 13:22, 21 June 2016 (UTC)
  • Symbol support vote.svg Support, no doubt. --Achim (talk) 13:25, 21 June 2016 (UTC)
  • Symbol support vote.svg Support --EugeneZelenko (talk) 13:53, 21 June 2016 (UTC)
  • Symbol support vote.svg Support --1971markus ⇒ Laberkasten ... 15:33, 21 June 2016 (UTC)
  • Symbol support vote.svg Support - was a hardworking admin and checkuser - just remember to take regular breaks and stick to a low-fat diet when clearing out the backlog. Green Giant (talk) 16:42, 21 June 2016 (UTC)
  • Symbol support vote.svg Support Please! eurodyne (talk) 18:55, 21 June 2016 (UTC)
  • Symbol oppose vote.svg Oppose You all please pardon me for spoiling the party. The absence of admin tools undoubtedly has done INC good, and from my POV it should remain this way. Maybe after two years without unnecessary drama, retirements, and follow-up comebacks (latest one was January this year), we can discuss further, but so far I am not convinced. --A.Savin 21:09, 21 June 2016 (UTC)
  • Symbol support vote.svg Support - Jcb (talk) 22:17, 21 June 2016 (UTC)
  • Symbol support vote.svg Support. Strong yes. INeverCry is a very dedicated user that develops an excellent job for many years. Good luck! Érico (talk) 20:05, 22 June 2016 (UTC)
  • Symbol support vote.svg Support Magog the Ogre (talk) (contribs) 04:02, 25 June 2016 (UTC)
  • Symbol support vote.svg Support --Юкке (talk) 07:27, 25 June 2016 (UTC)
  • Symbol support vote.svg Support Taivo (talk) 10:33, 25 June 2016 (UTC)
  • Symbol support vote.svg Support --Steinsplitter (talk) 11:04, 25 June 2016 (UTC)
  • Symbol support vote.svg Support --Wdwd (talk) 16:59, 25 June 2016 (UTC)
  • Symbol support vote.svg Support since you're a good admin and every extra minute with you on the buttons is a plus. But it's hard for me to believe you this time: you first need to prove it. Remember, you were promoted (and removed) from CU three times already too... And each time you said that you were stable now. Trijnsteltalk 23:32, 25 June 2016 (UTC)
  • Symbol oppose vote.svg Oppose - Have been on Wikiland long enough to know that people never change, I trust INC as an editor, but I can no longer trust him with sysop bits..too much power for someone who has shown little ability to use it right...to quote spiderman, "With Great Power comes Great Responsibility"..--Stemoc 05:05, 26 June 2016 (UTC)

CommentsEdit

  • A.Savin makes a completely valid point. I honestly feel that I'm over my old drama and nonsense, but only time will serve to convince others of this. All I can say is that, whether this readmin request succeeds or not, I'll continue participating here in a calm and steady manner. I feel better with no drama, and I don't doubt Commons has had enough of my past drama too. One thing I figured out through my de-sysop was how much I really enjoy being here and working on Commons, and that my drama and impulsive retirements and comebacks only ever got in the way of that. When I came online this morning and saw the support votes, it certainly made me feel a lot better than any of my old nonsense ever did. INeverCry 23:15, 21 June 2016 (UTC)

We have no other admin, who had retired and came back so often as INC. A lot of users, including me, have said him (without any effect) not to retire so often. I think, that taking couple of months for wikibreak is totally normal and does not need putting down admin rights. Actually I do not believe, that INC adminship will last more than a year, but I feel, that even during this time he will be generally useful to the project. I promise: this is the last time, when I will support INC, next time I will oppose. Taivo (talk) 10:52, 25 June 2016 (UTC)


Requests for license reviewer rightsEdit


Requests for permission to run a botEdit

Before making a bot request, please read the new version of the Commons:Bots page. Read Commons:Bots#Information on bots and make sure you have added the required details to the bot's page. A good example can be found here.

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

Any user may comment on the merits of the request to run a bot. Please give reasons, as that makes it easier for the closing bureaucrat. Read Commons:Bots before commenting.

YiFeiBot (talk · contribs) (26)Edit

Operator: Zhuyifei1999 (talk · contributions · Number of edits · recent activity · block log · User rights log · uploads · Global account information)

Bot's tasks for which permission is being sought: From COM:BWR, mostly similar to Commons:Bots/Requests/YiFeiBot_(20), differences:

Automatic or manually assisted: Automatic unsupervised

Edit type (e.g. Continuous, daily, one time run): weekly

Maximum edit rate (e.g. edits per minute): 6 edits / min

Bot flag requested: (Y/N): N

Programming language(s): python: pywikibot

Zhuyifei1999 (talk) 09:36, 22 June 2016 (UTC)

DiscussionEdit

  • Test run ✓ Done 20 edits --Zhuyifei1999 (talk) 09:43, 22 June 2016 (UTC)
    Can't the wikidata stuff be directly pulled by some magic? --Krd 10:19, 22 June 2016 (UTC)
    Magic? I haven't taught my bot magic-crafting; in fact, I don't know much magic here. Perhaps you can find a magician for me? --Zhuyifei1999 (talk) 11:37, 22 June 2016 (UTC)
  • The test run looks good. The bot logic should be very simple, so I do not expect much misfiring. All the mismatches are reported in Category:Pages using authority control with parameters where I (I do not notice anybody else doing it) clean them by hand. As for pulling wikidata items by some magic. I can not think of a way to do it. The wikidata items might be already linked to the categories through Commons category (P373) but there is no way for us to detect it (that I know of). In the mean time our {{Authority control}} templates are much better off with more up-to-date Wikidata identifiers. and Wikidata can benefit from merging with Commons identifiers. Please approve. --Jarekt (talk) 13:05, 22 June 2016 (UTC)
  • I think will be good idea to change edit summary text to make clear that Wikidata ID is added to Template:Authority control call. --EugeneZelenko (talk) 13:59, 22 June 2016 (UTC)
    ✓ Done 21 edits Special:Diff/199670971 had an unexpected space (fixed now) --Zhuyifei1999 (talk) 16:26, 22 June 2016 (UTC)

If there are no objections, I think task should be approved. --EugeneZelenko (talk) 14:03, 24 June 2016 (UTC)

  • Symbol keep vote.svg Agree --Jarekt (talk) 18:47, 24 June 2016 (UTC)

Abbe98 Bot (talk · contribs)Edit

Operator: Abbe98 (talk · contributions · Number of edits · recent activity · block log · User rights log · uploads · Global account information)

Bot's tasks for which permission is being sought:

Update the Template:Map to a new version that can be previewed at commons.wikimedia.beta.wmflabs.org. This update is a part of the Wikimaps Warper Individual Engagement Grant project and the new Map template is supposed to be used at a workshop next week(at Wikimania). There is about 12000 pages that will need to be updated.

Automatic or manually assisted: Automatic

Edit type (e.g. Continuous, daily, one time run): One time run

Maximum edit rate (e.g. edits per minute): 50 edits/minute, (this number is based on simulation, I simulated the entire process, but with actual edits the rate might be lower).

Bot flag requested: (Y/N): Y

Programming language(s): Python(PyWikiBot as framework)

Abbe98 (talk) 11:11, 15 June 2016 (UTC)

DiscussionEdit

  • Please make a few test edits. --Krd 12:06, 15 June 2016 (UTC)
It should be noted that such test edits will break existing applications such as the Wikimaps Warper witch depends on the template, those applications is supposed to be updated in parallel to this update. --Abbe98 (talk) 15:00, 15 June 2016 (UTC)
I have now notified the application owners and will await their response. --Abbe98 (talk) 15:15, 15 June 2016 (UTC)

Requests for commentEdit

Read in another language