Wikimedia Commons

共享資源:管理员

This page is a translated version of a page Commons:Administrators and the translation is 100% complete. Changes to the translation template, respectively the source language can be submitted through Commons:Administrators and have to be approved by a translation administrator.

Shortcuts: COM:A • COM:ADMIN • COM:SYSOP

本页面被视为维基共享资源的正式指引。
它阐明了大多数编者原则上认可并普遍遵循的标准或行为。必要时你可以随意更新本页面。但是，重大修改的建议请在讨论页面提出。
Other languages:
本頁簡而言之： 维基共享资源的管理员是指那些有额外技术能力来管理站点的用户。他们能够删除和恢复文件和页面、保护页面、封禁用户、重命名文件，以及执行其他管理任务。当前维基共享资源共有187名管理员。用户可申请并完成投票过程来成为管理员。

此页解释了管理员（有时叫做admins或者sysops）在维基共享资源上的职责。请注意，此职务的的细节，以及授予管理员权限的方式，可能与其他项目不同。

如果你需要管理员的帮助，请移步管理员公告板。

现时在维基共享资源上有187 名管理员。

什么是管理员？

Administrators as of 1月 2024
Listing by: Language • Date • Activity [+/−]

Number of Admins: 187

  1. -revi, ko, en-3
  2. 1234qwer1234qwer4, ru, de-4, en-3
  3. 1Veertje, nl, en-4, de-1, fr-1
  4. 32X, de, en-2, hsb-1, ru-1
  5. 99of9, en (bureaucrat)
  6. A.Savin, ru, de-4, en-2
  7. Abzeronow, en, fr-1
  8. Achim55, de, en-3, nds-3, la-2
  9. AFBorchert, de, en-3
  10. Ahonc, uk, ru-4, en-2, de-1
  11. Aka, de, en-3
  12. Alno, fr, en-3, es-2, pt-1
  13. Андрей Романенко, ru, en-3, uk-3, be-2, fr-2, lv-2
  14. Ankry, pl, en-2, ru-1
  15. AnRo0002, de, en-2, fr-2, es-1
  16. Anthere, fr, en-3
  17. AntiCompositeNumber, en, fr-2 (steward)
  18. Aude, en, ar-2, de-2, es-3
  19. Benoît Prieur, fr, en-3, pt-2, es-1, it-1, hy-1
  20. Billinghurst, en
  21. Blackcat, it, en-3, fr
  22. BrightRaven, fr, en-3, nl-2, es-2, zh-1
  23. Butko, ru, uk-2, en-1
  24. Captain-tucker, en
  25. Christian Ferrer, fr, en-2, es-2
  26. Ciell, nl, en-2, de-1
  27. Common Good, en
  28. CptViraj, gu, hi-4, en-3
  29. Cromium, en, de-1, fr-1
  30. Cybularny, pl, en-2, es-1, de-1
  31. Czar, en
  32. DaB., de, en-1
  33. DarwIn, pt, en-3, es-2, fr-2, gl-2, ca-1, it-1, oc-1
  34. Davepape, en
  35. De728631, de, en-5
  36. DerHexer, de, en-3, grc-3, la-3, es-1 (steward)
  37. Dharmadhyaksha, mr, en-3, hi-3
  38. DMacks, en
  39. Didym, de, en-2, fr-2
  40. Dyolf77, ar, fr-5, en-2, it-1, es-1
  41. D-Kuru, de, en-2, it-1
  42. Ebrahim, fa, en-3
  43. Elcobbola en, de (checkuser)
  44. Ellin Beltz, en (bureaucrat)
  45. Ellywa, nl, en-2, de-1, fr-1
  46. Emha, de, bar, en-3, fr-1
  47. Érico, pt, en-2, es-1
  48. EugeneZelenko, ru, be, en-2, bg-1, pl-1 (bureaucrat)
  49. Explicit, en, es, ko-2
  50. Ezarate, es-3, en-1
  51. Fitindia, en-3, hi-2, mr-2
  52. FunkMonk, da, en-4, no-3, fo-2, sv-2, de-1, es-1
  53. Gbawden, en-3, af-1
  54. Geagea, he, ka-3, en-3, ru-1
  55. Geni, en
  56. George Chernilevsky, ru, uk-3, de-2, en-2, bg-1, la-1, be-1, fr-1
  57. Gestumblindi, als, de, en-3
  58. Gnangarra, en, nys-1
  59. GPSLeo, de, en-2
  60. GreenMeansGo, en
  61. Grin, hu, en-3, de-1
  62. Hekerui, de, en-4
  63. Herbythyme, en, fr-2, es-1, it-1
  64. Hesperian, en
  65. Holly Cheng, en, ja-2
  66. Huntster, en
  67. Indeedous, de, en-3, fr-2
  68. Infrogmation, en, es-1
  69. IronGargoyle, en, de-1
  70. Jameslwoodward, en, fr-1 (bureaucrat, checkuser)
  71. Jaqen, it, en-2
  72. Jarekt, pl, en
  73. JarrahTree, en, id-1
  74. Jcornelius, de, lt-2, la-2, en-2, pt-2, fr-1
  75. Jdforrester, en
  76. Jean-Frédéric, fr, en-4, es-1
  77. Jianhui67, en, zh-4, ja-2, ms-1
  78. Jmabel, en, es-3, ro-2, de-1, ca-1, it-1, pt-1, fr-1
  79. Joergens.mi, de, en-3
  80. JoKalliauer, de, en-3
  81. Jon Kolbert, en, fr-4, de-2 (steward)
  82. Josve05a, sv, en-3
  83. Julo, pl, en-2, de-1, ru-1
  84. Jusjih, zh, en-3, fr-2, ko-1
  85. Kadı, tr, en-5, fr-2, az-2
  86. Kaldari, en
  87. Kallerna, fi, en-3, sv-2, de-1
  88. King of Hearts, en, zh-3, es-2, ja-1
  89. Klemen Kocjancic, sl, en-3, de-2, hr-1, bs-1
  90. Krd, de, en-3 (bureaucrat, checkuser)
  91. Krinkle, nl, en-3, de-2
  92. Kritzolina, de, en-3, fr-2, it-1
  93. Leit, de, en-3, fr-1
  94. Léna, fr, en-3, es-1
  95. Leyo, gsw, de, en-3, fr-3, es-1, la-1
  96. Lofty abyss, en, mt, it-2
  97. Lymantria, nl, en-3, de-2, fy-2, fr-1, zea-1
  98. Magog the Ogre, en, es-2
  99. Mahagaja, en, de-4, fr-2, ga-2, la-2, cy-1
  100. Maire, pl, en-4, es-2, fr-2, de-2, ru-1
  101. Marcus Cyron, de, en-2
  102. Masur, pl, en-3, de-1
  103. Materialscientist, en-4, ru-4, nl-3, fr-1, es-1
  104. MB-one, de, en-3, fr-1, pt-1
  105. MBisanz, en
  106. Mdaniels5757, en, es-1
  107. MGA73, da, en-3, de-2, no-1, sv-1
  108. Mhhossein, fa, en-3, ar-1
  109. Micheletb, fr, en-3, it-1, es-1
  110. Mike Peel, en, pt-2, fr-1
  111. Minorax, en, zh (oversighter)
  112. Missvain, en
  113. Mitchazenia, en, es-2
  114. Miya, ja, en-2
  115. Moheen, bn, as-1, bpy-1, en-3, hi-1, hif-1
  116. Morgankevinj, en
  117. MPF, en, da-2, de-1, fr-1
  118. Multichill, nl, en-3, de-1, fr-1
  119. Mys 721tx, zh, en-3
  120. Nagy, de, en-3, fr-2, es-1, sv-1
  121. NahidSultan, bn, en-3, bpy-1
  122. Natuur12, nl, en-3, de-1
  123. Nick, en, sco-2, fr-1
  124. notafish, fr, en-4, de-3, es-2, it-2
  125. odder, pl, en-4, de-2 (bureaucrat, oversighter)
  126. Otourly, fr, en-2, it-1
  127. P199, en, nl, fr-2, tl-2, de-1
  128. Pi.1415926535, en, es-2
  129. Platonides, es, en-2, fr-1
  130. Poco a poco, es, de-4, en-3, fr-2, it-2, pl-2, pt-1
  131. Podzemnik, cs, en-2
  132. Polarlys, de, en-2, fr-1, no-1
  133. Pyb, fr, en-2
  134. Pymouss, fr, en-3, de-2, it-2, he-1
  135. Racconish, fr, en-4
  136. Ragesoss, en, de-1, fr-1
  137. Ra'ike, de, en-2
  138. Rama, fr, en-3, de-2, la-2, es-1, it-1, ja-1 (oversighter)
  139. Rastrojo, es, en-3, fr-2, eo-1
  140. Raymond, de, en-3, nl-1 (oversighter)
  141. Red-tailed hawk, en, es-4, pt-2, ug-1
  142. Regasterios, hu, en-1
  143. Rehman, en, si-1
  144. Reinhard Kraasch, de, en-3
  145. Rimshot, de, en-4, fr-2, it-1
  146. Romaine, nl, en-3, de-2, af-1, fr-1
  147. Rosenzweig, de, en-3, fr-1, la-1
  148. Royalbroil, en, es-1
  149. RP88, en, de-1
  150. Rubin16, ru, tt, en-4
  151. Rudolphous, nl, en-3, de-2
  152. Ruthven, it, fr, en-4, es-4, nap-4, ca-2, de-1
  153. Sanandros, als, de, en-3, fr-1
  154. Satdeep Gill, pa, en-5, hi-5, es-3, fr-2, fa-1
  155. Shizhao, zh, en-1, ru-1
  156. Spiritia, bg, en-3, ru-2, mk-2, de-1
  157. Sreejithk2000, ml, en-3, hi-3, ta-1, kn-1
  158. Steinsplitter, bar, de-4, it-3, en-1
  159. Stifle, en, ga, fr-2, de-1
  160. Storkk, en, fr-3, de-2, eo-2
  161. Strakhov, es, en-2
  162. TadejM, sl, en-3, de-2, fr-2
  163. Taivo, et, en-3, ru-3, de-1
  164. Tarawneh, en, ar, de-1
  165. Teles, pt, en-3, es-2
  166. Themightyquill, en, fr-2, de-1, hu-1
  167. TheAafi, ks, ur-5, en-3, hi-2, ar-1
  168. The Squirrel Conspiracy, en
  169. Thibaut120094, fr, en-2, ja-1
  170. Thuresson, sv, en-3, no-2
  171. Trijnstel, nl, en-4, de-1, fr-1 (checkuser)
  172. Tulsi, ne, mai, en-3, hi-2, hif-2, bh-1
  173. Túrelio, de, en-3, es-1
  174. VIGNERON, fr, de-2, en-2, zh-1
  175. Wdwd, de, en-2
  176. Well-Informed Optimist, ru, uk-4, en-3
  177. Wikitanvir, bn, en-3, de-2, as-2, bpy-1
  178. Wutsje, fy, nl, en-3, de-2, fr-1
  179. Yann, fr, en-4, hi-2, gu-1
  180. Yasu, ja, en-2, de-1
  181. Ymblanter, ru, en-3, de-2, fr-2, nl-2, it-1, es-1
  182. Yuval CT, he, en-3
  183. Zzyzx11, en, es-1, fr-1
  184. علاء, ar, en-4, he-1, es-1 (steward)
  185. Abuse filter, (automated account)
  186. CommonsDelinker, (bot) see request
  187. KrinkleBot, (bot) see request

