Commons:Moderators

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search
Commons Administrator.svg
Administrators as of June 2018 [+/−]
Listing by language
Listing by date
Listing by activity

Number of Admins: 225

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

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

Op Commons:Moderators staat alle noodzakelijke informatie over moderatoren van Wikimedia Commons en de pagina bevat ook de stemming over aanmeldingen voor moderatorrechten. Ook aanvragen voor bots worden hier behandeld.

Wat zijn moderatoren?[edit]

Moderatorrechten zijn voor gekende en vertrouwde gebruikers van de gemeenschap die bekend zijn met het beleid van Commons. Het hebben van deze rechten heeft geen enkele invloed op de inhoud van het project. Een moderator is een vertrouwde gebruiker die:

  • Pagina's beveiligt en de beveiliging op kan heffen.
  • Pagina's verwijdert en weer terughaalt.
  • Afbeeldingen en andere bestanden verwijdert.
  • Gebruikers (de)blokkeert.
  • Systeemteksten en andere beschermde pagina's wijzigt.

Gebruikers met check user-rechten kunnen daarnaast ook controleren of een gebruiker meer dan één account gebruikt (sokpoppen). Bureaucraten hebben ook de mogelijkheid om:

  • andere gebruikers moderator te maken.
  • gebruikersnamen te wijzigen (zie gebruikersnaam wijzigen).
  • botbitjes toe te kennen en af te nemen.

Verwachtingen van een moderator[edit]

Het is mogelijk moderatorrechten op Commons aan te vragen als je aan de volgende criteria voldoet:

  • Je bent bekend met wikimediaprojecten. Je moet de laatste twee maanden bijgedragen hebben en de doelen van dit project begrijpen en ondersteunen.
  • Je hebt een gebruikerspagina op Commons, draagt bij aan Commons en hebt minimaal 200 wijzigingen gemaakt (uploads of tekstueel).
  • Je gaat akkoord met het volgen van het relevante beleid en respecteert de consensus van de gebruikers van Commons.

Net als bij het beheerdersbeleid op Meta, kan een inactieve beheerder deze rechten weer worden ontnomen. Volgens dit beleid wordt iedere inactieve beheerder op Commons zijn beheerdersrechten afgenomen. "Inactief" betekent geen wijzigingen in de afgelopen zes maanden en minder dan 50 wijzigingen in het afgelopen jaar. Inactieve beheerders kunnen zich volgens de reguliere procedure opnieuw aanmelden.

Aanvraag moderatorrechten[edit]

  • Aanvragen staan gedurende zeven (7) dagen voor stemmen en opmerkingen. Moderatorrechten worden toegekend bij een meerderheid van ten minste 75% en minimaal vier (4) positieve stemmen. In dit geval wordt het verzoek doorgestuurd aan een bureaucraat voor uitvoering.
  • Op deze pagina staan ook andere aanvragen. Zo kan je hier bijvoorbeeld een aanvraag voor een botbitje plaatsen voordat je een robot gaat gebruiken.
  • Eerdere aanvragen zijn te vinden in het archief.

Hoe je moderatorrechten aanvraagt[edit]

Maak een subpagina Commons:Administrators/Requests and votes/Gebruikersnaam met de volgende tekst en neem de pagina bovenaan op in Administrators/Requests and votes:

===[[User:Gebruikersnaam|Gebruikersnaam]]===
{{custom edit|Template:Administrators/Requests and votes/Gebruikersnaam|text='''Vote'''}}

Reden waarom je beheerder wilt worden. ~~~~

====Votes====

Kandidaten[edit]

Purge the cache

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 Commons[edit]

All applications made on the above pages are automatically transcluded onto this page.

How to comment and vote[edit]

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 rights[edit]

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 rights[edit]

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 bureaucratship[edit]

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 adminship[edit]

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.

No current requests.


Requests for license reviewer rights[edit]

Requests for permission to run a bot[edit]

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.

JonHaraldSøbyWMNO-bot (talk · contribs)[edit]

