Commons:Administrador

From Wikimedia Commons, the free media repository
Jump to: navigation, search
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 December 2016 [+/−]
Listing by language
Listing by date
Listing by activity

Number of Admins: 239

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

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

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.

Revent[edit]

Vote

Note: Scheduled to end no earlier than 04:26, 4 December 2016 (UTC)

Links for Revent: Revent (talk · contributions · deleted user contributions · recent activity · logs · block log · global contribs · SULinfo)

The need for actual oversight is, frankly, rather rare on Commons... most deletions are simply due to the regular copyright issues. However, when people do need material to actually be oversighted, it is not infrequent for them to show up on IRC... such cases, that deserve oversight, are not uncommonly handled as a regular deletion by one of the admins present. Due to the nature of Commons, and the massive number of things deleted on a daily basis, that is typically not problematic... but, having one of the people frequently available on IRC able to actually apply 'oversight' deletion to such material would be a good thing... I think that the community is likely to trust that I would not apply the 'higher level' of deletion to material that was not in accordance with the specific criteria defined in the policy... the most common cases being that someone 'accidentally' uploaded a file that included something like a SSN.

Basically, the rationale for this request is that it is not (on Commons) a level of trust much beyond that of a regular admin, and that being more responsive to 'urgent' requests from random people would be a good thing. Reventtalk 04:26, 20 November 2016 (UTC)

