Commons:Администраторы

Кто такой администратор?

Технически

Администраторы — это участники с расширенными техническими возможностями, а именно:

• удаление и восстановление страниц, изображений и других файлов, а также просмотр их удалённых версий;
• установка и снятие защиты страниц, редактирование полностью защищённых страниц;
• блокировка и разблокировка зарегистрированных участников, IP‐адресов или диапазонов;
• редактирование интерфейсных страниц в пространстве имён MediaWiki;
• скрытие отдельных версий файлов или других страниц;
• переименование файлов (доступ к этому инструменту имеют также участники из группы «Переименовывающие файлы»);
• быстрый откат правок (доступ к этому инструменту имеют также участники из группы «Откатывающие»).

Всё это вместе известно как «инструменты администратора».

Роль в сообществе

Администраторский доступ предоставляется по результатам открытого обсуждения/голосования опытным и заслуживающим доверия членам сообщества, знакомым с правилами Викисклада, и согласившимся взять на себя дополнительную работу по его обслуживанию. За исключением функций, требующих применения инструментов администратора, пользователи не получают со статусом администратора какого‐либо особенного влияния, и их вклад в обсуждениях и голосованиях имеет такой же вес, как и вклад обычного участника. Конечно, некоторые администраторы более влиятельны, но это не результат их администраторских полномочий самих по себе, а результат личного доверия сообщества к ним.

Administrators as of August 2016 [+/−]

Listing by language Listing by date Listing by activity

