Last modified on 22 November 2011, at 17:50

Commons:Administratorët

Në gjuhët tjera :

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

Commons Administrator.svg

Të drejtat e administrimit ju jepen përdoruesve të besuar, që në projektin Commons si dhe në projektet tjera kanë dëshmuar se i njohin dhe respektojnë rregullat në fuqi të projektit Wikimedia Commons. Në asnjë mënyrë nuk do të thotë kjo se administratorët mund të vendosin për projektin.


Tani për tani vlen kjo rregullore për administratorët.

Administratori është një përdoruesi i besueshëm që ka këto të drejta:

  • Mbrojtjen e faqeve të projektit nga redaktimi si dhe lirimin për redaktim të faqeve.
  • Grisjen e faqeve të projektit si dhe rivendosjen e faqes në projekt.
  • Grisjen e fotografive dhe skedave të tjera të bartura nga përdoruesit.
  • Bllokimin dhe çbllokimin e përdorimit të projektit nga përdoruesit.
  • Ndryshimin e parapamjes apo të faqeve të mbrojtura (p.sh.m.: ndryshimin e faqes kryesore)

Sejili nga ju ka mundësi të propozojë ndonjë përdorues si adminisrator, për këtë duhen pasur parasysh këto kritere:

  • Nuk jeni përdorues aq i ri në projektet Wikimedia. Keni qenë aktiv së paku dy muajt e fundit në projektin Commons dhe pranoni se i mbështetni qëllimet e projektit.
  • Keni një faqe personale dhe së paku keni ngarkuar 100 skeda (fotografi, tekste apo zë të regjistruar)
  • Keni punuar sipas rregullave themelore dhe keni respektuar votimet e përdoruesve të komunitetit në këtë projekt.
  • Përdoruesit e tjerë duhet t'ju pranojnë që ju do të jeni një administrator i zoti.

Përzgjedha zgjat zakonisht shtatë ditë. Të drejtat e administrimit lëshohen pasi të keni marrë së paku katër vota nga të cilat 75% duhet të jenë "PËR". Në rast të arritjes së 75% duhet njoftuar ndonjëri nga byrokratët për rezultatin, të cilin edhe do ta vlerësojnë.

Sipas rregullores së projektit "Meta për administratorë pasivë", e drejta previlegjeve mund të tërhiqet.

Vini Re!: Nuk është e thënë zotërimi i plotë i shkrimit të gjuhës angleze, edhe pse ai është i mirëpritur. Kryesorja është kontributi dhe aftësia e komunikimit me anë të së cilës arrihet fitimi i besushmërisë së komunitetit. Si do që të jetë, në pjesën e më poshtme për shkaqe teknike kërkesa bëhet në gjuhën angleze dhe shpjegimet e mëposhtme janë po në këtë gjuhë. Fat të mbarë!

Kërkesa për të drejtë administrimiEdit

Krijo një nën-faqe: Commons:Administrators/Requests and votes/Username me tekstin e mëposhtëm në gjuhën angleze:

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

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

===Votes===

dhe radhite në faqen: Administrators/Requests and votes.

Administrators as of July 2014 [+/−]
Listing by language
Listing by date

Number of Admins: 260

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

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

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!

How and where to apply for additional user rights on CommonsEdit

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

How to comment and voteEdit

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

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

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

Requests for adminshipEdit

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

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

MeisamEdit

Vote

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

Scheduled to end: 18:10, (UTC)

I would like to introduce to you Meisam. Meisam is an experienced contributor with more than 50.000 edits and he is an OTRS-agent so the tools would make his work easier. He is an image reviewer at Commons and an administrator at the Persian Wikipedia since 2009. He speaks some helpful languages, namely Azerbaijani and Persian. We don’t have many admins who speak those languages so his language skills would be a great complement to the current team of administrators.

He knows about copyright and he was even granted the admin tools at fa-wiki back in 2008 to deal with copyright violations. And he used to be a sysop at Wikidata as well. He is trusted and does his work well. He has been active at Commons for years but since April he became really active. He shows good skills when dealing with copyright violations, sock puppets etc.

In short, he would be a great administrator and he should be granted the tools since Commons would benefit from it for sure. Natuur12 (talk) 18:10, 29 July 2014 (UTC)

Thanks for the nomination and your trust in my abilities. I hope to be a help to Wikimedia Commons and all other projects benefiting from it. -- Meisam (talk) 18:16, 29 July 2014 (UTC)

