Commons:Administratoren

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:
Bahasa Indonesia • ‎Bahasa Melayu • ‎Canadian English • ‎Deutsch • ‎English • ‎Esperanto • ‎Lëtzebuergesch • ‎Nederlands • ‎Tiếng Việt • ‎Türkçe • ‎Zazaki • ‎als • ‎asturianu • ‎brezhoneg • ‎català • ‎dansk • ‎español • ‎français • ‎galego • ‎interlingua • ‎italiano • ‎magyar • ‎norsk bokmål • ‎occitan • ‎polski • ‎português • ‎português do Brasil • ‎română • ‎shqip • ‎sicilianu • ‎suomi • ‎svenska • ‎čeština • ‎Ελληνικά • ‎беларуская (тарашкевіца)‎ • ‎български • ‎молдовеняскэ • ‎русский • ‎українська • ‎հայերեն • ‎עברית • ‎العربية • ‎فارسی • ‎مصرى • ‎پښتو • ‎नेपाली • ‎मराठी • ‎हिन्दी • ‎বাংলা • ‎ગુજરાતી • ‎ไทย • ‎中文 • ‎日本語 • ‎한국어
Commons Administrator.svg

Diese Seite erklärt die Rolle von Administratoren (manchmal auch Admins bzw. Sysops) auf Wikimedia Commons. Bitte beachte, dass die Rolle der Administratoren und die Voraussetzungen, Administrator zu werden, von denen anderer Projekte abweichen können.

Wenn du die Hilfe eines Administrators brauchst, wende dich bitte an das Administrators' noticeboard.

Es gibt derzeit 218 Administratoren auf Commons.

Was ist ein Administrator?

Administrators as of August 2020 [+/−]
Listing by language
Listing by date
Listing by activity