If 187 is not the last number on this list, there may be an error or there are some users assigned temporarily.

技术

技术上，管理员在维基共享资源上有以下权限：

  • 删除和还原图像及其他上传的文件，并可浏览和恢复已删除的版本。
  • 删除和还原页面，并可浏览和恢复已删除的版本。
  • 保护页面和解除对页面的保护，并可编辑保护级别为“仅允许管理员”的页面。
  • 封禁和解封用户，进行IP地址（或IP段）的封禁。
  • 編輯沒有太多限制的的界面訊息（參見界面管理員）
  • 重命名文件。
  • 添加和删除用户组。
  • 配置上载向导。
  • 彻底删除和还原特定页面的日志和历史版本。
  • 从其他项目导入页面。
  • 合并页面历史。
  • 修改防滥用过滤器。
  • 移动页面时不创建来源页面的重定向。
  • 无视欺诈检查。
  • 一次将一条消息发送给多个用户。（群发消息）
  • 在API查询中使用更高的上限。

这些统称为管理工具。

社群角色

管理員是維基共享資源社群內有經驗的可信用戶，負責進階維護工作並且經公眾討論或投票已獲授權使用管理工具。不同的管理員有著不同的興趣和專長，但典型的管理員任務包括決策並關閉刪除請求、刪除版權違規、必要時恢復檔案、反破壞保護維基共享資源以及在模板和其他受保護頁面上作業。當然，其中有些工作也可以由非管理員完成。