VotesEdit

  • Symbol support vote.svg Support As nom. Natuur12 (talk) 18:11, 29 July 2014 (UTC)
  • Symbol support vote.svg Support per my suggestion ;-) Trijnsteltalk 18:17, 29 July 2014 (UTC)
  • Symbol support vote.svg Support Yann (talk) 18:17, 29 July 2014 (UTC)
  • Symbol support vote.svg Support trusted user --Steinsplitter (talk) 18:18, 29 July 2014 (UTC)
  • Symbol support vote.svg Support --Krd 18:19, 29 July 2014 (UTC)
  • Symbol support vote.svg Support trusted user and trusted nominator. Nick (talk) 18:32, 29 July 2014 (UTC)
  • Symbol support vote.svg Support Rzuwig 18:38, 29 July 2014 (UTC)
  • Symbol support vote.svg Support -FASTILY 19:06, 29 July 2014 (UTC)
  • Symbol support vote.svg Support unless you turn inactive like you did on Wikidata! Vogone (talk) 19:43, 29 July 2014 (UTC)
  • Symbol support vote.svg Support Alan (talk) 21:52, 29 July 2014 (UTC)
  • Symbol support vote.svg Support trusted user who will benefit from the tools. --Lewis Hulbert (talk) 22:26, 29 July 2014 (UTC)
  • Symbol support vote.svg Support trustworthy user with extra languages as a bonus.Green Giant (talk) 23:58, 29 July 2014 (UTC)
  • Symbol support vote.svg Support Right on! AZ and FA knowledge is an additional plus. --Hedwig in Washington (mail?) 00:20, 30 July 2014 (UTC)
  • Symbol support vote.svg Support - Magog the Ogre (talk) (contribs) 04:31, 30 July 2014 (UTC)
  • Symbol support vote.svg Support - JurgenNL (talk) 11:06, 30 July 2014 (UTC)
  • Symbol support vote.svg Support --Skeezix1000 (talk) 12:35, 30 July 2014 (UTC)
  • Symbol support vote.svg Support -- sats (talk) 14:37, 30 July 2014 (UTC)
  • Symbol support vote.svg Support - Azeri speaker admin is much nedded. Geagea (talk) 01:20, 31 July 2014 (UTC)
  • Symbol support vote.svg Support variation of administrators is a good thing. Hanay (talk) 09:38, 31 July 2014 (UTC)

CommentsEdit

Pictogram voting question.svg Question Hi, Meisam. I must ask an important question, because you are native speaker of Azerbaijan language. There is freedom of panorama in Armenia and no freedom of panorama in Azerbaijan. What about in Mountain Karabakh? Taivo (talk) 21:08, 30 July 2014 (UTC)

I'm not an expert in this matter. The copyright issue in the case of Nagorno-Karabakh is a bit complicated which mostly relies on the answer to his question: "which country's laws are applicable here?". The NKR affiliates to Azerbaijan under the principle of uti possidetis and is de jure a part of it as ex iniuria ius non oritur. (A detailed analysis can be found in "Heiko Krüger, The Nagorno-Karabakh Conflict - A Legal Analysis, Springer-Verlag, Berlin Heidelberg, 2010 ISBN 978-3-642-11787-9"). IMO it must follow the Azerbaijan's rules for FOP. But you should probably consult a lawyer! -- Meisam (talk) 22:20, 30 July 2014 (UTC)
Administrator of Commons must be an expert in copyright matters. We generally do not consult with lawyers, because we must be lawyers ourselves. Let's imagine, that a photo about Nagorno-Karabakh building is presented for deletion with reason "There is no freedom of panorama in Azerbaijan" and the uploader replies "There is freedom of panorama in Armenia". You have three possibilities: 1) close the request as deleted, 2) close the request as kept, 3) do not close the request and let the others to decide. Which one do you choose? Taivo (talk) 08:57, 31 July 2014 (UTC)
I won't close the request but add my own opinion as stated above to comments section, to rationalize the enforcement of Azerbaijan FOP laws. -- Meisam (talk) 09:44, 31 July 2014 (UTC)

Pictogram voting comment.svg Comment Please enable Prompt me when entering a blank edit summary in Special:Preferences. --EugeneZelenko (talk) 14:00, 31 July 2014 (UTC)

✓ Done Thanks for reminding. -- Meisam (talk) 15:47, 31 July 2014 (UTC)

Requests for bureaucratshipEdit

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

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

No current requests.

Requests for CheckUserEdit

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

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

