Commons:Administrateuren/lb

This project page in other languages:

Alemannisch | asturianu | български | brezhoneg | català | dansk | Deutsch | English | español | فارسی | suomi | français | magyar | italiano | 日本語 | 한국어 | Lëtzebuergesch |

Commons Administrator.svg

Membere vun der Communautéit, deene vertraut gëtt, an déi sech mat der Commons Policy auskennen, gëtt den Administrateurestatus accordéiert. Dëse Status gëtt awer keng spezifesch Extrarechter wat d'Editéieren ugeet.

Administrators as of May 2013 [+/−]
Listing by language
Listing by date

Number of Admins: 271

  1. 1Veertje, nl, en-4, de-1, fr-1
  2. 32X, de, en-2, hsb-1, ru-1
  3. 99of9, en (bureaucrat)
  4. á, fi, en-2, sv-2
  5. A.Savin, ru, de-4, en-2
  6. Adrignola, en
  7. AFBorchert, de, en-3
  8. Ahonc, uk, ru-4, en-2, de-1
  9. Aka, de, en-3
  10. Ala z, pl, en-2, ru-1
  11. ALE!, de, en-3, es-3, fr-1, it-1
  12. Alhen, es, en-2
  13. Alison, en, ga-3, fr-2, gd-1
  14. Alno, fr, en-3, es-2, pt-1
  15. Alpertron, es, en-3
  16. Amada44, de, en-3, fr-1
  17. Angr, en, de-4, fr-2, ga-2, la-2, cy-1
  18. AnRo0002, de, en-2, fr-2, es-1
  19. Anthere, fr, en-3
  20. Aude, en, ar-3
  21. Avenue, en, de-1, fr-1, it-1
  22. Avraham, en, he-2 (oversighter, steward)
  23. AVRS, ru, en-2, eo-2
  24. Axpde, de, en-4, es-1, fr-1, it-1, nl-1
  25. AzaToth, sv, en-4
  26. Badseed, el, en-3, it-1
  27. Bapti, fr, en-3, de-2
  28. Barcex, es, en-2, fr-1
  29. Bastique, en, fr-3, es-2, la-2, ga-1
  30. Bdk, de, en-2
  31. Bencmq, zh, en-3 (steward)
  32. Benoit Rochon fr, en-4
  33. Beria, pt, en-2, es-2
  34. Bidgee, en
  35. Billinghurst, en (steward)
  36. Blackcat, it, en-3, fr
  37. Blacklake, ru, en-2
  38. Blurpeace, en, es-1
  39. Butko, ru, uk-2, en-1
  40. Cambalachero, es, en-3
  41. Captain-tucker, en
  42. Cecil, de, en-3, fr-2, es-1, fi-1 (bureaucrat)
  43. Chatama, ja, en-1
  44. Chris 73, de, en-3, ja-1
  45. ChrisiPK, de, en-3, fr-1
  46. ChristianBier, de, en-3
  47. Ciell, nl, en-2, de-1
  48. Cirt, en, es-2
  49. Common Good, en
  50. CommonsDelinkerHelper (bot)
  51. Cookie, es, en-2
  52. Courcelles, en, es-2, fr-2
  53. Coyau, fr, en-1
  54. DaB., de, en-1
  55. Dantadd, it, pt, en-3, es-3, fr-3, gl-3, ca-2, ro-1, el-1
  56. Darwinius, pt, en-3, es-2, fr-2, gl-2, ca-1, it-1, oc-1
  57. Davepape, en
  58. David Levy, en
  59. Dcoetzee, en, fr-2, et-1, af-0
  60. Denniss, de, en-2, fr-1
  61. Dereckson, fr, en-3, de-1, nl-1
  62. Didym, de, en-2, fr-2
  63. D-Kuru, de, en-2, it-1
  64. Dschwen, de, en-3, fr-1 (bureaucrat)
  65. Edgar181, en, de-1, fr-1, es-1
  66. Effeietsanders, nl, en-3, de-1, fr-1, la-1
  67. Ejdzej, pl, en-2
  68. Elcobbola en, de
  69. Elitre, it, en-3, fr-2
  70. Elya, de, en-3, uk-2, ru-1
  71. EPO, da, en-3, de-1
  72. Érico Júnior Wouters, pt, en-2, es-2
  73. Esby, fr, en-3, de-1
  74. EugeneZelenko, ru, be, en-2, bg-1, pl-1 (bureaucrat)
  75. EVula, en
  76. Ezarate, es-3, en-1
  77. Fanghong, zh, en-2, fr-1
  78. Fastily, en, fr-2, zh-2
  79. Flominator, de, als, en-3
  80. Foroa, vls, nl, en-3, fr-2
  81. Funfood, de, en-2, bar-1
  82. FunkMonk, da, en-4, no-3, fo-2, sv-2, de-1, es-1
  83. Geagea, he, ka-3, en-3, ru-1
  84. Geni, en
  85. George Chernilevsky, ru, uk-3, de-2, en-2, bg-1, la-1, be-1, fr-1
  86. GeorgHH, de, en-1
  87. Gestumblindi, als, de, en-3
  88. Gmaxwell, en (checkuser)
  89. Gnangarra, en
  90. Golbez, en, ja-2
  91. Greudin, fr, en-2, de-1
  92. grin, hu, en-3, de-1
  93. Gruznov, ru, en-1, fr-1
  94. guillom, fr, en-3, de-1
  95. Heb, da, en-2
  96. Hekerui, de, en-4
  97. Herbythyme, en, fr-2, es-1, it-1 (checkuser)
  98. Hesperian, en
  99. High Contrast, de, en-3, fr-1
  100. HJ Mitchell, en
  101. Howcheng, en, ja-2
  102. Hystrix, de, en-1
  103. H-stt, de, en-4, fr-1
  104. INeverCry, en, es-1, ru-1
  105. Infrogmation, en, es-1
  106. JDavid, pl, en-2, de-1
  107. J Milburn, en
  108. Jafeluv, fi, en-4, fr-3, de-2, ru-2
  109. Jameslwoodward, en, fr-1 (checkuser)
  110. January, en
  111. Jaqen, it, en-2
  112. Jarekt, pl, en
  113. Jastrow, fr, en-3, de-1, it-1
  114. Jcornelius, de, lt-2, la-2, en-2, pt-2, fr-1
  115. Jdforrester, en
  116. Jean-Frédéric, fr, en-4, es-1
  117. JeremyA, en
  118. JGHowes, en, fr-2, de-1
  119. Jmabel, en, es-3, ro-2, de-1, ca-1, it-1, pt-1, fr-1
  120. Joergens.mi, de, en-3
  121. John Vandenberg, en
  122. Juliancolton, en (bureaucrat)
  123. Julo, pl, en-2, de-1, ru-1
  124. JuTa, de, en-2, fr-1
  125. Jusjih, zh, en-3, fr-1 (bureaucrat, steward)
  126. Kaldari, en
  127. Kallerna, fi, en-3, sv-2, de-1
  128. Kanonkas, no, en-4, nn-3, da-2, sv-2, de-1 (bureaucrat)
  129. Killiondude, en, es-3, ru-1
  130. King of Hearts, en, zh-4, es-3
  131. Klemen Kocjancic, sl, en-3, de-2, hr-1, bs-1
  132. Krd, de, en-3
  133. Krinkle, nl, en-3, de-2
  134. Krzysiu, pl, en-2, szl-2
  135. KTo288, en, zh-4
  136. Kved, es, en-3
  137. Kwj2772, ko, en-2
  138. Kyro, fr, de-3, en-2
  139. Leit, de, en-3, fr-1
  140. Léna, fr, en-3, es-1
  141. Letartean, fr, en-3
  142. Leyo, gsw, de, en-3, fr-3, es-1, la-1
  143. Lobo, es, ca-2, en-2
  144. Logan, en, es-3
  145. Lokal Profil, sv, en-4, pt-2, fr-1
  146. LtPowers, en, es-1
  147. Ludmiła Pilecka, pl, en-2, ru-1
  148. Ludo29, fr, en-2
  149. Lupo, de, en-3, fr-2, es-1, it-1
  150. Luxo, gsw, de-4, en-1, fr-1
  151. Lymantria, nl, de-2, en-2, fy-2, fr-1, zea-1
  152. Magister Mathematicae, es, en-4, pt-1 (checkuser)
  153. Magnus Manske, de, en-2
  154. Magog the Ogre, en, es-2
  155. Maire, pl, en-4, es-2, fr-2, de-2, ru-1
  156. MarcoAurelio, es, en-2, fr-2 (steward)
  157. Marcus Cyron, de, en-1
  158. Mardetanha fa, az, en-3, tr-2, ar-1 (checkuser, steward)
  159. Martin H., de, en-2 (checkuser)
  160. Masur, pl, en-3, de-1
  161. Matanya, en, he (steward)
  162. Materialscientist, en-4, ru-4, nl-3, fr-1, es-1
  163. Matt314, de, en-3, fr-2, es-1, zh-1
  164. Mathonius, nl, en-3, fr-1, de-1 (steward)
  165. Mattbuck, en, fr-1, la-1
  166. Maxim, ru, en-3, fr-2
  167. MBisanz, en (steward)
  168. McZusatz, de, en-3, es-1, la-1 swg-1
  169. Mentifisto, en, mt, it-2 (steward)
  170. MGA73, da, en-3, de-2, sv-1, no-1
  171. MichaelMaggs, en, fr-1
  172. Micheletb, fr, en-3, it-1, es-1
  173. Micki, sr, bs-4, hr-3, en-2
  174. Mitchazenia, en, es-2
  175. Miya, ja, en-2
  176. Mmxx, fa, en-3
  177. Mono, en
  178. Moogsi, en, la-2, fr-1, grc-1
  179. Morgankevinj, en, es-1, la-1
  180. Mormegil, cs, en-2, de-1
  181. Morning Sunshine, vi, en-3
  182. M0tty, fr, en-1
  183. MPF, en, da-2, de-1, fr-1
  184. Multichill, nl, en-3, de-1, fr-1
  185. Mys 721tx, zh, en-3
  186. Nagy, de, en-3, fr-2, es-1, sv-1
  187. Neozoon, de, en-4, nl-4, fr-2
  188. Nilfanion, en, fr-1
  189. NordNordWest, de, en-3
  190. notafish, fr, en-4, de-3, es-2, it-2
  191. O, zh, en-4, zh-wuu-2, zh-hu-3, yue-1 fr-1
  192. odder, pl, en-3, de-2 (oversighter)
  193. Okki, fr, en-2
  194. Otourly, fr, en-2, it-1
  195. PeterSymonds, en, de-1 (steward)
  196. Pharos, en, fr-1
  197. Philosopher, en, es-1, zh-1
  198. PierreSelim, fr, en-3, es-1
  199. Pitke, fi, en-4, sv-2
  200. Platonides, es, en-2, fr-1
  201. Podzemnik, cs, en-2
  202. Polarlys, de, en-2, fr-1, no-1
  203. Powerek38, pl, en-4, fr-2, es-1, de-1
  204. Pruneau, fr, en-4, de-1
  205. PumpkinSky, en, de-2
  206. Putnik, ru, en-2
  207. ~Pyb, fr, en-2
  208. Pymouss, fr, en-3, de-2, it-2, he-1
  209. Ragesoss, en, de-1, fr-1
  210. Ra'ike, de, en-2
  211. Rama, fr, en-3, de-2, la-2, es-1, it-1, ja-1 (oversighter)
  212. Rastrojo, es, en-3, fr-2, eo-1
  213. Raul654, en, es-1
  214. Raymond, de, en-3, nl-1 (oversighter)
  215. Rd232, en, de, es-2, fr-1
  216. Rehman, en, si-1
  217. Reinhard Kraasch, de, en-3
  218. Rillke, de, en-2, fr-1
  219. Rimshot, de, en-4, fr-2, it-1
  220. Romaine, nl, en-3, de-2, af-1, fr-1
  221. Ronhjones, en, fr-1
  222. Rosenzweig, de, en-3, fr-1, la-1
  223. Royalbroil, en, es-1
  224. Rubin16, ru, tt, en-3
  225. Rüdiger Wölk, de, en-2
  226. Russavia, en, ru-3 (bureaucrat)
  227. Sanandros, als, de, en-3, fr-1
  228. Sandstein, als, de, en-4, fr-3, it-1
  229. SatuSuro, en, id-1
  230. Sfu, pl, en-2
  231. Shizhao, zh, en-1, ru-1 (steward)
  232. Siebrand, nl, en-3, fr-1, de-1
  233. Skeezix1000, en, fr-2
  234. Spiritia, bg, en-3, ru-2, mk-2, de-1
  235. Sreejithk2000, ml, en-3, hi-3, ta-1, kn-1
  236. Steinsplitter, tir, de-4, it-3, en-1
  237. Steven Walling, en
  238. Stifle, en, ga, fr-2, de-1
  239. Sven Manguard, en
  240. Tabercil, en
  241. Tarawneh, en, ar, de-1
  242. Techman224, en
  243. TheDJ, nl, en-3, de-1, fr-1
  244. Thuresson, sv, en-3, no-2
  245. Tiptoety, en (checkuser, oversighter)
  246. Tom, en, es-1
  247. Trijnstel, nl, en-4, de-1, fr-1 (checkuser, steward)
  248. Trixt, it, en-2, fr-1
  249. tsca, pl, en, da
  250. Túrelio, de, en-3, es-1
  251. VIGNERON, fr, de-2, en-2, zh-1
  252. Waldir, pt, en-3
  253. Whym, ja, en-2
  254. Wikitanvir, bn, en-3, as-2, bpy-1 (steward)
  255. WJBscribe, en, fr-3, de-1
  256. Wknight94, en
  257. Wpedzich, pl, en-4, de-2 (steward)
  258. Wsiegmund, en, fr-1, es-1
  259. Wutsje, fy, nl, en-3, de-2, fr-1
  260. Wuzur, de, en-3
  261. wvk, de, en-4, fa-3, fr-2
  262. Yann, fr, en-3, hi-2, gu-1
  263. Yarl, pl, en-2, de-1, ru-1
  264. Yuval Y, he, en-3
  265. Zirland, cs, pl-3, en-3, sk-2, eo-2
  266. Zolo, fr, en-4, de-2, zh-2
  267. Zscout370, en, ja-3
  268. Zyephyrus, fr, en-3, la-3, el-2
  269. Zzyzx11, en, es-1, fr-1
  270. KrinkleBot, Bot account; temporary adminship for testing, see also Commons:Bots/Requests/KrinkleBot (2).
  271. Brion VIBBER, Temporary adminship: "Temporary enable to look into UW campaign setup". No exact expiry date.

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

