Open main menu

Wikimedia Commons β

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 May 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
  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. WJBscribe, en, fr-3, de-1 (global renamer)
  210. Wutsje, fy, nl, en-3, de-2, fr-1
  211. Wuzur, de, en-3
  212. wvk, de, en-4, fa-3, fr-2
  213. Yann, fr, en-4, hi-2, gu-1
  214. Yarl, pl, en-2, de-1, ru-1
  215. Yasu, ja, en-2, de-1
  216. Y.haruo, ja, en-1
  217. Ymblanter, ru, en-3, de-2, fr-2, nl-2, it-1, es-1
  218. Yuval Y, he, en-3
  219. Zhuyifei1999‎, zh, en-4
  220. Zzyzx11, en, es-1, fr-1
  221. とある白い猫, en, tr, az-3, ja-2, fr-1, nl-1
  222. CommonsDelinker, (bot)
  223. CommonsMaintenanceBot, (bot) see request
  224. Embedded Data Bot, (bot) see request
  225. GifTagger, (bot) see request
  226. 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.

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 225 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   

Support

votes or   

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   

Support

votes or   

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

No current requests.


Requests for license reviewer rightsEdit

No current requests.


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.

Revibot (talk · contribs) (4)Edit

Operator: -revi (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: Fix Category:Pages using ISBN magic links.

Automatic or manually assisted: Automatic, unsupervised

Edit type (e.g. Continuous, daily, one time run): one time run, then probably once in a month

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

Bot flag requested: (Y/N): N

Programming language(s): mw:Manual:Pywikibot/replace.py

  • Regex for replace.py will be -regex "ISBN\s+((97(8|9))?\s?-?([0-9]\s?-?){9}([0-9Xx]))([\D$])" "{{ISBN|\1}}\6"

I didn't run a test, yet. — regards, Revi 11:55, 18 May 2018 (UTC)

DiscussionEdit

  • Some suggestions to the regex:
  • You may want to built in a capitalization of the "x", for example, by using two regex (incl. some other changes):
-regex "[iI][sS][bB][nN]\s*((97(8|9))?\s?-?\s?([0-9]\s?-?\s?){9}([0-9X]))([\s\D])" "{{ISBN|\1}}\6"
-regex "[iI][sS][bB][nN]\s*((97(8|9))?\s?-?\s?([0-9]\s?-?\s?){9})x([\s\D])" "{{ISBN|\1X}}\5"
  • Currently, your regex will keep spaces and dashs. Do we want to remove them? --Schlurcher (talk) 23:22, 21 May 2018 (UTC)
    I don't want to make any user-visible changes. This is supposed to replace the function that will die soon to the working template, so nothing should change after the bot run (when someone sees the page). Dash or space or without it - which one to unify - that's not a decision to be made here, IMO. — regards, Revi 11:43, 22 May 2018 (UTC)
    Also AFAIK ISBN magic links only works when ISBN is in uppercase. isbn 9788937473135 don't work. (PS: ISBN9788937473135 also don't work.) — regards, Revi 11:49, 22 May 2018 (UTC)
    Please refer mw:Markup spec/BNF/Magic links for how MediaWiki finds ISBN to enbale Magic links. We do not have to care space and dash used at the same time for one separation("123 - 456", "123- 456" etc.), leading "ISBN" in lower case, and "ISBN" followed by number without space. Because they are not handled as ISBN Magic link by software, the pages which use them are not categorised in Category:Pages using ISBN magic links — which means that we can't tell where they are easily. If we want to change number fotmat, I think it is more then technical issue, and would need community consensus to do it.
    P.S. If you want to handle both upper and lower cases, just simple -nocase flag would be helpful. --IRTC1015 12:24, 22 May 2018 (UTC)
  • If anyone is curious, that regex code is a slightly altered version of one I used in kowiki to do the same job there. --IRTC1015 12:46, 22 May 2018 (UTC)
  • @-revi: It's better to use ([\D$]) instead of ([\s\D]), as former one doesn't work when ISBN is at the end of line. \s is useless because \D matches with space characters too :D --IRTC1015 06:01, 25 May 2018 (UTC)
    Thanks. — regards, Revi 19:47, 26 May 2018 (UTC)