No current requests.

Requests for Oversight rightsEdit

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

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

No current requests.


Requests for permission to run a botEdit

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

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

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

HiW-Bot (talk · contribs) (2)Edit

Operator: Hedwig in Washington (MAIL?)

Bot's tasks for which permission is being sought: Adding source, author, etc pp to information template. Replacing wrong licenses with accurate ones. Replacing categories.

Automatic or manually assisted: supervised and unsupervised, mostly supervised, some manual work as well. (e.g. manual edit needed before saving)

Edit type (e.g. Continuous, daily, one time run): As needed (depends on how many related files I find in Category:Images without source, which will be the main work area for now.

Maximum edit rate (eg edits per minute): 10/min (I think AWB throttles down to 10?) Less if prefered.

Bot flag requested: (Y/N): Y

Programming language(s): AWB

DiscussionEdit

Working on things like: Category:Electricity in Theory and Practice Where all/most files don't have a source. Example diff (via my main account using AWB). Sure, could been done by hand - this one category alone has 151 members. I'd really like to save myself the agony of having to click 151 times for this single category only. :) --Hedwig in Washington (mail?) 03:19, 27 July 2014 (UTC)

Will be good idea to perform test runs for different sets of images. Could you please make edit summaries more human reader friendly? --EugeneZelenko (talk) 14:01, 27 July 2014 (UTC)
The summary is auto created by AWB. Guess I should add my own again as I did here: File:Potop (1888) t.1.pdf.

The above categories are some examples of files where I removed the old google books template (the one with the license problem) and added a license. In order to do another set I have to find some in the no source pile, +50k. That might take a while. Is the older work sufficient? --Hedwig in Washington (mail?) 23:09, 27 July 2014 (UTC)

File:Serenata di Scappinu1.jpg is poetry, so {{PD-text}} should not be applied. --EugeneZelenko (talk) 14:13, 28 July 2014 (UTC)
✓OK {{PD-scan|PD-old-100}} and {{Book}} should have been used, my bad. I'll correct that in the next run. I plan of doing the book template after the source runs, some files have to be renamed to fit into a set and and and... There's a lot of additional work and research (source links, author, creator, ....) involved. By doing this in stages I'll have better control over what I am doing. :) --Hedwig in Washington (mail?) 16:01, 28 July 2014 (UTC)
Better summary: (Updating License, removing outdated Google books template) How do we proceed from here? :) --Hedwig in Washington (mail?) 03:43, 31 July 2014 (UTC)

LanguageScreenshotBot (talk · contribs)Edit

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

Bot's tasks for which permission is being sought: Uploading and editing the images uploaded by the bot.

Automatic or manually assisted: Manually Assisted

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

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

Bot flag requested: (Y/N): Y

Programming language(s): Ruby

LanguageScreenshotBot (talk) 07:43, 15 July 2014 (UTC)

DiscussionEdit

@Vikassy: 1500 edits/min is way way way too fast. May I suggest you read Commons:Bots#Bot_speed, and revise the request acordingly, especially if you don't have a bot flag? --Mdann52talk to me! 13:37, 15 July 2014 (UTC)
  • Initially we were uploading in parallel(as screenshots were taken in parallel). Hence the count came up to 1500 (as 30 screenshots in 50 languages [in future]). But now we modified it to run in serial, hence 1 upload every 5 seconds. --Vikas S Yaligar (talk)
    Bot uses categories like English (weird for File:VisualEditor Toolbar SpecialCharacters-de.png :-), but Category:VisualEditor has language-specific subcategories. Will be good idea to use them. --EugeneZelenko (talk) 14:07, 27 July 2014 (UTC)
    Thank you EugeneZelenko for this ! we have updated the code to use these subcategories. --Vikassy (talk) 13:21, 30 July 2014 (UTC)
    Please repeat test run. --EugeneZelenko (talk) 14:16, 30 July 2014 (UTC)
    How much files do you plan to upload in the next weeks/months/years? --Steinsplitter (talk) 15:37, 27 July 2014 (UTC)
    I don't know what Vikassy wants to do, but I can help you calculate the upper limit of what could be done: mw:Help:VisualEditor/User guide contains about 70 images, and most of them are language-specific. Translations have been started for about 80 languages. Therefore, if you tried to do absolutely everything, you might reasonably expect 5,600 images to start (maybe over the course of one month). After that, I would assume that updates are necessary as software changes are made, but that these changes will not involve all images. On the other hand, some images may change more than once. So you might expect another 5,000 images a year after that. Whatamidoing (WMF) (talk) 18:18, 28 July 2014 (UTC)