En Administrator ass einfach e vetrauenswürdege Member dee folgendes nach zousätzlech kann:

  • Säite spären an d'Spär nees ophiewen
  • Säite läschen oder Läschunge réckgängeg maachen
  • Biller an aner eropgeluede Fichiere läschen
  • Benotzer blockéieren an deblockéieren
  • den Interface an aner gespaarte Säite kënne verännert ginn.

Dir kënnt den Administrateurstatus fir Commons ënner folgende Critèren ufroen:

  • Dir sidd net komplett nei bei Wikimediaprojeten derbäi. Dir sidd en Editeur zënter op d'mannst zwee Méint an dir verstitt d'Ziler vum Projet a sidd mat dësen averstanen.
  • Dir hutt eng Benotzersäit op Commons a bedeelegt Iech och hei.
  • Dir akzeptéiert, iech un d'Commons-Regelen ze halen, an de Consensus tëscht de Memberen ze respektéieren.
  • Déi aner Benotzer sinn duerch e Consensus averstanen, Iech Administrateurerechter ze ginn.

Genee wéi bei der Policy for administrator access on Meta, kréien inaktiv Administrateuren hiren Accès ewechgeholl.

Requests for adminship

Create a subpage Commons:Administrators/Requests and votes/Username with the following text:

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

Reasons why you think you should be an admin. ~~~~

===Votes===

and list it on Administrators/Requests and votes.

No siwen Deeg, wa jiddwereen domadder averstanen ass, soll d'Ufro un e Bureaucrat weidergeleed ginn, fir d'technesch Formalitéiten ze regelen.


This project page in other languages:

Deutsch | English | español | +/−

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‎!

↑Jump back a section

How and where to apply for additional user rights on Commons

↑Jump back a section

How to comment and vote

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.

↑Jump back a section

Requests for adminship

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

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

SarahStierch

Vote

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

Scheduled to end: 17:21, (UTC)

I would like to present to the community User:SarahStierch. Sarah is known to many in the community; whilst I don't know her personally, I am familiar with her work and believe she would be a great candidate for Commons adminship. Sarah is an old-timer at GLAM-Wiki activities; she facilitated the massive donation by Commons:Walters Art Museum; she was Wikipedian in Residence of the Smithsonian Institution Archives of American Art and Smithsonian Institution Archives (both of whom have shared images with Commons). She also co-founded en:Wikipedia:WikiProject Public Art (http://www.flickr.com/photos/wsavespublicart/). So she is well qualified in terms of contributions to this project. In future Sarah will be participating in WLM US 2013 and is a trusted user with Upload Wizard rights.

Sarah is also an active OTRS member, and would definitely find the tools useful for OTRS work; with our semi-permanent backlogs she currently has to call upon other admins for undeletions and the like. She also holds image reviewer, OTRS member, file mover, rollbacker rights. I have no doubt that both Sarah and this community would benefit from her having the admin tools. russavia (talk) 16:18, 14 May 2013 (UTC)

Statement by SarahStierch

Hi everyone. This is flattering, thanks Russavia for assuming good faith in my work and trusting me with this opportunity. I accept this nomination and I hope that the community will as well. I totally agree that this would be a *big* relief for me for my OTRS work, which is where I often am doing things Commons related - permissions, photo submissions, etc. It would be awesome to be able to have the mop so I could work quietly and efficently without having to beg people to undelete content (or wait for someone to handle a ticket with a note stating that I need help with that). I also have interest in helping with deletion. We have so many nominations, and so many that need to be swiftly and efficently handled. I'd be really happy to be involved in that. And I'd get to engage in a mission I care so deeply for - free knowledge and free open data - in an even more in depth way. Thanks for your consideration every one. Sarah (talk) 17:21, 14 May 2013 (UTC)

<Ratinghistory-table-votes>

  • Symbol support vote.svg Support as nominator russavia (talk) 16:18, 14 May 2013 (UTC)
  • Symbol support vote.svg Support this OTRS member, trusted user, no worries, -- Cirt (talk) 16:29, 14 May 2013 (UTC)
  • Symbol support vote.svg Support - it's strange, some days ago two RfA were unsuccessfull, because "for OTRS you don't need Admintools/it's better not also have Admintools". Yes for her GLAM work. But please without gender politics here. Marcus Cyron (talk) 16:34, 14 May 2013 (UTC)
  • Symbol support vote.svg Support Sure thing. I believe Sarah has clearly shown her dedication to Wikimedia Commons, and that she can be trusted with the extra-buttons. Jean-Fred (talk) 16:40, 14 May 2013 (UTC)
  • Symbol support vote.svg Support Sarah makes a net positive contribution to every project she works on. She's sensible, reasonable and will use the tools to benefit Commons. —Tom Morris (talk) 17:28, 14 May 2013 (UTC)
  • Symbol support vote.svg Support per nom. INeverCry 17:38, 14 May 2013 (UTC)
  • Symbol support vote.svg Support welcome. --Túrelio (talk) 18:00, 14 May 2013 (UTC)
  • Symbol support vote.svg Support, excellent candidate. Trijnsteltalk 19:04, 14 May 2013 (UTC)
  • Symbol support vote.svg Support I like the "I don't know, I know less now" answers. Hopefully after being an admin for a bit, Sarah will become even more unsure. I'm voting as one of those "male Commonsists", but a massively gay one; if that makes any difference (perhaps waiving the gay card enough times might make it a non-issue Smile fasdfdsfoiueire.svg). As for the deleted Flickr account problem, I agree that is a problem - we should probably make more non-Admins licence reviewers, and be more open to staying sympathetic for cases of licence remorse. -- (talk) 19:21, 14 May 2013 (UTC)
  • Symbol support vote.svg Support Yes, of course. --MichaelMaggs (talk) 20:41, 14 May 2013 (UTC)
  • Symbol support vote.svg Support; delighted to see the name on the watchlist. Tom Morris says exactly what I would have done. Andrew Gray (talk) 21:07, 14 May 2013 (UTC)
  • Symbol support vote.svg Support a×pdeHello! 21:17, 14 May 2013 (UTC)
  • Symbol support vote.svg Support --Alan (talk) 21:36, 14 May 2013 (UTC)
  • Symbol support vote.svg Support I enjoy working with Sarah, and find she brings a strong work ethic, informed and interesting opinions, and a willingness to work things out. All of which are good qualities in an administrator. -Pete F (talk) 22:53, 14 May 2013 (UTC)
  • Symbol support vote.svg Support Very qualified. MBisanz talk 23:11, 14 May 2013 (UTC)

Comments

I basically had to stop doing the painful nomination and arguing about nudity and women's images on Commons. Part of this was because it was so demoralizing and depressing, and the other was the repeated "You'll never be an admin on Commons if you keep doing this," and I always wanted to be an admin on Commons. The fact that I let this argument – being made by male Commonists – trigger me to not participate in the conversations is an entirely different psychological issue in itself! Oy vey.

  • Do you mind explaining the background of this e–mail and those arguments being made by male Commonists? (As a sidenote, does the gender of editors who wrote that really make any difference?) Links to some exemplary DR nominations for those nudity and women's images would be appreciated. odder (talk) 17:57, 14 May 2013 (UTC)
Hi there. I haven't looked at any DR's related that type of content in a year at least now. It was a while ago. There were a few (presumed male) editors who really seemed to be triggered by me having interest in curating sexual content on Commons. It was something I went pretty crazy about a while back, so I don't even know what DR's triggered that conversation - and emotion wise I'd rather not revisit them. I've curbed that habit, that's for sure (now I just nominate things as I stumble across them, generally, and I'm not on witch hunts).
There is actually some psychological complexities to having men explain to a woman that she might not be able to "get a job" due to her behavior, so it was quite a hard experience for me to go through, and remains something I haven't forgotten. It has nothing to do with Commons, again, it's a psychological issuse that generally women have to deal with - having male colleagues or freinds tell you "you are too aggressive and vulgar, so you better be more well mannered or you'll never get hired," is something extremely painful to be told. It was really depressing for me. So yes, gender does make a difference. I know we'd like to think we live in a genderless world, but, we don't at this time. I thought I was doing important work, and shining light on something, and it turned out that people weren't happy with it. Again, anyone can look at my contributions for the past year or so. My contributions and interests have changed quite a lot (though I am a staunch advocate for certain policy change, I don't really have the interest in leading said changes at thist time). This is the reason I've been extremely nervous about going through adminship :( Sarah (talk) 18:15, 14 May 2013 (UTC)
Oh, and just a side note: a lot of the conversations that took place about my "possible role as an admin," never happened on wiki. Sarah (talk) 18:31, 14 May 2013 (UTC)
  • Pictogram voting question.svg Question What are the policy changes that you'd advocate for? (This question is partially related to the discussion ongoing on the said mailing list, which to me seems to be something less than the general Commons-bashing that is so popular among some circles.) odder (talk) 18:20, 14 May 2013 (UTC)
I'd like to see better policies - or more spelled out policies (and perhaps this has more to do with the Board in some ways) in regards to identifiable persons in private versus public. And again, this is where the board and the perhaps WMF legal can come in. It's a lot to unpack, and my feelings about things can evolve (i.e. my feelings have changed about an image filter - which I used to support, and I may still support a gadget, but not a permanent installation of one...the whole "Obama and gay marriage," thing :) ). I'm also pretty concerned about content being uploaded from Flickr where the Flickr accounts end up getting deleted. That is worrisome for me. That is all I can really think of right now. Sarah (talk) 18:35, 14 May 2013 (UTC)

Jcb (rights restoration)

Vote

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

Scheduled to end: 21:48, (UTC)

Jcb should be an admin again. They've been busy OTRSing and I want them to stop pestering me to undelete stuff! They lost adminship in November 2011 following issues regarding closing DRs without comment. I feel the tools would be useful to them, and that given the last fracas there are unlikely to be any more DR issues. -mattbuck (Talk) 21:48, 13 May 2013 (UTC)

See also Commons:Administrators/Requests/Jcb.
See also Commons:Administrators/Requests/Jcb_(de-adminship 2) for de-adminship request. odder (talk) 21:50, 13 May 2013 (UTC)

Statement by Jcb

If the community decides they want to accept me as an admin again, I would be happy to receive the tools. It's true they would be useful for me at the moment, especially while processing OTRS tickets.

I think the main cause for what happened in 2011 is that I tried to do way more work than I could reasonably handle. That caused me to deliver bad quality on DR closures (mainly lack of explanation where needed) and made it difficult to receive critism. I'm sorry for that and I will do what I can to avoid making those mistakes again.

If you have any feedback/critism/question/whatever about something I did, please feel free to leave a comment at my talk page. I always read everything posted there. Jcb (talk) 22:03, 13 May 2013 (UTC)