管理員被期望瞭解是項目的目標，並準備著與其餘有志人士一同做出建設性的貢獻。管理員理應瞭解並遵守指引政策，在合理時尊重社群共識。

除去需要使用管理工具的時候，管理員由於個人立場不同並無特殊編輯權限，在討論或公開投票內，他們的貢獻被看作與其餘任一普通編者相同。一些管理員可能會變得更有影響力，這不是因為他們的管理員地位，而是因為他們從社群中獲得了對其個人的信任。

對管理員的建議

請詳閱管理員手冊。

移除管理员权限

根据管理员离任方针，如果管理员不活跃或者滥用管理工具，权限会被解除。 在管理员解任请求中，不适用参选管理员时判断共识的标准。而应当是使用“多数共识”，即超过50%的用户达成解任共识即可解任管理员。

申請成為管理員

所有有意願成為管理員的使用者必須經過這個過程，自薦至申請成為管理人員，包括那些想重新上任的前任管理員。

首先，前往Commons:Administrators/Howto並閱讀那裏的資訊。隨後返回並在下方的段落遞交申請。

  • 如果他人提名閣下，請以陳述「我同意（I accept）」或是其餘類似字樣來接受，並在提名下方簽名。子頁面仍然需要被您或是您的提名人嵌入。


使用下方的方框，並將"Username"替換成您的用戶名。