Thank you Whatamidoing (WMF) for the calculating :) . I want to deploy these images in order of different languages, currently we are working on 3 languages[en, he, de]. You can checkout all screenshots in commons beta lab. We are planning to upload these for now, as a part of experiment. Later we will upload more images depending on percentage completion of translation in different languages. So finally it should end up with numbers similar to what Whatamidoing (WMF) has calculated. --Vikassy (talk) 12:51, 31 July 2014 (UTC)

Mdann52 bot (talk · contribs)Edit

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

Bot's tasks for which permission is being sought: transferring PD images from certain categories to Commons (en:User:Sfan00 IMG/License tags)

Automatic or manually assisted: manual

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

Maximum edit rate (e.g. edits per minute): 1 or 2, to allow review and manual appending of information

Bot flag requested: (Y/N): Yes no

Programming language(s): uses w:en:WP:FTCG

--Mdann52talk to me! 19:12, 11 July 2014 (UTC)

DiscussionEdit

Test run done on my alt account (User:Mdann52(alt)). --Mdann52talk to me! 19:12, 11 July 2014 (UTC)
Pleas create a user page for your bot. --Steinsplitter (talk) 19:14, 11 July 2014 (UTC)
Imho you don't need botflag (there is no need to tag new uploads as +b) --Steinsplitter (talk) 19:15, 11 July 2014 (UTC)
User page for bot created (and alt account redirected). I though +b would stop flooding, but it appears not in the case of uploads. --Mdann52talk to me! 19:55, 11 July 2014 (UTC)
Who is reviewing images before transfer?
I noticed also separate description clean up edits. Could you combine clean up and upload?
EugeneZelenko (talk) 14:09, 12 July 2014 (UTC)
@EugeneZelenko: I generally try to clean up the code as much as possible when I move the files, however nothing is perfect (!), so sometimes there are a few minor formatting issues to clean up. In terms of reviewing, the files in the category are being reviewed by both human's and bots, and I am also manually checking to ensure any URAA/PD issues are cleaned up before I initiate the transfer, and nominating them for deletion on EN if there are any issues. --Mdann52talk to me! 15:33, 12 July 2014 (UTC)

SamoaBot 4 (talk · contribs)Edit

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

Bot's tasks for which permission is being sought: "condense" multiple {{assessments}}-like templates into single ones (example)

Automatic or manually assisted: automatic (after test run)

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

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

Bot flag requested: (Y/N): N

Programming language(s): Python, PWB

--Ricordisamoa 04:02, 6 July 2013 (UTC)

DiscussionEdit

  • Looks OK for me. --EugeneZelenko (talk) 14:24, 6 July 2013 (UTC)
  • Please can you initiate (or point to) a community discussion involving FPC/QIC/VIC noticeboards to confirm that they want this? --99of9 (talk) 11:00, 11 July 2013 (UTC)
    • Unnecessary clutter/fragmentation of the file description page is no option, not now and not in future. -- Rillke(q?) 08:05, 20 July 2013 (UTC)
