Commons:Administrador

From Wikimedia Commons, the free media repository
Jump to: navigation, search
A página de projecto Administrador noutras línguas:

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

Shortcuts
COM:A
COM:ADMIN
Commons Administrator.svg

Esta página apresenta a informação essencial sobre os administradores do Wikimedia Commons, contendo também as votações de pedidos para administradores, burocratas, verificadores de IP e oversight. São também aqui tratados os pedidos de estatuto de bot.

Se você necessita da ajuda de algum administrador, por favor dirija-se a Commons:Administrators' noticeboard.

O que são administradores?[edit]

O direito de administrador (sysop) é outorgado aos membros da comunidade que são conhecidos, respeitados, dignos de confiança e que são conhecedores das regras sobre o Commons. O administrador não tem nenhuma autoridade editorial superior a qualquer outro usuário.

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

Number of Admins: 247

  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. AFBorchert, de, en-3 (bureaucrat)
  7. Ahonc, uk, ru-4, en-2, de-1
  8. Aka, de, en-3
  9. Alan, es, eu-3, en-2
  10. Alhen, es, 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 (steward)
  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. Ciell, nl, en-2, de-1
  41. Cirt, en, es-2
  42. Common Good, en
  43. Cookie, es, en-2
  44. Courcelles, en, es-2, fr-2
  45. Coyau, fr, en-1
  46. DaB., de, en-1
  47. Dantadd, it, pt, en-3, es-3, fr-3, gl-3, ca-2, ro-1, el-1
  48. Darwinius, pt, en-3, es-2, fr-2, gl-2, ca-1, it-1, oc-1
  49. Davepape, en
  50. David Levy, en
  51. Denniss, de, en-2, fr-1
  52. Dereckson, fr, en-3, de-1, nl-1
  53. DerHexer, de, en-3, grc-3, la-3, es-1 (steward)
  54. Dharmadhyaksha, mr, en-3, hi-3
  55. Didym, de, en-2, fr-2
  56. D-Kuru, de, en-2, it-1
  57. Dschwen, de, en-3, fr-1 (bureaucrat)
  58. Ebraminio, fa
  59. Edgar181, en, de-1, fr-1, es-1
  60. Elcobbola en, de (checkuser)
  61. Elitre, it, en-3, fr-2
  62. Ellin Beltz, en (bureaucrat)
  63. Elya, de, en-3, uk-2, ru-1
  64. Emha, de, bar, en-3, fr-1
  65. EPO, da, en-3, de-1
  66. Érico Júnior Wouters, pt, en-2, es-1
  67. Esby, fr, en-3, de-1
  68. EugeneZelenko, ru, be, en-2, bg-1, pl-1 (bureaucrat)
  69. EVula, en
  70. Ezarate, es-3, en-1
  71. Fanghong, zh, en-2, fr-1
  72. Flominator, de, als, en-3
  73. FunkMonk, da, en-4, no-3, fo-2, sv-2, de-1, es-1
  74. Geagea, he, ka-3, en-3, ru-1
  75. Geni, en
  76. George Chernilevsky, ru, uk-3, de-2, en-2, bg-1, la-1, be-1, fr-1
  77. Gestumblindi, als, de, en-3
  78. Gnangarra, en
  79. Golbez, en, ja-2
  80. Green Giant, en, de-1, fr-1
  81. grin, hu, en-3, de-1
  82. Gruznov, ru, en-1, fr-1
  83. Hedwig in Washington, de, en-4, nds-1
  84. Hekerui, de, en-4
  85. Hesperian, en
  86. HJ Mitchell, en
  87. Howcheng, en, ja-2
  88. Huntster, en
  89. Hystrix, de, en-1
  90. H-stt, de, en-4, fr-1
  91. Indeedous, de, en-3, fr-2
  92. INeverCry, en
  93. Infrogmation, en, es-1
  94. Jameslwoodward, en, fr-1 (bureaucrat, checkuser)
  95. January, en
  96. Jaqen, it, en-2
  97. Jarekt, pl, en
  98. JarrahTree, en, id-1
  99. Jastrow, fr, en-3, de-1, it-1
  100. Jcb, nl, en-3, es-3
  101. Jcornelius, de, lt-2, la-2, en-2, pt-2, fr-1
  102. Jdforrester, en
  103. Jean-Frédéric, fr, en-4, es-1
  104. JGHowes, en, fr-2, de-1
  105. Jianhui67, en, zh-3, ms-1
  106. Jmabel, en, es-3, ro-2, de-1, ca-1, it-1, pt-1, fr-1
  107. Joergens.mi, de, en-3
  108. John Vandenberg, en
  109. Julo, pl, en-2, de-1, ru-1
  110. JuTa, de, en-2, fr-1 (bureaucrat)
  111. Jusjih, zh, en-3, fr-1, ko-1 (steward)
  112. Kaldari, en
  113. Kallerna, fi, en-3, sv-2, de-1
  114. Kanonkas, no, en-4, nn-3, da-2, sv-2, de-1 (bureaucrat)
  115. Killiondude, en, es-3, ru-1
  116. King of Hearts, en, zh-3, es-2
  117. Klemen Kocjancic, sl, en-3, de-2, hr-1, bs-1
  118. Krd, de, en-3 (bureaucrat, checkuser)
  119. Krinkle, nl, en-3, de-2
  120. Krzysiu, pl, en-2, szl-2
  121. KTo288, en, zh-4
  122. Kwj2772, ko, en-2
  123. Kyro, fr, de-3, en-2
  124. Leit, de, en-3, fr-1
  125. Léna, fr, en-3, es-1
  126. Letartean, fr, en-3
  127. Leyo, gsw, de, en-3, fr-3, es-1, la-1
  128. Lobo, es, ca-2, en-2
  129. Logan, en, es-3
  130. Lokal Profil, sv, en-4, pt-2, fr-1
  131. LtPowers, en, es-1
  132. Ludo29, fr, en-2
  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 (checkuser)
  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. Mathonius, nl, en-3, fr-1, de-1 (steward)
  145. Mattbuck, en, fr-1, la-1
  146. Maxim, ru, en-3, fr-2
  147. MBisanz, en (steward)
  148. McZusatz, de, en-3, es-1, la-1 swg-1
  149. Mentifisto, en, mt, it-2 (steward)
  150. MGA73, da, en-3, de-2, sv-1, no-1
  151. MichaelMaggs, en, fr-1 (bureaucrat)
  152. Micheletb, fr, en-3, it-1, es-1
  153. Mitchazenia, en, es-2
  154. Miya, ja, en-2
  155. Mmxx, fa, en-3
  156. Mono, en
  157. Morgankevinj, en, es-1, la-1
  158. Mormegil, cs, en-2, de-1
  159. M0tty, fr, en-1
  160. MPF, en, da-2, de-1, fr-1
  161. Multichill, nl, en-3, de-1, fr-1
  162. Mys 721tx, zh, en-3
  163. Nagy, de, en-3, fr-2, es-1, sv-1
  164. NahidSultan, bn, en-3, bpy-1
  165. Natuur12, nl, en-3, de-1
  166. Neozoon, de, en-4, nl-4, fr-2
  167. Nick, en, sco-2, fr-1
  168. Niklem, ru, en-3
  169. Nilfanion, en, fr-1
  170. NordNordWest, de, en-3
  171. notafish, fr, en-4, de-3, es-2, it-2
  172. O, zh, en-4, zh-wuu-2, zh-hu-3, yue-1 fr-1
  173. odder, pl, en-3, 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. Rubin16, ru, tt, en-3
  205. Sanandros, als, de, en-3, fr-1
  206. Sandstein, als, de, en-4, fr-3, it-1
  207. SarahStierch, en
  208. Shizhao, zh, en-1, ru-1
  209. Siebrand, nl, en-3, fr-1, de-1
  210. Skeezix1000, en, fr-2
  211. Sphilbrick, en
  212. Spiritia, bg, en-3, ru-2, mk-2, de-1
  213. Sreejithk2000, ml, en-3, hi-3, ta-1, kn-1
  214. Steinsplitter, bar, de-4, it-3, en-1
  215. Stifle, en, ga, fr-2, de-1
  216. Tabercil, en
  217. Taivo, et, en-3, ru-3, de-1
  218. Tarawneh, en, ar, de-1
  219. Techman224, en
  220. Teles, pt, en-3, es-2 (steward)
  221. Thibaut120094, fr, en-2, ja-2
  222. Thuresson, sv, en-3, no-2
  223. Tiptoety, en (checkuser, oversighter)
  224. Tom, en, es-1
  225. Trijnstel, nl, en-4, de-1, fr-1 (checkuser, steward)
  226. tsca, pl, en, da
  227. Túrelio, de, en-3, es-1
  228. VIGNERON, fr, de-2, en-2, zh-1
  229. Waldir, pt, en-3
  230. Wdwd, de, en-2
  231. Whym, ja, en-2
  232. Wikitanvir, bn, en-3, as-2, bpy-1 (steward)
  233. WJBscribe, en, fr-3, de-1
  234. Wsiegmund, en, fr-1, es-1
  235. Wutsje, fy, nl, en-3, de-2, fr-1
  236. Wuzur, de, en-3
  237. wvk, de, en-4, fa-3, fr-2
  238. Yann, fr, en-3, hi-2, gu-1
  239. Yarl, pl, en-2, de-1, ru-1
  240. Ymblanter, ru, en-3, de-2, fr-2, nl-2, it-1, es-1
  241. Yuval Y, he, en-3
  242. Zolo, fr, en-4, de-2, zh-2
  243. Zzyzx11, en, es-1, fr-1
  244. CommonsDelinker, (bot)
  245. CommonsMaintenanceBot, (bot) see request
  246. GifTagger, (bot) see request
  247. KrinkleBot, (bot) see request

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