<Ratinghistory-table-votes>

  • Symbol support vote.svg Support (as nominator). -mattbuck (Talk) 21:48, 13 May 2013 (UTC)
  • Symbol support vote.svg Support - I believe in Jcb. --Sreejith K (talk) 22:17, 13 May 2013 (UTC)
  • Symbol support vote.svg Support I will miss Could somebody restore these files... We received permission. Face-grin.svg --Alan (talk) 22:18, 13 May 2013 (UTC)
  • Symbol support vote.svg Support I think Jcb's statement above addresses the key issues that caused his de-adminship. --99of9 (talk) 22:20, 13 May 2013 (UTC)
  • Symbol support vote.svg Support --Steinsplitter (talk) 22:34, 13 May 2013 (UTC)
  • Symbol support vote.svg Support From everything I've read above, this sounds like a model example of how to respond when de-sysopped. OTRS is a great place to develop skills in handling requests in a sensible and communicative manner. (I don't think I have any direct experience to go on.) -Pete F (talk) 23:10, 13 May 2013 (UTC)
  • Symbol support vote.svg Support. Érico Wouters msg 23:20, 13 May 2013 (UTC)
  • Symbol support vote.svg Support. Agree with assessment, above. Cheers, -- Cirt (talk) 00:51, 14 May 2013 (UTC)
  • Symbol support vote.svg Support Deserves another chance. King of ♠ 03:00, 14 May 2013 (UTC)
  • Symbol support vote.svg Support I hope you'll return to DR work. INeverCry 03:03, 14 May 2013 (UTC)
  • Symbol oppose vote.svg Oppose -- Jcb, the behaviour that triggered your de-adminship went far beyond what you acknowledged above, and since you don't seem to have fully acknowledged your disruptive behaviour, I think it is very likely you never really understood what you were doing wrong. Geo Swan (talk) 03:13, 14 May 2013 (UTC)
  • Symbol support vote.svg Support Why not? -FASTILY 04:20, 14 May 2013 (UTC)
  • Symbol support vote.svg Support. It's been one and a half years, and Jcb's statement goes a long way addressing the concerns that led to the desysopping. Jafeluv (talk) 06:21, 14 May 2013 (UTC)
  • Symbol support vote.svg Support. Geagea (talk) 08:59, 14 May 2013 (UTC)
  • Symbol support vote.svg Support as per King of Hearts. --A.Savin 09:10, 14 May 2013 (UTC)
  • Symbol neutral vote.svg Neutral I'm all for giving a second chance, so I am not opposing, but I can't quite convince myself to support resysopping as the current re-nom statement does not do a good job on recognizing past problems, or explain why these will not re-occur. My example DRs below were slippery, so I will not judge Jcb to harshly for not picking up on the deeper policy issues. Hopefully no admin would close DRs this difficult without more serious thought and a better explanation of policy, rather than being overly swayed with the votes (which in both these cases were extensively canvassed off-wiki and I would prefer this to be noted in any closure). In my view, Jcb's statement "a clear consensus in favour of deletion, so that will be the only possible conclusion" is incorrect and shows a lack of understanding of the responsibility to implement policy when reviewing a complex DR. I'll consider changing my vote before closure if the re-nom statement is revised, though this may not be necessary for the outcome that Jcb is hoping for. -- (talk) 10:51, 14 May 2013 (UTC)
    • You can't be serious, Fae. With such an overwhelming support for deletion, and especially due to lack of consent, the only possible closure of that particular DR is to delete those pictures. This is what I'm intending to do after the week passes. odder (talk) 11:17, 14 May 2013 (UTC)
      • I'm not suggesting anything for the particular DR, the principle however, is that admins have a duty to implement policy. There may be a DR where 10 votes all say to keep and just 1 to delete, but if this would lead to Commons hosting a copyvio, the correct closure would be to delete. When there is a visible record of off-wiki canvassing (or possibly off-wiki harassment that may put members of our community in fear of off-wiki retribution for even openly expressing a counter-view) admins should take particular care in considering policy, rather than an apparent "consensus". No, I'm not joking as you well know. -- (talk) 11:36, 14 May 2013 (UTC)
        • And yet, whatever happens off-wiki should not have any influence on decisions that are being made on the basis of project policies; when there is no evidence of consent for pictures taken in a private environment — especially in case of nude pictures — the policy dictates their deletion. odder (talk) 12:00, 14 May 2013 (UTC)
          • If you carefully read my last statement, you will find us in agreement. The problem is understanding the meaning of "a clear consensus" when this has been manipulated by off-wiki canvassing. I fully agree that off-wiki material should not influence on-wiki decisions; when a apparent consensus has evidence of manipulation, this principle should apply and an admin closing a DR must take the responsibility to implement this principle. I suggest a longer discussion, if you want it, is held somewhere like AN rather than taking this request on a tangent. -- (talk) 12:10, 14 May 2013 (UTC)
            • I think Jcb just meant to say, "this DR is obvious," and didn't really intend to make a blanket statement. I don't think we need to worry about Jcb not using his judgment; in fact, his desysoping was due to overuse of that. -- King of ♠ 18:54, 14 May 2013 (UTC)
  • Symbol support vote.svg Support. For having the guts to say sorry. And for all (good) hard work he did; I bet he could do much more. Plus, for such a long-time volunteer, it is very unlikely that he would do any harm intentionally. Rehman 15:06, 14 May 2013 (UTC)
  • Symbol support vote.svg Support Given his commitment below, I can support this. russavia (talk) 15:20, 14 May 2013 (UTC)
    • Russavia, sorry, but I think your short list of Jcb's lapses is seriously incomplete. I suggest Jcb routinely behaved in a highly misleading manner in 2011, and, as I commented below I suggest Jcb is being misleading here, in this current discussion today. If he can't or won't be candid here, where he is claiming he has turned over a new leaf, what confidence can any ordinary contributor who was at the receiving end of his counter-policy use of administrator authority have that he won't continue to abuse his authority, as if nothing had changed? Geo Swan (talk) 18:17, 14 May 2013 (UTC)
      • We are all entitled to our opinions. I don't think I commented at the de-adminship, but I was actually in favour of it -- even now we see some remnants of problems. However, I am taking Jcb at their word with their responses to my questions, and if there are serious relapses I would expect the community to be swift in action, and I think he would be expecting that too. russavia (talk) 22:45, 14 May 2013 (UTC)
  • Symbol support vote.svg Support. --Túrelio (talk) 16:22, 14 May 2013 (UTC)
  • Symbol neutral vote.svg Neutral Do not want to vote down, but still very bad memories.--Ymblanter (talk) 18:21, 14 May 2013 (UTC)
  • Symbol support vote.svg Support off course Ezarateesteban 18:41, 14 May 2013 (UTC)
  • Symbol support vote.svg Support, very active and helpful user. Trijnsteltalk 19:02, 14 May 2013 (UTC)

Comments

  • Hi Jcb. I refreshed my memory of what happened in 2011 and I voted for a de-sysop back then, as I was concerned that you had demonstrated some problems with making personal comments about other editors in DRs, and I thought you might have a particular issue with dealing with sexual content on Commons in an impartial way. Two years is a long time, and the examples I picked up on were unlikely to be your everyday behaviour, so I'm happy to think of those discussions as tucked away in the archives. Could you demonstrate where you have more recently dealt better with conflict but were still passionate about the issues? In addition, I would appreciate your thoughts on how you would summarise and close these two quite different and difficult DRs on sexual content:
    1. Commons:Deletion requests/Files of Austin photoguy50
    2. Commons:Deletion requests/Template:The Hot sex barnstar
    -- (talk) 22:37, 13 May 2013 (UTC)
    • It's difficult to show a recent conflict situation, because most regarding Wiki are in OTRS (so confidential). Last weeks I responded to several angry emails and I have been able to achieve understanding by most of the mailers, staying calm and polite while explaining the situation. (e.g. people who saw their article nominated for deletion). In real life I've had to deal with a lot of conflicts in the past two years. Most of the time I wasn't one of the opponents, but I was helping to calm down the situation. Being the leader of a development aid organization, I spend every summer in a poor country with a group of young people to help building necessary buildings like schools. If you put a group together for 3 weeks, 24 hours a day, in an uncomfortable environment while working hard, it's inevitable that you will have conflicts in the team from time to time. But it's very important to resolve them as soon as possible, because there is no way to separate the opponents for the rest of the summer and an ongoing conflict will endanger the mission.
    • About the DRs you mentioned: The first one has a clear consensus in favour of deletion, so that will be the only possible conclusion. Lack of consent by the depicted women is the main issue here. I strongly agree with that concern. Another, weaker but still valid, issue is that they are out of scope. I also agree with that deletion reason. None of the files seems to be useful for any educational purpose within a Wikimedia project. The second DR seems to have a big majority in favour of keeping. Personnally I really don't care whether such a template exists or not. Nobody in the DR mentions any urgent reason for deletion (e.g. copyvio), so I would follow the majority and keep-close the DR, because the majority of the responders like to keep it and there is no forcing reason to delete. Jcb (talk) 23:39, 13 May 2013 (UTC)
      • Just a note that the barnstar discussion has a number of improbable conditionals, plenty of sarcasm, proponents of the deterioration of Commons, etc. Non-native English speakers may want to be cautious about closure. --99of9 (talk) 06:23, 14 May 2013 (UTC)
        Indeed, a brave admin might find policy reasons to want to close either of these "difficult" DRs as the reverse of the apparent consensus. Smile fasdfdsfoiueire.svg -- (talk) 09:07, 14 May 2013 (UTC)
  • Jcb, you invited interested parties to leave their questions on your talk page -- not here. But, don't you have a long history of erasing questions your don't want to address from your talk page, so they are not recorded in your talk page archive? [1], [2], [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] During your deadminship discussion you pointed to your talk page archive, claiming it showed you did not have a long history of ingoring good faith questions -- when you had misleadingly manually removed civil, good faith questions so they wouldn't be present in your archive? So I will ask my questions and make my comments here.
  • Jcb, weren't you an unforgiveable bully to regular contrinbutors, when you were an administrator? Isn't this one of the serious problems with your administratorship you have not acknowledged here?
    • To interject re: the line above -- the use of the word "unforgivable" makes this a pretty unhelpful comment. A central task of a nomination like this is to determine whether or not something can/should be forgiven; presupposing an answer one way or the other makes the question impossible to answer in a fruitful way. -Pete F (talk) 14:03, 14 May 2013 (UTC)
  • Jcb, didn't you engage in deceptive, misleading practices, that give the strong appearance you did not want to be held accountable for your actions? Since you haven't acknowledged these deceptive, misleading practices, aren't you still giving the strong appearance you can't or won't be held accountable for your actions?
  • In the previous discussion I described the problems posed by supervolunteers -- and how supervolunteers can be crippling for a project, because a large fraction of them start to act like their extraordinary commitment of time entitles them to act as if the regular rules no longer apply to them. Commons:Administrators/Requests/Jcb (de-adminship)#The dangers of volunteers who want to_do more than their share I feel very strongly that Jcb proved himself to be a super-volunteer, and this this is the root explanation of his deeply troubling use of his administrator authority to retaliate against good faith contributors.
  • Towards the end of the deadminship discussion I wrote:
In my opinion we remain accountable for our actions, essentially forever. In my opinion, we can expect good faith contributors to extend to us an amnesty for past mistakes -- when we have fully demonstrated we recognize those past mistakes. This crucial demonstration that you understand the concerns expressed about your behavior is largely absent here. I don't think we can assume you do understand those elements of your problematic behavior you have not addressed. Since you haven't made an effort to show you understood our concerns I think we really have no choice but to assume you will continue in all the problematic behaviors you have not acknowledged were mistakes, if you are allowed to retain full or partial administrator authority.
No one expects you, or any other contributor here, to be perfect, to never make mistakes. But, a corollary of our policies and conventions on civil and collegial communication, is that we have to tell our fellow contributors when we realize we have made a mistake. When we don't they have to assume we haven't clued in, and that we will continue to repeat the same mistakes, over and over again. Even though your talk page bears a promise that you will consider the possibility you may have made a mistake your record shows you an ongoing failure to acknowledge mistakes.
You still haven't made a meaningful effort to acknowledge the problematic behaviours you engaged in -- not even close. So I suggest none of us should trust you won't engage in exactly the same problematic behaviour all over again. Geo Swan (talk) 06:41, 14 May 2013 (UTC)
  • Is there any reason why everyone who voiced an opinion in the original deadminship discussuion should have a neutral heads-up about this discussion left on their talk page? Geo Swan (talk) 06:44, 14 May 2013 (UTC)
A few comments on your list of talkpage reverts:
  • The list looks longer than it is, because you double-posted three of them, so in fact you provided 13 diffs instead of 16.
  • In this revert I removed an automated notification, but you forgot to mention that ten minutes earlier Marac reverted the action that caused the notification.
  • In one of the cases a complete discussion was moved to my talkpage and I moved it back, leaving a link to the original location.
  • this revert (and I saw one other example of this issue in your list) was done because the comment had landed at the wrong place. I should have moved it to the bottom of the page instead, which I will do in future cases.
I disagree with your point of view about the danger of what you call a 'super-volunteer'. I know quite a lot of valuable small organizations that simply wouldn't be able to exist without one or to people really going for it. Jcb (talk) 10:43, 14 May 2013 (UTC)
Jcb, could you please mention some of the principles you consider (or will consider) when making a decision about whether or not to delete a message from your user talk page? In what cases do you feel it is justified, and in what cases should the temptation be resisted? -Pete F (talk) 14:03, 14 May 2013 (UTC)
Deletions at my talk page have been exceptional. I think Geo Swan found most of them, compared to over 600kb stored in my archive. If I receive an automated notification because one of my uploads got tagged by mistake (like placing {no license} where a valid license was present), I may remove that notification after dealing with the tag. But in general comments will stay. Reverts like this won't happen again, I will move the comment to the bottom of the page instead. Jcb (talk) 15:33, 14 May 2013 (UTC)
Interesting. I think there are plenty of circumstances where removing unwelcome comments is perfectly reasonable. It might be necessary for somebody in a position of trust to exercise more discretion in that kind of deletion, but I'm surprised that you would commit to preserving comments in nearly all cases. Anyway, thanks for the answer. -Pete F (talk) 15:45, 14 May 2013 (UTC)
Jcb, I apologize to you and other participants here for including three duplicates in the list of 16 misleading exisions to your talk page. I overstruck the duplicates above. However I am extremely disturbed by how you misleadingly characterized the remaining exisions, as if they were routine.
I seems to me that in characterizing the remainder as routine you have been highly misleading. It seems to me you are showing that basically nothing has changed since 2011, and that you are prepared to be highly misleading in your attempts to evade responsibility for your actions.
Several of the comments you excised were from User:Saibo -- someone I don't know: [17], [18], [19], [20], [21]. But even if, for the sake of argument, Saibo was considered a troll by some, his or her comments here were civil, and correct. You acknowledged above that you were wrong to close DRs without explanation, so his or her civil reminders that you were doing so was not "spam" and it was not "trolling". He or she was in the right to remind you or your responsibilities, and you were wrong to characterize them as trolling or spam back in 2011, and it is highly misleading of you to imply their excision was the routine kind of excision anyone would do. Rather it was an early and civil heads-up of one of the main issues that cost you your administratorship.
Three of the comments are similar civil and policy based concerns that did not merit excision: [22], [23], [24].
Three of the comments you excised were from me: [25], [26], [27], I too was addressing valid policy based concerns, and I believe my comments merited a civil and substantive reply. Your excision of them in 2011 strongly suggested to me that you were unwilling or unable to take responsibility for the actions you took as an administrator. I am afraid you still don't seem prepared to acknowledge that you gave the strong appearance of misusing your administrator authority to delete material I needed for work I was doing not out of a policy based concern but instead solely because my civil good faith question and concerns had pissed you off.
I don't think anything has really changed. Here we are, at your attempt to get your administratorship restored, and it seems to me you are still prepared to try to mislead people over the nature of these excisions. Geo Swan (talk) 18:02, 14 May 2013 (UTC)