@99of9: I'm a bit busy at the moment, could you please initiate (and point to) such community discussion? --Ricordisamoa 17:34, 17 August 2013 (UTC)
@99of9: where should the discussion take place? What are "FPC/QIC/VIC noticeboards"? --Ricordisamoa 03:55, 3 September 2013 (UTC)
Sorry I haven't got around to it either. Here is FPC talk, QIC talk, and VIC talk. Most of the regulars in those communities will have those pages watchlisted. --99of9 (talk) 05:45, 3 September 2013 (UTC)
I have sent them identical messages pointing to this page. --Ricordisamoa 07:55, 3 September 2013 (UTC)
  • Fine for me. — TintoMeches, 08:13, 3 September 2013 (UTC)
  • I endorse the objective of reducing page clutter by having assessment-like templates being shown together in a more consistent manner, and I understand the good intentions from the bot implementer to have a bot do that tedious task. I do have some serious reservations about the {{Assessments}} template itself as I find it adds visual clutter and confusion, especially when used for merging FP, QI and VI into the same template with its current implementation. My concerns are
    1. The visual appearance of the template is for me an eyesore when more than one type of assessment is used, see File:Acrocinus longimanus MHNT femelle.jpg for an example where, the template is used for both FP, QI and VI. There are three frames in different colours and inside the box three logos in different colors and styles. Yak! For the Valued image project we spend a lot of time originally in crafting a nice colour scheme for the frame and background colour, which very nicely matches the logo, on which much time was spend. These colours are a trademark of the individual projects and gives project assessment identity. By putting it all together in one monster templte with frames in frames, as has been done, the project identiity is lost.
    2. The usage for VI is not 'approved' (nor documented) and I would object to using it for VI. For instance the Assessment template does not (as far as I know) support the important scope parameter, which is in the {{Valued image}}, nor am I sure it categorizes the file page correctly as the Valued image template does or correctly supports the subpage parameter (when it deviates from the default).
    3. The implementation for the Assessments template is terribly complicated because it is trying to do way too many things at the same time. As a consequence it is very often broken (see the talk page and archives) for its long and troublesome history. It is only a few users here who can actually edit it and maintain it.
    4. Bots specific to the QI, VI and FP projects will continue to add the old templates. Thus this bot will have to run regularly to merge the templates. It should be checked with the other bot implementers that this merge does not influence any of their bot tasks in unforeseen manners.
    5. Although parameter names for the Assessment templates has improved, I find the 1, 3, etc. values in the template confusing and non-human readable.
  • Due to these concerns, and since there is not community consensus that an all-engulfing template is a better solution than the existing stand-alone templates, I cannot support this template merge as is. And I will revert any such changes made on photos I have uploaded. If there is a community consensus, that we really want to do the merge as suggested, I will respect that (very reluctantly).
  • That said, I also understand that the current situation with the stand-alone templates, placed randomly on the file page and in more or less random order is confusing and improvable. I am just not sure, that merging them into the Assessment monster is the right solution. I would much rather like to see some smart logic by which, when placed side by side in consistent order, the existing templates would render in a neater way, say in in three columns if FP, QI and VI (I do not know if this is technically possible). That would make template maintenance easier (like adding new languages), and it would be easier for the project-specific bots to add them and change them. Something like, when you place a {{Location}} template underneath an {{Information}} template you get a nice consistent view from which it appears when looking at the file page, that it is one integrated table, like here for example. I think a wider community discussion regarding this is needed to get some mockups on the table to understand what is possible in a way, where both a nice visual appearance with project identities are maintained, where the visual clutter is lowered, where it is easy to maintain the template code, and where changes to project-specific bots are minimal.
  • For now I can endorse having the bot order the templates consistently, e.g., first FP, then QI, then VI, under information and location info, but nothing more until a community consensus is achieved.