投票

任一註冊用戶都可以在這投票，不过那些很少甚至沒有編輯過的人的票可能不會被計算在內。閣下最好在  Support或  Oppose時都給予理由，這能幫助行政員更好地做出决策。有支持理據的論證會比簡單的投票更被看重。

上任管理员通常需要75%的支持率，并至少需要有8人同意。来自未注册用户的投票将不被计入。不管怎样，关闭个案的行政员可以自行考虑社群共识，最终决定并不只基于原始数据。如果行政员认为需要更好地确定社区共识，可以酌情延长投票的时间。

由于需计算成功或失败率，  Neutral投票将不被计入投票总数。然而，这些评论是讨论的一部分，并可能会说服其他人，还有助于关闭个案的行政员更好地了解社群共识。

清除缓存使用下方的编辑链接来编辑嵌入后的页面。

申请成为管理员

 watch

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.


Kallerna (de-adminship)

Related requests:

Vote

Kallerna (talk · contributions · deleted user contributions · recent activity · logs · block log · global contribs · CentralAuth) (Activity: Talk Commons DR)

Scheduled to end: 01:43, 15 January 2024 (UTC)

A consensus (with 17 supports vs 3 opposes) to start this process was reached on this Administrators' Noticeboard thread. The rationales are pretty much the same as in the first de-adminship attempt (which was closed as inadmissible because there was no clear consensus at that point). The current problems with Kallerna are wheel-warring (unblocking a user without prior attempt to contact the admin who performed the block), and use of admin privileges despite possible conflict of interest. Additionally: problematic behaviour, arrogancy, uncivil remarks such as "Please do not block users who do not share the same views as you", "I'm here to contribute to the project, not to discuss with trolls".

With that said, I hereby request to review whether Kallerna still has the trust of Commons community to hold the admin flag. Thanks --A.Savin 01:43, 8 January 2024 (UTC)Reply[reply]