Pictogram voting question.svg Question Jcb, one of the main concerns that people had was the lack of quality in your closes and a lack of communication with editors who had questions in relation to those closes. With a simple yes or no answer, do you acknowledge that they were amongst the issues that led to your de-adminship? I asked you this question on IRC and you acknowledged in the affirmitive, and mentioned you basically stated as such in your request. Given this, do you commit yourself to the following: 1) not to attend to DRs in a "robo-admin" way; 2) providing clear rationales for all closes (even if "as per nom" for simple, obvious DRs) to demonstrate that the DR has been read entirely; and 3) respond to all queries from editors whom query any closes (in a COM:MELLOW way). If you can commit to that here, I would both support you and hold you to it. russavia (talk) 11:47, 14 May 2013 (UTC)

I agree that this was an important issue in 2011. I see the importance of your three points and I commit to it. Jcb (talk) 11:55, 14 May 2013 (UTC)
  • Russavia, sorry, I think your list Jcb's lapses was incomplete. Over and above failing to leave closing explanations in DRs, over and above not answering good faith queries, Jcb engaged in misleading behaviour. As I noted above removing civil good faith comments from his talk page was highly misleading. As I noted above, trying to tell those participating in this discussion that his previous obfuscation of good faith policy based concern as routine maintenance strongly suggest to me at least, that he doesn't understand what is wrong with decpetively trying to evade responsibility for his actions.
Jcb used to disrespectfully fail to provide substantive answers to good faith contributors who had questions about his DRs on his talk page. And then, when discussions were initiated as to whether those files should be restored, he would sometimes weigh in -- but in a way that seemed to me to be misleading and indicative of a woeful unwillingness to be held responsible for his actions. He would weigh in to these discussions as if he were an uninvolved third party. He would leave these rather vague comments as if he was supporting the decision of the closing administrator. These vague supportive comments from an uninvolved third party fell far short of the specific, substantive comments the closing administrator should make. Some closing administrators don't weigh in during the undeletion discussions, trusting that the closing comments they left at the DR, and the explanation they supplied at their talk page, after the DR, were sufficient. But for closing administrators like Jcb, who didn't explain at the DR, or at their talk page, it seems to me that comments that look like he was trying to masquerade as an uninvolved third party while not as bad as employing sockpuppets were misleading in the same way as employing sockpuppets.
Rightly or wrongly Jcb lost the general community's trust that he was closing DRs related to human sexuality in an neutral, objective manner. He should have realized, months before his de-adminship discussion, that the could no longer close DRs related to human sexuality, and should confine himself to weighing in those discussions with a substantive policy based comment. Continuing to close these DRs, when his closures were so often challenged and so often reverted, showed bad judgement and disrespect for the community.
Jcb went beyond merely not measuring up to WP:MELLOW, he mocked newbies. That is terrible because it was abusive, and it was terrible because we need experienced contributors to set an example. We particularly need administrators to set a good example as newbies deserve to be able to trust that the example they should follow.
In my particular case he went beyond failing to respond in a civil, substantive way to my civil, good faith concerns. About a week or ten days after our first interaction he chose to delete material I was relying on in a DR with a pitifully flimsy justification for deletion. It was extremely inconvenient for me. It was extremely inconvenient for me over the course of 150 hours of my volunteer time. It was extremely inconvenient for me almost two months. I gave him several opportunities to quietly revert his actions. He blew me off and acted like I was a vandal.
Some of Jcb's supporters implied I was making a mountain out of a molehill to be so concerned over a single DR. But it was a DR that caused me to grit my teeth in frustration over his intransigence over 150 hours I worked on uploading the files related to that DR. I was reminded of his instransigence almost every day for almost two months. I have acknowledged that there may be some other reason for his maddening unwillingness to either explain his deletion, or to revert his deletion. But the longer he was instransigent the harder it has been to resist concluding the sole explanation for the deletion was malice, that he never imagine he had a valid justification for this deletion, but he thought he could get away deleting material I was relying on to retaliate against me for asking him tough questions he couldn't answer. I believe my questions and comments in 2011 were all substantive, and were all civil, and any resentment he felt was wildly misplaced.
Note, you won't find even an iota of acknowledgment on Jcb's part that he never had any justification for the delete conclusion of that DR.
All participants on the WMF projects are supposed to be civil and collegial at all times. I am used to encountering fellow contributors who fall short of that standard. The best thing to do is to try one's best and not respond in kind to uncivil contributors. I do my best to remain civil when other contributors aren't civil. But there is a level playing field there. I think it is essential that the community in general, and the corp of administrators, close ranks and rein in administrators who give the appearance of bullying. At this point I don't really care if Jcb has an explanation that would convince people he didn't close that DR as delete out of malice. His two years of unwillingness to explain the closure or acknowledge it was a mistake, made it look like he was acting out of malice. Geo Swan (talk) 19:27, 14 May 2013 (UTC)
Geo Swan, if you have a genuine point to make, I think you have failed by making your own badgering the dominant theme here. I have no history with this user, but the only person who gives the appearance of badly needing to work on their collaborative skills on this RFA is…you. -Pete F (talk) 19:53, 14 May 2013 (UTC)
  • I think my record of interaction with Jcb, while he was an administrator, was a model of how to voice a policy based concern, and I think if you think I am "badgering" him now you might consider bearing in mind the possibility you don't understand how he has behaved in the past. Other administrators may see him as a generally cooperative team member, while ordinary contributors, who were at the receiving end of his behaviours can have a completely opposite impression. Geo Swan (talk) 20:56, 14 May 2013 (UTC)
↑Jump back a section

Is there any reason why all the contributors who participated in the de-admin discussions shouldn't receive a neutral heads-up of this discussion?

I repeat, is there any reason why all the contributors who participated in the de-admin discussions shouldn't receive a neutral heads-up of this discussion? Geo Swan (talk) 18:06, 14 May 2013 (UTC)

No. If you want to do so, and might phrase something neutral, then knock yourself out with posting heads-ups. At the moment there have been reasonable and direct questions pitched about concerns, so there should be no last minute surprises. Smile fasdfdsfoiueire.svg -- (talk) 18:13, 14 May 2013 (UTC)
I propose a message like the following:
In 2011 you participated in Commons:Administrators/Requests/Jcb_(de-adminship 2). That discussion ended with User:Jcb losing his administrator privileges.
I think you are entitled to be informed that it has been proposed that his administrator privileges be restored.
While there were various suggestions at the de-admin discussion that he be allowed conditional access to administrator privileges, the proposal at Commons:Administrators/Requests/Jcb (readmin) is for Jcb to have unconditional access to the administrator privileges restored.
Cheers Geo Swan (talk) 21:33, 14 May 2013 (UTC)
At a first attempt 61 people weighted in -- User:Cecil User:Jcb User:Saibo User:Mattbuck User:Geo Swan User:AzaToth User:Hekerui User:ANGELUS User:Léna User:Wsiegmund User:Trijnstel User:Blue Marble User:Fæ User:Blue Marble User:Herbythyme User:Ymblanter User:S Larctia User:Rd232 User:Pieter Kuiper User:Pill User:Beria User:AFBorchert User:CT Cooper User:Ajraddatz User:Fry1989 User:Geagea User:ABF User:Lymantria User:Yikrazuul User:Ezarate User:Neozoon User:A.Savin User:VR-Land User:Yann User:Jafeluv User:Olivier Bommel User:Kaldari User:Missvain User:Dcoetzee User:Amada44 User:Courcelles User:Niabot User:WizardOfOz User:Nevit User:Fastily User:TwoWings User:Wknight94 User:Pymouss User:SarekOfVulcan User:WJBscribe -User:Schwäbin User:PierreSelim User:Jastrow User:NVO User:Adrignola User:MoiraMoira User:Túrelio User:Skeezix1000 User:Jameslwoodward User:EugeneZelenko
Ten people who voiced an opinion here also voiced an opinion at the de-admin discussion.
Cheers Geo Swan (talk) 21:20, 14 May 2013 (UTC)
  • The "various suggestions" sentence is unnecessary and selectively chosen to support your agenda, please leave it out. I also think that replacing "I think you are entitled to be informed" by "This note is to inform" will make it more neutral. --99of9 (talk) 21:49, 14 May 2013 (UTC)
OK, how about:
In 2011 you participated in Commons:Administrators/Requests/Jcb_(de-adminship 2). That discussion ended with User:Jcb losing his administrator privileges.
This note is to inform you that User:Odder proposed Jcb have unconconditional access to administrator privileges restored.
Commons:Administrators/Requests/Jcb (readmin) is scheduled to close on May 20th.
Cheers Geo Swan (talk) 22:26, 14 May 2013 (UTC)
↑Jump back a section

Requests for bureaucratship

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.


↑Jump back a section

Requests for CheckUser

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.


↑Jump back a section

Requests for Oversight rights

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

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


↑Jump back a section

Requests for permission to run a bot

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.

SamoaBot 3 (talk · contribs)

Operator: Ricordisamoa (talkcontribsrecent activitycountblock logrights logupload logSUL)

Bot's tasks for which permission is being sought: internationalize file description pages, using apposite templates (like {{original upload log}}) and MediaWiki system messages (like {{int:license-header}})

Automatic or manually assisted: automatic unsupervised

Edit type (e.g. Continuous, daily, one time run): intermittently, at the operator's discretion

Maximum edit rate (e.g. edits per minute): 20-25 EPM

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

Programming language(s): Python (with PWB)

--Ricordisamoa 01:53, 14 May 2013 (UTC)