--Slaunger (talk) 19:12, 3 September 2013 (UTC)

  • I used to be sceptical about merging QI and VI into the Assessments template as well. I think condensation into a single template actually reduces clutter and presents a single compact box to the user. I think this is a usability improvement. I have no reservations about adding this functionality to the QICbot (and the VICbot). I've been playing with the excellent mwparserfromhell python module lately and using that module the task of adapting the bot should be super-easy. --Dschwen (talk) 21:09, 3 September 2013 (UTC)
    • I just had a look at mwparserfromhell. This looks like a most useful python module! So much easier to use than (arcane) regexes. --Slaunger (talk) 19:21, 4 September 2013 (UTC)
  • Furthermore if the current implementation of the template is considered an eyesore ;-) I would invest a little time in improving the template layout. The consolidation in wikitext space should be independent of that effort. Actually, the {{Assessments}} template could even be adapted to spit out an old style separate QI/VI box (although I think this would be counterproductive). --Dschwen (talk) 21:12, 3 September 2013 (UTC)
    • But it has to support the needed parameters before consolidating in wikitext such that no information is lost in the transition, and currently I do not think the template does - at least it is not documented. If consolidated, I agree it should not spit out separate QI/VI/FP frames exactly as the separate templates does now, but I think some middleground in the layout needs to be found, otherwise the increase in uglyness, outweighs the decrease in clutter IMO.
    • So you are not concerned about the continued maintenance of this monster template? I would much rather solve the issue with composition (make the overall template call the (possibly adapted) individual templates) instead of the current very complicated logic. Will be much easier to maintain. It is fine if you are willing to adapt two of the bots of course. Greatly appreciated. --Slaunger (talk) 21:23, 3 September 2013 (UTC)
      • This template could be made into a well documented easy to maintain LUA module :-). Any takers? Which template parameters are you worried about preserving? --Dschwen (talk) 22:49, 3 September 2013 (UTC) P.S.: Oh, while {{Quality image}} has no parameters the {{Valued image}} template does take a few. Yep, those should be conserved somehow. --Dschwen (talk) 22:51, 3 September 2013 (UTC)
        • I have never tried coding in Lua, but I had a look at it as used for Mediawiki templates. I looks like it has a low entry barrier. It reminds me very much of Python, which I am proficient in. So as a matter of fact I am tempted to 'take' that task of making a well-documented, easy to maintain and easy to test Lua template, with sensible and logical parameter names and values Smile. Considering how much I have been bitching about the assessments template I ought to take responsibility for improving Clin. However, it will take some time, as I need to understand a couple of things, like how to do internationalization in the best way, how to best structure the code, how to make sandbox mockup templates for testing and evaluation of different possibilities such that extensions with new languages and support for FP programs on different wikis can be done most easily. I need to understand what the possibilities are for making things look visually consistent, with minimum clutter and 718smiley.svg Awesome!. And most importantly, I will need to get consensus from the community about how this shall work, what shall be the scope of the template, by actually taking into account other users expectations and desires, unlike... I estimate this process will take the rest of the year 2013 given the limited spare time I have for this and the rigour with which I will approach this. If putting this bot on hold until then is acceptable, I will be happy to do that. --Slaunger (talk) 19:11, 4 September 2013 (UTC)
          • Alas User:Slaunger is on wikibreak. Would anyone else like to have a go at this? Otherwise I'm afraid we are not ready for this bot task. --99of9 (talk) 10:26, 13 January 2014 (UTC)
  • Interesting discussion, even if a bit too technical for me. As a "basic" user, I think that current templates are not so bad, but it looks sometimes very "random" on the file page (my choice should be: description, assessment templates, before license). I think that awarded pictures are not visible enough in "Commons". And I notice that if FP or VI pictures can be "delisted", it is not the case for QI (QI for one day, QI for ever), this should not been forgotten in case of a "merging" is decided (a template for "former FP" exists too...). No further opinion for the moment. Only my three cents.--Jebulon (talk) 13:53, 6 September 2013 (UTC)
  • @Ricordisamoa, @Slaunger, @99of9, @Dschwen: What's the state of this? Are we waiting for anything in particular, or can we push this request forwards (or else close as stale)? odder (talk) 19:33, 2 April 2014 (UTC)
  • Pictogram voting info.svg Bureaucrat note: I'm closing this request as stale given there have been no updates on it for more than two months, and no updates even though I pinged several people a week ago. odder (talk) 13:59, 9 April 2014 (UTC)

RestartEdit

  • Pictogram voting info.svg Bureaucrat note: I just heard back from @Ricordisamoa, so let's re-open this request and see where it'll get us. odder (talk) 18:51, 14 June 2014 (UTC)
    • Hello? odder (talk) 21:50, 25 June 2014 (UTC)

The bot could run on FPs that are also QIs, skipping VIs until {{Assessments}} supports them properly. Does anyone oppose simple mergers like that? --Ricordisamoa 00:09, 1 July 2014 (UTC)

That seems reasonable to me. --99of9 (talk) 01:43, 1 July 2014 (UTC)
Good; but there is an ongoing discussion on how to handle sets which may affect some previous cases too. Further, a change may be needed for {{Assessments}}. Jee 02:25, 1 July 2014 (UTC)

And what about the placement of {{Assessments}} within the page? If desired, the bot can adjust its position according to some policy/recommendation. --Ricordisamoa 15:22, 17 July 2014 (UTC)

I prefer it below {{Information}}. Some people prefer/move it above {{Information}}. I think it should be discouraged. Jee 15:55, 17 July 2014 (UTC)

MifterBot (talk · contribs)Edit

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

Bot's tasks for which permission is being sought: Check newly uploaded images to ensure they have a license tag. Reactivation of a former task Commons:Bots/Requests/MifterBot

Automatic or manually assisted: Automatic

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

Maximum edit rate (e.g. edits per minute): No more than 2 edits per minute (1 tag and 1 notification)

Bot flag requested: (Y/N): Yes, the script I used years ago broke around the same time I had a hardware failure so I stopped running the bot. Recently, I managed to get the script working again and resumed running my bot on the English Wikipedia here. It is the same script that I would use on commons.

Programming language(s): Python - A custom fork of pywikipedia

Mifter (talk) 13:53, 30 May 2014 (UTC)

DiscussionEdit

 Doing… Mifter (talk) 14:41, 30 May 2014 (UTC)