Number of Admins: 218

  1. -revi, ko, en-3 (steward)
  2. ~riley, en, fr-1, es-1
  3. 1989, en
  4. 1Veertje, nl, en-4, de-1, fr-1
  5. 32X, de, en-2, hsb-1, ru-1
  6. 4nn1l2, fa, en-3, ar-1
  7. 99of9, en (bureaucrat)
  8. A.Savin, ru, de-4, en-2
  9. Achim55, de, en-3, nds-3, la-2
  10. AFBorchert, de, en-3
  11. Ahmad252, fa, en-3, ar-1
  12. Ahonc, uk, ru-4, en-2, de-1
  13. Aka, de, en-3
  14. Alan, es, eu-3, en-2
  15. Alno, fr, en-3, es-2, pt-1
  16. Amada44, de, en-3, fr-1
  17. Андрей Романенко, ru, en-3, uk-3, be-2, fr-2, lv-2
  18. Ankry, pl, en-2, ru-1
  19. AnRo0002, de, en-2, fr-2, es-1
  20. Anthere, fr, en-3
  21. Arthur Crbz, fr, en-4, es-3
  22. Aude, en, ar-2, de-2, es-3
  23. AzaToth, sv, en-4
  24. Benoît Prieur,fr, en-3, pt-2, es-1, it-1, hy-1
  25. Benoit Rochon, fr, en-4
  26. Billinghurst, en
  27. Blackcat, it, en-3, fr
  28. BrightRaven, fr, en-3, nl-2, es-2, zh-1
  29. Butko, ru, uk-2, en-1
  30. Captain-tucker, en
  31. Christian Ferrer, fr, en-2, es-2
  32. Ciell, nl, en-2, de-1
  33. clpo13, en
  34. Common Good, en
  35. Cookie, es, en-2
  36. Czar, en
  37. DaB., de, en-1
  38. Dantadd, it, pt, en-3, es-3, fr-3, gl-3, ca-2, ro-1, el-1
  39. DarwIn, pt, en-3, es-2, fr-2, gl-2, ca-1, it-1, oc-1
  40. Davepape, en
  41. David Levy, en
  42. De728631, de, en-5
  43. Dereckson, fr, en-3, de-1, nl-1
  44. DerHexer, de, en-3, grc-3, la-3, es-1 (steward)
  45. Dharmadhyaksha, mr, en-3, hi-3
  46. DMacks, en
  47. Didym, de, en-2, fr-2
  48. Dyolf77, ar, fr-5, en-2, it-1, es-1
  49. D-Kuru, de, en-2, it-1
  50. Ebrahim, fa, en-3
  51. Elcobbola en, de (checkuser)
  52. Ellin Beltz, en (bureaucrat)
  53. Emha, de, bar, en-3, fr-1
  54. Érico, pt, en-2, es-1
  55. EugeneZelenko, ru, be, en-2, bg-1, pl-1 (bureaucrat)
  56. Explicit, en, es, ko-2
  57. Ezarate, es-3, en-1
  58. Fitindia, en-3, hi-2, mr-2
  59. Flominator, de, als, en-3
  60. FunkMonk, da, en-4, no-3, fo-2, sv-2, de-1, es-1
  61. Gbawden, en-3, af-1
  62. Geagea, he, ka-3, en-3, ru-1
  63. Geni, en
  64. George Chernilevsky, ru, uk-3, de-2, en-2, bg-1, la-1, be-1, fr-1
  65. Gestumblindi, als, de, en-3
  66. Gnangarra, en, nys-1
  67. Golbez, en, ja-2
  68. Green Giant, en, de-1, fr-1 (steward)
  69. GreenMeansGo, en
  70. grin, hu, en-3, de-1
  71. Guanaco, en, es-1
  72. Hanooz, fa, en-2
  73. Hedwig in Washington, de, en-4, nds-1
  74. Hekerui, de, en-4
  75. Herbythyme, en, fr-2, es-1, it-1
  76. Hesperian, en
  77. Howcheng, en, ja-2
  78. Huntster, en
  79. Indeedous, de, en-3, fr-2
  80. Infrogmation, en, es-1
  81. Jameslwoodward, en, fr-1 (bureaucrat, checkuser)
  82. Jaqen, it, en-2
  83. Jarekt, pl, en
  84. JarrahTree, en, id-1
  85. Jcornelius, de, lt-2, la-2, en-2, pt-2, fr-1
  86. Jdforrester, en
  87. Jdx, pl
  88. Jean-Frédéric, fr, en-4, es-1
  89. JGHowes, en, fr-2, de-1
  90. Jianhui67, en, zh-4, ja-2, ms-1
  91. Jmabel, en, es-3, ro-2, de-1, ca-1, it-1, pt-1, fr-1
  92. Joergens.mi, de, en-3
  93. JoKalliauer, de, en-3
  94. Jon Kolbert, en, fr-4, de-2
  95. Josve05a, sv, en-3
  96. Juliancolton, en
  97. Julo, pl, en-2, de-1, ru-1
  98. JuTa, de, en-2, fr-1 (bureaucrat)
  99. Jusjih, zh, en-3, fr-2, ko-1
  100. Kaldari, en
  101. Kallerna, fi, en-3, sv-2, de-1
  102. King of Hearts, en, zh-3, es-2, ja-1
  103. Klemen Kocjancic, sl, en-3, de-2, hr-1, bs-1
  104. Krd, de, en-3 (bureaucrat, checkuser, steward)
  105. Krinkle, nl, en-3, de-2
  106. Kwj2772, ko, en-3
  107. Leit, de, en-3, fr-1
  108. Léna, fr, en-3, es-1
  109. Leyo, gsw, de, en-3, fr-3, es-1, la-1
  110. Lofty abyss, en, mt, it-2
  111. Lymantria, nl, en-3, de-2, fy-2, fr-1, zea-1
  112. Magog the Ogre, en, es-2 (checkuser)
  113. Mahagaja, en, de-4, fr-2, ga-2, la-2, cy-1
  114. Maire, pl, en-4, es-2, fr-2, de-2, ru-1
  115. Marcus Cyron, de, en-2
  116. Mardetanha fa, az, en-3, tr-2, ar-1 (steward)
  117. Martin H., de, en-2
  118. Masur, pl, en-3, de-1
  119. Matanya, en, he (steward)
  120. Materialscientist, en-4, ru-4, nl-3, fr-1, es-1
  121. Mates, cs, en-3, sk-4, de-1
  122. Mattbuck, en, fr-1, la-1
  123. Maxim, ru, en-3, fr-2
  124. MB-one, de, en-3, fr-1, pt-1
  125. MBisanz, en
  126. MGA73, da, en-3, de-2, no-1, sv-1
  127. Mhhossein, fa, en-3, ar-1
  128. Micheletb, fr, en-3, it-1, es-1
  129. Mike Peel, en, pt-2, fr-1
  130. Missvain, en
  131. Mitchazenia, en, es-2
  132. Miya, ja, en-2
  133. Moheen, bn, as-1, bpy-1, en-3, hi-1, hif-1
  134. Morgankevinj, en
  135. MPF, en, da-2, de-1, fr-1
  136. Multichill, nl, en-3, de-1, fr-1
  137. Mys 721tx, zh, en-3
  138. Nagy, de, en-3, fr-2, es-1, sv-1
  139. NahidSultan, bn, en-3, bpy-1 (steward)
  140. Nat, en, fr, gsw-1, pl-1
  141. Natuur12, nl, en-3, de-1
  142. Neozoon, de, en-4, nl-4, fr-2
  143. Nick, en, sco-2, fr-1
  144. notafish, fr, en-4, de-3, es-2, it-2
  145. Nyttend, en, ang-1
  146. odder, pl, en-4, de-2 (bureaucrat, oversighter)
  147. Otourly, fr, en-2, it-1
  148. P199, en, nl, fr-2, tl-2, de-1
  149. Perhelion, de, en-3
  150. Pi.1415926535, en, es-2
  151. PierreSelim, fr, en-3, es-1 (oversighter)
  152. Pitke, fi, en-4, sv-2
  153. Platonides, es, en-2, fr-1
  154. Pleclown, fr, en-3
  155. Poco a poco, es, de-4, en-3, fr-2, it-2, pl-2, pt-1
  156. Podzemnik, cs, en-2
  157. Polarlys, de, en-2, fr-1, no-1
  158. Putnik, ru, en-2
  159. Pyb, fr, en-2
  160. Pymouss, fr, en-3, de-2, it-2, he-1
  161. Racconish, fr, en-4
  162. Ragesoss, en, de-1, fr-1
  163. Ra'ike, de, en-2
  164. Rama, fr, en-3, de-2, la-2, es-1, it-1, ja-1 (oversighter)
  165. Rastrojo, es, en-3, fr-2, eo-1
  166. Raymond, de, en-3, nl-1 (oversighter)
  167. Regasterios, hu, en-1
  168. Rehman, en, si-1
  169. Reinhard Kraasch, de, en-3
  170. Rimshot, de, en-4, fr-2, it-1
  171. Romaine, nl, en-3, de-2, af-1, fr-1
  172. Rosenzweig, de, en-3, fr-1, la-1
  173. Royalbroil, en, es-1
  174. RP88, en, de-1
  175. Rudolphous, nl, en-3, de-2
  176. Ruthven, it, fr, en-4, es-4, nap-4, ca-2, de-1
  177. Sanandros, als, de, en-3, fr-1
  178. Sealle, ru, en-4, pl-2, sk-2, uk-2
  179. Shizhao, zh, en-1, ru-1
  180. Spiritia, bg, en-3, ru-2, mk-2, de-1
  181. Sreejithk2000, ml, en-3, hi-3, ta-1, kn-1
  182. Srittau, de, en-3
  183. Steinsplitter, bar, de-4, it-3, en-1
  184. Stifle, en, ga, fr-2, de-1
  185. Storkk, en, fr-3, de-2, eo-2
  186. Strakhov, es, en-2
  187. Tabercil, en
  188. TadejM, sl, en-3, de-2, fr-2
  189. Taivo, et, en-3, ru-3, de-1
  190. Tarawneh, en, ar, de-1
  191. Techman224, en
  192. Teles, pt, en-3, es-2
  193. Themightyquill, en, fr-2, de-1, hu-1
  194. The Squirrel Conspiracy, en
  195. Thibaut120094, fr, en-2, ja-2
  196. Thuresson, sv, en-3, no-2
  197. Tomer T, he, en-3
  198. Trijnstel, nl, en-4, de-1, fr-1 (checkuser, steward)
  199. Tulsi Bhagat, ne, mai, en-3, hi-2, bh-2, hif-2
  200. Túrelio, de, en-3, es-1
  201. VIGNERON, fr, de-2, en-2, zh-1
  202. Wdwd, de, en-2
  203. Well-Informed Optimist, ru, uk-4, en-3
  204. Whym, ja, en-2
  205. Wikitanvir, bn, en-3, de-2, as-2, bpy-1
  206. Wutsje, fy, nl, en-3, de-2, fr-1
  207. Yann, fr, en-4, hi-2, gu-1
  208. Yarl, pl, en-2, de-1, ru-1
  209. Yasu, ja, en-2, de-1
  210. Y.haruo, ja, en-1
  211. Ymblanter, ru, en-3, de-2, fr-2, nl-2, it-1, es-1
  212. Yuval CT, he, en-3
  213. Zzyzx11, en, es-1, fr-1
  214. علاء, ar, en-4, he-1, es-1 (steward)
  215. Abuse filter, (automated account)
  216. CommonsDelinker, (bot) see request
  217. CommonsMaintenanceBot, (bot) see request
  218. KrinkleBot, (bot) see request

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