Votes

  •   Remove as nominator, for reasons already stated in the previous RfDA, and on ANU discussion. --A.Savin 01:43, 8 January 2024 (UTC)Reply[reply]
  •   Remove regretfully, per above.   Keep Their apologies seem reasonable and well-meant. We also are in huge need of admins. One less is no solution. However, the point should be made: no repetition of past mistakes. --Bedivere (talk) 02:41, 8 January 2024 (UTC)Reply[reply]
    Commons needs more admins, but not admins who cannot use their tools properly. --SHB2000 (talk) 04:43, 9 January 2024 (UTC)Reply[reply]
    Here both involved admins failed with their tools. -- Zache (talk) 15:22, 10 January 2024 (UTC)Reply[reply]
  •   Remove regretfully, per above.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 03:45, 8 January 2024 (UTC)Reply[reply]
  •   Remove Per ANU discussion and their comment about other people trolling. --Adamant1 (talk) 05:25, 8 January 2024 (UTC)Reply[reply]
  •   Remove While I would not have blocked Karelj, the unblock was performed without the mandatory consultation and the subsequent lack of accountability leaves us little choice. Guido den Broeder (talk) 06:06, 8 January 2024 (UTC)Reply[reply]
  •   Remove Regretully. Kallerna never fully addressed the issues raised on AN in my opinion Gbawden (talk) 06:14, 8 January 2024 (UTC)Reply[reply]
  •   Remove The following quote shows are huge misunderstanding of Commons policies: You are not a admin, and you are not involved in the matter - I did not have any reason to communicate with you. [1] (the part before the comma should be irrelevant) --Schlurcher (talk) 08:01, 8 January 2024 (UTC)Reply[reply]
  •   Remove Per ANU discussion. --Kritzolina (talk) 08:02, 8 January 2024 (UTC)Reply[reply]
  •   Remove regretfully, per my statement in the ANU discussion. --AFBorchert (talk) 08:11, 8 January 2024 (UTC)Reply[reply]
  •   Remove I'm not a frequent voter, and I'm rather a low-key contributor. Admin behavior referenced and linked by other voters is one of most discouraging parts of contributing to Wikipedia and Commons. --Tupungato (talk) 11:19, 8 January 2024 (UTC)Reply[reply]
  •   Keep I accept Kallerna's explanation and apology. Taivo (talk) 11:56, 8 January 2024 (UTC)Reply[reply]
  •   Keep No reason. Htm (talk) 13:13, 8 January 2024 (UTC)Reply[reply]
    @Htm：​ could you please elaborate by "no reason"? --SHB2000 (talk) 04:43, 9 January 2024 (UTC)Reply[reply]
    This section is for votes, not for discussing. I find your behavior very disturbing. I have talk page.-- Htm (talk) 09:18, 9 January 2024 (UTC)Reply[reply]
    No one in their right mind would consider asking for clarification "very disturbing behaviour". You still haven't answered my question. --SHB2000 (talk) 10:02, 9 January 2024 (UTC)Reply[reply]
    Could you please both tone it down? Keep the conversation civil please, wherever it takes place! Kritzolina (talk) 10:44, 9 January 2024 (UTC)Reply[reply]
  •   Keep Kallerna statement is far sufficiant, I quote: "I want to apologize everyone involved" or "This was obviously a mistake". If they do ten times the same thing, ok, but for the first error as administrator... that should be sufficiant IMO. Christian Ferrer (talk) 14:25, 8 January 2024 (UTC)Reply[reply]
  •   Keep Kallerna has apologized for his behavior (controversial unblocking) and offending remarks, and I feel no need to pursue the matter further. 0x0a (talk) 15:03, 8 January 2024 (UTC)Reply[reply]
  •   Delete They said they apologise, but I have the impression the don't understand the problem at any level and still consider the feedback a big waste of time. --Krd 16:32, 8 January 2024 (UTC)Reply[reply]
  •   Remove Regretfully. I do not find any sense in the responses from Kallerna. A well-sought sorry could have worked but I'm not finding it, and I seriously don't like ifs and buts.─ The Aafī (talk) 17:03, 8 January 2024 (UTC)Reply[reply]
  •   Remove I'd have been fine with a warning if they showed they understood that they screwed up majorly here, but they've doubled down on their behavior, they've never addressed their conflict in interest as far as the unblock because they were w:WP:Involved in the incident that caused the block, they clearly don't understand that Karelj's block was within policy and seems to have prevented future disruption. Abzeronow (talk) 18:07, 8 January 2024 (UTC)Reply[reply]
  •   Remove Commons deserves better. Natuur12 (talk) 18:46, 8 January 2024 (UTC)Reply[reply]
  •   Remove as the nominator of the original de-adminship nom – too bad they couldn't admit their mistake and apologise to A.Savin. --SHB2000 (talk) 04:41, 9 January 2024 (UTC)Reply[reply]
  •   Keep The initial block and removing the block were both done incorrectly. The related discussions after that were somewhat subpar, but I hope that participants will learn something from this and next time co-operation would work better. --Zache (talk) 06:00, 9 January 2024 (UTC)Reply[reply]
  •   Keep Ditto per Zache. --Robert Flogaus-Faust (talk) 08:46, 9 January 2024 (UTC)Reply[reply]
  •   Keep good sysop.--RZuo (talk) 11:50, 9 January 2024 (UTC)Reply[reply]
  •   Keep Per Zache --Julesvernex2 (talk) 11:58, 9 January 2024 (UTC)Reply[reply]
  •   Keep A single incident like this does not rise to the level of desysop. -- King of ♥ ♦ ♣ ♠ 17:15, 9 January 2024 (UTC)Reply[reply]
  •   Keep 1989 (talk) 17:34, 9 January 2024 (UTC)Reply[reply]
    Just a vote? --SHB2000 (talk) 12:42, 10 January 2024 (UTC)Reply[reply]
  •   Keep Kallerna has acknowledged the action taken was incorrect, "I should have not done it without discussing about it first."[2] While the communications on both sides were not ideal (the initial failure of Kallerna to acknowledge the problem vs the rapid escalation to desysop fairly early in the discussion) this appears to be a first offence in the 14 years since Kallerna became an admin. If any admin can limit themselves to one mistake every 14 years, I think that would be a good result for the community. If Kallerna hasn't learned from this and the poor decisions are repeated, it will be easy enough to consider whether a desysop discussion is appropriate at that time. From Hill To Shore (talk) 17:38, 9 January 2024 (UTC)Reply[reply]
  •   Remove regretfully. MZaplotnik(talk) 17:47, 9 January 2024 (UTC)Reply[reply]
  •   Keep, per King of Hearts. Érico (talk) 18:31, 9 January 2024 (UTC)Reply[reply]
  •   Remove Per above. Not convinced the "apology" is sincere, it seems to be a desperate, last-ditch attempt to retain the admin bit. -Fastily 23:39, 9 January 2024 (UTC)Reply[reply]
  •   Keep --RodRabelo7 (talk) 09:06, 10 January 2024 (UTC)Reply[reply]
  •   Keep I accept his apology and acknowledgement. --A1Cafel (talk) 15:26, 10 January 2024 (UTC)Reply[reply]
  •   Keep -- FitIndia Semi-retired 20:32, 10 January 2024 (UTC)Reply[reply]
  •   Keep this is not worth a desysop. Similar as King of Hearts. I hope kallerna and A.Savin can soon get along with each other again.Paradise Chronicle (talk) 21:58, 10 January 2024 (UTC)Reply[reply]
  •   Weak keep per King of Hearts (who, no, I am not related to) and FHTS. This is deeply troubling and they're certainly on thin ice, but I think a desysop is unnecessary for one isolated incident. Queen of Hearts ❤️ (she/they/ella/elle) 05:50, 11 January 2024 (UTC)Reply[reply]
  •   Keep per Zache and KoH. — Draceane talkcontrib. 12:39, 11 January 2024 (UTC)Reply[reply]
  •   Keep --Argenberg (talk) 23:52, 11 January 2024 (UTC)Reply[reply]
  •   Neutral --Ameisenigel (talk) 16:16, 12 January 2024 (UTC)Reply[reply]
  •   Keep Andy Dingley (talk) 18:11, 12 January 2024 (UTC)Reply[reply]
  •   Keep —MdsShakil (talk) 21:20, 12 January 2024 (UTC)Reply[reply]
  •   Remove not discussing the reversal, and the threatening nature of the comment sent to the original admin implying he blocked because he disagreed with the users opinions is very obviously wrong. The level of aggression and disrespect is extraordinary. If you are admin, then you do t wheel war. You discuss on the admin’s noticeboard. If this vote results in a deadmin, then I would like to see some sort of restriction placed on the former admin that prevents retaliation. - Chris.sherlock2 (talk) 22:14, 12 January 2024 (UTC)Reply[reply]
  •   Keep cool
  1. A user was blocked just for having a non-consensual opinion. Wikimedia Commons should be open to diversity.
  2. As Zache remarkably showed here, over hundreds of recent reviews, the user Karelj has never been really "uncivil". Just hastily shared singular and subjective opinions. No big deal. No drama at all.
  3. Admin Kallerna unblocked Karelj without discussion because the user was blocked without discussion.
  4. Admin Christian Ferrer politely suggested A.Savin that this minor incident was not worth a long and boring desysop procedure, but A.Savin reverted the comment as if the opinion was unacceptable. Why?!
  5. Admin Kallerna also made the effort to politely engage a discussion on the same talk page, "For your work, I've especially enjoyed the images from Moscow metro. Thanks for your contributions!", result "I don't need bla bla" was rather harsh in comparison, and very weird in this context supposed to deal with COM:CIVIL.
  6. Following this discussion, A.Savin goes to Kallerna's talk page to throw "seldom in my Wikimedia activity I had seen such childish behaviour by an admin". See Direct rudeness on COM:IDENTIFYUNCIVIL: (d) belittling a fellow editor".
  7. In the end, it's quite a mountain for such an insignificant event gone haywire. Please continue to preserve Wikimedia Commons as democratic platform. The day it will stop, we will just find another cool place. 🐸 Don't Worry, Be Happy ♫ -- Basile Morin (talk) 05:11, 13 January 2024 (UTC)Reply[reply]
  •   Keep There's no need for this drama; both administrators made mistakes, and instead of wasting our time here, we should move on and concentrate on making improvements to Wikimedia Commons. 20 upper 11:01, 13 January 2024 (UTC)Reply[reply]
  •   Remove -- أيوب (talk) 13:49, 13 January 2024 (UTC)Reply[reply]
  •   Keep Admin Kallerna has apologized for his controversial unblocking and offending remarks, I think there is no need to pursue the matter further. --Pimpinellus((D)) • MUC•K•T 14:19, 13 January 2024 (UTC)Reply[reply]
  •   Keep In my view a single incident and Kallerna has straightened that out. --Mosbatho (talk) 21:36, 13 January 2024 (UTC)Reply[reply]
  •   Remove --Mirer (talk) 02:20, 14 January 2024 (UTC)Reply[reply]
  •   Weak keep --Mateus2019 (talk) 07:16, 14 January 2024 (UTC)Reply[reply]
  •   Keep just a single incident, not a chronic behavioral issue. The issue is resolved, and we're just wasting time over this silly thing at this point. —Matrix(!) {user - talk? - useless contributions} 11:07, 14 January 2024 (UTC)Reply[reply]