Bot only updates log page, but not files/user talk pages. Is it intended? --EugeneZelenko (talk) 14:24, 31 May 2014 (UTC)
It is intended to update the log when it encounters an unknown template. Once logged I can modify the script to whitelist or ignore the template. This process takes a little trial and error as the bot has to run to see what templates it encounters. All the templates on the log have been integrated to the script (over time the log is rarely used once all the major templates are integrated into the script only catching oddball entries and the like). The large amount of Template:Photograph showing on the log is due to a user accidentally uploading a huge amount of images without a license tag. The user is an established user and uploaded other images around these with license tags so I'm guessing it was an error. However that resulted in a large number of log entries. I whitelisted the template and did a limited run to ensure that it would tag images like this in the future. I then stopped it to prevent inundating the user's talk page. Best, Mifter (talk) 16:45, 31 May 2014 (UTC)
See File:«Півострів Меганом» Остоматій Ліна ID 01-117-5005.jpeg and File:The Golden House, Venice, Italy-LCCN2001701053.tif for two examples of correct tags (more are in contribs). Best, Mifter (talk) 16:57, 31 May 2014 (UTC)
Edits looking OK imho. --Steinsplitter (talk) 10:56, 3 June 2014 (UTC)
Is it possible to analyze user contributions completely (after detecting problematic file) before adding warnings on user page? Just to avoid clutter there. If I'm not mistaken, one of recent bots was modified for such algorithm. --EugeneZelenko (talk) 14:12, 3 June 2014 (UTC)
The way the script is written that currently isn't possible. I can look into adding it in the future however if a user uploads multiple untagged files they would need multiple notices so it would add quite a bit to the script to balance past contributions with notification needs. Best, Mifter (talk) 21:55, 3 June 2014 (UTC)
See Commons:Bots/Requests/YiFeiBot (13). Please collaborate with owner to improve your code. --EugeneZelenko (talk) 14:06, 4 June 2014 (UTC)
I've spent a lot of time looking through the request and then at all of the edits the bot has made in the user talk namespace but I'm not sure the solution proposed there would work in this case. Except in exceptional circumstances a user wouldn't be uploading large numbers of files within a single hour, I'm not sure if it would be feasible to write code into the bot to check previous warnings taking into how long ago they were issued, by whom, any intervening edits, etc. For such rare circumstances I would hazard that rollback or talk page section archiving/removal could be the best tool as the amount of time and effort needed to code for such an unlikely eventuality wouldn't be worth the returns. Best, Mifter (talk) 20:54, 5 June 2014 (UTC)
@Zhuyifei1999. Could you help, please? --EugeneZelenko (talk) 14:14, 6 June 2014 (UTC)
I'm not sure what the problem here. At least imo ~20 notifications in ~1 hour isn't a good idea. Perhaps the bot could group the files by uploaders and make only one notification per uploader in a single run. (My bot achieved that by multiple queries to the database.) --Zhuyifei1999 (talk) 14:54, 6 June 2014 (UTC)
Multiple warnings were my concern too. I think will be good idea to help requester to improve his bot code. --EugeneZelenko (talk) 14:12, 7 June 2014 (UTC)
  • Pictogram voting question.svg Question This bot request appears to be stuck at the moment. Is there anything that we can do here, as bureaucrats, that could help move it forwards? I notice that there are some problems with the number of notifications the bot is currently sending out to users, can this be improved? Thanks, odder (talk) 21:31, 25 June 2014 (UTC)
I've been exploring the possibility of adding a counter to the bot's code so it doesn't warn people more than X times, however have been extremely busy recently so haven't had the time to move forward with it. For what it is worth, I still am not convinced that too many warnings is really an issue. If a user uploads files without a license they need to know about it, and I am not sure that the technical work required to add a counter is worth the small number of users it would effect. I've been running the bot on the English Wikipedia for a while (see en:special:contributions/MifterBot) and ran an older version of the bot here on Commons in 2008 (see Commons:Bots/Requests/MifterBot) and while the bot does issue multiple warnings where necessary it has only given out a large number of warnings a few times out of thousands of edits (and many of those multiple warnings were over a period of time as a user continued to upload untagged images). The reason that it issued numerous warnings to Fae in a short period of time was because she was uploading hundreds of files with a broken template (that was not a license) and as it found them it tagged and warned her. From my experience most new users don't blindly upload tens or hundreds of images without a tag in such a short period of time as that they would cause the bot to tag a huge number of files and issue a huge number of warnings, most would be blocked fairly quickly and even if there were a number of warnings, removing them is as simple as removing any other talk page message. I would like to run the bot a bit more to see how it performs without the outlier of Fae's images and to gather data on how likely a user is to upload numerous untagged files. Best, Mifter (talk) 13:02, 28 June 2014 (UTC)