Technisch

Administratoren sind Benutzer mit folgenden Rechten:

  • Bilder oder andere hochgeladene Dateien löschen und wiederherstellen bzw. gelöschte Versionen einsehen und wiederherstellen
  • Seiten löschen und wiederherstellen bzw. gelöschte Versionen einsehen und wiederherstellen
  • Seiten schützen und auch den Schutz wieder aufheben sowie geschützte Seiten bearbeiten
  • Benutzer und IP-Adressen/IP-Adressbereiche sperren und entsperren
  • Bearbeiten weniger eingeschränkter Oberflächenameldungen (siehe auch Commons:Oberflächenadministratoren)
  • Dateien umbenennen
  • Benutzer verschiedenen Gruppen hinzufügen und wieder daraus entfernen
  • Upload Wizard-Kampagnen konfigurieren
  • Einzelne Logbuch-Einträge sowie einzelne Versionen von Seiten löschen und wiederherstellen
  • Seiten aus anderen Wikis importieren
  • Versionsgeschichten von Seiten vereinen
  • Missbrauchsfilter-Einstellungen bearbeiten
  • Beim Verschieben die Erstellung einer Weiterleitung unterdrücken
  • Die Benutzernamens-Ähnlichkeitsprüfung und die schwarze Liste unerwünschter Seiten- oder Benutzernamen außer Kraft setzen
  • Gleichzeitig Nachrichten an mehrere Benutzer senden (massmessage)
  • Höhere Limits in API-Abfragen