Some test edits: Revision of File:Signator.jpg and Revision of File:Emerald spring in yellowstone.jpg --Ricordisamoa 05:02, 14 May 2013 (UTC)
Another: Revision of File:Hospital-quiron-san-sebastian.jpg (at the moment I'm checking every single diff before saving, later I could run it "bot-like") --Ricordisamoa 05:44, 14 May 2013 (UTC)

Discussion

  • The edits look fine to me. I know other bots do work like this, but I don't see much harm in redundancy, especially since you're making a few changes at once. Which portion of the file database do you plan to run it on? --99of9 (talk) 12:49, 14 May 2013 (UTC)
For example I can start from a search, or from pages that transclude {{ImageUpload}}: most times they are old, low-frequency-edited pages, and often contain superseded/superfluous syntax structures. --Ricordisamoa 13:36, 14 May 2013 (UTC)
Ok, that's fine by me. --99of9 (talk) 13:40, 14 May 2013 (UTC)
  • Looks OK for me, but will be good idea to borrow other trivial clean-ups ideas from similar bots. Like {{Location}} place, etc. --EugeneZelenko (talk) 14:21, 14 May 2013 (UTC)

Slick-o-bot-2 (talk · contribs)

Operator: Slick (talkcontribsrecent activitycountblock logrights logupload logSUL)

Bot's tasks for which permission is being sought: uploading, should do the same as User:Slick-o-bot, see there for examples/trail run, i.E. Category:Import by User:Slick-o-bot

Automatic or manually assisted: manually

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

Maximum edit rate (e.g. edits per minute): pywikipediabot framework default

Bot flag requested: (Y/N): Y

Programming language(s): python (pywikipediabot/upload.py)

Slick (talk) 14:14, 12 May 2013 (UTC)

Discussion

  • But why do you need second bot account? --EugeneZelenko (talk) 14:42, 13 May 2013 (UTC)
Currently Slick-o-bot is often busy because I work on Commons:Flickr_batch_uploading. So a second one will be fine to run two jobs at the same time. --Slick (talk) 15:30, 13 May 2013 (UTC)
Really? My bot doesn't know what "busy" means... Smile --Ricordisamoa 16:59, 13 May 2013 (UTC)
Currently I work on Commons:Flickr_batch_uploading/thaigov, I guess up to 10.000 images left. So this will take some time and the bot is blocked for other tasks. And I am not sure about running two upload tasks with the same account, I guess this will make trouble, so I need a second. --Slick (talk) 17:38, 13 May 2013 (UTC)
I don't think it will cause trouble, as long as they're not interfering with one another's files on your local machine. I've tried two different batches from different directories with pywikipedia bot before. --99of9 (talk) 12:51, 14 May 2013 (UTC)
I can try, but I tested if I login on Commons during the bot ist running and logout (with the same account as the bot) the bot stopped and request the password again. So I guess the api/login-token can only get onetime. (But I am not sure) I dont understand whats the problem to allow a second account? --Slick (talk) 13:03, 14 May 2013 (UTC)
I doing a test now if it work to run more than one job with the same account. Stay tuned. --Slick (talk) 16:57, 14 May 2013 (UTC)
Ok, it works to run two jobs with the same account at the same time. So my request can cancel and close. Thank you. --Slick (talk) 20:15, 14 May 2013 (UTC)

Xqbot (talk · contribs)

Operator: Xqt (talkcontribsrecent activitycountblock logrights logupload logSUL)

Bot's tasks for which permission is being sought: Running through Category:Pages with malformed coordinate tags and fixing invalid {{Location}} template coordinate parameters to the right form, e.g. fixing {{Location|51|58.8|0|N|0|12.92|0|E}} to {{Location|51|58|48|N|0|12|52.2|E}} per request

Automatic or manually assisted: automatic run

Edit type (e.g. Continuous, daily, one time run): every day if needed

Maximum edit rate (e.g. edits per minute): 5-12

Bot flag requested: (Y/N): Y

Programming language(s): Python (using mw:Pywikipediabot framework)

 @xqt 12:36, 12 May 2013 (UTC)

Discussion

  • Please use more descriptive edit summaries. --EugeneZelenko (talk) 14:07, 12 May 2013 (UTC)
Sorry, I cannot follow.  @xqt 14:56, 12 May 2013 (UTC)
I think something like Fixing/normalizing coordinates will be much more descriptive then Wikipedia python library; cosmetic changes. --EugeneZelenko (talk) 14:42, 13 May 2013 (UTC)
Yes, that comment will become more meaningful. But I didn't made test edits yet for this request. That message was done while preparing the last run requested at Commons:Administrators'_noticeboard#Category:Pages_with_malformed_coordinate_tags to touch these pictures because I found some problems with access rights until re-login the bot.  @xqt 04:51, 14 May 2013 (UTC)
  • The proposal looks fine. Go ahead and run test edits for this request. --99of9 (talk) 12:55, 14 May 2013 (UTC)

Smallbot (talk · contribs)

Operator: Smallman12q (talkcontribsrecent activitycountblock logrights logupload logSUL)

Bot's tasks for which permission is being sought: To upload ~500k files from the US National Archives and Records Administration based on a database dump provided in partnership with the Digital Public Library of America.

Example
File
Yes, We Have No Ambitions Today! - Nara - 1693425.jpg


Description
English: This cartoon plays off a line from a popular 1923 song ("Yes, We Have No Bananas!") to characterize car maker Henry Ford's Presidential ambitions--or lack thereof. Ford blames his busy schedule for his hesitation to jump into the "Presidential contest pool," while eager supporters encourage him to "come on in!" Berryman was correct in his prediction: Ford chose not to pursue the Presidency.
Author Berryman, Clifford Kennedy, 1869-1949
Date
National Archives and Records AdministrationLink back to Institution infobox template wikidata:Q518155
GLAMcamp DC 2012 - National Archives building 4.jpg
Native name National Archives and Records Administration
Location Washington, D.C. (headquarters), and many regional facilities and presidential libraries nationwide in the USA
Coordinates 38° 53′ 34.01″ N, 77° 1′ 22.71″ W Link to Google Maps  Link to OpenStreetMap
Established
Website www.archives.gov
Authority control
Record ID
NARA Logo created 2010.svg This media is available in the holdings of the National Archives and Records Administration, cataloged under the ARC Identifier (National Archives Identifier) 1693425.

This tag does not indicate the copyright status of the attached work. A normal copyright tag is still required. See Commons:Licensing for more information.


English | español | français | italiano | македонски | മലയാളം | Nederlands | polski | português | русский | slovenščina | Türkçe | Tiếng Việt | +/−

  • NWL-46-BERRYMAN-H009
Source U.S. National Archives and Records Administration
Permission
(Reusing this file)
Public domain This work is in the public domain in the United States because it is a work prepared by an officer or employee of the United States Government as part of that person’s official duties under the terms of Title 17, Chapter 1, Section 105 of the US Code. See Copyright.

Note: This only applies to original works of the Federal Government and not to the work of any individual U.S. state, territory, commonwealth, county, municipality, or any other subdivision. This template also does not apply to postage stamp designs published by the United States Postal Service since 1978. (See 206.02(b) of Compendium II: Copyright Office Practices). It also does not apply to certain US coins; see The US Mint Terms of Use.

Great Seal of the United States (obverse).svg
This file has been identified as being free of known restrictions under copyright law, including all related and neighboring rights.
Other versions Please do not overwrite original files: any restoration work should be uploaded with a new name and linked in this page's "Other versions =" parameter, so that this file represents the exact file found in the NARA catalog record to which it links. The metadata on this page was imported directly from NARA's catalog record; additional descriptive text may be added by Wikimedians to the template below with the "descriptions =" parameter, but please do not modify the other fields. (Please note: this template is not yet part of an official guideline or policy)
Ambox notice.png
The metadata on this page was imported directly from NARA's catalog record; additional descriptive text may be added by Wikimedians to the template below with the "Description=" parameter, but please do not modify the other fields.
Please help us by reporting errors! This may include misidentifications, erroneous images, typos in the metadata, possible copyright issues, and poor-quality images needing rescanning. (Be aware that, for documentary purposes, NARA often retains the original image captions, which may be erroneous, biased, or even misspelled.)


Automatic or manually assisted: Automatic

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

Maximum edit rate (e.g. edits per minute): 10-15, as fast as it uploads

Bot flag requested: (Y/N): No

Programming language(s): Python 3.2

Will use metadata from DPLA bulk download for NARA. The metadata is in json, and is converted formatted to the template by the bot.

Smallman12q (talk) 23:41, 8 May 2013 (UTC)

Discussion

For reference, a previous NARA batch upload was approved at Commons:Bots/Requests/US National Archives bot.Smallman12q (talk) 23:41, 8 May 2013 (UTC)

  • Yeah sure, looks good to me. --Dschwen (talk) 21:21, 9 May 2013 (UTC)
Usual suggestion: please use language template for Author/Source/Record ID fields. --EugeneZelenko (talk) 13:44, 11 May 2013 (UTC)
  • Please can you put a deeplink in the "source" field, as that is where most editors will look. I tried to get the original of this example, but apparently "The Online Public Access (OPA) system will be down for maintenance from May 10 to May 25.", so we may not be able to thoroughly test this for a couple of weeks. --99of9 (talk) 13:01, 14 May 2013 (UTC)
  • What kind of label is: "NWL-46-BERRYMAN-H009"? It might help to add the name of this kind of identifier. --99of9 (talk) 13:02, 14 May 2013 (UTC)
  • 500k files! Wow, this is huge, congratulations and good luck! --99of9 (talk) 13:09, 14 May 2013 (UTC)

Rybecbot (2) (talk · contribs)

Operator: Rybec (talkcontribsrecent activitycountblock logrights logupload logSUL)

Bot's tasks for which permission is being sought: Sometimes when files are transferred from Flickr by a bot, the tags on Flickr lead the bot to add inappropriate categories. For example, this photo of some rocks in shallow water was given the unhelpful categories Commons, Facebook, Flickr, Google, News, Pic, Wallpaper, Wiki, Wikipedia and Photographs. Mass importation of files causes a need for mass removal of categories, which is what this request is for.

Automatic or manually assisted:automatic with some supervision

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

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

Bot flag requested: (Y/N):Y

Programming language(s): Python (standard pywikipedia category.py or replace.py script)

Rybec (talk) 02:14, 31 March 2013 (UTC)

Discussion

  • Test edits have been done: 50 files were removed from the News category. Rybec (talk) 06:33, 31 March 2013 (UTC)
  • So do you remove every image in this kind of category, or only those from Flickr, or??? --99of9 (talk) 13:13, 31 March 2013 (UTC)
I think you could make better edit summaries, like Removing [[Category:News]]. Also will be good idea to remove from several categories at once edit when applicable. --EugeneZelenko (talk) 14:22, 31 March 2013 (UTC)
  • The bots that import images from Flickr don't create new categories, but only add images to categories that already exist, so my intention is not to get rid of the categories entirely. When a category should contain no images but only subcategories, then I would want to empty it of images, but typically there would be some images which belong and others which don't. My intention is to manually identify the ones which don't belong, make a list of them, then have the script make the changes.
I've done another three test edits to show removal of multiple categories in a single edit with a non-default edit summary: [28] [29] [30]. Rybec (talk) 21:09, 31 March 2013 (UTC)
Looks OK for me, but I think will be good idea to use link to categories in edit summary. --EugeneZelenko (talk) 14:36, 3 April 2013 (UTC)
I don't object to doing that. Rybec (talk) 00:48, 4 April 2013 (UTC)
I’ve have had the same kind of trouble with stuff bot-uploaded from Flickr being piled up in Category:Lisbon (a much more specific category than those above, of course), which is a pain to clean up manually. There’s a few things that the importing tool could do automaticly, like avoiding over-categorization (e.g. if a photo is under Category:Streets in Lisbon is should not be also under Category:Lisbon), but more or less human input and manual work is going to be needed sooner or later. A big problem is how to tell apart what media really belong in a given category from those that should be further moved to more detailed subcategories within the same tree. I’d really like to have separate "(cleanup)" subcategories for all categories afflicted by this kind of flooding, really. -- Tuválkin 20:18, 5 April 2013 (UTC)

SamoaBot 2 (talk · contribs)

Operator: Ricordisamoa (talkcontribsrecent activitycountblock logrights logupload logSUL)

Bot's tasks for which permission is being sought: detecting and logging (in a user subpage) SVG images without a proper xmlns declaration on the root <svg> element: those images aren't viewable at all in some browsers, and should be properly fixed (this can be done later, either manually or automatically)

Automatic or manually assisted: automatic, supervised

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

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

Bot flag requested: (Y/N): N (already flagged, see Commons:Administrateuren/SamoaBot)

Programming language(s): JavaScript, with Ajax (own code, will be published soon)

Ricordisamoa 04:56, 26 March 2013 (UTC)

Discussion

Here can be seen the log of all images detected so far.--Ricordisamoa 06:02, 26 March 2013 (UTC)

  • How hard would it be for your bot to fix them and reupload? --99of9 (talk) 23:42, 26 March 2013 (UTC)
    It is currently written in JavaScript (I plan to switch to Python in a few weeks), and Ajax upload isn't tested yet, but I will try to do as much as possible. In the meantime, it could however log these files. --Ricordisamoa 02:52, 27 March 2013 (UTC)
I think will be good idea to add maintenance template to image page too.
Edit summary for log action could be just file name with a link, log page name is self-explanatory.
EugeneZelenko (talk) 14:44, 27 March 2013 (UTC)
Does a proper template exist for these cases? (and I'll work on edit summary) --Ricordisamoa 06:14, 28 March 2013 (UTC)
{{BadSVG}} may be adapted for this purpose, or {{Cleanup image}} may be used. --EugeneZelenko (talk) 14:47, 28 March 2013 (UTC)
  • Pictogram voting info.svg Info In Firefox, you can use the sendAsBinary() method of your XHR-instance to upload the SVG. This avoids encoding issues (while some SVGs also work with the send method, this will screw up others). Downloading is very easy through a GET since the cross-origin-issue is resolved.
  • I created a sample that works with FF 19 (tested): User:Rillke/fastTransfer.js. It downloads and uploads a file immediately when invoked. You have access to the raw data in function _gotFile so you can manipulate that data. -- Rillke(q?) 20:43, 28 March 2013 (UTC)
  • I had a look with Firefox 19. It displayed two of the nine files on the list.
(E)-pent-2-ène.svg does not display
(Z)-pent-2-ène.svg does not display
(±)-Ethyl-2-methylbutyrate_Structural_Formulae_V.1.svg has been re-uploaded several times; version of 13:06, 26 March 2013 does not display and Mediawiki did not generate a thumbnail for it; other versions okay
1-Chlornaphthalin.svg displays correctly
1-jpg.svg Mediawiki says there's an error in the file; does not display in browser
1025arud.svg Mediawiki says there's an error in the file; does not display in browser
10th_Panzer_Division_logo_1.svg has been re-uploaded, but both versions displayed correctly
1422_Zeta_in_the_Serbian_Despotate_after_death_Balsa_III.svg does not display
1885ArmenianFlag.svg has since been re-uploaded; original file did not display
Rybec (talk) 22:21, 28 March 2013 (UTC)

OK, now I'm going to run a fixed version of the script; let's see... --Ricordisamoa 23:16, 28 March 2013 (UTC)

  • I tried to view the new additions to the list, with similar results: most of the files did not display, but one did. I don't know enough about the subject to say definitively that there are false positives.
1969_draft_lottery_scatterplot.svg file has been replaced; old version did not display in Firefox
1988_Illinois_Constitutional_Convention_Vote_pie_chart.svg file has been replaced; old version did not display in Firefox
1st_Panzer_Division_logo.svg displays correctly in Firefox
2-propil-amine.svg does not display in Firefox
201globe.svg file has been replaced; old version did not display in Firefox
250x250Feld.svg does not display in Firefox
2NOGCMOS.svg does not display in Firefox
Even with the possible false positives, the usefulness of this list is apparent. If making the list is all that this request covers, I fully support it (if the request is also about automatically fixing the problems that are found, I don't support that part: some unneeded changes might be made, and test edits fixing the SVG files haven't yet been done). Rybec (talk) 23:55, 30 March 2013 (UTC)
After 1st_Panzer_Division_logo.svg I changed the code, so it should work well now. --Ricordisamoa 10:54, 31 March 2013 (UTC)

I Symbol support vote.svg Support this request, but I'm leaning against applying the bot flag. If it's only editing one page, and even that only once per minute, I don't see it as necessary. Am I missing a reason you need the flag? --99of9 (talk) 11:10, 31 March 2013 (UTC)

The purpose of the bot flag is to avoid flooding RCs (if the bot's speed is out of control)... anyway, there's also the first request. --Ricordisamoa 13:57, 31 March 2013 (UTC)
What is final functionality? Will bot re-upload fixed files, or only log problematic files? If last is true, will be clean-up template added to file page? --EugeneZelenko (talk) 14:26, 31 March 2013 (UTC)
In case it is only logging, I can try to write a JavaScript-Bot which fixes the issue that does not need any other host than a compatible browser to run. IMHO a logging-bot does not need a bot-flag but it would be great if we could combine this functionality (detection and fixing). Then, we also do not need to log each occurrence or adding a template. -- Rillke(q?) 09:16, 1 April 2013 (UTC)
You get my {{support}} --Ricordisamoa 11:15, 1 April 2013 (UTC)
I need your source code. -- Rillke(q?) 09:54, 2 April 2013 (UTC)
User:Ricordisamoa/XMLNSense.js --Ricordisamoa 10:23, 2 April 2013 (UTC)

┌─────────────────────────────────┘
Thank you. → User:Rillke/MwJSBot.SVGXmlNSFixer.js. Log and continue-params are written to my user space by default but this can be customized by creating an own instance of window.SVGXmlNSFixer. Detection of svg root in its own svg namespace like for this file has to be fixed.

-- Rillke(q?) 20:35, 3 April 2013 (UTC)

So could you operate a real bot for this task? --Ricordisamoa 20:52, 3 April 2013 (UTC)
I've no dedicated server/computer for this task, if that is your question. But I think if I or someone else continue(s) running this JavaScript over all 666,540+ SVG files, it would be a good idea to ask whether other issues with SVG files should be considered as well. Also the speed/bandwidth is not really sufficient… -- Rillke(q?) 16:58, 4 April 2013 (UTC)
I meant "a flagged bot account"; BTW, I got the flag (for another task). --Ricordisamoa 18:47, 4 April 2013 (UTC)
I've no flagged bot account where the task would be appropriate to run under. -- Rillke(q?) 20:18, 4 April 2013 (UTC)
Would your script work on Chromium/Chrome? --Ricordisamoa 21:16, 4 April 2013 (UTC)
It seems so. At least the loop runs and the parser does its job. Not entirely sure whether the upload will work but it's very likely (it's using the usual XHR.send() as SVGs are UTF-8 encoded). -- Rillke(q?) 22:00, 5 April 2013 (UTC)
Should I continue running the script (e.g. under RillkeBot (not flagged)), would you like continuing running it, or do we want to split the load, are there questions left? -- Rillke(q?) 20:44, 14 April 2013 (UTC)
For me it's ok, but you should get a bot flag; I'm thinking it may be better to swich to Pywikipediabot, though. --Ricordisamoa 13:30, 15 April 2013 (UTC)

How many files are we approximately looking at? If it is of the order of a hundred or less then I suggest to just go ahead with it. --Dschwen (talk) 21:26, 9 May 2013 (UTC)

It would have to check all files on the Commons, and upload at least several hundred images... However, I have PWB installed, and will starting coding something tomorrow. --Ricordisamoa 21:54, 9 May 2013 (UTC)
First of all you'll have to check all SVG files. Secondly, when you code please make sure to do a http range request! Try downloading just the first kilobyte of each file you are analyzing. This should speed things up. Let me know if you need help with that in python, I've implemented it before. --Dschwen (talk) 22:38, 9 May 2013 (UTC)

Rybecbot (talk · contribs)

Operator: Rybec (talkcontribsrecent activitycountblock logrights logupload logSUL)

Bot's tasks for which permission is being sought: re-uploading photos which have been cropped to remove watermarks and editing accompanying text to indicate the watermark has been removed

Automatic or manually assisted: automatic, lightly supervised

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

Maximum edit rate (e.g. edits per minute): 2 when uploading files, 4 when changing text

Bot flag requested: (Y/N): Y

Programming language(s): Python (the Pywikipediabot upload.py script with minor changes and the replace.py script with no changes)

Rybec (talk) 05:29, 22 March 2013 (UTC)

Discussion

  • Badly needed. Please execute a batch of runs as an example. --Foroa (talk) 06:54, 22 March 2013 (UTC)
  • I'm having trouble doing the test edits because the newly-created bot account doesn't have reupload permission (just reupload-own)--I checked here. Rybec (talk) 12:18, 22 March 2013 (UTC)
    • Yes it's very nasty for new bot accounts. Should work now! -- Rillke(q?) 18:10, 22 March 2013 (UTC)
      Thank you! I've done the test edits. I only prepared 24 files to replace instead of the suggested 30 to 50. Rybec (talk) 20:42, 22 March 2013 (UTC)

Please do not continue until the bot preserves Metadata and please repair this for all edits done so far by the bot. Example where data is lost at File:047-1211 Enschede 125.JPG (before after processing). Please also include a meaningful upload/edit summary (like "image cropped to remove watermark"). Thank you! -- Rillke(q?) 21:55, 22 March 2013 (UTC)

Pictogram voting question.svg Question Which software do you use for cropping the file? Is it lossless? -- Rillke(q?) 22:02, 22 March 2013 (UTC)

  • Thanks for the review! I used jpegtran, which is lossless. I hadn't noticed the problem with the EXIF data; I don't know why that happened. Rybec (talk) 22:19, 22 March 2013 (UTC)
    • ExifTool is, for example capable copying (nearly) all metadata from the original file to the edited one. This way you could ensure they are never lost. -- Rillke(q?) 10:38, 23 March 2013 (UTC)
  • I've reverted my test/example edits. Rybec (talk) 22:34, 22 March 2013 (UTC)
    • Thank you. -- Rillke(q?) 10:38, 23 March 2013 (UTC)
  • Great demand exists for automated removal of watermarks, and this pioneering bot is brilliant :D I would say the exif is less important at the moment especially if the information is still made available with the older version. If it inspires people to make exif copying bots, all the better. I believe it is not long before we see watermark removal bots that mend the picture rather than crop, but for the time being, in these chaotic times where trigger fingers are blocking people for good contributions, Rybec's bot would help bring some badly needed relief and order. Rybec certainly seems responsive, capable, and I recommend flagging his bot forthwith ! I can't see maintenance and improvements being a problem. Penyulap 05:59, 23 March 2013 (UTC)
    • In this case they contained copyright and camera information and it is quite bad if they aren't visible any more at the file description page. -- Rillke(q?) 10:38, 23 March 2013 (UTC)
  • Pictogram voting question.svg Question: Does your bot automatically detect the watermarks or are you manually instructing what to crop? -- Rillke(q?) 10:38, 23 March 2013 (UTC)
    I was just using the identify command from Imagemagick to get the pixel size of downloaded images, subtracting 138 from the height, scripting jpegtran to crop to that size, and the only function of the bot is the re-uploading. I agree that the metadata is important. The problem was that I didn't use the "copy all" option to jpegtran. I've manually uploaded to File:1210_Turnhout_029.JPG one example of a file cropped with the "copy all" option. Its EXIF data is preserved. I also learned how to do an edit summary with the script: [31]. I've started another test run, with the metadata and the edit summaries. Rybec (talk) 11:51, 25 March 2013 (UTC)
  • Someone pointed out the need to remove {{watermark}} and the category Category:Uploads by Microtoerisme with watermarks. I was thinking that could be done with VisualFileChange.js. Rybec (talk) 12:47, 25 March 2013 (UTC)
Not remove "watermark", but change it to "watermark removed". ("watermark removed" is appropriate for these uploads) – JBarta (talk) 13:01, 25 March 2013 (UTC)
I've done a second test run, changing {{watermark}} to {{watermark removed}} and removing [[Category:Uploads by Microtoerisme with watermarks]] as described by Jbarta. The files can be seen at Special:ListFiles/Rybecbot. I've changed my request to add the use of the standard replace.py script for the textual changes. Rybec (talk) 21:41, 28 March 2013 (UTC)
Results look good to me. --VanBuren (talk) 21:52, 1 April 2013 (UTC)
I wasn't even aware that "Attribution metadata from licensed image" existed. Might I suggest that "watermark removed" is more used, more intuitive and easier to spot than the other? The resulting template on the image description page is the same either way. Just a thought. – JBarta (talk) 11:36, 6 April 2013 (UTC)
Assuming Jarry1250's Toolserver Template transclusion count tool is correct, {{Attribution metadata from licensed image}} is transcluded 6,192 times while {{Watermark removed}} is transcluded 3,422 times. If an image license doesn't require attribution, then {{Metadata from image}} can be used.--Rockfang (talk) 13:35, 6 April 2013 (UTC)
  • The mistaken edit found by Rockfang is one I did manually. When doing the textual replacements, the bot will look for the specific text "{{watermark}}" (by which I mean, enclosed in curly brackets) and change it. Only if {{watermark}} appeared twice already, or together with {{watermark removed}} would it make the same mistake I did. Face-smile.svg If it encounters "{{watermark removed}}" it does not do any replacement. In other words, it's not inserting {{watermark removed}} but rather changing {{watermark}} to {{watermark removed}}. For the text replacement task I want to use the standard replace.py script from pywikipedia. I don't especially mind using {{Attribution metadata from licensed image}} rather than {{watermark removed}}, although the latter is more succinct. On Wikipedia, using redirects in a similar manner is considered okay. Is it the same here? Is the redirect likely to be deleted? If not, it seems to me like a matter of indifference. Rybec (talk) 22:05, 6 April 2013 (UTC)

Hazard-Bot (talk · contribs)

Operator: Hazard-SJ (talkcontribsrecent activitycountblock logrights logupload logSUL)

Bot's tasks for which permission is being sought: Category replacements

Automatic or manually assisted: Automatically

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

Maximum edit rate (eg edits per minute):

Bot flag requested: (Y/N): No

Programming language(s): Python

There are cases when more help is wanted for category replacements. Now is an example. User:CommonsDelinker/commands has a backlog with, I believe, no bots working on it at the moment, so I'd like to be able to help out in such cases.  Hazard-SJ  ✈  01:36, 19 March 2013 (UTC)

Discussion

  • There has been some recent issues with SieBot recently that makes COM:CDC to be backlogged. I'd welcome very much a clone for performing those category moves when SieBot is not working. I support approval (with flag). —MarcoAurelio (talk) 15:20, 19 March 2013 (UTC)
  • Please make a test run if this is not standard bot. --EugeneZelenko (talk) 14:28, 20 March 2013 (UTC)
  • If this is not a standard bot, one has to care that nothing inside <nowiki><!-- --> or <source> is replaced. -- Rillke(q?) 17:46, 22 March 2013 (UTC)
  • I planned to use CategoryMoveRobot in category.py (PyWikipedia trunk). Originally, I was planning to manually start the bot for each request, but I could create an on-wiki page for the bot (or use the one currently in use) to use so I wouldn't have to manually start it each time. I'd still integrate the CategoryMoveRobot class into it, though. Would that be preferred? (P.S. SieBot is back up so there isn't much of a rush now.)  Hazard-SJ  ✈  00:27, 23 March 2013 (UTC)
    I think will be good idea to use User:CommonsDelinker/commands for list of requests and proceed automatically. --EugeneZelenko (talk) 14:30, 24 March 2013 (UTC)
    • In such a case, however, the completed requests won't be removed until someone comes along to do so manually, as my bot cannot edit that page.  Hazard-SJ  ✈  04:18, 26 March 2013 (UTC)
      • If you create a separate account for the task, that account could be admin-flagged so that it can edit the page. The task is important and it would be best to integrate a supplementary bot into the existing structure as neatly as possible. Rd232 (talk) 10:55, 3 April 2013 (UTC)
        Even if I'm not an admin myself (as is the current case)?  Hazard-SJ  ✈  23:09, 13 April 2013 (UTC)
        • Many moves require still manual intervention as many items cannot be bot moved and in some cases a redirect is created, otherwise deleted; I don't think that can be handled by a bot anyway. (I spend on average 2 minutes per category move on cleaning up). --Foroa (talk) 11:06, 3 April 2013 (UTC)
          Yes, moving categories it technically impossible, so without admin access it wouldn't be able to do the deletions, but rather, create the new category and request deletion of the old one.  Hazard-SJ  ✈  23:09, 13 April 2013 (UTC)
          • Ideally, the bot should be able to update the Wikidata structures as for example in d:Q1144392. --Foroa (talk) 11:11, 3 April 2013 (UTC)
            I agree: this is a very good idea. Conveniently, I'm already approved to do this on Wikidata.  Hazard-SJ  ✈  23:09, 13 April 2013 (UTC) This can't be done until Wikimedia Commons is somehow integrated into Wikidata.  Hazard-SJ  ✈  03:56, 21 April 2013 (UTC) It's currently not possible to search for values of D:P:P373 via the API. The only way to get to the relevant Wikidata item would be, considering there is a (correct) link in a template on the category page (such as in {{w}}), go to the Wikipedia page, then the item (if there is one), then change the value of p373.  Hazard-SJ  ✈  04:42, 21 April 2013 (UTC)
  • For the record, SieBot is, again, down, so I've gone ahead and coded the bot. I've ran a 16-edit trial with it here, doing four requests in all. Of course, as I already mentioned, the bot isn't able to edit the queue page, since the current one is fully protected. Also, for now, I'm just marking the old category as a category redirect to the new one.  Hazard-SJ  ✈  03:56, 21 April 2013 (UTC)
  • We need at least one other bot looking at the commands. SieBot is asleep way too often. However
    1. If the bot behaves differently from SieBot, it should replace it and not work alongside it
    2. If the bots are to work concurrently, you would have to account for more than one bot picking up the same request (as neither can edit User:CommonsDelinker/commands to remove a request before they start executing it).
If the bot doesn't behave like SieBot, can you specify in the request how it differs? Does the bot alter the old category for example (afaik SieBot does not)? –⁠moogsi (blah) 02:40, 28 April 2013 (UTC)
As for working concurrently, the only (if not, main) problem if they're working on the same category at the same time would be an edit conflict, which is already handled. Specifically, the bot currently creates the new category page if it doesn't exist (attributing the authors in the summary, or on the talk page if the list is too long), then moves the categories. After it determines that the category is empty, it replaces the content of the old category page with {{Category redirect|"new category name"}}. All that can be seen from the trial I made. As for behaving differently, I think the main difference is the implementation, and probably that my bot actually edits the old category afterwards (not sure if SieBot does that).  Hazard-SJ  ✈  02:56, 28 April 2013 (UTC)
{{Move}} requests have to be stripped during the transfer, no need to remove it from the delinker queue as it needs manual inspection (5 % of moves need manual intervention or category restructuring). --Foroa (talk) 16:08, 29 April 2013 (UTC)
I can implement that.  Hazard-SJ  ✈  02:25, 30 April 2013 (UTC)
  • Symbol support vote.svg Support I want to make it clear that I support the proposal in its current form, before I start talking about additional features :) One thing which SieBot doesn't do (and which I think wouldn't be difficult to implement) is leave edit summaries for category moves. {{move cat}} has a reason parameter which basically goes unused, as SieBot operates apparently without purpose –⁠moogsi (talk) 19:35, 12 May 2013 (UTC)

If nobody has further objections, I propose that we approve this request. I expect that there will be some teething issues, but am confident that the bot operator is capable and will be sufficiently responsive to resolve them. --99of9 (talk) 13:32, 14 May 2013 (UTC)

UWCTransferBot (talk · contribs)

Operator: Ahonc (talkcontribsrecent activitycountblock logrights logupload logSUL)

Bot's tasks for which permission is being sought: I wrote a bot using php for transfering free images from Ukrainian Wikipedia to Commons. It is an alternative to CommonsHelper, as CommonsHelper often generates bad descriptions and they are to be checked and fixed, and my bot is better adjusted for it. Images will be checked by local sysops before transfer.

Automatic or manually assisted: automatic

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

Maximum edit rate (eg edits per minute): 5-10

Bot flag requested: (Y/N): Y

Programming language(s): PHP, based on Chris G's botclasses framework.

Anatoliy (talk) 21:52, 18 March 2013 (UTC)

Discussion

Looks like human review before transfer is good idea (example: File:Вп станция сихов.jpg). Also better author attribution is possible (File:Врубель Серафим.jpg, File:Бівуак. Чатир-Даг..JPG). As well as better categorization (File:Голосіїв.jpg).
EugeneZelenko (talk) 14:18, 19 March 2013 (UTC)
Situation like in first example is fixed. Such images will not transfered from uk-wiki. They should be transfered from original wiki (in this example Russian). Categories for Commons are taken from template 'Move to Commons' in file description in local wiki.--Anatoliy (talk) 12:00, 8 May 2013 (UTC)
  • Please can you internationalize the headings to save us having to do this [32] --99of9 (talk) 13:26, 14 May 2013 (UTC)
    Fixed. Changes will be applied during next run.--Anatoliy (talk) 17:02, 14 May 2013 (UTC)

JAnDbot (talk · contribs)

Operator: JAn Dudík (talkcontribsrecent activitycountblock logrights logupload logSUL)

Bot's tasks for which permission is being sought: replacing text, recategorization, maybe more

Automatic or manually assisted: both

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

Maximum edit rate (eg edits per minute):

Bot flag requested: (Y/N): Yes (global bot)

Programming language(s): pywikipedia

JAn Dudík (talk) 10:29, 21 February 2013 (UTC)

Discussion

Could you be a bit more specific please about what you intend to do with your bot? --Dschwen (talk) 14:37, 21 February 2013 (UTC)

Since there was zero further input from the requester I will close this as stale soon. --Dschwen (talk) 23:13, 12 March 2013 (UTC)

I want to use bot mainly for mass recategorization or mass replacing of text, see contributions. Maybe, when Wikidata will be able to store links to commons, I'll work on this field too. JAn Dudík (talk) 07:12, 13 March 2013 (UTC)

You mean the several thousand edits your bot made without having a flag? Please don't do that or we will have to block the bot. Recategorizations are already performed by User:Category-bot. And I won't give out a bot flag for a maybe job. I'll close this one. You are welcome to reopen a request if and when you have a specific task (that is not already covered by an existing bot). --Dschwen (talk) 15:26, 13 March 2013 (UTC)

Although I agree that the unapproved volume was inappropriate, the 23 Feb URL format changes like this look useful. So if you can give us a clear, more focused/limited scope, I'd potentially support. --99of9 (talk) 22:44, 13 March 2013 (UTC)

Maybe we could create a template for "URL REKOS", to prevent all those bot edits. --Ricordisamoa 22:23, 25 March 2013 (UTC)

Neuchâtel Herbarium (talk · contribs)

Operator: Chandres (talkcontribsrecent activitycountblock logrights logupload logSUL)

Bot's tasks for which permission is being sought: Upload of the pictures created by the commons:Neuchâtel Herbarium project

Automatic or manually assisted: semi automatic, I launch the script manually for a fixed number of picture to upload , but once it's started the process is automatic

Edit type (e.g. Continuous, daily, one time run):around 40 000 pictures remain to be upload, by batch when I'm available to control the upload process, no full automatic work

Maximum edit rate (eg edits per minute):4-5 upload per minute

Bot flag requested: Y:

Programming language(s):

Chandres (talk) 14:27, 13 February 2013 (UTC)

Discussion

It might be a good idea to respect the capitalisation of the categories. So far, I renamed the categories of the majority of your uploads. --Foroa (talk) 14:56, 13 February 2013 (UTC)
Thanks for the warning , we update the script and I will correct the already upload pictures.--Chandres (talk) 15:01, 13 February 2013 (UTC)
I think will be good idea to use Bot in account name. Why Template:Information is not used? --EugeneZelenko (talk) 15:46, 13 February 2013 (UTC)
It's not really a bot account, it's always me behind, but used with a script. --Chandres (talk) 18:05, 20 February 2013 (UTC)
Well, using [[tl|Specimen}} is probably some sub-project policy which we could argue against until we are blue in the face... The sourcecode of the description page is formatted in a very confusing way. It took me 3 minutes to figure out where the closing template braces are and to realize that {{Information field}} is uses within the description field. This needs to be made clearer. --Dschwen (talk) 16:26, 13 February 2013 (UTC)
 {{Specimen
 |taxon=Abies alba
 |authority=
 |institution={{Institution:University of Neuchâtel}}
 |description=
 {{en|1=Neuchâtel Herbarium - ''[[:en:Abies alba]]''}}
 {{de|1=Neuchâtel Herbarium - ''[[:de:Abies alba]]''}}
 {{fr|1=Neuchâtel Herbarium - ''[[:fr:Abies alba]]''}}
 {{it|1=Neuchâtel Herbarium - ''[[:it:Abies alba]]''}}
 |date=
 |source={{own}}
 |author=[[User:Neuchâtel Herbarium|Neuchâtel Herbarium]]
 |permission=
 |other_versions=
 |other_fields={{Information field|name={{Occupation|1=Botanist}}|value=?}}
 }}
Actually it is a minor miracle that the old version doesn't produce invalid HTML. If you want to use {{Information field}} please add it to the other_fields parameter. --Dschwen (talk) 16:34, 13 February 2013 (UTC)
Is this being adressed? --Dschwen (talk) 17:06, 19 February 2013 (UTC)
Yes, if , see below :-)--Chandres (talk) 18:05, 20 February 2013 (UTC)
Do we need the "description" ? It seems redundant with other parameters. I have proposed an alternate layout at File:Neuchâtel Herbarium - Abies alba - NEU000003665.tif. --Zolo (talk) 20:09, 14 February 2013 (UTC)
The actual description field is important for the project by the providing the links to the wikipedia articles in several language, especially the swiss one. But if anybody has ideas on how improving this information part, I will be more than happy! --Chandres (talk) 08:35, 18 February 2013 (UTC)
You mean, in this case, the link to en:Abies alba. There is a link to the corresponding category in the header. I would also prefer a link to Wikipedia, but we should be able to have that once wikidata: is deployed to Commons (hopefully, in a few months). Personnally, I find it unintuitive and rather confusing to have two different links just a few lines away from each other, without clear rationale why one links to Wikipedia and the other to Commons. --Zolo (talk) 05:06, 19 February 2013 (UTC)
I find that the link the the commons category give less information than a link to the wikipedia article, but maybe we could improve the wording of the description to be more explicit. The idea of having the link to wikipedia article is "reader oriented", whereas commons category is really "wikimedian oriented". I don't want to wait for Wikidata deployment, we never what will happend, and we can always run a bot to correct that afterwards. --Chandres (talk) 18:05, 20 February 2013 (UTC)

