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 April 2016 [+/−]
Listing by language
Listing by date
Listing by activity

Number of Admins: 244

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

The system currently recognizes 244 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 244 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.

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.

Josvebot (talk · contribs) 2Edit

Operator: Josve05a (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: Tagging orphaned talkpages (talk pages without corresponding file/galley/cateory page) for deletion (CSD G8).

Automatic or manually assisted: Automatic

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

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

Bot flag requested: (Y/N): N

Programming language(s): AWB Using http://quarry.wmflabs.org/query/9152 Josve05a (talk) 05:10, 20 April 2016 (UTC)

DiscussionEdit

  • Example contributions. Riley Huntley (talk) 05:51, 20 April 2016 (UTC)
  • Please disable section headers in the edit summary; seems unnecessary. {{SD|G8}} does not allow you to explain that it is an automated request; {{Speedy|[[User:Josvebot|Bot]]: [[COM:CSD#G8|CSD G8]] (page dependent on deleted or non-existent content)}} would be more preferable imoh (or any other method that accomplishes the same). Could you also get some blue in the edit summary (i.e. CSD G8)? I don't like the edit summary in general, but the edits are more important. Riley Huntley (talk) 05:59, 20 April 2016 (UTC)
  • Please only tag pages that have been last edited some time ago, I suggest at least 7 days, to not interrupt ongoing discussions. --Krd 07:48, 20 April 2016 (UTC)
  • Hmm..I'd have to create soe very specific regex for this...hmm...let me get back to you allon that one. Josve05a (talk) 08:07, 20 April 2016 (UTC)
    Thank you for taking care! It's hard to notice talk pages when using batch deletion :-) I agree with Riley and Krd suggestion. Probably edit summary should contain beginning of page text, like default log entry for deletion. --EugeneZelenko (talk) 14:03, 20 April 2016 (UTC)
    • Without creating a separate module, it will be both difficult to code a thing to add the content of the talk in an edit summary, but also confusing for "new users". The current template (see below) is "dated", as to allow conversation to take place before deletion etc. All in all, I think we've reached a good compromise between the edit summary and tagging. @EugeneZelenko: What do you think? Josve05a (talk) 22:47, 28 April 2016 (UTC)
  • Just adding on some helpful advice while bored waiting for my tasks to be closed :P. The following in your query are redundant; (These are en.wikipedia specific templates that Commons do not have. I imagine it might also speed up the search.)
AND p1.page_id NOT IN (SELECT
                        page_id
                      FROM page
                      JOIN templatelinks
                      ON page_id = tl_from
                      WHERE tl_title="G8-exempt"
                      AND tl_namespace = 10)
AND p1.page_id NOT IN (SELECT
                        page_id
                      FROM page
                      JOIN templatelinks
                      ON page_id = tl_from
                      WHERE tl_title="Rtd"
                      AND tl_namespace = 10);
I'm sorry. My computer completely broke and became non-responsive, and have had to find an emergency solution now, while I wait for the IT-technicians to fix it. I haven't checked that query out yet, but I do like to create a new template, however I have a few other ideas. I could add such a template, but it should wait 7 days before it categorize it in a CSD-category, like a "slow-deletion" template (such as "No source"), in order to not tag a current discussion for deletion, and if there is a current discussion, somebody can remove it/add a parameter of some kind. Josve05a (talk) 06:38, 28 April 2016 (UTC)
{{Orphaned talk page since}} (Thanks to Riley)! Daily categories will (read "can") be created (if approved) by Riley's bot(s). Josve05a (talk) 20:12, 28 April 2016 (UTC)

┌─────────────────────────────────┘
Test running on a few pages right now. Seems like it is doing the trick. Josve05a (talk) 22:31, 28 April 2016 (UTC)

Krdbot 3 (talk · contribs)Edit

Operator: Krd (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: Per User talk:Krd#Bot/request is was requested to gather files from specific FlickR users into the appropriate photographs_by category. Affected FlickR users to be determined by manual request.

In detail, e.g.:
Parse through the file pages looking for "author = [https://www.flickr.com/people/95704119@N08 Franz Johann Morgenbesser" and add images to Category:Photographs by Franz Johann Morgenbesser if not already present.

Test edit: Special:Diff/190444822

Automatic or manually assisted: Automatic

Edit type (e.g. Continuous, daily, one time run): continuous / on request

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

Bot flag requested: (Y/N): N

Programming language(s): Perl

--Krd 11:41, 17 March 2016 (UTC)

DiscussionEdit

Symbol support vote.svg Support Makes sense. --Steinsplitter (talk) 12:09, 17 March 2016 (UTC)

Looks OK for but I think will be good idea to add Flickr user name into category. Just for possible verification purposes. --EugeneZelenko (talk) 14:18, 17 March 2016 (UTC)
I'm not sure if I get that. Where excatly to add what? --Krd 20:27, 17 March 2016 (UTC)
@EugeneZelenko: do you mean this? Otherwise, looks good. Riley Huntley (talk) 21:54, 17 March 2016 (UTC)
Something like that, but will be good idea to use template for this purpose, may be without text visible to users. --EugeneZelenko (talk) 14:20, 18 March 2016 (UTC)
I do not disagree, but I have no idea how this should look. Please feel free to suggest anything. --Krd 07:44, 25 March 2016 (UTC)
  • Symbol support vote.svg Support Sure. Yann (talk) 11:18, 18 March 2016 (UTC)
  • Symbol support vote.svg Support This should reduce the workload of the community. -- Poké95 02:00, 19 March 2016 (UTC)
  • Any update on this? This is ok for me, I think. Poké95 07:18, 11 April 2016 (UTC)
  • Oh wait, why this bot is too slow? 1 edit per minute seems to be not enough for me. If you are worried about the performance of the servers, you should not worry, because there are semi-automated tools that are faster than a bot, and there is no performance issues. Maybe make your bot more aggressive, increasing it to 6 edits per minute (that's still slow for me though, but let's be conservative)? Poké95 07:23, 11 April 2016 (UTC)
    We can speed it up up to some maxlag value, but I don't consider that necessary for a non-realtime job. 6 epm is possible of course. --Krd 07:41, 11 April 2016 (UTC)

Can this be approved? If not, please advise what is missing. Thank you. --Krd 07:15, 20 April 2016 (UTC)

@EugeneZelenko: Please check if there is anything missing. Thank you. --Krd 06:34, 25 April 2016 (UTC)
As I wrote, template for category (for symmetry and possible checks) will be good idea for this task. --EugeneZelenko (talk) 13:55, 25 April 2016 (UTC)
I don't understand how this could look like. Can you give an example? --Krd 14:05, 25 April 2016 (UTC)
If a template is to be added, it makes more sense to do it manually. This bot's focus is on adding images to the category, not on the category itself. Riley Huntley (talk) 01:12, 26 April 2016 (UTC)
Template make sense to verify content of category. Since category relates to Flickr account, it's reasonable to state this fact in it. --EugeneZelenko (talk) 14:21, 26 April 2016 (UTC)
I'm still missing an example. Can you provide one, please. Thank you. --Krd 14:39, 26 April 2016 (UTC)
Something like {{FlickrAccount|95704119@N08}}. --EugeneZelenko (talk) 14:05, 27 April 2016 (UTC)
It has already been confirmed above that this shall be done for the Category, manually before the job starts. --Krd 14:09, 27 April 2016 (UTC)

BMacZeroBot (talk · contribs) 5Edit

Operator: BMacZero (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: Replace templates like {{PD-old-50}}, {{PD-old-50-1923}}, and {{PD-old-50-1996}} with {{PD-old-auto}}, {{PD-old-auto-1923}}, and {{PD-old-auto-1996}} respectively (including 'deathyear' parameter) where the page with the license also has a Creator template acting as an author with a readable death year.

This will usually be run at the same time as the task from Commons:Bots/Requests/BMacZeroBot 4. BMacZero (talk) 18:25, 12 March 2016 (UTC)

Automatic or manually assisted: Automatic

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

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

Bot flag requested: (Y/N): N (already has)

Programming language(s): C#

BMacZero (talk) 18:25, 12 March 2016 (UTC)

DiscussionEdit

I did a test run of 30 - see bot contribs. BMacZero (talk) 18:25, 12 March 2016 (UTC)

Looks good to me. --Krd 05:40, 13 March 2016 (UTC)
I think will be good idea to use link to templates in edit summaries. --EugeneZelenko (talk) 15:36, 13 March 2016 (UTC)
I refined the edit summaries (after a few small snafus), and ran more tests. I also fixed a problem with handling licenses inside {{PD-Art}}. BMacZero (talk) 06:43, 14 March 2016 (UTC)
Looks OK for me, but it's seems logical to use Wikidata as source of death date (if creator template is available). --EugeneZelenko (talk) 14:17, 14 March 2016 (UTC)
Added and tested a few. BMacZero (talk) 04:51, 15 March 2016 (UTC)
But could be date of death queried without copying it to file description? --EugeneZelenko (talk) 14:13, 15 March 2016 (UTC)
Oh I see what you mean. I hadn't considered that. I suppose it could be done with Arbitrary Access (eventually), though I don't think it can be done completely automatically - a bot would probably still have to go through and add the Creator's Wikidata ID as a parameter. Unless Scribunto can pull info from the Creator template on the page that transcludes the module? Maybe someone knows more. BMacZero (talk) 16:01, 15 March 2016 (UTC)
@BMacZero: Please advise what this is going to mean. Is this request obsolete per above comment? --Krd 09:18, 28 March 2016 (UTC)
@Krd: I started a discussion at Commons:Village_pump#Proper_implementation_of_PD-old-auto_with_Arbitrary_Access. BMacZero (talk) 16:57, 28 March 2016 (UTC)
Both User:Jarekt and I (so far) feel that the current implementation of PD-old-auto is still the best one. That would mean that we should go ahead with this request (can give the VP thread more time if you like, though). BMacZero (talk) 20:46, 4 April 2016 (UTC)
The deathyear seems the simpler and most clear. It is also a system we have been using for a while. I am OK with creating new mechanisms of passing information around by "quering without copying it to file description" but at the moment I can not think of a way to do it (we could copy Wikidata Q-codes instead and add an expensive function to look up the deathyear). So I would stick to the old ways of doing businesses. --Jarekt (talk) 01:59, 5 April 2016 (UTC)
By the way Some comments about edits:
  • I would not do {{PD-old-100}} -> {{PD-old-auto}} conversions. {{PD-old-auto}} will do a lot of non-trivial calculations before calling {{PD-old-100}}. I think we should verify and even add unused deathyear for clarity. But {{PD-old-100}} is so much simpler.
  • Edits like this are not the best option. If there is PD-Art or PD-Scan than PD-old-uto should be combined with it. Multiple PD-old templates should be merged.
  • Could you test on tricky cases with multiple Creator templates. PD-1923 (or {{PD-1996}}) and PD-old templates, which should be combined, etc.
--Jarekt (talk) 02:17, 5 April 2016 (UTC)
All sounds good - will do it when I get a chance. BMacZero (talk) 21:01, 6 April 2016 (UTC)
We may need to put this request on hold. I'm not sure when the next chance I'll get to work on it will be. BMacZero (talk) 17:20, 16 April 2016 (UTC)

Requests for commentEdit

Read in another language