Diese Rechte sind allgemein als Administrationswerkzeuge bekannt.

Rolle in der Gemeinschaft

Administratoren sind erfahrene und vertrauenswürdige Mitglieder der Commons-Benutzerschaft, die zusätzliche Verwaltungsaufgaben übernommen haben und nach Konsens/Abstimmung mit den Administrationswerkzeugen ausgestattet wurden. Administratoren haben unterschiedliche Interessen- und Fachgebiete; typische Aufgaben eines Administrators sind die Bearbeitung und Erledigung von Löschanträgen, das Löschen von Urheberrechtsverletzungen, das Wiederherstellen von Dateien, das Schützen von Commons vor Vandalismus und die Bearbeitung von Vorlagen und anderen geschützten Seiten. Selbstverständlich können einige dieser Aufgaben auch von Benutzern ohne erweiterte Rechte erledigt werden.

Von Administratoren wird erwartet, dass sie die Ziele des Projekts verstehen und bereit sind, konstruktiv mit anderen auf diese Ziele hinzuarbeiten. Administratoren sollten außerdem Commons' Richtlinien verstehen und befolgen und gegebenenfalls den Konsens der Community befolgen.

Außerhalb von Rollen, die die Benutzung von Administrationswerkzeugen bedingen, haben Administratoren keine besondere redaktionelle Autorität durch ihre Position. In Diskussionen und Abstimmungen werden ihre Beiträge genauso behandelt wie die jedes anderen Benutzers. Einige Admins werden vielleicht einflussreicher, nicht aufgrund ihrer Position als solche, sondern aufgrund des persönlichen Vertrauens, das sie aus der Community gewonnen haben.

Vorschläge für Administratoren

Bitte lies Commons:Ratgeber zur Administratorentätigkeit.

Entzug von Adminrechten

Gemäß der Entzugs-Richtlinie können Adminrechte bei Inaktivität oder Missbrauch wieder entzogen werden.

Bewerbung als Administrator

Alle Benutzer, die Administratorenrechte erlangen möchten, müssen durch diesen Prozess gehen und eine Anfrage zu Administratorenrechten stellen, das schließt auch alle ehemaligen Administratoren ein, die ihre früheren Rechte wiedererlangen möchten.

Gehe als erstes auf Commons:Administrators/Howto und lies dir die Seite gründlich durch. Danach kannst du zurückkommen und im folgenden Abschnitt deine Kandidatur starten.

  • Nachdem du auf den passenden Button geklickt und die Unterseite angelegt hast, kopiere den Link zur Unterseite, beispielsweise „Commons:Administrators/Requests/Benutzername“, bearbeite Commons:Administrators/Requests und füge ihn oben im entsprechenden Abschnitt ein. Danach umschließe ihn mit doppelten geschweiften Klammern (beispielsweise {{Commons:Administrators/Requests/Username}}), um die Unterseite einzubinden. Fordere eine Beobachtungslisten-Benachrichtigung unter MediaWiki talk:WatchlistNotice an, oder bearbeite MediaWiki:WatchlistNotice, um eine solche zu erstellen, wenn du Administrator bist.
  • Wenn du von jemandem nominiert wurdest, akzeptiere bitte die Nominierung durch einen kurzen Kommentar und deine Signatur. Die Unterseite muss dann durch dich oder den Nominierenden entsprechend eingebunden werden.
Ersetze in der folgenden Box Username durch deinen Benutzernamen:


Abstimmung

Jeder registrierte Benutzer kann sich an der Abstimmung beteiligen. Wenn ein Benutzer bisher erst wenige oder gar keine Beiträge gemacht hat, könnte seine Stimme jedoch nicht vollständig gewichtet werden. Es ist gern gesehen, wenn die Gründe für   Support- oder   Oppose-Stimmen angegeben werden, da dies dem Bürokraten, der über den Antrag entscheidet, bei seiner Entscheidung hilft. Eine gute Begründung, bei Bedarf mit entsprechenden Nachweisen, kann stärker gewichtet werden als eine bloße Pro- oder Kontra-Stimme.

Damit der Antrag erfolgreich ist, werden normalerweise mehr als 75 % Zustimmung und mindestens 8 positive Stimmen erwartet. Allerdings hat der bearbeitende Bürokrat einen Spielraum bei der Einschätzung des Community-Konsens und die Entscheidung muss nicht ausschließlich auf bloßen Zahlen beruhen.

  Neutrale Kommentare werden zur Ermittlung der prozentualen Pro-/Kontra-Ergebnisse nicht mitgezählt. Jedoch sind solche Kommentare Teil der Diskussion, können andere Diskussionsteilnehmer umstimmen und dem Bürokraten beim Verständnis des Community-Konsens behilflich sein.