If no bureaucrat cares, I'll run 5 to 10 test run by Monday 15:00 UTC, just to ensure the stuff won't break. — regards, Revi 19:47, 26 May 2018 (UTC)
To be honest, I don't fully understand this request, but as you know what you're doing, please continue. I think this can be approved if the test cycle is successful. --Krd 05:35, 27 May 2018 (UTC)

Frettiebot (talk · contribs)Edit

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

This bot adds Wikidata Infobox to czech community pages (by Mike Peel script). Sometime there will be other tasks by czech communnity. I am requesting for bot flag, because my bot (Frettiebot) was blocked after few edits, its a mistake, because at Czech language Wikipedia or Wikidata i have bot flag and it is ok for thousands of edits and there is not at commons, unfortunately, sorry.

Bot's tasks for which permission is being sought: Wikidata Infobox for czech articles

Automatic or manually assisted: Half automatic, i manual start my bot and looks, which its do.

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

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

Bot flag requested: (Y/N): Y

Programming language(s): Python

Frettie (talk) 16:16, 9 May 2018 (UTC)

DiscussionEdit

  •    Comment This isn't a problem from my perspective, but I should note that User:Pi bot will run through these categories eventually. It's currently going through Category:Art as a test of a big category, and I'll start it from Category:CommonsRoot soon (maybe next week), but I'm focusing on adding ~600,000 commons sitelinks through d:Wikidata:Requests for permissions/Bot/Pi bot 2 first. Thanks. Mike Peel (talk) 16:54, 9 May 2018 (UTC)
    • Perfect, good work!--Frettie (talk) 18:57, 9 May 2018 (UTC)
      • Just to note: Pi bot's run to add the Commons sitelinks on Wikidata is now complete, and it's now focusing on infoboxes here, starting from CommonsRoot. Thanks. Mike Peel (talk) 23:17, 11 May 2018 (UTC)
  • (Edit conflict) Does this run the exact same script as Commons:Bots/Requests/Pi_bot_1. If so, could you explain the rationale fot having multiple bots for the same task? If not, could you explain the differences? --Zhuyifei1999 (talk) 16:55, 9 May 2018 (UTC)
    • If there is similar bots for one thing, there will be faster. There is not differences.--Frettie (talk) 18:57, 9 May 2018 (UTC)
      If there happens to be some bug in the script, will you be able to fix them? --Zhuyifei1999 (talk) 20:07, 9 May 2018 (UTC)
      • I think yes, but if there is mistake in Mike's script, there will be corrected by Mike and i adopt this again. --Frettie (talk) 10:08, 11 May 2018 (UTC)
The general expectation is that you are able to correct mistakes in Mike's script if necessary. Please confirm. --Schlurcher (talk) 17:28, 11 May 2018 (UTC)
As a practical test, I've made a few changes to the script recently, @Frettie: can you explain what I've changed and why? Thanks. Mike Peel (talk) 23:17, 11 May 2018 (UTC)
I like your original python code, the targetcats, which was filled in cycle - its interesting. Now you are set seen categories (like a history view) and "what all i want to browse in future from my root category". And while there is some active category, which is not "seen" (because seen category is set only, which become "active" for next iteration), go through this category. Maybe the for cycle with subcategory generator will be slow if there will be too much categories (but its ok, too fast run is not good in this case).--Frettie (talk) 16:35, 12 May 2018 (UTC)
The new category walker is mostly designed for speed, since checking if a given subcategory is included in a list of categories is much slower than checking if it's in a set - although I also preferred the older version as it was more straightforward! I also changed a few things in the 'addtemplate' function, though, can you see why? Thanks. Mike Peel (talk) 23:31, 14 May 2018 (UTC)
Hi Mike, there is check if wikidata item is exist, if not, "skipping" next lines (return 0), and this is earlier. There is not processed list without category main topic by target link. Return 0/1 helps to compute count of modified categories. Sorry for late reaction.--Frettie (talk) 08:25, 21 May 2018 (UTC)
  • I generally don't mind multiple bots for the same task if they are programmed to some extend independently. This will have the merit that they can supplement each other. As I understand this is a second bot running exactly the same script. There is less benefit in having this as long as the other bot is well maintained and running. During the request for Commons:Bots/Requests/Pi_bot_1 we allowed for a higher edit rate than normal to accommodate for the number of edits. So, please provide additional rational except they will be faster together to support this request. Also note that during Commons:Bots/Requests/Pi_bot_1 there was some consideration on the server load these edits might put on Wikidata (not Commons). With two independent bots acting this will be more challenging to monitor. --Schlurcher (talk) 23:33, 9 May 2018 (UTC)
    • Yes, there will by challenging to monitor this, but (maybe) it's better, to edit some known categories (like czech themes).--Frettie (talk) 10:08, 11 May 2018 (UTC)