Operator: Jon Harald Søby (WMNO) (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: Uploading images in cooperation with Wikimedia Norge's GLAM partners.

Automatic or manually assisted: Automatic, but supervised – it will only run when I am online and available.

Edit type (e.g. Continuous, daily, one time run): Intermittently when our partners have available material.

Maximum edit rate (e.g. edits per minute): AndreCostaWMSE-bot, which runs on the same framework, seems to make one edit every ~2 minutes when it is active, so something close to that.

Bot flag requested: (Y/N): Y

Programming language(s): Python; using the Pywikibot-based Wikimedia-Commons-uploads framework from Nordic Museum.

Jon Harald Søby (WMNO) (talk) 08:57, 6 June 2018 (UTC)

Discussion[edit]

  • Please make test run. --EugeneZelenko (talk) 14:06, 6 June 2018 (UTC)
    • @EugeneZelenko: Working on it, but the script needs some more changes than I thought to work for our use-case. Unfortunately I won't have time to work on that until August because of vacation time, Wikimania, etc., so this request could be put on hold until then (even archived, and I can un-archive it once I restart the work). Jon Harald Søby (WMNO) (talk) 23:24, 19 June 2018 (UTC)

Whymbot (talk · contribs)[edit]

Operator: Whym (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: I would like to redact location information which was likely to be published inadvertently from ~1000 file pages. This is in response to a recent incident regading a Commons mobile app I help developing. For further background, please read https://github.com/commons-app/apps-android-commons/wiki/June-2018-incident .

The job is two-fold:

  • Removing location information from the latest version of the file page - this will only be done when the location information has been there since the first revision of the page. Otherwise, I assume it has already been fixed and removing it is counter-productive.
  • Deleting the contents of the applicable revisions

Example: let's say I published a file with a location information template which contains upload-time location of my mobile device that I didn't want to publish (first revision of the file page), and since then I edited it and changed location to the place I know the subject really was (second revision of the file page). My script will not edit the page, but delete the content of the first revision.

So far, it appears to involve 938 pages, 3294 revisions. I collected the data last Friday and I expect a small additional number of applicable revisions have been produced since then.

Automatic or manually assisted: manually assisted

Edit type (e.g. Continuous, daily, one time run): I expect most of the job will be done in a week. However, because not all Android users will download the mobile app's fixed version immediately, I would probably need another run or two after a while. Even considering that, I'd say one month will be enough. The expected number of edits and logged actions will be 3k-6k.

Maximum edit rate (e.g. edits per minute): 1 edit per minute

Bot flag requested: (Y/N): actually I'm not sure if bot flag is needed considering the expected number of edits and logged actions. It will definitely need sysop flag for performing revision deletion.

Programming language(s): a script based on the Pywikibot framework

I realize this may not be the most typical case of using bots, especially because it involves revision-deletion. Please advise me if you have other ideas on how to get job done. whym (talk) 14:46, 14 June 2018 (UTC)

Discussion[edit]

  • I considered asking for oversighting instead of deleting and I notified the oversight mailing list on June 11 - I have not received a response since then. It seems prudent to perform deletion in the meantime if oversight is going to take a longer time (or the request is going to be rejected eventually). whym (talk) 14:46, 14 June 2018 (UTC)
  • Question: Should I seek using a sysop-bot or my main sysop account? Either way, the temporary flag(s) can expire after one month's time for this job. whym (talk) 14:46, 14 June 2018 (UTC)
  • Looks good, thanks for writing the bot to perform this very much needed operation. Commons allows bot test runs, feel free to perform one, for instance on a test image created for this purpose with a previous version of the app. Syced (talk) 02:52, 15 June 2018 (UTC)
    • @Syced: Thanks for the suggestion. I performed a test and results are visible at [1][2]. Because I made a typo in the first run, I restored one revision and run it again with a fixed version. whym (talk) 10:58, 18 June 2018 (UTC)
  • It'll be good idea if bot will leave trace in oversight comment. --EugeneZelenko (talk) 13:36, 16 June 2018 (UTC)
    • @EugeneZelenko: As for deletion reason and edit summary, does this [3] seem appropriate? I'm not sure what I can do for oversighting. I could share my script but I would be unable to test and adjust it for them. As for 'comment', I'll definitely make sure linking this page in the edit summary and deletion comment. whym (talk) 10:58, 18 June 2018 (UTC)
      I meant that request to hide location information should be log entry. Test edit refer only to this request. --EugeneZelenko (talk) 13:43, 18 June 2018 (UTC)
      Sorry, I'm still confused. The wording I was going to use was "Redacting location information: Commons:Bots/Requests/Whymbot" which clarifies that it's hiding location information. Does it look okay to you? If not, can you suggest a complete wording? whym (talk) 00:31, 20 June 2018 (UTC)
      How does bot detect targets? By uploader request? By request for oversight? Other methods? Whatever method is, reference to request should be mentioned in log entry. --EugeneZelenko (talk) 14:08, 20 June 2018 (UTC)
      The is no individual request to refer to other than this. I was going to perform mass redaction of all files in the list I created, just to be safe. We could later inform uploaders offering to restore it, or introducing oversight for further redaction via a mass message. The point is that most of them are likely to have been unaware of the publication due to the app's UI that misrepresented the app's feature, so mass redaction seems safer and speedier. Alternatively we could ask and wait before redacting, but then what to do when there is no response? I consider it an emergency response. The detection criteria and technical details are described in [4] but to put it briefly, it covers photos that satisfy all of 1) contributed via the app 2) EXIF doesn't contain location 3) location template added by the app, and the result is the 938 pages I mentioned. whym (talk) 07:16, 21 June 2018 (UTC)
  • I think this should be approved to be done with the main account. --Krd 06:56, 19 June 2018 (UTC)

Requests for comment[edit]

Centralized discussion

Template: View • Discuss  • Edit • Watch