Commons:İdareberi

From Wikimedia Commons, the free media repository
Jump to: navigation, search
Administrators as of February 2016 [+/−]
Listing by language
Listing by date
Listing by activity

Number of Admins: 252

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

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


Requests for adminship[edit]

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.

Shortcut
COM:VOTE
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 Commons[edit]

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

How to comment and vote[edit]

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

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

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

Requests for Oversight rights[edit]

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

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

No current requests.

Requests for CheckUser rights[edit]

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

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

No current requests.

Requests for bureaucratship[edit]

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

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

No current requests.

Requests for adminship[edit]

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

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

No current requests.


Requests for license reviewer rights[edit]


Requests for permission to run a bot[edit]

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

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

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

Mu301Bot (talk · contribs)[edit]

Operator: Mu301 (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:

  1. Batch upload images and maintenance of file descriptive info and categorization of files on behalf of:
    1. Institution:Brown University Library such as historic photos that are {{PD-old}} for example the images at the Ladd Observatory Blog
    2. Institution:Ladd Observatory such as the examples at Commons:Ladd Observatory
    3. Institution:Retro-Computing Society of Rhode Island such as the examples at Commons:Retro-Computing Society of Rhode Island
  2. Upload of dynamic content for learning resources at Wikiversity which could be of interest to the larger Wikimedia community. See File:Mu301test.jpg, for example.

Automatic or manually assisted:

Mostly supervised and manually assisted. Automatic unsupervised operation for routine maintenance of file descriptions only or for special astronomical events which I will alert the community about ahead of time.

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

Uploads are mostly one time run. Maintenance of file descriptors as needed.

Exceptions are events where the bot would upload a new image version per community approved schedule. Currently updating File:Mu301test.jpg once per day. For special events (ie. w:Transit of Mercury or a lunar eclipse) a new revision of an image would be uploaded every 5 min. for about 12 hours or less.

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

Will not exceed standard pywikipedia put throttle and use maxlag. Typically put throttle is 60 or 20.

Bot flag requested: (Y/N):

Y

Programming language(s):

Manual:Pywikipediabot

--Mu301 (talk) 02:07, 9 February 2016 (UTC)

Discussion[edit]

@EugeneZelenko: Special:Contributions/Mu301Bot --Mu301 (talk) 18:38, 11 February 2016 (UTC)
Institution/author updates look OK for me.
Please use edit summary like MediaWiki:HotCat.js for category changes.
Please make test uploads.
EugeneZelenko (talk) 15:15, 12 February 2016 (UTC)

RileyBot (talk · contribs) 8[edit]

Operator: Riley Huntley (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: Commons:Village_pump/Archive/2015/06#Request shows consensus for removal of "uploaded by" in the file namespace, as it has caused confusion in the past. I am requesting openended removal of "Uploaded by" and similiar phrases that fall within the same scope. As shown here, McZusatz was doing this job with YaCBot. However, his bot is no longer running the task nor was it approved. I am looking to run it openendly for all uploaders, in order to ensure that external re-users of Commons content are able to attribute Commons materials inline with the stated licences. I have gone ahead and done a trial run of 20 edits.

Automatic or manually assisted: Automatic

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

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

Bot flag requested: (Y/N): No

Programming language(s): Pywikipediabot

Riley Huntley (talk) 19:53, 6 February 2016 (UTC)

If there is consensus to do so the function schould be enabled again in YaCBot. YaCBot is also doing a lot of other stuff (cleanup tasks). Can your bot do the cleanup stuff as well? --Steinsplitter (talk) 20:46, 6 February 2016 (UTC)
So the bot that runs the task without seeking approval, would get to continue the task after I get it approved for them? Not sure what I think about that. In any case, yes, my bot can do cleanup stuff as well. Riley Huntley (talk) 20:55, 6 February 2016 (UTC)
YaCBot is approved for doing cleanup tasks (bot operators are not expected to re-apply every time they want to implement a small alteration). Commons sense schould be used. I see no problem if your bot does that task as well, there are ten thousands of affected pages. --Steinsplitter (talk) 21:11, 6 February 2016 (UTC)
Thanks for the explanation. Riley Huntley (talk) 22:10, 6 February 2016 (UTC)
@McZusatz: --Steinsplitter (talk) 21:16, 6 February 2016 (UTC)
Related discussions about YaCBot on this task: Commons:Village_pump/Archive/2015/07#Redundant, Commons:Bots/Requests/YaCBot_(confirmation), Commons:Administrators'_noticeboard/Archive_54#YaCBot. Simply removing the tags may raise the same controversy as in the first discussion. --Zhuyifei1999 (talk) 21:21, 6 February 2016 (UTC)
I missed those, thanks for linking them. I am more than willing to do the same as layed out in Commons:Bots/Requests/YaCBot (confirmation) as well as offering opt out of the user categories. Riley Huntley (talk) 22:10, 6 February 2016 (UTC)
I am ok if this task is done by a separate bot. You could even keep your current bot logic and do it without the opt-out (instead ask about opt-in to removal by the uploader on their talk page to avoid controversy). I know that russavia opted in to the removal, so you already got quite a batch of files. --McZusatz (talk) 21:51, 7 February 2016 (UTC)
Opt in it is! Riley Huntley (talk) 02:40, 8 February 2016 (UTC)
I am happy to see a more cautious opt-in approach, which was missed in the YaCBot run. It would probably worth getting a more public consensus so that any account has been inactive for a long period, such as no edits for more than 2 years, could be asked to opt-out if they care. Fiddling about with user categories by bot, will remain controversial. -- (talk) 08:28, 9 February 2016 (UTC)
Public consensus will be gathered if/when it gets to that point. :) Riley Huntley (talk) 10:02, 10 February 2016 (UTC)

If there are no objections, I think task should be approved. @Krd: and @EugeneZelenko: Riley Huntley (talk) 10:02, 10 February 2016 (UTC)

@Krd: and @EugeneZelenko: - Pinging again. Riley Huntley (talk) 03:20, 13 February 2016 (UTC)

De-flag[edit]

Following the first, second and third bot de-flagging run, an analysis of bot activity has been performed, and provided a list of bots without edits/actions in the last 2 years.

While we do not have a local bot de-flagging policy as of yet, this follows the precedent set in the first three deflagging runs, where we tentatively agreed to remove bot flags from accounts unused for a period as significant as two years.

As is the case with inactivity run for sysops, each and every owner of this request will be informed by posting a message on their talk page and sending them an e-mail.

To do[edit]

  • Create list & start request: ✓ Done
  • Notify users via talk: ✓ Done
  • Notify operators via mail: ✓ Done
    Accounts with E-Mail function disabled: Cactus26, Docu, Stefan2, Wizzard, Marc
  • Deflag accounts: Time2wait.svg 

Affected bots[edit]

The following accounts are flagged as bots and have been inactive for more than two years:

Username Owner Last edit Current status
SieBot (talk · contributions · user rights management) Siebrand 20140105 Hourglass 2.svg
LivingBot (talk · contributions · user rights management) Jarry1250 20140104 Hourglass 2.svg
SDrewthbot (talk · contributions · user rights management) billinghurst 20140102 ✓ Flag removed
SamatBot (talk · contributions · user rights management) Samat 20131218 Hourglass 2.svg
GerWsUpload (talk · contributions · user rights management) joergens.mi 20131217 Hourglass 2.svg User request, flag should stay, new uploads will come --Jörgens.Mi Talk 20:16, 1 February 2016 (UTC)
CactusBot (talk · contributions · user rights management) Cactus26 20131216 Hourglass 2.svg
File Upload Bot (Kaldari) (talk · contributions · user rights management) Kaldari 20131203 Hourglass 2.svg
AvocatoBot (talk · contributions · user rights management) Avocato 20131125 Hourglass 2.svg
InductiveBot (talk · contributions · user rights management) Inductiveload 20131124 Hourglass 2.svg
BotMyShinyMetalAss (talk · contributions · user rights management) Pleclown 20131119 Hourglass 2.svg
Olafbot (talk · contributions · user rights management) Olaf 20131115 Hourglass 2.svg
Legobot (talk · contributions · user rights management) Legoktm 20131114 Hourglass 2.svg
RKBot (talk · contributions · user rights management) Reinhard Kraasch 20131112 Hourglass 2.svg
NordiskaMuseetBot (talk · contributions · user rights management) Prolineserver 20131107 Hourglass 2.svg
Gabrielchihonglee-Bot (talk · contributions · user rights management) Gabrielchihonglee 20131028 Hourglass 2.svg
WillieBot (talk · contributions · user rights management) Mono 20131026 Hourglass 2.svg
BotMultichillT (talk · contributions · user rights management) Multichill 20130921 Hourglass 2.svg
SLQbot (talk · contributions · user rights management) John Vandenberg 20130918 Hourglass 2.svg
Nikbot (talk · contributions · user rights management) Filnik 20130830 Hourglass 2.svg
ArthurBot (talk · contributions · user rights management) Mercy 20130820 Hourglass 2.svg
O (bot) (talk · contributions · user rights management) O 20130816 Hourglass 2.svg
MerlIwBot (talk · contributions · user rights management) Merlissimo 20130809 Hourglass 2.svg
Rybecbot (talk · contributions · user rights management) Rybec 20130714 Hourglass 2.svg
TronaBot (talk · contributions · user rights management) Coet 20130703 Hourglass 2.svg
Xqbot (talk · contributions · user rights management) Xqt 20130521 Hourglass 2.svg
Smallbot (talk · contributions · user rights management) Smallman12q 20130510 Hourglass 2.svg
RileyBot (talk · contributions · user rights management) Riley Huntley 20130328  User requested that flag be kept
Aibot (talk · contributions · user rights management) A1 20130307 Hourglass 2.svg
Category-bot (talk · contributions · user rights management) Docu 20130302 Hourglass 2.svg
Sz-iwbot (talk · contributions · user rights management) Shizhao 20130204 Hourglass 2.svg
Stefan2bot (talk · contributions · user rights management) Stefan2 20130130 ✓ Flag removed
Wizzo-Bot (talk · contributions · user rights management) Wizzard 20121210 Hourglass 2.svg
File Upload Bot (Vonvikken) (talk · contributions · user rights management) Vonvikken 20121107 Hourglass 2.svg
РобоСтася (talk · contributions · user rights management) Lvova 20121024 Hourglass 2.svg
AusTerrapinBotEdits (talk · contributions · user rights management) AusTerrapin 20120721 Hourglass 2.svg
FotothekBot (talk · contributions · user rights management) Multichill 20120626 Hourglass 2.svg
ElCarbot (talk · contributions · user rights management) El Caro 20120609 Hourglass 2.svg
MarcBot~commonswiki (talk · contributions · user rights management) Marc 20120418 Hourglass 2.svg
GeographBot (talk · contributions · user rights management) Multichill 20110314 Hourglass 2.svg
MultichillAWB (talk · contributions · user rights management) Multichill 20090906 Hourglass 2.svg
File Upload Bot (Omnedon) (talk · contributions · user rights management) Omnedon 20090605 Hourglass 2.svg

No reaction since last run[edit]

Operators of following bots haven't replied in the request (Hourglass 2.svg) in the last run:

Discussion[edit]

What is the point of this? It seems like it's just a waste of people's time. Yes, I am in fact planning on using my bot account in the near future to do a mass upload from the Folger Shakespeare Library. But I don't get GLAM contributions every year. Who does? Frankly I find it sad that volunteers are having to spend time justifying their bots flags instead of doing more productive work. What is the danger of someone having a bot that is inactive for more than 2 years? What problems has this actually caused? It seems like it is just red tape and bureaucracy that will drive away volunteers. Sorry for posting such a rant, but I really don't understand the purpose of this. Kaldari (talk) 17:58, 28 January 2016 (UTC)

I also plan on using my bot in the near future again. Tasks, usually mass typo-corrections, come in irregularly, and as long as bot operators are actually competent enough to not destroy the project there should not be any need to deflag. As far as I know we haven't needed strict "policing" per se, and when we do run into rogue bots, they get taken care of rather quickly and without much bureaucracy involved. --O ( • висчвын) 21:19, 28 January 2016 (GMT)
Same, it's convenient to have an already flagged bot for when someone has a request on IRC or some other medium. Legoktm (talk) 10:13, 29 January 2016 (UTC)

I agree with this process, and it is sad to see that my bot is inactive for more than two years now (time is running!). I plan to organize photo contests this year again, and I would like to use my bot for this activity. If you decide to deflag my bot, I will accept it, and I will request the flag later, when I need it again. Samat (talk) 19:16, 28 January 2016 (UTC)

  • I suggest that you remove the bot flag from Stefan2bot. The bot isn't currently editing on this project, and I assume that the flag will be re-added should I ever submit a new bot request. I currently only need a bot flag on enwiki, but not here. --Stefan2 (talk) 16:45, 30 January 2016 (UTC)
    • Thanks for letting us know about this, @Stefan. Do feel free to apply for the flag again when the need arises. odder (talk) 19:10, 30 January 2016 (UTC)

Yah, more red tape to drive active contributors away. User:BotMultichillT is my labs version of User:BotMultichill so I would like to keep that around. For the other accounts, if you want to make sure I never use them again, sure, deflag them. Multichill (talk) 21:40, 2 February 2016 (UTC)

I gave some positive feedback on COM:BN for the way deflagging of old accounts was being handled. To be honest if you have odd accounts that you leave unused for over 2 years, you may want to rationalize them a little bit, or at least refresh their descriptions before you start operating them again. I would hope that 'crats will reflag bots with a good history, just by the operator informally asking for the flag at BN or similar and not have to jump through hoops of filling out bureaucratic requests. Perhaps someone that does this sort of reflagging could confirm here that the process will be this simple? @Odder: as the most likely respondent. -- (talk) 16:59, 4 February 2016 (UTC)

Commented there. In short: yes, if reasonable and possible per policy. --Krd 18:08, 4 February 2016 (UTC)
Good to hear, sounds like a friendly way of handling flags. -- (talk) 18:53, 4 February 2016 (UTC)
Thanks for bringing this up, @. As you might have noticed, our process of approving bot requests has gotten faster and simpler over the past few years, and in particular over the last year or so, thanks to the continued involvement of Eugene and Krd. So while new bot operators already have an easier time getting their tasks approved and their bots flagged, I see no real need to have proven and trusted bot operators to go through this — albeit simplified — process again. I think that a simple request on the bureaucrats' noticeboard would generally suffice to re-flag an unused bot unless there are obvious reasons not to do so (ie. original flag was lost „under the cloud“). We have in the past accepted returning administrators after a 48-hour period for feedback, and I think we could use the same period for returning bots without much hindrance. P.S. For documentation purposes, let's just make sure that such requests are always submitted to the bureaucrats' noticeboard rather than a user's talk page or via private e-mail or any other medium. odder (talk) 20:06, 4 February 2016 (UTC)
  • SQLbot hasnt finished its task, however the remaining uploads are much harder to process requiring more software enhancements. John Vandenberg (chat) 00:35, 8 February 2016 (UTC)

Requests for comment[edit]

Centralized discussion

Template: View • Discuss • Edit • Watch