Do you see any concerns with edits from User:Pi bot that require deeper understanding of the categories? --Schlurcher (talk) 17:28, 11 May 2018 (UTC)
    • To clarify, it was the server load increase due to refreshing pages on Commons that use Wikidata information that I was worried about, so that's somewhere between server load on commons and on wikidata. The main limitation I've found with the bot code so far is that it takes time to work through the categories and find ones to add the infobox to (since it checks each category in series), so it helps to have multiple copies running with different target categories. Plus, it helps to have someone else here that knows how to run the code in case I'm not available in the future (since it'll be useful to keep running this after the main run to catch new categories that the infobox can be added to). Thanks. Mike Peel (talk) 23:17, 11 May 2018 (UTC)
  • I generally support multiple bot on the same task for positive redundancy, but only if the code runs slowly and is certain to avoid conflicts. Just running it twice to double the speed doesn't appear as good idea to me. If I'm mistaken, please advise. --Krd 05:42, 27 May 2018 (UTC)

FinnaUploadBot (talk · contribs)Edit

Operator: Zache (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: Uploads images from Finna.fi (2016 press release) which is online catalog and API for Finnish museums, libraries and archives and part of the Finlands national digital library service. Finna aggregates its data from organizations own databases so that there is a single endpoint. It also relays data to downstream partners like to Europeana. The basic operation is that users give a finna-id as a parameter and then the tool will read CC0 licensed metadata for the photo and checks if the license of the photo is licensed as CC0, CC-BY OR CC-BY-SA. If everything is ok then the tool will upload the photo.

The request is for larger uploads like thousands of photos and for keeping tool available for single uploads. Here are Example uploads and There is a discussion about the tool in COM:AN/U FinnaUploadBot (link to archive) where it was said that it will need a bot permission.

Automatic or manually assisted:

Automatic, user need to manually tell what to upload but there is no confirmation for each diff.

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

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

Bot flag requested: (Y/N): Y

Programming language(s): PHP, currently logic is built top of the https://github.com/legoktm/harej-bots/blob/master/botclasses.php Zache (talk) 05:38, 22 April 2018 (UTC)

DiscussionEdit

Quote from COM:CRT#Country-specific_laws The safest way to apply international copyright law is to consider the laws of all the relevant jurisdictions and then use the most restrictive combination of laws to determine whether something is copyrighted or not.'. If we would follow that the license would be CC-BY. --Zache (talk) 09:09, 29 April 2018 (UTC)
This Commons:Project scope/Precautionary principle is also official policy of Wikimedia Commons --Zache (talk) 21:06, 5 May 2018 (UTC)
That discussion is now archived to Commons:Administrators' noticeboard/User problems/Archive 69#User:FinnaUploadBot.   — Jeff G. ツ please ping or talk to me 05:44, 14 May 2018 (UTC)
  •    CommentZache how do you plan to address the concerns raised by Majora? Thank you. Wikicology (talk) 19:55, 22 April 2018 (UTC)
From a technological point of view, it is quite easy to handle. If we don't like to automatically upload images which are old enough to be in public domain and they are licensed to other than PD or cc0 then you can just add a test for it and if the test fails then do not to upload the image.
From a legal point of view, eg is Majora's concern about license valid, it is fuzzier because it is a valid argument that GLAMs have rights related to their digital reproductions of out-of-copyright works based on Finland's copyright law. So one can't just say that city of Helsinki or ministry of education and culture of Finland is fraudulently slapping restricted licenses on PD content when they are opening it at all. It is, however, unclear if the GLAM's argument for the rights would hold if it would be tested in court. The GLAMs which we are currently speaking about are in the front line of opening data in Finland. en:Finnish National Board of Antiquities (part of the ministry of education) have opened 200000 photos and are doing Wiki Loving Monuments with WMFI. Helsinki city museum which photos I was uploading opened 50000 hi-res photos and city as whole is doing a lot of open source work with OpenStreetMap, data, and API. So the position is that the opensource community in Finland are pointing out current problems and giving them reasons to do the right thing and seeing how far we can get. Last february National gallery of Finland opened their digital reproductions of out-of-copyright works under CC0 ( after years work ) which is kind of a test for other museums to see if it is good idea or not. --Zache (talk) 09:21, 23 April 2018 (UTC)
Pinging Zhuyifei1999 and Fae for insights. Regards. T Cells (talk) 09:39, 24 April 2018 (UTC)

I asked the Helsinki City Museum yesterday why their license is CC-BY for digital reproductions of out-of-copyright works and not public domain / CC0. I haven't yet got an answer. However, the relevant pieces from Copyright Act of Finland as far as I know are in Chapter 5 - Rights related to copyright and under the Section 49 - Producer of a catalogue and a database (607/2015) and Section 49a - Photographer. Section 49 protects the amount of work which is used to make the database but not single items in it. One can copy some photos manually, but downloading significant parts of the database using bots is prohibited. Section 49a protects photographs that are not works of art and requirement for getting the protection is that the photograph has been taken. For this argument (which I copied to COM: AN/U for Majora) is that digital reproductions of out-of-copyright are new photographs and thus they are covered by 49a. Currently, there are no decisions related to this argument for 49a by copyright council of Finland or a court. Kuvasto's opinion when it was asked by fiwiki was that museum can make and sell copies of the photographs but making digital reproductions doesn't extend the original protection. --Zache (talk) 09:08, 26 April 2018 (UTC)

Helsinki city museum's answer was that they are moving to CC0 for out of copyright works on their 2019 update, but not before because of the implementation reasons. This was in their plans before I asked about it. It was also OK for them to change the licenses for en:Signe Brander and fi:Ivan Timiriasew to CC0 or {{PD-Finland}} if it helps us. They also noted that most of the museums in Finland are in internal discussions about whether opening the archives is a good idea at all and the best practice is going forward step by step and not to scare GLAM people off.
I also updated the copyright status of reproductions of out-of-copyright works in Finland to COM:CRT#Finland (diff)
@~riley, Majora: In other ways question about CC-BY vs CC0 seems to be stalled and just for FYI. WMFI have a Wikigap event on 2018-05-08 where one planned track would be to add photos of historical women from Finna to articles. Second event related to this topic is a rephotography trip to Suomenlinna where we would be using photos from SA-kuvat (military archives), Helsinki city museum and Finnish National Board of Antiquities which are currently all under CC-BY and older than 50 years. The rephotography trip is also for testing of our WLM rephotography contest ideas. WMFI plan for WLM is to make national rephotography contest of old historical buildings as part of the WLM. For then-and-now photo pairs the old pictures are needed too. --Zache (talk) 08:25, 29 April 2018 (UTC)

Organizations in Europe are legally entitled to add a layer of copyright to material they make available through neighbouring rights. This is not a practice we want to encourage, but are we going to exclude them from Commons? This is not an isolated case. I personally would like to praise these institutions for the work they have done opening their materials. Sadly, they are following the national recommendations for open licensing. There's work to do, but don't you think we could cheer and let them experience the positive outcomes of open licensing rather than put them down. If this was a court case, they might still win. – Susanna Ånäs (Susannaanas) (talk) 16:32, 27 April 2018 (UTC)

How long is this procedure going to take? @Romaine, Jean-Fred: This is blocking the development for Wiki Loves Monuments 2018 in Finland, where old openly licensed images will be rephotographed. – Susanna Ånäs (Susannaanas) (talk) 18:42, 13 May 2018 (UTC)
@Majora: Could you please comment if there are issues remaining? Thank you. --Krd 05:22, 14 May 2018 (UTC)
@Krd: My apologies for not responding sooner. My concerns were always two fold. One, Zache was running an unauthorized bot on Commons. This solves that. Two, that they were misrepresenting the license that these photos are actually under. Section 49, as linked to above, is irrelevant as I read it. That has to do with databases. Think SQL. Think MediaWiki. Now, whether or not the "catalogue" part of that paragraph includes this type of information is highly debatable and from a programming standpoint, where I think this section is actually referring to, it would make more sense if it was referring to a something different entirely. Section 49a is precisely why we have {{PD-Finland50}}. Zache's editing of the copyright information for Finland (COM:CRT#Reproductions of out-of-copyright works) seems to be a misrepresentation or misunderstanding and should be removed. Section 49 appears to be referencing something completely different as indicated by it further stating that it applies to "tables" or "programs". Again, this is indicative that that section is talking about something completely unrelated to the issue at hand. If the museum has not responded as to why they have put the photos under a non-PD license then there does still seem to be a problem here that needs to be resolved. Please note, these photos are probably fine for Commons anyways and they will all have to undergo license review. If you just want to approve this and let the reviewers sort it out (a large undertaking but not unprecedented) then I wouldn't have a problem with that. But the changes to the CRT page need to be undone. Preferably by someone who has the extra authority (ie the mop) to make those changes stick. --Majora (talk) 00:36, 15 May 2018 (UTC)
@Majora: Just to be clear:
  1. Section 49 is much broader in Finland. Traditional examples for catalogue, table or database in Finland are the list of the name days or the phone book. It doesn't care specific implementation or format of the data.
  2. Helsinki City Museum did answer. The CC-BY license could be used because they owned the copies and they had already the CC0 for out of copyright works in their internal pipeline which they hoped to solve the issue for us too.
--Zache (talk) 05:15, 15 May 2018 (UTC)

┌─────────────────────────────────┘
Who says that section 49 is much broader exactly? You? If there are no specific court cases on the matter, which you have already said there are not above, then we have to interpret the law as it is written. We don't have the luxury of just saying whatever we want or believing what anyone else says. The way that section is written does not apply to this situation and without a court case saying that is is much broader than written we can't just go with what you say. That isn't how it works here.

Second, please stop saying CC0. There is absolutely no indication whatsoever anywhere on finna.fi that the images are under CC0. CC0 is a completely separate and distinct copyright license with its own legal code. It is not a catch all term for public domain images. The fact that you continue to use CC0 in this manner shows that you don't understand that and therefore you do not understand copyright licensing. If the museum really did use the term "CC0" then they were either parroting back exactly what you sent them or they too do not understand what they are talking about. Either explanation reduces my confidence that the copyright license is correct from reasonable doubt to nil. I have zero confidence whatsoever that finna.fi is using the correct copyright license here. Whether or not the bot is going to be approved is beyond my pay grade but only because the images are probably fine for hosting here and that they all have to be licensed reviewed anyways. Otherwise I would strongly oppose the approval of this bot since there seems to be a several gross misunderstandings here. --Majora (talk) 20:16, 15 May 2018 (UTC)

Who says that section 49 is much broader exactly: Copyright counsil of Finland. As an example there is statement TN:2000:9 where the digitized flags in the catalog weren't protected by section 1 or 5 as independent works, but the collection of flags was protected by section 49. (summary, full text) Copyright council statement for name days is TN 2013:8 and for phone book is TN 1987:16.--Zache (talk) 00:10, 16 May 2018 (UTC)
And about the rest. You don't need to trust to my interpretation of section 49a. You can always check the copyright status of digital reproductions in different EU countries from outofcopyright.eu map. --Zache (talk) 01:31, 16 May 2018 (UTC)
I think the copyright question is a relevant factor, but can unlikely be answered within the scope of this request. I'd like to suggest to raise the copyright topic at a more prominent place and get back with the consensus achieved. If you disagree, please advise. --Krd 05:47, 27 May 2018 (UTC)

Requests for commentEdit

  Centralized discussion

Template: View • Discuss  • Edit • Watch