Number of Admins: 241 -revi, ko, en-3 (global renamer) ~riley, en, fr-1, es-1 1Veertje, nl, en-4, de-1, fr-1 32X, de, en-2, hsb-1, ru-1 99of9, en (bureaucrat, global renamer) A.Savin, ru, de-4, en-2 Achim55, de, en-3, nds-3, la-2 AFBorchert, de, en-3 (bureaucrat) Ahonc, uk, ru-4, en-2, de-1 (global renamer) Aka, de, en-3 Alan, es, eu-3, en-2 Alison, en, ga-3, fr-2, gd-1 Alno, fr, en-3, es-2, pt-1 Alpertron, es, en-3 Amada44, de, en-3, fr-1 Angr, en, de-4, fr-2, ga-2, la-2, cy-1 Ankry, pl, en-2, ru-1 AnRo0002, de, en-2, fr-2, es-1 Anthere, fr, en-3 Aude, en, ar-2, de-2, es-3 Avenue, en, de-1, fr-1, it-1 Avraham, en, he-2 (oversighter, steward) AzaToth, sv, en-4 Badseed, el, en-3, it-1 Barcex, es, en-2, fr-1 Bastique, en, fr-3, es-2, la-2, ga-1 Basvb, nl, en-3, de-2 Benoit Rochon fr, en-4 Beria, pt, en-2, es-2 Billinghurst, en Blackcat, it, en-3, fr BrightRaven, fr, en-3, nl-2, es-2, zh-1 Butko, ru, uk-2, en-1 Cambalachero, es, en-3 Captain-tucker, en ChrisiPK, de, en-3, fr-1 Christian Ferrer, fr, en-2 Ciell, nl, en-2, de-1 Common Good, en Cookie, es, en-2 Courcelles, en, es-2, fr-2 Coyau, fr, en-1 Czar, en DaB., de, en-1 Dantadd, it, pt, en-3, es-3, fr-3, gl-3, ca-2, ro-1, el-1 Darwinius, pt, en-3, es-2, fr-2, gl-2, ca-1, it-1, oc-1 Davepape, en David Levy, en De728631, de, en-5 Dereckson, fr, en-3, de-1, nl-1 DerHexer, de, en-3, grc-3, la-3, es-1 (steward) Dharmadhyaksha, mr, en-3, hi-3 DMacks, en Didym, de, en-2, fr-2 Dschwen, de, en-3, fr-1 (bureaucrat) D-Kuru, de, en-2, it-1 Ebrahim, fa Edgar181, en, de-1, fr-1, es-1 Elcobbola en, de (checkuser) Eleassar, sl, en-3, de-2, fr-2 Elitre, it, en-3, fr-2 Ellin Beltz, en (bureaucrat) Elya, de, en-3, uk-2, ru-1 Emha, de, bar, en-3, fr-1 EPO, da, en-3, de-1 Érico, pt, en-2, es-1 (global renamer) EugeneZelenko, ru, be, en-2, bg-1, pl-1 (bureaucrat) Ezarate, es-3, en-1 Fanghong, zh, en-2, fr-1 Flominator, de, als, en-3 FunkMonk, da, en-4, no-3, fo-2, sv-2, de-1, es-1 Geagea, he, ka-3, en-3, ru-1 Geni, en George Chernilevsky, ru, uk-3, de-2, en-2, bg-1, la-1, be-1, fr-1 Gestumblindi, als, de, en-3 Gnangarra, en Golbez, en, ja-2 Green Giant, en, de-1, fr-1 grin, hu, en-3, de-1 Gruznov, ru, en-1, fr-1 Hedwig in Washington, de, en-4, nds-1 Hekerui, de, en-4 Herbythyme, en, fr-2, es-1, it-1 Hesperian, en HJ Mitchell, en Howcheng, en, ja-2 Huntster, en Hystrix, de, en-1 H-stt, de, en-4, fr-1 Indeedous, de, en-3, fr-2 INeverCry, en, es-1, ru-1 Infrogmation, en, es-1 Jameslwoodward, en, fr-1 (bureaucrat, checkuser) January, en Jaqen, it, en-2 Jarekt, pl, en JarrahTree, en, id-1 Jastrow, fr, en-3, ro-2, de-1, it-1 Jcb, nl, en-3, es-3 Jcornelius, de, lt-2, la-2, en-2, pt-2, fr-1 Jdforrester, en Jean-Frédéric, fr, en-4, es-1 JGHowes, en, fr-2, de-1 Jianhui67, en, zh-3, ms-1 (global renamer) Jmabel, en, es-3, ro-2, de-1, ca-1, it-1, pt-1, fr-1 Joergens.mi, de, en-3 John Vandenberg, en Josve05a, sv, en-3 Julo, pl, en-2, de-1, ru-1 JuTa, de, en-2, fr-1 (bureaucrat) Jusjih, zh, en-3, fr-1, ko-1 Kaldari, en Kallerna, fi, en-3, sv-2, de-1 Kanonkas, no, en-4, nn-3, da-2, sv-2, de-1 (bureaucrat) Kelly, en King of Hearts, en, zh-3, es-2 Klemen Kocjancic, sl, en-3, de-2, hr-1, bs-1 Krd, de, en-3 (bureaucrat, checkuser) Krinkle, nl, en-3, de-2 KTo288, en, zh-4 Kwj2772, ko, en-2 Leit, de, en-3, fr-1 Léna, fr, en-3, es-1 Leyo, gsw, de, en-3, fr-3, es-1, la-1 Lokal Profil, sv, en-4, pt-2, fr-1 Lymantria, nl, de-2, en-2, fy-2, fr-1, zea-1 Magog the Ogre, en, es-2 (checkuser) Maire, pl, en-4, es-2, fr-2, de-2, ru-1 (global renamer) Marcus Cyron, de, en-2 Mardetanha fa, az, en-3, tr-2, ar-1 (steward) Martin H., de, en-2 Masur, pl, en-3, de-1 Matanya, en, he (steward) Materialscientist, en-4, ru-4, nl-3, fr-1, es-1 Mattbuck, en, fr-1, la-1 Maxim, ru, en-3, fr-2 MBisanz, en (steward) McZusatz, de, en-3, es-1, la-1 swg-1 Mentifisto, en, mt, it-2 (steward) MichaelMaggs, en, fr-1 (bureaucrat) Micheletb, fr, en-3, it-1, es-1 Missvain, en Mitchazenia, en, es-2 Miya, ja, en-2 Mmxx, fa, en-3 Mono, en Morgankevinj, en, es-1, la-1 Mormegil, cs, en-2, de-1 M0tty, fr, en-1 MPF, en, da-2, de-1, fr-1 Multichill, nl, en-3, de-1, fr-1 Mys 721tx, zh, en-3 (global renamer) Nagy, de, en-3, fr-2, es-1, sv-1 NahidSultan, bn, en-3, bpy-1 Natuur12, nl, en-3, de-1 Neozoon, de, en-4, nl-4, fr-2 Nick, en, sco-2, fr-1 Niklem, ru, en-3 Nilfanion, en, fr-1 NordNordWest, de, en-3 notafish, fr, en-4, de-3, es-2, it-2 Nyttend, en, ang-1 odder, pl, en-4, de-2 (bureaucrat, oversighter) Okki, fr, en-2 Otourly, fr, en-2, it-1 P199, en, nl, fr-2, tl-2, de-1 Pi.1415926535, en, es-2 PierreSelim, fr, en-3, es-1 (oversighter) Pitke, fi, en-4, sv-2 Platonides, es, en-2, fr-1 Pleclown, fr, en-3 Poco a poco, es, de-4, en-3, fr-2, it-2, pl-2, pt-1 Podzemnik, cs, en-2 Polarlys, de, en-2, fr-1, no-1 Powerek38, pl, en-4, fr-2, es-1, de-1 PumpkinSky, en, de-2 Putnik, ru, en-2 Pyb, fr, en-2 Pymouss, fr, en-3, de-2, it-2, he-1 Ragesoss, en, de-1, fr-1 Ra'ike, de, en-2 Rama, fr, en-3, de-2, la-2, es-1, it-1, ja-1 (oversighter) Rastrojo, es, en-3, fr-2, eo-1 Raymond, de, en-3, nl-1 (oversighter) Rehman, en, si-1 Reinhard Kraasch, de, en-3 Revent, en Rillke, de, en-2, fr-1 Rimshot, de, en-4, fr-2, it-1 Rodhullandemu, en, fr-1, de-1, sv-1 Romaine, nl, en-3, de-2, af-1, fr-1 Ronhjones, en, fr-1 Rosenzweig, de, en-3, fr-1, la-1 Royalbroil, en, es-1 RP88, en, de-1 Rubin16, ru, tt, en-3 (global renamer) Rudolphous, nl, en-3, de-2 Sanandros, als, de, en-3, fr-1 Sandstein, als, de, en-4, fr-3, it-1 Sealle, ru, en-4, pl-2, sk-2, uk-2 Shizhao, zh, en-1, ru-1 Siebrand, nl, en-3, fr-1, de-1 Sphilbrick, en Spiritia, bg, en-3, ru-2, mk-2, de-1 Sreejithk2000, ml, en-3, hi-3, ta-1, kn-1 Steinsplitter, bar, de-4, it-3, en-1 (global renamer) Stifle, en, ga, fr-2, de-1 Storkk, en, fr-3, de-2, eo-2 Tabercil, en Taivo, et, en-3, ru-3, de-1 Tarawneh, en, ar, de-1 Techman224, en Teles, pt, en-3, es-2 (steward) Thibaut120094, fr, en-2, ja-2 Thuresson, sv, en-3, no-2 Tom, en, es-1 Trijnstel, nl, en-4, de-1, fr-1 (checkuser, steward) tsca, pl, en, da Túrelio, de, en-3, es-1 VIGNERON, fr, de-2, en-2, zh-1 Waldir, pt, en-3 Wdwd, de, en-2 Whym, ja, en-2 Wikitanvir, bn, en-3, as-2, bpy-1 (steward) WJBscribe, en, fr-3, de-1 (global renamer) Wsiegmund, en, fr-1, es-1 Wutsje, fy, nl, en-3, de-2, fr-1 Wuzur, de, en-3 wvk, de, en-4, fa-3, fr-2 Yann, fr, en-3, hi-2, gu-1 Yarl, pl, en-2, de-1, ru-1 Yasu, ja, en-2, de-1 Ymblanter, ru, en-3, de-2, fr-2, nl-2, it-1, es-1 Yuval Y, he, en-3 Zhuyifei1999‎, zh, en-4 Zzyzx11, en, es-1, fr-1 とある白い猫, en, tr, az-3, ja-2, fr-1, nl-1 CommonsDelinker, (bot) CommonsMaintenanceBot, (bot) see request GifTagger, (bot) see request KrinkleBot, (bot) see request The system currently recognizes 241 administrators. If that is not the last number in the list above, there is an error in the list.