Um administrador é basicamente um usuário autorizado que pode:

  • proteger e desproteger páginas;
  • apagar e recuperar páginas;
  • apagar e recuperar imagens e outros arquivos;
  • bloquear e desbloquear usuários;
  • editar a interface e outras páginas protegidas.

Qualquer usuário pode solicitar ser administrador no Commons caso atenda aos seguintes critérios:

  • Estar familiarizado com o funcionamento dos projetos da Wikimedia. Ter editado em algum projeto de Wikimedia durante ao menos dois meses.
  • Entender e aceitar as metas do projeto e as suas políticas assim como respeitar a opinião geral que expressem os usuários do projeto.
  • Ter uma página de usuário em Commons e contribuir aqui. Ter pelo menos 200 edições (carregamentos de media ou outras edições). Alguns usuários têm padrões pessoais mais exigentes que estes.
  • Ao solicitar ser administrador, receber um apoio em consenso do conjunto de usuários votantes.

Assim como na política para ser administrador no Meta (en), administradores inativos podem perder sua responsabilidade de administrador. No Commons, qualquer administrador com menos de cinco acções administrativas nos últimos seis meses é considerado inactivo e pode perder o estatuto. Os administradores inactivos podem pedir novamente estatuto através do processo normal. Ferramenta de verificação de actividade.