Comments

The Truth Is Out There —kallerna (talk) 08:53, 8 January 2024 (UTC)Reply[reply]

And this smörgåsbord of several difflinks should say what exactly? --A.Savin 12:12, 8 January 2024 (UTC)Reply[reply]
I did not want to make a long explanation all over again. I would just like to see you apologize Karelj for your inadequat block. If the community thinks I should not have admin tools after my mistake and following apology, then I respect that view. —kallerna (talk) 13:27, 8 January 2024 (UTC)Reply[reply]
Pointing out a possible error by another admin doesn't excuse your behavior. Instead of abusing your tools, you could have started a discussion about that block. Guido den Broeder (talk) 14:31, 8 January 2024 (UTC)Reply[reply]
It's a pretty minor mistake in the grand scheme of things, but still not good. If you do lose the privilege I encourage you to continue contributing and reply at some point in the future since it's that major of an issue to begin with. --Adamant1 (talk) 15:46, 8 January 2024 (UTC)Reply[reply]
You are correct Guido, that is why I have apologized my actions. Adamant1, I have been here for more than 15 years, I have no intentions to stop my contributions. —kallerna (talk) 18:05, 8 January 2024 (UTC)Reply[reply]
I hope you won’t retaliate if you do lose your privileges. The way you spoke to SHB2000 on the admin noticeboard was not great. - Chris.sherlock2 (talk) 22:17, 12 January 2024 (UTC)Reply[reply]
Strange that you are expecting me to seek Karel's pardon. I didn't treat him uncivil, unlike he treated Cart (and never apologized for this). The block was not abusive or bad-faith in any event. But if you are convinced that admins should apologize for past blocks, then feel encouraged to demand some Russian Wikipedia admins to do so first, who had abusively blocked me several times for void reasons, probably over political hate. --A.Savin 20:12, 8 January 2024 (UTC)Reply[reply]
@A.Savin：​ As I said earlier, admins should understand each other reasons rather than being right. I explain how I see what happened. From Kallerna's point of view, your rationale for blocking Karelj based on the given examples was insufficient. In this case, one example was extended in your blocking rationale to repeated very disrespectful comments at FPC recently. Based on Karelj voting comments, your claim was not true. When the admin makes such claims as part of the block, it tarnishes the target's reputation, and action will be required when one notices it. From your side, I think you thought that Karelj's comments were enough for blocking. It is also complex to explain when negative opinnion is bad as the integral part of FPC is also that users can give opposing and critical opinnions. So I would like not to be too harsh if somebody tries to make commenting more friendly. -- Zache (talk) 05:46, 9 January 2024 (UTC)Reply[reply]
<redacted>. 151.37.254.208 16:30, 9 January 2024 (UTC)Reply[reply]
A.Savin, can you explain why you removed the above comment? Btw, you were blocked on ru.wikipedia for incivility. If you import that and call it abusive, expect people to reply.
Kallerna, why did you think it a good idea to be the one to revert that? Guido den Broeder (talk) 20:29, 9 January 2024 (UTC)Reply[reply]
The above comment by an IP is indeed a troll, and there are good reasons to remove it. Yann (talk) 20:37, 9 January 2024 (UTC)Reply[reply]
Being blocked for expressing political opinions IS abusive, though, if I understand correctly (A.Savin, please correct me if I'm wrong). --SHB2000 (talk) 21:56, 9 January 2024 (UTC)Reply[reply]

Minor terminology quibble: wheel warring is when an admin action is reinstated, not when one is undone. The unblock was inappropriate, though, to be clear. — Rhododendrites talk |  16:34, 8 January 2024 (UTC)Reply[reply]

With respect, that is not accurate. A wheel war includes reverting an admin action without consensus or discussion. This was absolutely an example of wheel warring. - Chris.sherlock2 (talk) 22:21, 12 January 2024 (UTC)Reply[reply]
Description in enwiki is: Wheel warring is when an administrator's action is reversed by another administrator, but rather than discussing the disagreement, administrator tools are then used in a combative fashion to undo or redo the action. With very few exceptions, once an administrative action has been reverted, it should not be restored without consensus. wp:Wikipedia:Administrators -- Zache (talk) 23:16, 12 January 2024 (UTC)Reply[reply]
Yeah, I wouldn’t want to rely on the English Wikipedia when it comes to administration. - Chris.sherlock2 (talk) 11:14, 13 January 2024 (UTC)Reply[reply]

if sysops have different opinions about an action that can only be done by sysops (delete, protect, block), that action should be reviewed by the community. meanwhile, when the action is being reviewed, or if no consensus can be reached, the default should be the least restrictive action, i.e. undelete, unprotect, unblock.

in other words, it should not require more than 1 user to undo a single sysop's decision, but rather a majority consensus is needed to affirm a single sysop's decision.--RZuo (talk) 12:00, 9 January 2024 (UTC)Reply[reply]

  • This may be obvious to people who have followed the AN discussion, but I think it should be indicated somewhere in the request that A.Savin was/is involved in the (initial) controversy leading up to this request, and that "the admin who performed the block" is A.Savin. That part was not immediately clear to me. whym (talk) 03:48, 10 January 2024 (UTC)Reply[reply]
  •   Comment I haven't followed these events closely, so I am choosing not to vote, but I'm troubled by the thought that if an admin continues functioning as such while lacking the confidence of some of the other admins, in addition to other long-time users, that could damage confidence in the moderation team, overall. I appreciate that some reflection has taken place, but should there be an agreement that any future irregularity would lead to, say, a 3-month suspension of Kallerna's sysop tools? -- Ikan Kekek (talk) 02:49, 14 January 2024 (UTC)Reply[reply]
  • I was new to the desysop process prior to this. I was a little surprised that the sysop and desysop processes have different thresholds (75% confidence of the community to become an admin vs 50% confidence of the community to remain one) but those thresholds must have come about from community consensus. The consensus must have anticipated a greater degree of disharmony to allow the threshold for removal to be at 50% instead of 25%. While it is a good idea to sometimes revisit a previous consensus to check current community thinking, it is probably not the best time to do so 1 day before a 7 day desysop process concludes. Sanctions short of desysop should probably be discussed outside of this desysop process, as you would do with any normal situation. However, "any future irregularity" is probably too low a bar to judge future behaviour. It is an open invitation to anyone with a grudge to try to provoke a reaction and label the reaction as "irregular." From Hill To Shore (talk) 04:34, 14 January 2024 (UTC)Reply[reply]
    I take your point, but I do think this situation warrants additional discussion, even outside of this current desysop nomination. Perhaps some consideration could be made of what kinds of actions have antagonized other admins and other constructive users, and there could be at least some informal agreement to revisit things if such actions are repeated. -- Ikan Kekek (talk) 08:29, 14 January 2024 (UTC)Reply[reply]
  • Ikan Kekek, sorry I think your idea is not excellent, because there will be a proposal to suspend A.Savin's tool reciprocally. A large number of participants openly reported here and in the previous discussion that they considered the initial block unwarranted / inappropriate. I also think that if an admin comes to block you sometimes for a questionable reason, say you forgot to say "hello", then you'll probably be grateful to the person who takes the responsibility to unblock you immediately, instead of asking the community "saying hello is it an essential prerequisite?" Let's move on. Enough dust shaken off on this matter, in my opinion. -- Basile Morin (talk) 01:33, 15 January 2024 (UTC)Reply[reply]
    The reason wasn't so stupid, but I don't think we should be afraid of a discussion of Alex's behavior, if warranted - and not as the tit for tat you seem to be suggesting. I should say, suspensions for incivility can be appropriate but shouldn't be done without warning except in cases that are so obvious as to be uncontroversial, which this one was not. I haven't looked at this situation in detail but do know what comments were made at FPC. But anyway, start the thread if you like. -- Ikan Kekek (talk) 08:37, 15 January 2024 (UTC)Reply[reply]
  • No like. Your idea, not mine. And never said it was "stupid", just "not excellent" IMHO. Kind regards -- Basile Morin (talk) 09:00, 15 January 2024 (UTC)Reply[reply]
    I was saying the block reason wasn't as stupid as forgetting to say hello. -- Ikan Kekek (talk) 11:10, 15 January 2024 (UTC)Reply[reply]
  • Hmm... in this case the reviewer forgot to say "sorry" and "I my opinion". Also he made spelling mistake ("reasonon" instead of "reason") -- Basile Morin (talk) 11:24, 15 January 2024 (UTC)Reply[reply]

Please turn the page as soon as this voting pool has ended. We're in 2024, happy new year. -- Basile Morin (talk) 01:33, 15 January 2024 (UTC)Reply[reply]

申请成为行政员

 watch

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

  • Please read Commons:Bureaucrats 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.

申请成为用户查核员

 watch

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.

申请成为监督员

 watch

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.

参见

Retrieved from "https://commons.wikimedia.org/w/index.php?title=Commons:Administrators/zh&oldid=815179861"