The addition of "dried pressed specimen" is ok in english, but would complicated ,without benefice, the script in other language. I will control after upload if all description are present.--Chandres (talk) 06:51, 3 May 2013 (UTC)

  • I don't completely understand your answer. Do you mean that you do not know the translation for "dried pressed specimen" in the languages you plan to use, or do you mean that it would be hard to add the words to each language? (Sorry for the slow reply) --99of9 (talk) 13:13, 14 May 2013 (UTC)

Smallbot (talk · contribs)

Operator: Smallman12q (talkcontribsrecent activitycountblock logrights logupload logSUL)

Bot's tasks for which permission is being sought: To upload files related to Commons:Batch uploading/ECGPedia The files that will be uploaded can be found at User:Smallbot/source/Cardionetworks

This is based on OTRS Ticket#2011102310008874 . The ticket is a year old.

Related discussions:

Automatic or manually assisted:automatic

Edit type (e.g. Continuous, daily, one time run): One time run...though there may be future uploads

Maximum edit rate (eg edits per minute): depends on upload speed (10)

Bot flag requested: (Y/N): N

Programming language(s): VBScript (Javascript, XMLHTTP, MSHTML, XMLDOM, COM).

Smallman12q (talk) 16:56, 1 December 2012 (UTC)

Discussion