Sugestões para administradores[edit]

...se você fala outras línguas[edit]

  • Por favor participe na Esplanada em Português e noutras línguas que compreenda. Este é um dos poucos sítios em que usuários podem pedir ajuda na sua própria língua.
  • Por favor veja o Centro de coordenação de traduções, uma página de coordenação da tradução de páginas do Commons para outras línguas.

Pedidos[edit]

Administrador[edit]

Utilize a caixa abaixo, substituindo username pelo seu nome de usuário:



Ver também: Commons:List of administrators, Commons:List of bureaucrats

Verificador de IP (CheckUser)[edit]

Utilize a caixa abaixo, substituindo username pelo seu nome de usuário:



Ver também: Commons:List of checkusers

Flags para bots[edit]

Utilize a caixa abaixo, substituindo BotName pelo nome de usuário do seu bot:



Ver também Commons:Bots/Requests for flags para se inteirar de todo o processo.

A seguir[edit]

  • Após a criação da subpágina, liste-a em Requests and votes, no topo da secção.
  • Se outra pessoa o nomeou, por favor indique a sua aceitação da nomeação declarando "Aceito" ou algo semelhante, e assinando abaixo da nomeação. Esta acção deixa claro que você aceita a nomeação e mostra quando você a aceitou, algo necessário para contar o tempo que passa desde a nomeação (para que um burocrata não feche a nomeação demasiado cedo por engano).

Transformando-se em um administrador[edit]

Após sete dias, caso tenha você tenha recebido pelo menos quatro votos e pelo menos 75% a favor, um burocrata verificará a existência de consenso; caso exista, alterará seu estatuto para administrador.

Os pedidos concluídos são arquivados em Commons:Administrators/Archive.

Candidatos[edit]

Purga da cache Use o "edit" abaixo para editar a página em transclusão dos pedidos e votações.


This project page in other languages:

Deutsch | English | español | +/−

Shortcut
COM:VOTE

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.

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]


Neolexx[edit]

  • Neolexx (talk · contributions · deleted user contributions · recent activity · logs · block log · global contribs · SULinfo) (assign permissions)
  • Reason: Commons contributor since 2009, autopatroller right granted this year (w/o my request). Not a crucial info here but to mention that I have reviewer rights at my home wiki. I do believe I learned which licenses are allowed and disallowed on Wikimedia Commons and I am familiar with restrictions that may apply, such as freedom of panorama. I also learned and understood the Image-reviewer right including that I can not review my own uploads. NeoLexx (talk) 16:39, 30 June 2015 (UTC)
  • Scheduled to end: 16:39, (UTC) (at least)
Comments
  • Symbol support vote.svg Support A envie de bien faire et de s'investir et de participer bénévolement. En plus, il a bien lu qu'il ne peut pas relire ses propres imports, ce qui lui évitera surement une rapide crucifixion (lol). -- KAPour les intimes 09:23, 1 July 2015 (UTC)


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.

Tulsibot (talk · contribs)[edit]