Cache leeren Benutze den untenstehenden Bearbeiten-Link, um die eingebundene Seite zu bearbeiten.

Requests for adminship

Wenn die Anfragen erledigt sind, sollten die hier aufgelisteten Seiten in Commons:Administrators/Archive archiviert werden.

  • Bitte lies Commons:Administratoren, bevor Du hier postest oder abstimmst. Jeder angemeldete Benutzer kann wählen, wobei diejenigen, die wenige oder keine vorherigen Bearbeitungen haben, möglicherweise nicht vollständig gezählt werden.

Martin Urbanec

Vote

Martin Urbanec (talk · contributions · deleted user contributions · recent activity · logs · block log · global contribs · CentralAuth)

Scheduled to end: 17:19, (UTC)

Hello everyone,

my name is Martin Urbanec, and I am mainly active at the Czech Wikipedia, where I serve as an admin, bureaucrat and CheckUser (used to be an arbitrator as well). Globally, I serve as a Wikimedia Steward. You can also know me from the Wikimedia Technical community (see Phabricator), mainly focused on site requests.

If promoted, I would like to directly deal with cross wiki abusers that often make their way to Wikimedia Commons, help the counter vandalism unit, and also help to decrease the backlog Commons has. Given I am also an OTRS agent, I would also like to use the bit to undelete images with a late-delivered permission in OTRS. I am also happy to lend my hand with whatever needs to be done, and my RfA isn't limited to those fields.