A lot of the files lack a description. Also, how should author information be handled? There are a number of .swf, a format that will never be supported on commons Bugzilla26269, that could be converted to a supported video format. The .avi could be converted to a supported video format.Smallman12q (talk) 16:56, 1 December 2012 (UTC)

Please make test uploads. --EugeneZelenko (talk) 15:42, 2 December 2012 (UTC)
First, I need to verify the OTRS ticket and make the relevant template. I've asked at Commons:OTRS/Noticeboard#Cardio_Networks.Smallman12q (talk) 17:33, 2 December 2012 (UTC)
The answer from another OTRS volunteer on that page:
License template exist at Template:Cardionetworks permission that provides the relevant details. Regards -- KTC (talk) 18:14, 2 December 2012 (UTC)
Hope this helps, if not, don't hesitate to remove the {{section resolved}} template and ask further! Trijnsteltalk 18:57, 2 December 2012 (UTC)
Thanks. Didn't know the template was already made. Will do upload later this week.Smallman12q (talk) 20:39, 2 December 2012 (UTC)
Wonderful. Will these images all be put together in a single category? Do you need anything further from my end? James Heilman, MD (talk) 18:34, 13 December 2012 (UTC)
I don't see the test uploads yet. Also can you supply links to a few swf files? If they are either static or videos they could be converted as well. Do you have a solution for converting the avi videos yet? --Dschwen (talk) 00:46, 16 January 2013 (UTC)

Working-I'm going to do this upload this week..was busy with Commons:Gerald R. Ford Presidential Library and Museum but they seem to be stuck in a bureaucratic quagmire. The .swf files have an equivalent .avi file (my guess is the .swf is just a flash wrapper for those who can't play .avi but have flash). The .avi will be converted to the webm format(which the commons now supports) before upload. I am in the process of downloading the files... probably around 10GB + for each wiki. I've written a script that will download all files, the file history table for each file, and text of the file for a wiki so this may be handy for future uploads. A lot of the files lack any text so I'm not sure what to put for these. Any thoughts are welcome.Smallman12q (talk) 00:41, 28 January 2013 (UTC)

What are some examples of fills missing text? James Heilman, MD (talk) 01:02, 28 January 2013 (UTC)
There are quite a few files missing text. Have a look at User:Smallbot/source/Cardionetworks/Example to see how the uploads will look (including those missing text). Let me know if it looks okay.Smallman12q (talk) 17:18, 29 January 2013 (UTC)
Yes that is okay. We will need to go through and add this after the fact. James Heilman, MD (talk) 02:01, 31 January 2013 (UTC)
A few peculiarities
  • Afib_ecg.jpg (and a few more) == Description == inside the description value in the Information template.
  • 2072.jpg this description is not useful (maybe tag everything with a description of less then 10 chars as needing description)
  • Course.jpg this is most likely a copyright violation (stock image, compare to this image or do google image search or tineye.
That last point makes me a bit uneasy about the whole task. --Dschwen (talk) 21:39, 31 January 2013 (UTC)
I've uploaded ECGpedia at Category:Media from CardioNetworks ECGpedia. I fixed the description issue I believe. I will go back and add {{Description missing}} to descriptions with less than 10 characters. I've requested speedy-delete for File:Course (CardioNetworks ECGpedia).jpg I'll do uploads of the other pediass tmrw.Smallman12q (talk) 03:49, 1 February 2013 (UTC)
Sure so 2) the HR = 32 means that the heart rate is 32, standard shorthand and useful 3) I have sent a note to the up loader there and we will figure out who has copied from who. Does look like it is from here though [33]. The point is the ECGs though and not the clip art. James (log in appears broken)
Ok, so it was probably a fluke. I suggest you go ahead and do a few more test uploads. We should be able to resolve this quickly if you have time. --Dschwen (talk) 02:49, 2 February 2013 (UTC)
@Dschwen Resolve what exactly? I'll do echopedia.org next.Smallman12q (talk) 19:32, 2 February 2013 (UTC)
This bot request. --Dschwen (talk) 15:23, 3 February 2013 (UTC)