Operator: Tulsi Bhagat (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: Checking recently uploaded files and reporting if any problem in the image's description.

Automatic or manually assisted: Manually assisted

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

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

Bot flag requested: (Y/N): y

Programming language(s): Python

-- Eagle.svg.png Tulsi Bhagat (Talk) 09:16, 27 June 2015 (UTC)

Discussion[edit]

Pictogram voting question.svg Question What are the reports used for, who is processing them in which way? What in the exact problem of e.g. File:!Mein Coughlin.jpg listed in the report, and by which critera was it detected? --Krd 12:56, 27 June 2015 (UTC)

@Krd: The reports are used for informing about the errors found on uploaded files. Filbot is processing them with a fake license. The exact problem of e.g. File:!Mein Coughlin.jpg is that it has a fake license: Template:cc-by-2.0. It was detected while using bot and the reports observed. Thank you -- Eagle.svg.png Tulsi Bhagat (Talk) 15:11, 27 June 2015 (UTC)
I don't get that. How in detail do you detect that the license is fake? --Krd 15:19, 27 June 2015 (UTC)
Why is File:!Mein Coughlin.jpg tagged exactly? Which script do you use? And please remove the file from your signature. --Steinsplitter (talk) 15:44, 27 June 2015 (UTC)
@Krd: I detect that license is fake by running my Tulsibot using checkimages.py script. This script helps in checking recently uploaded files, a file description and other problems in the image's description. Thank you -- Eagle.svg.png Tulsi Bhagat (Talk) 17:29, 27 June 2015 (UTC)
I don't know what checkimages.py is intended for, but either it's severely broken or you are using is wrong. Example: File:! Schleswig-Holstein meerumschlungen 02.jpg was neither recently uploaded nor are there any problems at all. Also you did not provide any reasoning which Commons procedure you intended task is helpful for. Please advise in detail. Thank you. --Krd 07:27, 28 June 2015 (UTC)
Symbol oppose vote.svg Oppose He just runs checkimages.py which everyone with pywikibot can run. The user has a bad understanding about licenses (see his deleted uploads). I also thinks he isn't experienced enough to operate a bot here on commons. --Steinsplitter (talk) 17:33, 27 June 2015 (UTC)
@Steinsplitter: sorry! As, I am windows pywikibot core user. I use checkimages.py script. It has mentioned above that this script helps in checking recently uploaded files, a file description and other problems in the image's description.-- Eagle.svg.png Tulsi Bhagat (Talk) 17:39, 27 June 2015 (UTC)
@Steinsplitter: I can operate and handle my bot here on commons. If else any mistakes i will responsible for it and you may block my bot for a while. -- Tulsi Bhagat (Talk) 17:52, 27 June 2015 (UTC)
@Steinsplitter: Hi! sir, I want to say that When i started contributing for the first time here on commons and at that time the images was uploaded by me. I was not aware of rules, copyrights or licenses but now i am aware and well known of copyrights or licenses rules. Thank you -- Tulsi Bhagat (Talk) 18:00, 27 June 2015 (UTC)
@Steinsplitter: and @Krd: I think Tulsi Bhagat should given a chance to prove himself by doing trial edits using bot within a short period of time atleast 1 or 2 days. Thank you Bijay Chaurasia (Talk) 08:51, 29 June 2015 (UTC)
Tulsi Bhagat has uploaded a lot of copyvios, i don't feel comfortable that he runs a copyvio-finder bot. Running ckeckimages.py is not hard, but maintaining it is hard. I don't believe that Tulsi Bhagat has the necessary code skills to maintain this script (at least a basic understanding of COM:L is required, but i fail to see that too). --Steinsplitter (talk) 09:31, 29 June 2015 (UTC)
@Steinsplitter:sir, i request you to close this disscusion; I'll right back after 2 or 3 weeks. Thank you Tulsi Bhagat (Talk) 15:34, 29 June 2015 (UTC)

WMPL GLAM Bot (talk · contribs)[edit]

Operator: Yarl (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: file upload

Automatic or manually assisted: automatic

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

Maximum edit rate (e.g. edits per minute): hard to say, depends on file size

Bot flag requested: (Y/N): Y

Programming language(s): Java, custom softwate for each upload, here's first one

Yarl 19:07, 4 February 2015 (UTC)

Discussion[edit]

  • Tiny test run for you. Yarl 19:07, 4 February 2015 (UTC)
    • In the test run I see accession numbers quoted on the image page, but I can only see a match to this number at the source website when I examine the photo link embedded in the HTML rather than being visible on the page. Is this a true accession number for the archived photograph, or is it a potentially transient identity for the website digital image? -- (talk) 12:37, 5 February 2015 (UTC)
      • @ Numbers like "000925n" are their inventory number. Numbers in their URL path (like "84") are probably made due to some kind of technical limitations. Yarl 19:45, 6 February 2015 (UTC)
    • By the way, though there is no consensus on format, putting the accession number in brackets in the filename is not my personal preference due to potential problems with searches and queries on the title. Maybe you could consider the more simple <collection abbreviation><identity> at the end of the name like "<title> AMU000926n"? -- (talk) 12:37, 5 February 2015 (UTC)
  • Did the original author release these under the CC license? Or is the GLAM somehow claiming copyright and authority to license? --99of9 (talk) 05:15, 5 February 2015 (UTC)
    • @99of9: These files are under CC license, see footer. Yarl 19:45, 6 February 2015 (UTC)
      • @Yarl: the footer CC appears to apply to "design and implementation" (as opposed to the picture) if my google translate is correct. But you haven't actually answered my question - assuming you are correct about CC, who assigned the license? --99of9 (talk) 02:51, 7 February 2015 (UTC)
        • @99of9:: They (Józef Burszta Digital Archives), take a look at this page, Google Translate is good enough to understand. Yarl 12:50, 8 February 2015 (UTC)
          • @Yarl: So as I understand it, the photographer Andrzej Brencz donated a hard copy or photonegative to Józef Burszta (or the archive bearing his name), and it was later scanned and digitized in 2014? Usually a donation like that does not transfer copyright (but in some cases it is part of the contract). Is there evidence somewhere that this copyright was transferred at the time of donation, to entitle JBDA to release it under a free license? --99of9 (talk) 23:35, 8 February 2015 (UTC)
            • @99of9:: All photos are taken by employees and doctoral students of Adam Mickiewicz University during academic research, so their work is owned by university. JBDA is part of university archives, so situation is clear. More information about project is here (in Polish). Yarl 19:38, 9 February 2015 (UTC)
              • @Yarl: At my university, and most others I know, students retain the intellectual property over all of their work. Just giving a copy to the archives does not invalidate that. So the situation at JBDA is very unclear to me. --99of9 (talk) 10:11, 22 February 2015 (UTC)
                • @99of9: From what I know, everything is legally OK. They will send, however, clarification to OTRS. Yarl 22:07, 24 February 2015 (UTC)
                  • Ok, please pass on to them the specific concern about whether they own the intellectual property behind the photograph, not just a hard copy of the photograph itself. That's what will determine whether they should assert that they are the copyright owner. --99of9 (talk) 04:00, 25 February 2015 (UTC)
  • We do have bots with multiple operators for pragmatic reasons of maintenance and it is unusual to have a single bot account for indefinite multiple programmes of a Chapter; in fact I think this would be the first one on Commons based on User:Fæ/Userlist#bots, though one may be a less active account.
Other bots devoted to uploads are more often either associated with one operator or a single programme/archive for a donating organization. In this way there is long term accountability and there is more likely to be consistency in approach along with persistent improvement. I am also concerned that having "official Chapter bots" may discourage volunteers who do similar projects in the same country as the Chapter from working on their own "non-Chapter" bots as they might feel they need the Chapter's permission or be obliged to use the group account so that the Chapter gets political credit for future funding applications.
Would it damage anything if the scope of this bot were changed so that it became more specific than being potentially operated by anyone associated with a WMPL project? -- (talk) 12:18, 5 February 2015 (UTC)
  • Right, so since some time we have official paid GLAM coordinator in WMPL and my task, as a volounteer, is to upload obtained data. I don't want to do it using private bot (YarluFileBot), because it doesn't look professional in my opinion. I also don't want to take attribution, because most of work on upload (meetings, agreements) is done by WMPL employee. Regarding your concerns about bot ownage: I will own this account, no plans to change it. Yarl 19:45, 6 February 2015 (UTC)
  • Please use language templates for Depicted place and Photographer fields. --EugeneZelenko (talk) 15:17, 5 February 2015 (UTC)
    • @EugeneZelenko: By language templates you mean templates like {{en|text}}? Depicted place is indeed in Polish, so I'll add it, but photographer is just a name. It still needs lang. template? Just asking, because I've never seen combination like this. Yarl 19:45, 6 February 2015 (UTC)
      • In theory other Latin-based languages may use transliteration which could be different from Polish original, not talking about other scripts. --EugeneZelenko (talk) 15:13, 7 February 2015 (UTC)
  • It'll be good idea to add template which will request for human help with categorization. --EugeneZelenko (talk) 15:19, 5 February 2015 (UTC)
    • Yes, good point. Yarl 19:45, 6 February 2015 (UTC)
  • @99of9, EugeneZelenko, : Do you have more concerns guys? Just to be sure. Yarl 21:33, 21 February 2015 (UTC)
    What is conclusion about language templates? --EugeneZelenko (talk) 15:07, 22 February 2015 (UTC)
    No problem, can be added. I'll run second test run in a few days if needed. Yarl 22:07, 24 February 2015 (UTC)
Regarding legal issues: The archive has agreements with authors or their heirs to submit works on CC BY-SA 3.0 or later. They have submitted samples of such agreements. They also sent to OTRS their own agreement with complete list of files for which it is applicable. See (those who have access): [1]. Polimerek (talk) 11:36, 11 March 2015 (UTC)
@Polimerek: What the ticket confirms exactly? I don't speak this language, but i can't find something like CC-BY in the ticket. Does not looks like COM:CONSENT for me. Best --Steinsplitter (talk) 11:43, 11 March 2015 (UTC)
All documents (signed scans) are in pdf-s or zipped files attached to the E-mails. Agreement is in first and last E-mail (OTRS_UAM.pdf), the lists of works are attached in zipped files in the last E-mail. What do you want more? Polimerek (talk) 14:21, 11 March 2015 (UTC)
@Polimerek: I have overlooked the attachment, it never hurts to ask :-) --Steinsplitter (talk) 15:53, 11 March 2015 (UTC)
When you say "The archive has agreements with authors or their heirs to submit works on CC BY-SA 3.0", where did you get that information from, is it in one of the documents? Also, "They have submitted samples of such agreements." which zip file has a sample agreement in it? (I also don't speak Polish, so it is hard for me to locate this.) --99of9 (talk) 00:32, 12 March 2015 (UTC)
Zip files contains only list of files and objects with information who was author and/or donator, however they sent me directly several samples of agreements with authors and their heirs. They contain a clause that they grant copyrights to the University archive under condition that archive will publish it under CC BY-SA 3.0 PL license. The archive already did it already on their own page. Our GLAM coordinator have seen all these agreements in real. Agreements between Archive and authors/heirs cannot be made public as they contain personal data (home addresses etc.) and some donators (heirs of the authors) prefer to stay anonymous. Polimerek (talk) 22:28, 15 March 2015 (UTC)
@99of9: To clarify: WMPL was provided by JBDA with 1. The standard localised Polish consent statement (in the OTRS_UAM.pdf file) 2. Zip files mentioned by Polimerek: For each creator of images, an individual list of files released on a BY-SA license (for example, see file named "Linette Bogusław" for a 34-page-long list of images to which the BY-SA license and OTRS agreement applies); and 3. Scans of standardised license agreements the Adam Mickiewicz University (parent institution of the JBDA) had signed with listed image creators or their inheritors (one sample for creator agreement, another for inheritor agreement) fulfilling all the CC-BY-SA 3.0 PL and compatible license requirements. These have been sent for verification to Polimerek, an OTRS pl operator - and have been successfully verified (I am not an OTRS operator, but being the "WMPL employee" mentioned by Yarl I've been communicating with JBDA and have also laid eyes on this paperwork). So we've got a full set of JBDA permissions, as Polimerek stated above. --Marta Malina Moraczewska (talk) 23:13, 15 March 2015 (UTC)
The OTRS template should be used on the file description page. Apart from that, i have no further concerns. Best --Steinsplitter (talk) 17:26, 11 June 2015 (UTC)
@Yarl: Can you setup a custom license template that describes or lists the released images as best as possible, and use that with the uploads? See Category:Custom license tags with OTRS permission for examples. --Krd 17:31, 11 June 2015 (UTC)

Commons fair use upload bot (talk · contribs)[edit]

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

Files that are subject to deletion requests or other deletion processes which may be suitable to remain hosted on other Wikimedia projects (at this time localization is set up for the English Wikipedia, English Wikisource and the Estonian Wikipedia) may use the {{Fair use delete}} or {{PD-US-1923-abroad-delete}} templates so that the bot can perform the localization. When the bot is done localizing, the template is swapped to a speedy delete template.

Note that the bot only localizes images when a current administrator has added the relevant template. See the procedure description on the bot user page.

This bot was successfully running from 2012 through to summer 2014 on the Toolserver. In migrating I have been rewriting the code from mwclient to Pywikibot and have set up the service on labs under commonsfairuseupload. The source code can be found at https://github.com/faebug/fuub.

Automatic or manually assisted:

Automatic.

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

Hourly run, executed on WMFlabs.

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

When the bot was running previously, there was an average of a handful in a day. There is no need for this to be a fast bot and considering what it does (linear local downloads), I would expect a practical maximum of about 2 images processed in a minute.

Bot flag requested: (Y/N): Y

Programming language(s): Python, Pywikibot core.

(talk) 12:44, 15 January 2015 (UTC)

Discussion[edit]

  • The rewrite to Pywikibot is happening now, so I would expect the bot to remain in trials/testing for a couple more weeks depending on how much wiki-time I find to spend completing the migration. I have put a notice on COM:AN for comment, as the bot is focused on supporting admins who are responsible for assessing if an image is suitable for localization. -- (talk) 12:44, 15 January 2015 (UTC)
See also enwiki request in processxaosflux Talk 14:39, 15 January 2015 (UTC)
  • Seems useful. Let us know when you have done some trials. --99of9 (talk) 05:03, 5 February 2015 (UTC)
    • I've been delayed on revisiting the code, mainly due to some disillusionment as a volunteer. However I expect to get this running in March and we should be able to point to some tests at that time. -- (talk) 10:43, 5 February 2015 (UTC)
  • , is this on the back burner then? If so, that is a pity because it would have been a very useful service. Green Giant (talk) 07:58, 2 June 2015 (UTC)
I have a lot on in real life, and I confess to being disillusioned that a Commons admin can make legal threats against me and no action was taken. Considering the false and stupid allegations made about me on Commons and OTRS by certain people as part of the fracas around Russavia, I am disappointed that not a single apology has been forthcoming for publicly smearing my character. With time to reflect I was more damaged by this than I expected.
I still intend to implement and test out the FUUB, but I am prioritizing real life urgent matters and giving myself time to feel happier about this project before I do. When I return I shall probably run another RFA, operating tools like FUUB is severely hampered if I cannot delete or restore files myself, as this is central as to why they are needed. If I get rejected again, maybe it's time to move on and leave the project for those that want to run it like a boy's club. -- (talk) 14:52, 2 June 2015 (UTC)
@: Please advise: Do you prefer to keep this request open until you are ready for test edits, or should we close it for now and reopen it later? Thank you. --Krd 16:46, 28 June 2015 (UTC)
If it's no hassle I'd rather just leave it open. I have a massive simple logistics commitment for a couple of months, but the fraud case is a mountain of research and distracting because it is disturbingly unpleasant and much more significant than anyone expected. So my volunteer work is little bits and bobs right now and I will probably avoid committing to any bigger stuff over the summer. As I mentioned on en.wp if someone wants to invest their time getting the FUUB running before that, I am happy to leave it. -- (talk) 16:56, 28 June 2015 (UTC)

Dexbot (talk · contribs)[edit]

Operator: Ladsgroup (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: Adding {{Information}}

Automatic or manually assisted: Automatic

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

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

Bot flag requested: (Y/N): N

Programming language(s): python

Amir (talk) 02:07, 25 December 2014 (UTC)

Discussion[edit]

It's another step in metadata clean up (Further discussions). It only fixes when the description is one line and consists more than 5 words. The bot detects language of the description (that's why the description has to be more than 5 words) and adds proper information template. I did ~50 edits for test [2] you can check.

I'd rather we don't make up explicit {{own}} claims if the uploader made no such assertion. File:Denmark-Norway and possessions.png, for example, is clearly not the uploader's own work, but based on a pre-existing blank world map. LX (talk, contribs) 10:27, 25 December 2014 (UTC)
I've looked at the edits. Can you except certain templates? In this edit the bot added only the template to the description, while this template would be on a better place outside the information template. Other issues were found with this edit were the uploader claims another date, however the exif-date aggressor with you thus some weird edge case you can't possibly watch out for (other one same uploader). Same story for this one (1 year and 1 day of). this edit has the same source issue as mentioned by LX, but I don't see how that's fixable. And finally the most important one: this edit. This file was imported from en-wiki and given a "self" template, however the uploader is not the author of the work! This is going to happen with quite some files and is a big error. Some fixes could be to exempt descriptions with a user name (linked either this wiki or cross-wiki) which is not the same as the uploader. And exempt descriptions which say transferred/en wiki etc. Mvg, Basvb (talk) 12:22, 25 December 2014 (UTC)
The source issue is fixable by not making stuff up and instead leaving the source field blank. That will put the files into the maintenance category Files with no machine-readable source, which is where such files belong until they're manually fixed (or deleted, where appropriate). LX (talk, contribs) 13:21, 25 December 2014 (UTC)

@LX, Basvb:For the first issue: I will skip descriptions that consists only template(s). About the EXIF differences: I have no idea how to fix or skip them and IMO corrupted EXIF is not our problem. and about the {{self}} template: I can skip if someone else is mentioned in the text but for other cases I think it's not a problem that should be considered at this level. Honestly I think it's better to mark them with {{own}} because it makes these data a machine-processable data and it will be easier to find errors i.e. Using {{self}} is an error but when we mark them with {{own}}, errors are become easier to find, Specially in the future when new system of metadata is being used Amir (talk) 13:00, 26 December 2014 (UTC)

I agree that a self license should hold some form of own work from a Wikimedian (could also be an imported file from another project). I forgot to say in my last reaction that I really like your language determination, that seems to work well. Mvg, Basvb (talk) 13:15, 26 December 2014 (UTC)

Amir, what are you using for language detection? --Dschwen (talk) 22:20, 5 January 2015 (UTC)

@Dschwen: Hey, I use langdetect and accept the result if the number is more than 90% (usually it's less 70% or more than 99.999%). Amir (talk) 17:27, 6 January 2015 (UTC)

If there are no further issues, I suggest that we close this request as successful. --99of9 (talk) 04:54, 5 February 2015 (UTC)

I stand by my objection against making up source and authorship claims when no such claims were made by the uploader, which the bot is still doing. (In the linked example, from looking at the user's other uploads, it's probably a correct assumption, but the bot seems to just be guessing blindly.) I don't see how finding errors are made any easier by having to dig through the file description's page history to see that the uploader never actually claimed what we now claim about these files. If you want to make errors obvious, make it clear that these are assumptions made by a nonthinking entity. ("Source: No machine readable source provided. Own work assumed based on copyright claims." / "Author: No machine readable author provided. User:Example assumed based on copyright claims.") LX (talk, contribs) 22:04, 5 February 2015 (UTC)
@LX: Help me understand the issue a bit more. The previous version of that file had {{self}}, which states "I, the copyright holder of this work, hereby publish it..." Isn't that a strong statement of both authorship and source? --99of9 (talk) 23:08, 5 February 2015 (UTC)
No, it is not. There are several reasons why someone who is not the author may be the copyright holder: inheritance, works made for hire and copyright transfer come to mind. A person who takes a work for which the copyright has expired and makes copyrightable modifications to it would also be the sole copyright holder but not the sole author of the resulting work. Also, while it's demonstrably far from a guarantee that people won't wilfully misspeak, requiring users to assert that they are the author, that they are uploading their own work, and that they are the copyright holder has certain practical benefits. It's harder for copyright violators to feign ignorance and claim that they simply didn't understand that at least one of the three claims were false, and it gives the truly ignorant three different paths to enlightenment. As a consequence, it provides a little more security for reusers. I assume it's for these reasons that Commons:Licensing#License information states that author/creator of each media file must be provided on every file description and that "A generic license template which implies that the uploader is the copyright holder (e.g. {{PD-self}}) is no substitution for this requirement." (Original emphasis as used in the policy.) LX (talk, contribs) 01:04, 6 February 2015 (UTC)
Ok thanks, I now understand which angle you are working. I agree this will cause trouble when owner!=author. I'm not sure I agree that requiring a further assertion of authorship is realistic now for long-uploaded files with long-gone uploaders. In those cases, either a bot cleans up based on (usually reasonable) assumptions, humans clean up one-by-one based on (better?) assumptions, we leave messy forever, or we delete. I take it you favour one of the middle two options? --99of9 (talk) 01:28, 6 February 2015 (UTC)
I'm fine with the first option as long as the assumptions are clearly identified as such, ideally using templates for automatic categorisation and translation. That not only benefits human readers, but it also helps future, more specialised bot tasks, human cleanup efforts and (when appropriate) deletion processes. The statement that license templates do not constitute source or authorship information has been explicit in the licensing policy since June 2007, so while it may not be realistic to expect retired users to come back and improve their file descriptions, files (directly) uploaded to Commons after that date without explicit source and authorship information should be considered more problematic than older uploads. Not being able to automatically make such distinctions is, in my opinion, far messier than the current state of affairs. LX (talk, contribs) 07:06, 6 February 2015 (UTC)

@Ladsgroup: Could you please comment on the objections raised? Thank you. --Krd 17:15, 11 June 2015 (UTC)

It would be good if we have a note added by bot stating "Own Workd (based on license)" (like based on EXIF data; which can be clearly wrong lots of times). I easily add it the code if people agree on this Amir (talk) 17:09, 15 June 2015 (UTC)
I don't think that wording would be at all clear to most reusers. I stand by the wording I originally proposed above, but as long as it's done via a template, the wording can be changed and translated, so that's the main thing. LX (talk, contribs) 19:19, 15 June 2015 (UTC)
@LX: Can you create the template? Thanks Amir (talk) 14:46, 19 June 2015 (UTC)
I've created {{Own assumed}} and {{Author assumed}}. They could use a few more translations. LX (talk, contribs) 23:01, 19 June 2015 (UTC)
I switched the first one to use Translate, in order to get more translations. Jean-Fred (talk) 12:26, 21 June 2015 (UTC)
Doesn't seem to have worked. Now it just renders as a redlink: Template:Own assumed/i18n/en. LX (talk, contribs) 17:26, 21 June 2015 (UTC)
...so I reverted it. Feel free to redo whatever you tried to do, but please make sure the result is something that's in a usable state. Cheers, LX (talk, contribs) 19:40, 23 June 2015 (UTC)
Sorry for the overlook (I had made sure it worked in my interface but did not check English) − I fixed it now (phab:T56579 keeps biting me). Jean-Fred (talk) 20:40, 23 June 2015 (UTC)

@LX: I made about 50 edits based on your template. Does it look good? [3] Amir (talk) 20:44, 30 June 2015 (UTC)

It's better, but the authorship information is still made-up, and that should be pointed out as well. Please use {{Author assumed}} as well. Thanks, LX (talk, contribs) 20:51, 30 June 2015 (UTC)
@LX: Made another 50 edits. [4] Is it good now? Amir (talk) 18:47, 1 July 2015 (UTC)
Hi Amir! Yes, based on the sample I looked at, I have no objections at this point. Thanks, LX (talk, contribs) 18:55, 1 July 2015 (UTC)
Looks fine for me too. --Steinsplitter (talk) 18:58, 1 July 2015 (UTC)

Again then, if there are no further objections, I suggest we close this request as successful. --99of9 (talk) 00:58, 2 July 2015 (UTC)

Requests for comment[edit]

Centralized discussion

Template: View • Discuss • Edit • Watch