I have general knowledge about the copyright law (mainly in Czech Republic's copyright code), as well as Commons's licensing requirements, and I believe I can make use of such knowledge as a Commons admin.

If there is anything else you would like to know, please let me know, I am happy to answer any questions.

Best, --Martin Urbanec (talk) 17:19, 30 July 2020 (UTC)

Votes

  •   Support 1st vote and first comment. This might sound similar to YouTube comments. // Eatcha (talk) 17:40, 30 July 2020 (UTC)
  •   Support - obviously a competent user from their permissions elsewhere ~~ Alex Noble/1-2/TRB 17:45, 30 July 2020 (UTC)
  •   Support --Rschen7754 18:01, 30 July 2020 (UTC)
  •   Support -Killarnee (CTU) 18:16, 30 July 2020 (UTC)
  •   Support Why not Martin? You are clearly a trusted and helpful user. T CellsTalk 19:03, 30 July 2020 (UTC)
  •   Support. --- FitIndia Talk 19:16, 30 July 2020 (UTC)
  •   Support Christian Ferrer (talk) 20:23, 30 July 2020 (UTC)
  •   Support I have positive experiences of interacting with Martin Urbanec from SWAT. 4nn1l2 (talk) 20:49, 30 July 2020 (UTC)
  •   Oppose Majority of your contributions are reverts and global renaming. You do very little maintenance. I'd prefer a candidate who's engaged with Commons, not just experiences from different projects. 1989talk 20:57, 30 July 2020 (UTC)
      Addendum Tagging plain text and signature images as no permission? Not good... 1989talk 20:30, 1 August 2020 (UTC)
    Agreed, I should be more careful with the "select all" feature when doing bulk tasks. Reverted myself for the signatures. I think the other images does not fall below the treshold of originality, and as such, needs a release. --Martin Urbanec (talk) 20:41, 1 August 2020 (UTC)
    Like this one? 1989talk 20:44, 1 August 2020 (UTC)
    How about this one? 1989talk 21:19, 1 August 2020 (UTC)
    It isn't purely text, someone had to think to create both images. It may look simple, but it might also took hours to create (I mean, for the original author). Moreover, both images are probably not their own work anyway. --Martin Urbanec (talk) 21:23, 1 August 2020 (UTC)
    That doesn't matter. Both images + more you tagged are clearly in the public domain. 1989talk 21:25, 1 August 2020 (UTC)
      Oppose exactly per this. 1234qwer1234qwer4 (talk) 21:22, 7 August 2020 (UTC)
  •   Oppose Per 1989 and your OTRS work is absolutely unacceptable. I'm greatly concerned, for example, that you do not know the difference between the subject of the photo and the author of a photo. Copyright initially vests with the latter, yet you accepted the OTRS from the former for File:Ragy Thomas photo.jpg, with no evidence of a transfer (the OTRS interface has a template explicitly for such a scenario!) For File:Marieme 2020.jpg you accepted a ticket with no contact or evidence of permission from the author. I do not trust that you understand basic aspects of copyright or our COM:EVID requirements. Эlcobbola talk 21:30, 30 July 2020 (UTC)
    • Thank you for your vote. However, I disagree with your evaluation. As far as I can see, the first photo's permission was sent by the noted author (Eric Egerton) rather than subject (Ragy Thomas). Moreover, this photo is very likely to be a corporate authorship, and in many jurisdictions, the employer holds the permission by law, with no specific need for transfer. That is why the permission always needs to contain a claim of authorship. In the second case, the photo's permission was indeed sent by the noted author, from their personal mailbox. --Martin Urbanec (talk) 22:00, 30 July 2020 (UTC)
      • You're correct in the first regard; I referenced the wrong image and as I cannot find the one to which I intended to refer, I've struck that issue and am happy to consider it thus non-existent and my error--my apologies. I find, however, your comment regarding corporate authorship concerning. Corporations generally do not keep professional photographers on staff (especially small ones like Sprinklr) and independent contractors would generally retain intellectual copyrights. That image notwithstanding, you've not addressed the second image and, as supplemental concerns: for File:Mathias Kiss.jpg you accepted permission from a person who is not the author stated in the metadata; you accept images (e.g., File:Jos.Jindra Kunvald 1958 - 30 km b.jpg) from people claiming images are from "family archives" with no evidence that 1) a family member was the photographer and 2) that the sender of the correspondence was the heir who inherited the intellectual property. There are tickets from a theatre formed in 1990 purporting to license images that appear from the turn of the 20th century. Etc. Again, I am concerned that you do not have an adequate appreciation for parties who genuinely hold copyrights and of our evidence requirements for the same. Эlcobbola talk 22:58, 30 July 2020 (UTC)
        • Hello, I did react to the second image - I said that the release sent to OTRS was sent by the author as noted in the Commons file. Moreover, the release was signed by the author.
        • Ad File:Mathias_Kiss.jpg, the file doesn't contain any metadata, but is large enough so it is plausible it is the original. I wasn't able to find the image elsewhere, and the release doesn't have any obvious issues. It is correct the OTRS agents can never be 110% sure about the image's status, because copyright law allows for so many possibilities - and in most (if not all) cases, only the author can be sure about the copyright status. The sense of releases is to shift the responsibility to someone else. It is similar to licenses in the real world. If someone claims they are an author, offers you a license, you pay for it, and use the work, you live in good faith your usage is authorized. Of course, it is possible you paid a frauder, but it allows you to shift the damages elsewhere. This applies to other listed cases as well.
        • Ad File:Jos.Jindra_Kunvald_1958_-_30_km_b.jpg, the release does actually state "I, Name, birth certificate number XXX, heir of copyright, agree...". Obviously, that may or may not be true - in those cases, OTRS agents have to more or less rely on the individuals sending the release they are correct - as agents are not law enforcements, they can virtually never be absolutely sure, regardless how good permission you show.
        • Ad File:Divadlo_Tábor_Oskar_Nedbal.jpg, I admit there was a tiny mistake on my end (the release states "I, author", while it should likely say "I, representative of the copyright holder"), but the release is otherwise fine. You are not right the theatre was formed in 1990. The theatre exists there since at least 1840, see cs:Divadlo_Tábor, or even the link you posted. As any theatre, the theatre in Tábor changed names over time, and in 1990, it was renamed to Oskar Nedbal Theatre, as a sign of appreciation to Nedbal. Change of names doesn't affect the corporation itself, it is still one corporation, having all the rights it had before, including the picture's copyright.
        • --Martin Urbanec (talk) 12:19, 31 July 2020 (UTC)
  •   Oppose I've thought about this and feel there is a degree of badge collecting here. I'm guessing current activity levels will reduce after this RfA ends. --Herby talk thyme 11:01, 31 July 2020 (UTC)
  •   Oppose - I'm with Herby. Stewarts only should be in seldom and special exceptions become Commons Admins. Only if they really very active here. and less than 9.000 Edits in 5+ years is definetly not enogh to show enough knowledge in the here required fields of work. -- Marcus Cyron (talk) 14:28, 31 July 2020 (UTC) PS: a short look into MU's world: asking for a global ban for machine translations. Global bans are not for such things. Even you are not understand those things how should I know you understand Commons rules?
  •   Support I have very good experience with Martin from cswiki. I don't agree that Martin is just a "badge-collector". — Draceane talkcontrib. 15:02, 31 July 2020 (UTC)
  •   Oppose per Herby --DCB (talk) 19:59, 31 July 2020 (UTC)
  •   Support, of course!   — Jeff G. please ping or talk to me 01:33, 1 August 2020 (UTC)
  •   Support. – Ammarpad (talk) 04:07, 1 August 2020 (UTC)
  •   Support Trusted, LGTM --DannyS712 (talk) 05:01, 1 August 2020 (UTC)
  •   Support I personally don't agree being Martin termed as Badge or Hat collector. They have been quick and helpful when it comes in Steward work and I believe given an opportunity they will do their best here. Also this rights will help them in their x-wiki work. Best wishes --✝iѵɛɳ२२४०†ลℓк †๏ мэ 08:58, 1 August 2020 (UTC)
  •   Support. —Hasley 16:06, 1 August 2020 (UTC)
  •   Weak support In generally I feel that they will be a reasonable admin. I am a little scared about the zealous answers to the copyright questions below. I would not want admins to fail to see context and to always assume copyright violation when a photo is made in an inaccessible interrior. A lot of times it can mean a violation, but far from always. Hopefully they will grow. ℺ Gone Postal ( ) 20:15, 1 August 2020 (UTC)
  •   Support Jianhui67 TC 08:55, 2 August 2020 (UTC)
  •   Oppose I wanted to support because your steward work is excellent but a basic understanding of copyright law seems lacking. Effort has nothing to do with copyright for example. At least not in Europe and the US. I don't expect admins to understand every aspect of copyright law (no admin does) but I do expect them to be familiar with our basic policies, guidelines and help pages. Natuur12 (talk) 10:41, 2 August 2020 (UTC)
  •   Oppose Sorry, not convinced + per others. Some of your uploads seem not properly licensed, such as [1], [2] --A.Savin 15:05, 2 August 2020 (UTC)
  •   Support. Experienced with the tools and language skills is a plus. So, opposing votes are not convincing. Érico (talk) 21:04, 2 August 2020 (UTC)
    What could be more convincing for opposing a Commons adminship applicant, rather than apparently unsatisfactory knowledge of Commons' Licensing policy, Érico? Just curious, --A.Savin 14:23, 5 August 2020 (UTC)
  •   Support Sure. --আফতাবুজ্জামান (talk) 16:53, 3 August 2020 (UTC)
  •   Support --janbery (talk) 17:59, 3 August 2020 (UTC)
  •   Oppose Sorry, for several reasons mentioned above me from badge collection to low activity levels as low as only 254 deleted edits? and understanding of copyrights, wrongly handled OTRS tickets as mentioned above. And importantly I don't understand the need to collect so many rights on several projects like this? When one is already taking care of many responsibilities! QueerEcofeminist "cite! even if you fight"!!! [they/them/their] 14:55, 4 August 2020 (UTC)
  •   Support --Pimpinellus((D)) • WikiMUC • 13:41, 5 August 2020 (UTC)
  •   Weak oppose Though I appreciate Martin's Steward work, the answers from him shows that he doesn't have a clear understanding on copyright and OTRS issues. --A1Cafel (talk) 14:44, 5 August 2020 (UTC)
  •   Oppose good Steward/Meta User, but because of the concerns raised by A.Savin, etc. i cannot support the RFA at this time. --Steinsplitter (talk) 15:46, 5 August 2020 (UTC)
  •   Support: If I'm not sure making a decision I leave it to others. Martin will do it the same way. So to me there is no reason to oppose. --Achim (talk) 07:48, 6 August 2020 (UTC)
  •   Support Minoraxtalk (formerly 大诺史) 09:05, 6 August 2020 (UTC)
  •   Support. In my opinion Martin will not break Commons, but he MUST thoroughly learn copyright, use his powers with caution and ask advice, when in doubt. Taivo (talk) 10:36, 6 August 2020 (UTC)
  •   Support per Achim55 and Tiven2240. -- CptViraj (talk) 10:51, 6 August 2020 (UTC)
  •   Support We have deletion requests open back to December 2019, so if Martin, or anybody else qualified in the same way, offers a helping hand, this shouldn't be refused. --Krd 09:49, 7 August 2020 (UTC)
  •   Support. -- Geagea (talk) 10:37, 7 August 2020 (UTC)
  •   Weak support, with the same reasons as Krd and the same serious reservations as Taivo. —Mdaniels5757 (talk) 17:48, 7 August 2020 (UTC)
  •   Support--Path slopu (Talk) 05:54, 8 August 2020 (UTC)

Comments

  •   Question You are patrolling new uploads, and come across a photo which is claimed to be "own work". Under what conditions would you accept the claim without further proof, and when would you demand more evidence? In the latter case, please list the different kinds of evidence that the uploader might need to supply depending on the situation. -- King of ♥ 04:42, 31 July 2020 (UTC)
    • Hello, thank you for the question. Firstly, I would search the photo using the "search by image" functionality of Google Images. If found elsewhere, I would always require a release. If not found elsehwere, I would accept the photo if it looks like "likely" it is their own work - it seems shootable according to the information present in the image. For portrait photos of well-known persons, especially if they look professional, I would generally require a release sent to the OTRS, as it is unlikely a random person on the street would be able to shoot that photo. Similary, photos shooted in publicly-unavailable interior places would generally warrant a release. In another words, as long as the author's authorship claim seems to be plausible, I would generally not have an issue with patrolling the photo. --Martin Urbanec (talk) 11:56, 31 July 2020 (UTC)
  •   Question A monument in the United States was built and placed in a public area in 1948, and the sculptor died in 1965. How would you determine whether photos of the monument can be uploaded to Wikimedia Commons? -- King of ♥ 04:42, 31 July 2020 (UTC)
    • Hello, thank you for your question. Freedom of panorama concept in the Unites States applies only to "architectual works" in public areas, where architectual work is defined as "design of a building as embodied in any tangible medium of expression, including a building, architectural plans, or drawings", and building as "humanly habitable structures that are intended to be both permanent and stationary, such as houses and office buildings, and other permanent and stationary structures designed for human occupancy, including but not limited to churches, museums, gazebos, and garden pavilions". Those definitions exclude monuments, statues and similar. Hence, it is necessary to assess if the monument is still protected by copyright, or if it is in the public domain. In the United States, works first published before 1964 (which means the monument you mentioned is in this group) are protected for 28 years after publication, unless the copyright owner filled for renewal between the 27th and 28th year of copyright term. According to what you wrote, the author died before they could fill for renewal. As such, the right to renewal is automatically vested in their heirs. [3]. If author's heirs did fill for a renewal, the monument is still copyrighted (and as such, inadmissible unless a release is sent to OTRS). If they did not (which is likely, but I cannot be 100% sure), the work is in public domain, and can stay at Commons. --Martin Urbanec (talk) 11:56, 31 July 2020 (UTC)
      • Good answer, but incomplete. What else must the copyright holder have done to retain their copyright, besides registering and renewing with the Copyright Office? (Hint: At the very beginning.) -- King of ♥ 13:26, 31 July 2020 (UTC)
        • Sorry. They would need to include a copyright notice, which was required prior 1989. --Martin Urbanec (talk) 14:02, 31 July 2020 (UTC)
          • You are right that pre-1989 works in general require a copyright notice, but the situation is a bit different for public art. Since 1978, placing a work in public view is no longer considered publication; the copyright holder must have authorized the sale or distribution of copies of the work to the public. So in the vast majority of cases, only pre-1978 public art can be public domain due to no notice, as most post-1978 public art is considered unpublished. See Commons:Public art and copyrights in the US. -- King of ♥ 14:46, 31 July 2020 (UTC)
            • Thanks for the clarification. According to the page you linked, putting a monument in public area would be considered publishing prior to 1978, so I feel the copyright notice should be there for the monument to be covered. --Martin Urbanec (talk) 21:25, 1 August 2020 (UTC)
              • Selfish question just for my own information. Is it "a thing" that there are statues erected prior to 1978 that have little copyright notices at the bottom somewhere? That seems somewhat counter-intuitive. GMGtalk 12:25, 2 August 2020 (UTC)
  •   Comment I think will be good idea to extend voting for week. --EugeneZelenko (talk) 13:29, 7 August 2020 (UTC)
    Seems like a waste of time. Happened previously and nothing much changed besides baseless accusations being in place, which to this day is still there... By the way, there can't be exceptions. Admin nominations being extended should be part of the guidelines (COM:A#Voting). Not sure if the changes should happen through the bureaucrat team or community discretion. 1989talk 14:04, 7 August 2020 (UTC)
    Wasn't aware of this already being a bureaucrat standard. Never mentioned in Commons:Administrators, so I added it in. 1989talk 12:29, 8 August 2020 (UTC)
  • I support. Don't think it's a a waste of time. -- Geagea (talk) 18:01, 7 August 2020 (UTC)

Bürokratenkandidatur starten

Wenn die Anfragen erledigt sind, sollten die hier aufgelisteten Seiten in Commons:Bureaucrats/Archive archiviert werden.

  • Bitte lies Commons:Bürokraten, bevor Du hier postest oder abstimmst. Jeder angemeldete Benutzer kann wählen, wobei diejenigen, die wenige oder keine vorherigen Bearbeitungen haben, möglicherweise nicht vollständig gezählt werden.

No current requests.

CheckUserkandidatur starten

Wenn die Anfragen erledigt sind, sollten die hier aufgelisteten Seiten in Commons:Checkusers/Archive archiviert werden.

  • Bitte lies Commons:Checkuser, bevor Du hier postest oder abstimmst. Jeder angemeldete Benutzer kann wählen, wobei diejenigen, die wenige oder keine vorherigen Bearbeitungen haben, möglicherweise nicht vollständig gezählt werden.

No current requests.

Oversightkandidatur starten

Wenn die Anfragen erledigt sind, sollten die hier aufgelisteten Seiten in Commons:Oversighters/Archive archiviert werden.

  • Bitte lies Commons:Oversighter, bevor Du hier postest oder abstimmst. Jeder angemeldete Benutzer kann wählen, wobei diejenigen, die wenige oder keine vorherigen Bearbeitungen haben, möglicherweise nicht vollständig gezählt werden.

No current requests.

Archiv

Du findest bisherige Adminkandidaturen unter Commons:Administrators/Archive.

Siehe auch