Votes[edit]

  1. Symbol support vote.svg Support MCMLXXXIX 04:33, 20 November 2016 (UTC)
  2. Symbol support vote.svg Support Christian Ferrer (talk) 05:39, 20 November 2016 (UTC)
  3. Symbol support vote.svg Support DatGuy (talk) 12:05, 20 November 2016 (UTC)
  4. Symbol oppose vote.svg Oppose As I don't have any trust whatsoever in this user as sysop; so it is just logical that I would have no trust in them as oversighter. --A.Savin 12:58, 20 November 2016 (UTC)
  5. Symbol support vote.svg Support --Steinsplitter (talk) 14:27, 20 November 2016 (UTC)
  6. Symbol support vote.svg Support. -- Geagea (talk) 14:31, 20 November 2016 (UTC)
  7. Symbol support vote.svg Support - Trustworthy admin, I see no red flags here. Support. –Davey2010Talk 14:59, 20 November 2016 (UTC)
  8. Symbol support vote.svg Support No concerns with Revent. Nick (talk) 16:09, 20 November 2016 (UTC)
  9. Symbol support vote.svg Support Of course. Very trustworthy admin. Reguyla (talk) 00:04, 21 November 2016 (UTC)
  10. Symbol support vote.svg Support Definitely. I nominated him for adminship previously and he has proven himself to be a good admin. I am happy to support this nomination. Trusted and capable user. Why not? Jianhui67 talkcontribs 00:13, 21 November 2016 (UTC)
  11. Symbol support vote.svg Support Why not? He's active and he does not participate in any hassle. Taivo (talk) 08:07, 21 November 2016 (UTC)
  12. Symbol support vote.svg Support We need an extra oversighter and well, Revent is active and trusted. Natuur12 (talk) 22:09, 21 November 2016 (UTC)
  13. Symbol support vote.svg Support Good answers to questions below, trustworthy. Like those above said, why not? -- Poké95 10:50, 22 November 2016 (UTC)
  14. Symbol support vote.svg Support has continually displayed exemplary judgment as far as I have seen. Storkk (talk) 13:53, 22 November 2016 (UTC)
  15. Symbol support vote.svg Support Trijnsteltalk 00:40, 23 November 2016 (UTC)
  16. Symbol support vote.svg Support Revent has a proven track record as an active, capable and trusted adminsitrator here on Commons. The answers provided show that he is as prepared for the role as one can possibly be, and I am happy to support his candidacy. I am convinced that Revent will make an excellent addition to the oversight team and that he will very quickly learn the tricks of the trade. Being an oversighter is a lone and thankless job, so enjoy the spotlight, and good luck :-) odder (talk) 09:06, 23 November 2016 (UTC)
  17. Symbol support vote.svg Support Since there are only a total four oversighters, two of whose name I know, I trust Revent and the answers below are good. --Sebari – aka Srittau (talk) 23:38, 23 November 2016 (UTC)
  18. Symbol support vote.svg Support 5 is a good number. Marcus Cyron (talk) 04:24, 24 November 2016 (UTC)
  19. Symbol support vote.svg Support Raymond 07:33, 24 November 2016 (UTC)
  20. Symbol oppose vote.svg Oppose Sorry. From my experience, this user is highly biased in handling cases. He prefer to keep his mouth closed when his friends make a mistake; jump in when even see some minor mistakes on the other end. So not even suitable to held an admin flag. (I had conflict of opinions with many users here holding higher rights here. But it doesn't matter; most of them are able to handle each cases neutrally.) Jee 03:45, 25 November 2016 (UTC)
  21. Symbol support vote.svg Support Highly active and knows how to use the tools, always available on IRC where there is a need for people with oversight access to be "actually" present..--Stemoc 04:05, 25 November 2016 (UTC)
  22. Symbol support vote.svg Support Trusted user. --Yann (talk) 10:37, 25 November 2016 (UTC)
  23. Symbol support vote.svg Support --jdx Re: 11:36, 25 November 2016 (UTC)
  24. Symbol support vote.svg Support -- Revent is one of the few admins I respect a lot and I have so much trust in them. Wikicology (talk) 07:14, 27 November 2016 (UTC)
  25. Symbol support vote.svg Support satisfactory answers below --Zhuyifei1999 (talk) 07:55, 27 November 2016 (UTC)
  26. Symbol oppose vote.svg Oppose Per A.Savin and Jee. While Revent gives good answers to the "interview questions" below, Oversight is an extension of Admin and I'm afraid I don't believe Revent should be an admin. Classic example of an RFA about seeking file/maintenance admin powers and not become involved in controversial people admin activities yet ends up doing so in a very biased way, and very much not being the "impartial voice of reason" he promised to be. I wish we had separation of file/maintenance admin abilities as very few people demonstrate the neutrality and wisdom needed for people admin. I can't support oversight for someone who I would not support being admin. -- Colin (talk) 15:04, 27 November 2016 (UTC)
  27. Symbol keep vote.svg Keep Within COM:SCOPE. -- とある白い猫 ちぃ? 23:29, 28 November 2016 (UTC)
    @とある白い猫: What do you mean? This isn't a DR --Zhuyifei1999 (talk) 02:45, 29 November 2016 (UTC)
  28. Symbol support vote.svg Support Mostly due to availability in addition to the obvious capability and trust. Revent is online regularly for long lengths of time, so he'll be particularly useful handling any high-priority requests for oversight. ~ Rob13Talk 08:02, 29 November 2016 (UTC)
  29. Symbol support vote.svg Support Always been sensible and reliable. Oversight is not a task that I would wish on anyone. Hopefully Revent will keep a light touch and walk away from the right if it becomes a burden. -- (talk) 22:01, 29 November 2016 (UTC)

Comments[edit]

  • Pictogram-voting-question.svg Question Let's assume I'm not convinced by your candidacy statement. Why do you think I should support your nomination? Have you got any experience in dealing with non-public personal information, both on-wiki and outside of it (also in the context of Wikimedia)? If so, what is it? What do you think you will bring to the role? odder (talk) 08:05, 20 November 2016 (UTC)
A several part question, so I'll answer it in several parts.
  • As far as dealing with 'private information' outside of the projects, I was a member of the US Navy with an SCI clearance. I also worked for a number of years as a income tax preparer for H&R Block, where I dealt with the personal financial information of hundreds of clients, was subject to financial privacy laws, and had access to large amounts of personal information. I was also an 'enumerator' for the 2010 US Census, where I was sworn to a confidentiality oath under the penalty of five years in federal prison if I disclosed personal information. This history of dealing with such material stretches back, now, for about 20 years.
  • I have been a member of the OTRS team for several months now, after being prompted repeatedly, a role that requires the agent to also be aware of, agree to, and comply with the WMF's privacy policies.
  • OS would not seem to be, generally, a 'deliberative' task, so other than an awareness of what 'is' non-public personal information, all that I can really honestly say I would bring to the role is an increase in the availability of 'oversight-level' deletion, for when 'random' members of the public appear on IRC in a panic about the exposure of their personal information. Other than cases where the material is a matter of either 'accidentally outing themselves', or 'accidentally giving the world the ability to steal their identity', oversight deletions are a matter of either egregious attack usernames or actions taken on the request of WMF legal.
  • I do think that I, however, have a good working relationship with both a couple of the current oversighters, and several of the stewards, and would have no trouble with discussing cases reasonably when needed. Reventtalk 23:24, 20 November 2016 (UTC)
  • Pictogram-voting-question.svg Question What is it in your opinion that oversighters do as part of their duties? Have you ever requested the use of suppression before? odder (talk) 08:05, 20 November 2016 (UTC)
  • The main duty of an oversighter is, obviously, to permanently suppress instances of 'non-public personal information' that were either inadvertently, or maliciously, published to the wiki. I have requested the use of oversight multiple times, over the years, and never been denied... the first time, as I recall, was where a FOIA request had resulted in the release of portions of a military record, then uploaded to the wiki, that included both the birthdate and SSN of the servicemember. After redacting the SSN, and uploading a new copy, I asked for revision deletion of the original. Another (recent) case was where an editor had accidentally uploaded the 'wrong file' that was, essentially, a financial document.
  • Outside of that, the other major task of an oversighter is to suppress material upon the request of WMF legal. Reventtalk 23:24, 20 November 2016 (UTC)
  • Yes, I have read the policies and signed both confidentiality agreements, long ago, and I submitted a copy of my ID when I requested OTRS access. Other than simply being aware of what information actually 'is' covered by the policies, the main affect on the work of an oversighter, or anyone with access to such information, is "You don't talk about Fight Club". You cannot keep personal records of such information, or discuss the information itself, or even it's nature, in anything but the most generic terms with anyone who does not personally have valid access to the same information due to a role that they currently hold. Reventtalk 23:24, 20 November 2016 (UTC)
  • Pictogram-voting-question.svg Question Have you enabled two-factor authorization on your account? If not, why not? Do you think two-factor authorization should be compulsory for all Commons functionaries (oversighters, checkusers and bureaucrats)? If not, why not, and if yes, why? odder (talk) 08:05, 20 November 2016 (UTC)
  • Yes, I enabled 2FA within a few hours of it being made available to administrators. Without going too in depth into the technical details, I do think that 2FA should be required for all functionaries, on all projects, and I think the recent security breaches make why fairly clear. When the security of an account is based upon only a single 'secret' (a password) the security is only as good as the quality of the password, and the security of the password file. It seems to be the case that the attackers have been able, through some means, to obtain the hashed passwords of at least some administrators, and subject them to an offline brute force attack. TOTP (what we are using for 2FA) is the current 'best practice' for account security, and does not rely on person who owns the account being aware of technical details of password security... it depends on a completely different paradigm, 'something you have', not 'something you know'. Reventtalk 23:24, 20 November 2016 (UTC)
  • Pictogram-voting-question.svg Question How much time do you think it takes to perform oversight tasks? How many requests do you think are dealt with every month? Is this information available publicly? And finally, do you think you have the spare time to actually do this job? odder (talk) 08:10, 20 November 2016 (UTC)
  • To answer the first part explicitly, I cannot imagine that in the vast majority of cases where oversight is needed it would be at all time consuming... it would just be a matter of seeing that it was needed, and then actually 'doing' it. As far as how many requests are dealt with... since I can't look at the suppression log (which is itself suppressed), I cannot answer that 'directly', but COM:OS/S indicates that one or two requests a day is typical. I think the real concern is, simply, that when a request for oversight is made, it is 'by it's nature' an urgent request, and so it's important that it can be dealt with quickly... I think I have a well-known history of being 'around', and available and willing to respond to issues, most of the time. Reventtalk 23:24, 20 November 2016 (UTC)
  • Pictogram-voting-question.svg Question What's missing from this request page? odder (talk) 08:10, 20 November 2016 (UTC)
@Odder: A closure time... isn't adding that your job? :P Reventtalk 23:24, 20 November 2016 (UTC)
  • Pictogram-voting-question.svg Question I am not an oversighter (not even an admin), but oversight is very sensitive, more sensitive than checkuser (IMO). I am not doubting your trustworthiness in handling personal information, I just want to be sure before I cast my !vote. Here are some cases that I think you may encounter when you are an oversighter. Would you use normal revision deletion (which admins can use) or oversight? Please explain for each case.
    1. Unintentionally published personal information (the easiest part, I'm sure you can answer this Face-wink.svg)
    2. Copyright violating content (whether that would be text or media)
    3. Published IRC logs of a channel not allowing public logging
    4. Personal information about a minor, intended
    5. Unintentional revealing of someone's IP address (this is mostly because of being accidentally logged-out while editing)
    6. Confidential documents, like DNA tests, medical tests, and information from intelligence agencies
  • Optional question: Why did you chose oversight instead of checkuser? Isn't checkuser is more needed than oversight?
  • Thanks, Poké95 11:59, 21 November 2016 (UTC)
The use of oversight is very limited by the policy, and most 'deletable' material shouldn't be oversighted. He's my answers, tho.
1. Obviously, oversight. Unintentional (or malicious) disclosure of non-public personal information is the main use of the tool.
2. Copyright violations are not oversighted, normally. There is a 'use case' in the policy that allows for oversight to be used for doing so 'on the advice of Wikimedia Foundation counsel', but I can't really imagine a circumstance where Legal would ask for such an oversight that wasn't done as an Office Action, and even material removed after a DMCA notice is normally not oversighted.
3. IRC logs, from 'non-publically-logged' channels, are simply a copyright issue, and would only be a matter for oversight if there was material in the log that 'itself' was oversightable.
4. Personal information 'intentionally made public' by a minor is a sticky one... when a person makes their own information public, it's normally their right to do so, but it's very easy to imagine cases of very young minors exercising extremely bad judgement about the type of material that they put online. If I felt that a specific case was so egregious that it was likely to place a minor in actual 'physical danger' (I'm thinking of geotagged pedophile bait, here) I would of course oversight it, report it to the WMF, and discuss it with the other oversighters.... even if it was decided that such an oversight was an overreaction, it's reversible, and if the safety of a minor is potentially involved it would be wiser to remove the material while it was discussed.
5. An editor's IP address, unless they intentionally make it public, is protected by the privacy policy, and can be oversighted if they ask. In my experience, however, people usually just ask that it be 'deleted', and it's handled by a 'regular' administrator. I would not 'on my own initiative' oversight an IP address if simple deletion was all that was requested, but I would mention that it could be if the person wanted.
6. You cross two different types of 'confidential' material here. "Medical records" are quite clearly oversightable unless it's definitively established that the affected person themselves consented to their publication. "Classified" material, like intelligence agency documents, is not itself 'inherently' oversightable, and in many cases not even deletable (I'm thinking of File:Prism slide 5.jpg), but it's easy to assume that such material could itself contain non-public personal info, and the correct answer would probably be to redact that information, and then oversight the unredacted version. We should not be used to disseminate material that would place identifiable people at physical risk.
Just to make it clear, that I held a US government security clearance does not mean that I am legally obligated to attempt to censor classified (or allegedly classified) material. I am only prohibited from disseminating material that I 'know' is classified because I myself learned it from a confidential source, and to be honest, 99% of that was incredibly boring and technical design details of naval nuclear reactors.
As far as 'why oversight vs checkuser', I really have no interest in being a CU... that job is a matter of 'investigating' people, really, and to be honest the tool is overrated (the level of technical knowledge needed to avoid CU is not especially high, as many people have demonstrated over time). CU is about, really, being able to 'look at' private information, while OS is about 'suppressing' private information. We've 'lost' two oversighters in the past year, moving us back down to just four people, and it seems like a good idea to reduce our 'bus factor' by training up at least one more before we have more attrition. Reventtalk 21:17, 21 November 2016 (UTC)
@Revent: In other words CU requires technical knowledge and interpretation skills where as OS is intended to merely suppress private information such as addresses, real names and other info that were added out of malice or in error? -- とある白い猫 ちぃ? 02:02, 4 December 2016 (UTC)

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]

No current requests.


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.

BrackiBot (talk · contribs)[edit]

Operator: Brackenheim (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: minor edits using AutoWikiBrowser, such as removing/adding categories or corrections of misspellings in file descriptions ...

Automatic or manually assisted: manually for the first edits to ckeck, if AWB works correct, then automatically

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

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

Bot flag requested: (Y/N): Y

Brackenheim (talk) 10:10, 24 November 2016 (UTC)

Discussion[edit]

Test run on Commons comming soon. Here are some examples on de.wiki: [1], [2] or [3] --Brackenheim (talk) 10:21, 24 November 2016 (UTC)

Ok, here an example on Commons. Do I really have to wait seven days or could I help earlier? Kind regards, --Brackenheim (talk) 12:33, 24 November 2016 (UTC)
Sorry, but i think this request regarding the upwiz category removal has to be denied for two reasons:
  • We are getting problems with the jobqueue if we run moor bots on this task, see phab:T151196. Otherwise the current bots would run with moor speed.
  • Removing the category is not enough, a COM:Regex cleanup is needed.
Best --Steinsplitter (talk) 14:14, 24 November 2016 (UTC)
Thank you for that information. I was in hope, that there would be not such a problem with AWB ... Isn't COM:Regex included in AWB's cleanup (the function "aply general fixes")? --Brackenheim (talk) 14:29, 24 November 2016 (UTC)
"aply general fixes" is for wikipedia fixes. --Steinsplitter (talk) 14:32, 24 November 2016 (UTC)
What a pity ... --Brackenheim (talk) 14:34, 24 November 2016 (UTC)
Problems with the jobqueue seems to be fixed, see: grafana.wikimedia.org --Brackenheim (talk) 17:19, 24 November 2016 (UTC)
How are you going to deal with "automatic" spell checking with descriptions that may be in any language? — xaosflux Talk 04:56, 26 November 2016 (UTC)
I will just fix descriptions in German or English. Or mistakes, which are wrong in every language, e. g. "HIV-Virus" instead of "HI-Virus". --Brackenheim (talk) 00:00, 27 November 2016 (UTC)
I'm not sure if these corrections are worth any effort. Do file descriptions have to be typographically correct? --Krd 09:57, 2 December 2016 (UTC)

Requests for comment[edit]

Centralized discussion

Template: View • Discuss  • Edit • Watch