CommonsMaintenanceBot (talk · contribs)Edit

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

Bot's tasks for which permission is being sought:

Task Status Test edit Approved
Archiving pages like Commons:Deletion requests/mobile tracking  running Special:Diff/126830384, Special:Diff/126839875 Bureaucrat's name here
Removing expired messages from MediaWiki:WatchlistNotice (needs sysop flag) ✓ implemented Special:Diff/126839605 odder (talk)
Watching recent changes of MediaWiki JavaScript pages, running JSHint over the old revision and the new revision. Reverting to old revision if more issues appear in the new revisionperhaps not for now and generally notifying the editing user about issues, except they opted out; writing full report to a subpage of Commons User scripts (MediaWiki pages go to the message cache) and maintaining a table of scripts and their JSHint and esprima status (needs sysop flag for deleting obsolete error reports of scripts that are valid)  running reports, user notification odder (talk)
Watching recent changes in user namespace and for JavaScript pages, run esprima, jshint; for CSS run PrettyCSS (which comes with a validator) over the new revisions. If issues are found, they are reported to the user.  running user notification Bureaucrat's name here
Watching recent changes of MediaWiki CSS pages, running a CSS validator over it and doing the same as done with JSHint, except reverting.  running reports, report page, user notification Bureaucrat's name here
Possibly taking over Undeletion Request archiving if we decide to create one subpage per request needs discussion Status Testedit Bureaucrat's name here
Possibly deleting files (considering all the points requested there) needs implementation Status Testedit Bureaucrat's name here
Watching recent changes of Lua pages, running a Lua linter over it and doing the same as done with JSHint, except reverting. Status Testedit Bureaucrat's name here
Updating data source for MediaWiki:Gadget-markAdmins.js (this should actually go to MediaWiki:Gadget-markAdmin-data.js) (needs sysop flag).  running page Bureaucrat's name here
Task Status Testedit Bureaucrat's name here

Automatic or manually assisted: Automatic, running on wmf-labs.

Edit type (e.g. Continuous, daily, one time run): Archiving Commons:Deletion_requests/mobile_tracking: Once per week

Maximum edit rate (e.g. edits per minute): No throttle, just following mw:API:Etiquette. Sheduled by xcrontab, job submitted to grid engine.

Bot flag requested: (Y/N): Y

Sysop flag requested (administrator status): (Y/N): Y

Programming language(s): JavaScript. Running on Node.js - source code available on GitHub (On labs: /data/project/commons-maintenance-bot/)

Rillke(q?) 14:42, 14 April 2014 (UTC)

DiscussionEdit

  • Please make a test run for each task. --EugeneZelenko (talk) 14:11, 15 April 2014 (UTC)
    • @Rillke: Are there any updates on the state of this request? Specifically, did you make test runs for all tasks listed above? Thanks! odder (talk) 14:53, 13 June 2014 (UTC)
      • Sounds like a task for tonight. -- Rillke(q?) 18:06, 13 June 2014 (UTC)
  • Pictogram voting question.svg Question Can you provide some more examples for the verification of CSS pages so I can have a deeper look at it? Thanks :-) odder (talk) 21:28, 25 June 2014 (UTC)
    • Are you out for specific pages? Then just edit them :) The bot stalks the recent changes so feel free to vandalize MediaWiki:Test.css or any other CSS page in the MW namespace after creating it with good content. -- Rillke(q?) 23:19, 25 June 2014 (UTC)
  • @Jarekt, Zolo, Odder: Would a Linter for Lua be something worth consideration? The bot is running and filling Tool Labs with 900 MiB of RAM anyway. (Python needs 300 MiB less but I don't like it.) -- Rillke(q?) 23:23, 25 June 2014 (UTC)
    • @Rillke: If you want to implement a linter for Lua scripts, then it's just fine with me :-) odder (talk) 14:45, 1 July 2014 (UTC)

Requests for commentEdit

Centralized discussion

See also Commons:Village pump/Proposals

Please help by translating these messages into other languages.

Note: inactive discussions, closed or not, should be archived.

Archive  • Discussion • Edit • Page history • Watch