Как стать администратором

Требования к кандидатам

Вы можете запросить административный доступ, если удолетворяете следующим критериям:

• Вы имеете достаточный опыт работы на Викискладе. Вы были редактором по меньшей мере 2 месяца, понимаете и согласны с задачами проекта.
• У вас есть персональная страница участника на Викискладе и вы сделали здесь как минимум 100 правок (загруженных файлов или исправлений в тексте).
• Вы согласны соблюдать соответствующие правила и соблюдать консенсус участников Викисклада.

Процесс номинации

Номинация обычно продолжается семь дней для голосования и комментариев. За предоставление статуса администратора должны проголосовать 75% от принявших участие в голосовании, но не меньше 4 человек. В этом случае, запрос должен быть направлен бюрократу, который проведет необходимую работу.

Неактивный администратор

Как и на Мета-вики, неактивный администратор может быть лишён статуса. В соответствии с этим правилом, любой администратор, в течение продолжительного времени не использующий администраторские инструменты, может быть лишён администраторских прав. Под «неактивностью» понимается отсутствие правок за последние 6 месяцев и менее 50 правок за последний год. Администраторы, лишённые статуса по причине неактивности, могут снова подать заявку на статус администратора на общих условиях.

Сделать запрос на присвоение статуса

администратора

Use the box below, replacing username with your username:

См. также: Commons:List of administrators

бюрократа

Use the box below, replacing username with your username:

См. также: Commons:List of bureaucrats

чекъюзера

Use the box below, replacing username with your username:

См. также: Commons:List of checkusers

ревизора

Use the box below, replacing username with your username:

См. также: Commons:List of oversighters

Запросить разрешение на использование бота

Use the box below, replacing botname with your bot's username:

See Commons:Bots/Requests for the whole process.

Кандидаты

Purge the cache

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

• Oversighter: Commons:Oversighters/Requests
• Checkuser: Commons:Checkusers/Requests
• Bureaucrat: Commons:Bureaucrats/Requests
• Administrator: Commons:Administrators/Requests
• License reviewer: Commons:License review/requests
• Bot: Commons:Bots/Requests

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

How to comment and vote

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  Support votes or  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

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.

Requests for CheckUser rights

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.

Requests for bureaucratship

watch

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

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.

No current requests.

Requests for license reviewer rights

No current requests.

Requests for permission to run a bot

watch

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.

Josvebot (talk · contribs) 3

Operator: Josve05a (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: Move files from Category:Logos to Category:Unidentified logos

Automatic or manually assisted: Automatic

Edit type (e.g. Continuous, daily, one time run): One time run, with option to run multiple times if needed

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

Bot flag requested: (Y/N): N

Programming language(s): AWB

Josve05a (talk) 01:27, 8 August 2016 (UTC)

Discussion

• Please make test run. --EugeneZelenko (talk) 14:05, 8 August 2016 (UTC)

@EugeneZelenko: 50 edits  Done Josve05a (talk) 15:04, 8 August 2016 (UTC)

Please don't use section headers in edit summaries. Will be good idea to follow MediaWiki:Gadget-HotCat.js style of edia summaries, or replace > with to. --EugeneZelenko (talk) 14:00, 9 August 2016 (UTC)

@EugeneZelenko: Regarding the "< vs to", I totally agree, and will modify. Regarding the section headers, I'm not sure if it is able to be turned off in AWB... Josve05a (talk) 14:12, 9 August 2016 (UTC)

Please read the manual. ~riley (talk) 00:09, 10 August 2016 (UTC)

I have read that. Still can't find the setting... Josve05a (talk) 15:53, 14 August 2016 (UTC)

@Josve05a: Options > "Do not use section edit summaries". ~ Rob₁₃^Talk 15:29, 19 August 2016 (UTC)

AvicBot (talk · contribs)

Operator: Avicennasis (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: Running toollabs:ahechtbot/Paolo_Monti.txt per this request.

Automatic or manually assisted: Automatic

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

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

Bot flag requested: (Y/N): N

Programming language(s): Pywikibot

sısɐuuǝɔıʌ∀ (diskuto) 18:41, 30 July 2016 (UTC)

Discussion

• Please make a test run. --EugeneZelenko (talk) 14:01, 31 July 2016 (UTC)

34 edits done. There was one hiccup edit which I corrected in the code. Edit summaries were trimmed as the length was throwing errors. I can do more, if needed, but this should demonstrate the code. sısɐuuǝɔıʌ∀ (diskuto) 15:31, 31 July 2016 (UTC)

Could consecutive changes like this be done in one single edit? --Krd 07:16, 1 August 2016 (UTC)

Unfortunately not. Replace.py only allows for one substitution per run. sısɐuuǝɔıʌ∀ (diskuto) 06:27, 2 August 2016 (UTC)

The you have to modify Replace.py or write a own script :-). --Steinsplitter (talk) 10:48, 2 August 2016 (UTC)

Here a blank line (\n) has been left. And we use "Bot: .*" on commons, not ".* (bot edit)" --Steinsplitter (talk) 10:56, 2 August 2016 (UTC)

There's nothing in the bot policy that prohibits multiple edits, nor mentions edit summaries. Even User:SteinsplitterBot has only used "Bot: .*" on 290 out of the last 500 edits it's done. :-) Though it's easy (if trivial) to change the edit summary. sısɐuuǝɔıʌ∀ (diskuto) 15:32, 2 August 2016 (UTC)