┌─────────────────────────────────┘
For Echopedia, a lot of the files have no description, I will see if I can get some from the template on case files pages.Smallman12q (talk) 02:32, 5 February 2013 (UTC)

I have had a look at both ECGpedia and Echopedia and am sceptical as to the usefulness of this bot approach. What it does on the Commons end (i.e. after spidering the source side) is (1) upload the files with (2) information on source, author and licensing, (3) add maintenance categories. For most of the files, this leaves Commons users with the tasks of (4) providing descriptions, (5) providing content categories and (6) renaming the files to Commons standards. That is a lot to ask for, and so I would personally favour an approach more akin to Flickr2Commons, in which individual Commons users import selected materials, and thus take responsibility for them here. Another thing I noticed is that the image pages over there link to "description pages" on Commons, which never exist because the files have the " (CardioNetworks ECGpedia)" suffix here. Has that anything to do with their collaboration with us or is this simply an error in their MediaWiki configuration? -- Daniel Mietchen - WiR/OS (talk) 22:38, 8 February 2013 (UTC)
I tend to agree with Daniel here. There hasn't been a lot of discussion whether this stuff should be imported. I can see that some of the files can provide educational value, but this is largely dependent on good descriptions. Is there an anticipated use for those file on Wikimedia projects? Ie. Wikiversity cardiology? ;-) --Dschwen (talk) 23:01, 8 February 2013 (UTC)
An obvious use case would be WikiProject Medicine but the usefulness certainly depends on the quality of the descriptions and discoverability by way of categories (or perhaps file names). -- Daniel Mietchen - WiR/OS (talk) 23:05, 8 February 2013 (UTC)
For the stuff already imported, I suggest adding specific (rather than things like {{Description missing}}) maintenance categories that address the points 4-6 in my comment from an hour ago, i.e. something like Category:Media from CardioNetworks ECGpedia missing descriptions (for which an alternative would be CatScan), Category:Media from CardioNetworks ECGpedia missing categories (these have not been tagged at all, by the way, since Category:Media from CardioNetworks ECGpedia had not been marked as hidden and thus counted as a content category) and Category:Media from CardioNetworks ECGpedia needing file name review. This way, people interested in helping out with ECGpedia can dive right in and do not have to spend time searching for files in need of their help. -- Daniel Mietchen - WiR/OS (talk) 23:25, 8 February 2013 (UTC)

In terms of converting multimedia files to OGG, it may be worthwhile to have a look at media.py. Adding WebM support to that is easy. -- Daniel Mietchen - WiR/OS (talk) 23:02, 8 February 2013 (UTC)

For converting to .webm, I'll be calling w:FFmpeg in a subprocess from python. Daniel Mietchen's description above is fairly accurate as my bot is spidering and then uploading whatever info it can get...which isn't that much. The links to commons from the pedia pages are non-existent (it's a bug). I could add a custom description missing template and whatnot. So far, none of the files are being used...so I'm not sure if I should upload more files for Echopedia. I will post a note to WikiProject Medicine as to whether this upload is worthwhile.Smallman12q (talk) 22:37, 14 February 2013 (UTC)

I plan to go through the ECGs, add descriptions and than add many of them to the appropriate Wikipedia article. James Heilman, MD (talk) 01:37, 15 February 2013 (UTC)

I've uploaded ECHOpedia to Category:Media from CardioNetworks ECHOpedia. I could do animated gifs for the videos, but most would fall in the 25-30 million total pixel range and currently only less those with 25 million will be rendered.Smallman12q (talk) 17:19, 18 February 2013 (UTC)
Upload videos as videos. It makes no sense to convert them into animated GIFs nowadays. --Dschwen (talk) 22:20, 18 February 2013 (UTC)
Thumbnail not animated

The videos are 1-2 second clips. Here's what a gif version would look like.Smallman12q (talk) 22:39, 18 February 2013 (UTC)

Five times the file size, conversion loss, and no apparent advantage. Why on earth would you convert to anmated GIF?! --Dschwen (talk) 23:33, 18 February 2013 (UTC)
Gifs may be easier to use in some places and can loop by default. Anyhow, it's probably not worthwhile. PCIpedia is up next...it's ~200 files.Smallman12q (talk) 01:06, 19 February 2013 (UTC)

Smallbot (talk · contribs)

Operator: Smallman12q (talkcontribsrecent activitycountblock logrights logupload logSUL)

Bot's tasks for which permission is being sought: To upload the NOAA Office of Response and Restoration Photo Collection. 4000 files of high-res JPG and PCD. I plan to convert PCD to 2048*3072 JPG for upload.

See User:Smallbot/source/NOAA Office of Response and Restoration Photo Collection for more details.

Automatic or manually assisted: Automatic

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

Maximum edit rate (eg edits per minute): 5-10 (depends on upload speed)

Bot flag requested: (Y/N): N

Programming language(s): VBScript (Javascript, XMLHTTP, MSHTML, XMLDOM, COM).

Source: User:Smallbot/source/NOAA Office of Response and Restoration Photo Collection

Smallman12q (talk) 22:52, 21 November 2012 (UTC)

Discussion

The extracted metadata is limited the galleries 1,2, and 3. (See the xml files of User:Smallbot/source/NOAA Office of Response and Restoration Photo Collection). I'm not sure how to name the files where there is no metadata.Smallman12q (talk) 22:52, 21 November 2012 (UTC)

Can you give examples of how the file names will be constructed, and can you point us to an example of missing metadata? --Dschwen (talk) 08:02, 24 November 2012 (UTC)
I've posted a table here. Some of the items have no description, some have a vague description ("??Oregon somwhere"), some have conflicting descriptions ("Roebling Steel, Roebling, NJ 4/4/90 Water treatment facility located on the banks of the Delaware River." and "Roebling Steel, Roebling, NY 4/4/90 Water treatment facility located on the banks of the Delaware River.") Should I upload with multiple descriptions?
Some are very good. From gallery 4, they follow this pattern: <incident>, <place>, <State>, <Date>. <Description>. such as "Powell Duffryn chemical storage tank incident, Savannah, Georgia, April 1995. Data from a berm chracterization overhead used during the Powell Duffryn incident."Smallman12q (talk) 20:05, 24 November 2012 (UTC)
I suggest the bot includes all descriptions, and humans can work out which one is true. It looks like the directory structure has some info when there is no description. So how do you propose to construct filenames? --99of9 (talk) 11:39, 3 December 2012 (UTC)

┌─────────────────────────────────┘
Gallery 4 is the most complete. I've created a table here. I'll take the first 230 characters of the description as the filename.Smallman12q (talk) 02:45, 11 December 2012 (UTC)

I'm happy to approve the gallery 4 upload. For the others, especially those without descriptions, I'd like to see an example of the proposed filenames before upload. --99of9 (talk) 11:29, 7 March 2013 (UTC)

タチコマ robot (talk · contribs)

Operator: とある白い猫 (talkcontribsrecent activitycountblock logrights logupload logSUL)

Bot's tasks for which permission is being sought: Bot will tag featured pictures from other wikis (main concern is ar.wikipedia) using {{Assessments}}.

Automatic or manually assisted: Automatic, unsupervised after the generation of the list of pages to be edited.

Edit type (e.g. Continuous, daily, one time run): infrequent runs to tag new promotions/demotions

Maximum edit rate (eg edits per minute): 60

Programming language(s): AWB, bot already has a flag

-- とある白い猫 ちぃ? 07:36, 24 September 2012 (UTC)

Discussion

  • Please make a test run. --EugeneZelenko (talk) 14:55, 24 September 2012 (UTC)
    • Certainly. -- とある白い猫 ちぃ? 14:31, 6 October 2012 (UTC)
      • It seems like someone has already manually tagged the images. I can demonstrate with another wiki if you approve. -- とある白い猫 ちぃ? 15:06, 6 October 2012 (UTC)
        • A small test run from any wiki would help us to evaluate this. --99of9 (talk) 03:55, 11 October 2012 (UTC)
  • I don't quite understand this request. Is this about extending the scope of a previously approved bot request? For the description it sounds like this is a small one time task. Does this warrant a request? --Dschwen (talk) 15:23, 2 November 2012 (UTC)
    • I doubt it would be one-time, since other wikis are going to be periodically featuring pictures and not marking them here. But it does seem like it would be infrequent. – Philosopher Let us reason together. 12:41, 1 December 2012 (UTC)
      • @Dschwen: It's quite common sense that small one time tasks (or small few times task) don't warrant a request, and I think such request basically give more work to bureaucrats, who have already a lot of work - judging by this page. Anyway, as far as I can see, bot policy is very strict about bots running without requesting, and there are no written exceptions in policy. IMO, providing some clear exceptions for low volume tasks would benefit bureaucrats, bot users and the project.--Pere prlpz (talk) 16:05, 11 December 2012 (UTC)
  • Four months and still no report of a test run. I will close this as stale within the next few days. --Dschwen (talk) 17:19, 27 February 2013 (UTC)
    • What exactly am I supposed to test? I am merely trying to understand the nature you want me to run. How many edits would be sufficient? My plan is to grab a category off a wiki that has featured pictures and use a regex to apply it to the assessments template (or add the template if it isn't present). -- とある白い猫 ちぃ? 23:58, 2 April 2013 (UTC)
      • 30-50 edits per step III of Commons:Bots/Requests. --99of9 (talk) 00:08, 3 April 2013 (UTC)
        • I might not be able to generate 30 edits due to people manually tagging which is why I was asking. I am processing all 3,345 files from and hopefully I have enough to reach that mark. -- とある白い猫 ちぃ? 16:08, 6 April 2013 (UTC)
          • Yeah I only have 17 edits (edit summary: "adding enwiki fa assessment, replaced: {{Assessments| → {{Assessments|enwiki=1|)"). It is a simple regex in AWB. Is this sufficient? -- とある白い猫 ちぃ? 19:09, 6 April 2013 (UTC)
  • Also, please note that 60 edits per minute is much higher than the normal maximum. --99of9 (talk) 00:09, 3 April 2013 (UTC)
    • This has been discussed before. Is there any reason why we have to worry about such an arbitrary number bot operators disregard? It artificially creates a massive backlog as 1000 edits would take 16.66 hours to complete. I have placed a remark on the talk page of the policy to avoid duplication. -- とある白い猫 ちぃ? 15:30, 6 April 2013 (UTC)
1000 edits would take 100 minutes with recommended maximum bot speed. I think that is a reasonable speed fot this kind of task. Bots can make errors and if they do they should not do it at to high speed. This bot needs to be fixed so that it links to correctly named nomination pages at English Wikipedia, like this. It also needs to make sure that the pictures it tags really are featured pictures, eg File:Eastern Screech Owl.jpg does not seem to ever have been featured and File:Ebony Bones backup performer.jpg seems to have been delisted as featured picture. /Ö 19:59, 6 April 2013 (UTC)
FA Page ghosts on en.wikipedia
  Eastern_Screech_Owl.jpg
  Ebony Bones-01.jpg
Linking to nomination pages is a later issue. Not all of them are marked on en.wikipedia or on commons and crawling for them is a non-trivial task. That is a future task I hope to tackle.
The idea is also to sync enwiki (and other wikis) delistings with commons. The bot has no way of verifying if a file is actually featured or if it tagged without even being nominated. It can however check if files are in the en:Category:Featured pictures or not. The two mentioned files were in the category or at least en.wikipedia reported them as such (Eastern_Screech_Owl.jpg doesn't exist as a page on en.wikipedia despite appearing on category, Ebony Bones-01.jpg is a redirect on en.wikipedia to Ebony Bones backup performer.jpg which is the matching image which again shouldn't appear on category). On my second sweep I'd run a similar regex to en:Category:Wikipedia former featured pictures. Also not everything is nicely marked so catching problematic images is again a future development task.
The restriction is no faster than 1 edit/10sec according to the linked policy page. Simple math is 10sec*1000=10,000secs, 10,000/60=166.66... minutes, 166.66.../60=2.77... hours, provided bot does not spend any time doing anything. I do not want to add a 10 second counter between edits which would serve no purpose than waste my time. I do not see the point of a speed limit for bots. It was thrown in as an idea that servers couldn't handle such speeds. Developers disagreed and did not see a problem. The quicker the bot edits the better as edits would be rolled out quicker. That way I can change the parameters to work on the next wiki. This script would probably check for about 20 wikis that have featured pictures - of which most don't have that many files or new files. This task would take probably no more than 20 edits per month after the initial run. I do not believe the speed limit is based on consensus mind you. Let's discuss bot speeds on Commons talk:Bots as its a more general question if this is worth tracking and enforcing.
-- とある白い猫 ちぃ? 02:36, 7 April 2013 (UTC)
Please notify me on my talk page if there are any developments here. I cannot watch a page forever. :/ -- とある白い猫 ちぃ? 22:56, 20 April 2013 (UTC)
↑Jump back a section

Requests for comment

Centralized discussion

Please help by translating these messages into other languages.
Note: inactive discussions, closed or not, should be archived.
Archive  • Discussion • Edit • Page history • Watch
↑Jump back a section

Read in another language

This page is available in 1 language

Last modified on 22 November 2011, at 17:47