You should follow standard practices, multiple edits aren't. The ad hominem argument here is not helpful at all. --Steinsplitter (talk) 15:50, 2 August 2016 (UTC)

If this were an ongoing task, I could see the value of combining edits. As this is a one-time run, however, I don't think it'll be an issue. I hope that multiple edits alone are not reason enough to decline this request. I don't have the time to write a new script to combine them. This request is only to try and help an outstanding request of over two months. sısɐuuǝɔıʌ∀ (diskuto) 16:14, 2 August 2016 (UTC)

How many pages are effected by this task? Or more specifically in this case, how many edits are estimated for this task? I as well do not support the bot making multiple edits for the same task on the same page because the operator is using a generic script. ~riley (talk) 04:55, 6 August 2016 (UTC)

4645 categories matching the criteria, most containing one file. Guessimating an average of 1.3 files per category, that's 6038ish pages, times two edits as currently proposed, around 12077 edits. Quite larger than I had originally anticipated. I will see if I can put something together to merge the two edits in question down to one. sısɐuuǝɔıʌ∀ (diskuto) 06:40, 6 August 2016 (UTC)

Wyangbot (talk · contribs)

Operator: Wyang (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: Batch uploading Ancient Chinese character images for use on Wiktionaries (PD-ancient).

Automatic or manually assisted: Mostly automatic (supervised).

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

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

Bot flag requested: (Y/N): Y.

Programming language(s): Python (Pywikibot)

Wyang (talk) 01:44, 8 July 2016 (UTC)

Discussion

• Please don't make large batch uploads before this discussion end.
• Please create bot user page (see {{Bot}}).
• Please wrap all text English text in {{ACClicense}} in {{en}} (but this is not related to bot directly).

EugeneZelenko (talk) 13:57, 8 July 2016 (UTC)

• Setting aside the fact that the user has already run this script on their main account for a total of 4,256 uploads, and then proceeded to make a bot account only to do another ~4k uploads and ignore almost every instruction on Commons:Bots/Requests.. I am opposed to the only page content being one single template (i.e. File:ACC-j15190.svg contains only {{ACClicense|出|oracle|oracle|j15190||}}). Please improve the edit summary by giving a short explanation instead of replicating the page content in the edit summary. "See the date of uploads shown in the "File history" section." and "see contributor name shown in the "File history" section." are also not satisfactory to Common's standards. ~riley (talk) 20:12, 10 July 2016 (UTC)

  This is the default format for the Ancient Chinese character project; see for example File:馬-bigseal.svg. I'd love to write a separate summary but mw:Manual:Pywikibot/upload.py does not seem to allow for customised edit summaries. Wyang (talk) 22:19, 10 July 2016 (UTC)

  Agree, the single line is the standard form for the ACClicense template. But see below. Michelet-密是力 (talk) 06:47, 16 July 2016 (UTC)

Please help make this as prompt as possible - pages on the English Wiktionary are waiting for these images to be uploaded to display their contents properly (wikt:Module:zh-glyph). Newly uploaded entries are made to conform to existing formats. This is a one-time upload so even a temporary bot flag would be sufficient. Wyang (talk) 22:25, 10 July 2016 (UTC)

Pages on the English Wiktionary are patient (supposing they have an inner life), and so are English Wiktionary users. If the new format is a problem, just revert to the previous one. Michelet-密是力 (talk) 06:47, 16 July 2016 (UTC)

Any updates? It has been more than one week now. Entries on the English Wiktionary are being compromised. Wyang (talk) 02:10, 16 July 2016 (UTC)

Discussion 2 - objections

Some problems and objections, these uploads are not acceptable, at least in this format :

• Massive uploads from public accessible databases are legally a problem. Any single character by itself is public domain, given its old age, but a database in itself is protected, even when publicly accessible, and cannot be copied as a whole. As said in Richard Sears's Agreement, the database owner has allowed extractions of characters one at a time, not massive uploads.
  Before doing something like that, it should be made clear either that Richard Sears agrees to it, or that there is no problem for such uploads (including diplomatic ones) whatever his objections may be.
• (It seems I'm the only active ACC project contributor.) There is a problem with the ACClicense template, with respect to the ACC project conventions.
  1. Richard Sears has not given his agreement for such massive uploads. The mention «Courtesy & permission & Copyright from Richard Sears website © 2003 (see Richard Sears Agreement)» should not be used, it is usurped.
  2. To be usable with other wiki's models, within the ACC project, file names should be something like file:公-seal.svg, with the Chinese character in the first position of the name, not file:ACC-b01050.svg.
  3. If the files are to be used under the ACC project, they should rather be 300x300 px and the character should be 5 px from both edges (either vertical or horizontal, whichever is the longest dimension).
  4. Using the ACClicense template automatically gives some classifications, that mean that some more work is to be done on these characters, but they are unusable in that case. The category:ACC needing decomposition comes with characters whose decomposition have not been given (with the component1=... parameters), but no decomposition will be available for bot uploads. Idem, Category:-stroke ancient Chinese characters means that the "strokes=" parameter has not been filled (and counting strokes is obviously impossible for a bot). Using the ACClicense leads to clutter these categories with unwanted files.
• With the upload format, there is no simple way to identify if a picture for a given Chinese character is available.
• Richard Sears has indeed made a terrific job with his site, and thanks should be given to him for that, but the information he gives should be proofread before being used :
  1. His classification is not accurate and can be misleading. Characters may have composition variants, and the picture given on a page often relates to a variant, that is to say another unicode character (see for instance File:弈-bigseal.svg, found on the 奕 page instead of the 弈 one).
  2. There is no need ever to duplicate multiple instances of simple character (公 is an obvious example). Multiplicity is fine for Richard Sears' database, which intends to be exhaustive, but how can it comply with any of the Wikimedia project ?

Before allowing such uploads :

• Do not use the ACC license.
• Clarify the legal status of the massive database transfer.
• Clarify the use of multiple instances with respect of a Wikimedia project scope.
• Create a license template that reflects the legal status of the upload and the purpose of the picture series.

Past uploads should at least be modified as for the license being used. Michelet-密是力 (talk) 06:47, 16 July 2016 (UTC)

With some chances, a bot upload for small seal character would be OK, though, since there is almost never a multiple choice for them ; and in that case the ACC file format can easily be satisfied. Michelet-密是力 (talk) 07:05, 16 July 2016 (UTC)

Thanks for the various comments. I set up Template:ACC-PD-ancient as the license template for the uploaded entries, which differs from the ACC license template in the following ways:

1. Removed the courtesy attribution to Sears' website. The ancient script images are public domain images, as their creators have long deceased and what we and Sears' did was merely digitalising the script forms, similar to the case of Template:PD-chem for chemical structures.
2. Removed the requirements for component decomposition and stroke number. This information can be automatically later by bots if so desired.

You are correct in saying that one image can be mapped to multiple characters and association of characters with images may not be correct. This is the reason the images are uploaded as their identifiers, rather than the tentative modern characters they represent. A separate system has been uploaded on the English Wiktionary to identify each of the images with characters (and vice versa). This is stored at wikt:Module:zh/data/glyph-data, and such method of storage allows easy rectification. Multiple correspondences of an image are faithfully preserved.

The reason multiple images for a particular script for a character are uploaded is because all the script forms are different, some significantly so, and some subtly so. Displaying all possible variants of a character paves way for credible character shape origin/evolution explanations on Wiktionaries and allows for completeness. The script forms are hidden by default. Please see wikt:公 for an example.

Please let me know if there are any queries. Wyang (talk) 13:57, 16 July 2016 (UTC)

Discussion 3 - database protection & project scope

A/ With your creating Template:ACC-PD-ancient two of my four objections are answered. You could use that template on some of your uploads so the result can better be appreciated.

B/ Still two objections to go:

Clarify the legal status of the massive database transfer.

Remember that the characters being public domain is not the point: the database itself is protected as such. Indeed, Sear has “only” digitalized the pictures, AND his work is protected as such. You may legally copy part of a database (ie, some characters from time to time) but not all of it, as long as the database is protected. See w:Database Directive or here or anywhere there for information on legal database protection.

The comparaison with template:PD-chem is irrelevant, the pages thus uploaded on Commons are not a massive upload from an existing database. Most of these files actually appear to be "own works".

Furthermore, there has been a consensus within Commons to recognize Sear's work, both because it has been an awesome work, and because he authorized Commons to upload pictures from his database. This is why his pictures are given priority, even when equivalent pictures may be available elsewhere (the Chinese text project pictures come from an "ancient Chinese character" font, that has most probably been itself taken on Sear's database).

A massive upload would contradict this recognition and may appear as irrespectful. This is why I have a strong objection to doing such a thing. But if the Commons community changes its mind and thinks otherwise, my opinion could of course be outnumbered.

Clarify the use of multiple instances with respect of a Wikimedia project scope.

See Commons:Project scope : «The aim of Wikimedia Commons is to provide a media file repository [...] that acts as a common repository for the various projects of the Wikimedia Foundation». You can't upload things on commons unless it falls within the scope of a Wikimedia project - see Commons:Deletion policy#Out of scope.

The general purpose for the Wiktionary is given in wikt:Wiktionary:Welcome, newcomers: “We aim to include not only the definition of a word, but also enough information to really understand it”. The «etymology» section for a Chinese character is described in wikt:en:Wiktionary:About Han script#Etymology , its purpose is «explaining the development of the character form».

Your explanation saying that «all the script forms are different, some significantly so, and some subtly so. Displaying all possible variants of a character paves way for credible character shape origin/evolution explanations on Wiktionaries and allows for completeness» misses the point of justifying such inclusions: Sear's database collects all instances found in historical documents of such or such character, and the Wiktionary project has no need for such completeness. If differences are subtle, they are not needed for an etymology explanation; and if differences are important, they will be a source of confusion for the reader (and most of the time correspond to a different character and should relate to a different etymology).

What is needed for an etymological section is not to be exhaustive, but to provide the best selection of characters that will explain the original form and its developments along time. This is precisely what the ACC project is doing. Given the choice, the pictures for each kind of script are carefully selected according to their ability to explain the development of the character form, and the character decomposition is (normally) given to allow for comparisons within compound characters.

This is the system used on most Wiktionaries. This is the system that has been used so far on the English wiktionary. That is, before you modified the "Han etyl" template on the 8th of July, without ever discussing the opportunity of doing so. «A separate system has been uploaded on the English Wiktionary» - indeed, but it is your own work, made single-handedly, without any discussion nor consensus, and most probably outside the project scope.

Before arguing by yourself about the opportunity to force down your modifications to the English Wiktionary, please start a discussion and reach a consensus about your changes on the relevant English Wiktionary discussion pages - your arguments and my objections may be transferred there as well.

Michelet-密是力 (talk) 09:35, 20 July 2016 (UTC)

Thanks for the input. With regard to the license, Commons:Ancient Chinese characters/Richard Sears Agreement states that his images are released under the GNU General Public License (GPL), which is a free license guaranteeing others the freedoms to run, study, share (copy), and modify the original material. The Commons page notes:

"Please note: the images themselves are in the public domain and therefore not subject to the terms of the GPL. However, the GPL does apply to the database schema and Sears's methods of organizing the images. Additionally, as Sears has gone to a great deal of trouble to convert these ancient images into GIFs and is releasing his work under a free license, we should comply with his requests as faithfully as we can."

In other words, the GPL license cannot be applied to the images themselves - it is only the organisation of the images which can be subject to GPL. On the English Wiktionary, pages have duly noted the source of the images providing links to Sears' page. The template Template:ACC-PD-ancient can be modified to a GPL license too if that is needed.

Using one image from each script stage for a discussion on the evolution of character is simply grossly insufficient. There is so much variation even in a certain stage of characters which often invokes debates in the literature and difficulty in reaching a consensus as to what the character actually represents. Please have a read of the English Wiktionary's passage for our previous example of wikt:公#Glyph origin to see what is meant by this. Other examples include wikt:兮#Glyph origin, wikt:典#Glyph origin, wikt:共#Glyph origin, wikt:具#Glyph origin... plus many more, although I haven't got around to expanding on the explanations of the graphical evolution since it is halted by this. You would easily understand what I mean if you flip through any decent Chinese books on character origins; it's amazing how the ancient people only left us with these characters without ever clearly explaining why they drew them as such. The design may have been "obvious" to the original inventors, but the modern people simply have no idea, and the theories people put forth can be hugely divergent from one another.

In regard to the template change, I don't believe a discussion is very fruitful and necessary in this case. There is a betterment of the glyph origin sections and there is no opposition from the small Chinese-editing community on Wiktionary. There was no consensus for the initial format of the template "Han etym" on Wiktionary either. Wyang (talk) 13:10, 22 July 2016 (UTC)

You seem not to be willing to understand the problems, and you do not answer the objections :

• Databases ARE protected as such, and a MASSIVE upload would BE ILLEGAL. See the references above and answer that point, without discussing the fact that glyphs by themselves are public domain, which is NOT discussed here.
• Your examples (公, 兮, 典, 共, 具) clearly demonstrate that in fact there is little variation on those examples, and that the pictures are presented systematically, without any selection. You do not need all instances for variation discussion. Contrarily to your sayings, your template is not meant to select or discuss variations.

If indeed your interest were to discuss graphical etymological variations, this is what you would be doing on the en:Wiktionnary, and you would quickly realize that the whole series from Sear's database is not needed for such discussions. See for comparison the French entries (公, 兮, 共, 具) where the graphic meanings and possible variations are indeed discussed (for instance in 共) without ever needing more pictures. The point is: When there is some variation, it can be discussed with a couple of pictures, and the whole picture series is not needed for that. Therefore you are not justified to upload the whole series using this (outstretched) "justification".

Michelet-密是力 (talk) 08:13, 23 July 2016 (UTC)

Veto

You are here to discuss whether Commons should authorize Wyangbot to proceed on massive uploads on Sear's database, that you started on Commons without discussion nor consensus, because you want to use it on the English Wiktionary through the "Han etyl" template, which you modified without discussion nor consensus on the English Wiktionary. On all projects it is bad practice to disorganize the project to prove your point. Your argument is obviously artificial and do not reflect the real use you intend on the English Wiktionary, and this goes way beyond the limits of "assume good faith". Given that you refuse to discuss the objections and oppose fallacious arguments to maintain your initial position, I change my  Disagree to a  Veto.

• If you really want to prove that you are interested in discussing the "hugely divergent theories" on the wiktionnary page, just do it, discuss the (公, 兮, 典, 共, 具)-pages according to what you pretend to be doing, and we'll discuss the result when you're done.
• Before arguing by yourself about the opportunity to force down your modifications to the English Wiktionary, and your uploads to the Commons database, please start a discussion and reach a consensus about your changes on the relevant English Wiktionary discussion pages - your arguments and my objections may be transferred there as well.
• If no consensus is seen on the Wiktionary on your approach, in a month or two a mass deletion will be asked on your previous Commons uploads, for lack of relevance.

Michelet-密是力 (talk) 08:13, 23 July 2016 (UTC)

Let's be positive, though : the bot and the bitmap->svg transformation is a nice hack (wow), and it's indeed a pity not to use it. As said previously, uploadings limited to the small script characters would be without choices to be made between versions, OK with respect to project scopes, and OK legally and ethically, since these characters are found in various places such as Chinese Text Project or xiaoxue or internationalscientific or in the 北師大說文小篆 font. Michelet-密是力 (talk) 08:33, 23 July 2016 (UTC)

@Wyang: Please comment on the above suggestion. Thank you. --Krd 09:13, 23 July 2016 (UTC)

Wow. What can I say. Complete neglect of the GPL (license) status that the images are released under and the note that the images themselves are not even protectable under GPL on the agreement page. Obliviousness to the apparent variation that exists within a single script stage of Chinese characters (e.g. wikt:公#Glyph origin). Hostility towards new ideas and bullying of new users. Very, very disappointed. Wyang (talk) 21:41, 23 July 2016 (UTC)

Abbe98 Bot (talk · contribs)

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

Update the Template:Map to a new version that can be previewed at commons.wikimedia.beta.wmflabs.org. This update is a part of the Wikimaps Warper Individual Engagement Grant project and the new Map template is supposed to be used at a workshop next week(at Wikimania). There is about 12000 pages that will need to be updated.

Automatic or manually assisted: Automatic

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

Maximum edit rate (e.g. edits per minute): 50 edits/minute, (this number is based on simulation, I simulated the entire process, but with actual edits the rate might be lower).

Bot flag requested: (Y/N): Y

Programming language(s): Python(PyWikiBot as framework)

Abbe98 (talk) 11:11, 15 June 2016 (UTC)

Discussion

• Please make a few test edits. --Krd 12:06, 15 June 2016 (UTC)

It should be noted that such test edits will break existing applications such as the Wikimaps Warper witch depends on the template, those applications is supposed to be updated in parallel to this update. --Abbe98 (talk) 15:00, 15 June 2016 (UTC)

I have now notified the application owners and will await their response. --Abbe98 (talk) 15:15, 15 June 2016 (UTC)

@Abbe98: Is there any update? --Krd 17:23, 11 July 2016 (UTC)

Yes the applications now support both the old and the new template and the update was delayed to after Wikimania, I will make the test edits the upcoming weekend when I got the time to watch them closely, pinging you once I'm done. --Abbe98 (talk) 17:42, 11 July 2016 (UTC)

@Abbe98: Following up on this, any update? ~riley (talk) 04:45, 6 August 2016 (UTC)

There is currently a upstream issue in mwparserfromhell that's being investigated. --Abbe98 (talk) 05:23, 9 August 2016 (UTC)