Meta:Babel: Difference between revisions

Revision as of 10:51, 2 December 2020

Latest revision as of 23:35, 25 August 2025

Line 1:

{{Babel header|uselang= {{uselang}}}}

{{Autoarchive resolved section | age = 1 | archive = '((FULLPAGENAME))/Archives/((year))-((month:##))' | timeout = 30}}

{{Communication}}

__TOC__

== Change to translatewiki.net/Miraheze-Meta page translation target languages ==

== Wiki of functions naming contest - Round 2 ==

Currently, the page translation target language configuration on Wikimedia Meta-Wiki were [[gerrit:plugins/gitiles/operations/mediawiki-config/+/3630b918def79de3da490799b2dac77442ff140a/wmf-config/InitialiseSettings.php#7561|inherited from the "language converter page translation model"]].

<div class="plainlinks mw-content-ltr" lang="en" dir="ltr">

{{int:Hello}}.

Reminder: Please help to choose the name for the new Wikimedia wiki project - the library of functions. The finalist vote starts today. The finalists for the name are: <span lang="en" dir="ltr" class="mw-content-ltr">Wikicode, Wikicodex, Wikifunctions, Wikifusion, Wikilambda, Wikimedia Functions</span>. If you would like to participate, then '''[[m:Special:MyLanguage/Abstract Wikipedia/Wiki of functions naming contest/Names|please learn more and vote now]]''' at Meta-wiki.

{{Int:Feedback-thanks-title}} --[[m:User:Quiddity (WMF)|Quiddity (WMF)]]

</div> 22:10, 5 November 2020 (UTC)

<!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Distribution_list/Global_message_delivery&oldid=20564572 -->

However, this actually created several problems including the broken page transclutions with malfunctioned language converter tags exposed and using the workaround of [[Template:Conversion-zh]], [[Template:LC zh]]. More breakages could be found on [[phab:T328838]].

== Gadget for steward/renamers ==

I would like to propose to use the [[gerrit:plugins/gitiles/translatewiki/+/a86463dad55cd8dc4697399537619643d23eee2d/mw-config/TranslateSettings.php#172|"translatewiki.net page translation model"]]/[https://github.com/miraheze/mw-config/blob/cca495152a9e4a2eac3ee911faa2501c8b652a74/LocalSettings.php#L6011 "Miraheze Meta page translation model"] instead on Meta-Wiki after the related [[wikifunctions:Wikifunctions:Project_chat/Archive/2025/05#Change_to_translatewiki.net-like/Miraheze-Meta-like_page_translation_target_languages|proposal had been discussed, supported and approved]] and [[gerrit:1143697|changes had been done]] on Wikifunctions.

Hello everyone, From an internal discussion between Global renamers and Stewards there has been almost unanimous support that request should be handled by someone familiar with project or language unless it's a simple request (doesn't include blocks and sanctions).

Below are examples of the proposed translation model.

To mark the origin of request in [[Special:GlobalRenameQueue|Queue]] we have been using [[User:Ladsgroup/GlobalRenamQueueHelper.js]] user script, but the issue is that every new renamer have to install it or some might even do not know about it. So I propose it to be added as a gadget for steward section and enable it by default for Stewards and Global renamers. Thanks! &#8208;&#8208;[[User:1997kB|1997kB]]&nbsp;([[User_talk:1997kB|talk]]) 07:19, 9 November 2020 (UTC)

* https://translatewiki.net/wiki/Special:Translate?group=page-Project%3AAbout&action=page&language=zh-hans&filter=

:{{ping|Ladsgroup}} do you agree to have your script moved to the mediawiki namespace? You won't be able to edit it there (as I'm sure you're aware) so I want to confirm. If you agree, I can move forward with converting it to a gadget tomorrow - as far as I can tell the only dependency is <code>mediawiki.api</code> (though that isn't explicitly loaded in the current code, it should be included as a dependency for the gadget to make sure it is always available). Thanks, --[[User:DannyS712|DannyS712]] ([[User talk:DannyS712|talk]]) 07:58, 9 November 2020 (UTC)

* https://translatewiki.net/wiki/Special:Translate?group=page-Project%3AAbout&action=page&language=zh-hant&filter=

::@[[User:DannyS712|DannyS712]] I'm fine with moving the code to mediawiki namespace. [[User:Ladsgroup|Amir]] ([[User talk:Ladsgroup|talk]]) 06:44, 10 November 2020 (UTC)

* https://meta.miraheze.org/wiki/Special:Translate?group=page-Miraheze+Meta&action=page&language=zh-hans&filter=

:: Thank you {{ping|Ladsgroup}}! This gadget is very useful. I have a question for you though. Would it be possible to allow sorting by the column "local wiki"? If not it is still okay, ctrl+f still works fine. Cheers! [[User:Nadzik|Nadzik]] ([[User talk:Nadzik|talk]]) 08:19, 10 November 2020 (UTC)

* https://meta.miraheze.org/wiki/Special:Translate?group=page-Miraheze+Meta&action=page&language=zh-hant&filter=

:::@[[User:Nadzik|Nadzik]] Hey, Unfortunately that's not possible. It'll be possible once [[phab:T217099]] will resolve. [[User:Ladsgroup|Amir]] ([[User talk:Ladsgroup|talk]]) 17:03, 10 November 2020 (UTC)

::::According to [[phab:T217099#6387917]] that'd require a schema change and a code change later. Is that doable? While the script is indeed very useful, it'd be better IMHO if the extension gave that info to us directly. Thanks. &mdash;[[User:MarcoAurelio|MarcoAurelio]] ([[User talk:MarcoAurelio|talk]]) 17:07, 11 November 2020 (UTC)

:Looks good to me! [[User:Martin Urbanec|Martin Urbanec]] ([[User talk:Martin Urbanec|talk]]) 13:45, 10 November 2020 (UTC)

::Great idea! It's a very useful script and all renamers/stewards should have it enabled by default! --[[User:Superpes15|Superpes15]] ([[User talk:Superpes15|talk]]) 15:05, 10 November 2020 (UTC)

:@[[User:Ladsgroup|Ladsgroup]] I tested the script out on the beta cluster - for "missing" users (i.e. after they have been renamed, if you're looking in [[Special:GlobalRenameQueue/closed]]) it shows "undefined" - is this intentional? If it is, I'll move the script as-is to a gadget, but if not I thought you should have a chance to fix it before you can no longer edit the script [[User:DannyS712|DannyS712]] ([[User talk:DannyS712|talk]]) 22:34, 10 November 2020 (UTC)

::Script updated, though it still won't fill the local wiki field if the requester cannot be identified via API anymore. I think this is the best we can do for now.--[[User:Sakretsu|Sakretsu]] ([[User talk:Sakretsu|炸裂]]) 12:11, 11 November 2020 (UTC)

::@[[User:DannyS712|DannyS712]] Done by Sakretsu. I don't think the script will be set in stone, worst case, I request a change on its talk page. [[User:Ladsgroup|Amir]] ([[User talk:Ladsgroup|talk]]) 12:24, 11 November 2020 (UTC)

:{{doing}} switching to a gadget now --[[User:DannyS712|DannyS712]] ([[User talk:DannyS712|talk]]) 20:53, 12 November 2020 (UTC)

::{{ping|1997kB|Ladsgroup|Martin Urbanec}} {{done}}, now available as a gadget enabled by default [[User:DannyS712|DannyS712]] ([[User talk:DannyS712|talk]]) 20:59, 12 November 2020 (UTC)

More briefly for the <code>zh</code> part: The old configuration can only translate into <code>zh</code> while the new configuration can translate into <code>zh-hans</code> (for <code>zh-Hans-CN</code>, <code>zh-Hans-MY</code>, <code>zh-Hans-SG</code>), <code>zh-hant</code> (for <code>zh-Hant-TW</code>) and <code>zh-hk</code> (for <code>zh-Hant-HK</code>, <code>zh-Hant-MO</code>).

== Include autopatrol rights with Int-Admin ==

Without using /zh-hans, /zh-hant, /zh-hk, we have to pass the language tag every time using message bundle messages.

Hello, there can be some cases where non-admin granted such rights. There is no reason to not trust them with autopatrol, and I think there can be a bundling of autopatrol with interface-admin. [[User:Camouflaged Mirage|Camouflaged Mirage]] ([[User talk:Camouflaged Mirage|talk]]) 18:02, 11 November 2020 (UTC)

<syntaxhighlight lang="lua">

* I was literally about to create this thread. Support adding autopatrol to the interface-administrator group. &mdash;[[User:MarcoAurelio|MarcoAurelio]] ([[User talk:MarcoAurelio|talk]]) 18:06, 11 November 2020 (UTC)

-- Wrapping all of them under /zh using {{LC zh|, without using /zh-hans, /zh-hant, /zh-hk

* {{support}} --[[User:Novak Watchmen|Novak Watchmen]] ([[User talk:Novak Watchmen|talk]]) 18:12, 11 November 2020 (UTC)

tmb.new( mb_page_title, lang_tag ):t( message_key ):params( lang_tag ):plain()

*{{Support}} —[[User:Atcovi|Atcovi]] [[User talk:Atcovi|(Talk]] - [[Special:Contributions/Atcovi|Contribs)]] 18:18, 11 November 2020 (UTC)

</syntaxhighlight>

* {{s}}. <span style="font-size: smaller; font-style: italic;">Sgd.</span>&nbsp;&mdash;[[user talk:Hasley|<span style="color: #0645AD;">Hasley</span>]] 19:23, 11 November 2020 (UTC)

* {{s}} --[[User:Krd|Krd]] 19:37, 11 November 2020 (UTC)

* {{weak oppose}} for principle reasons. As stated at [[Limits to configuration changes]], it is the policy to not grant any other permissions to the interface admin group. The purpose of that policy is to make wikis not to grant the permission unless the user ''really'' needs to edit JS/CSS, thus restricting the number of holders to the absolute minimum (as it's one of the most sensitive permissions we can grant). I agree that autopatrol probably won't trigger such response, but my principles-liking myself doesn't like adding any permissions to that group anyway. <small>There is really no reason to not duplicate the groups through; at least it makes revoking easier :))</small> --[[User:Martin Urbanec|Martin Urbanec]] ([[User talk:Martin Urbanec|talk]]) 20:16, 11 November 2020 (UTC)

*:Just to be clear, this is a meta-wiki only proposal. CN admins have autopatrol I don't see why IAs can't. It's not as if we grant IA for the user to be autopatrol. {{re|Martin Urbanec}} [[User:CM-Public|CM-Public]] ([[User talk:CM-Public|talk]]) 20:38, 11 November 2020 (UTC)

*::However, if sysdevs are against this idea per Limits to configuration changes, then I guess there's nothing we can do here, I will gladly withdraw this proposal. Advice will be much appreciated? [[User:Camouflaged Mirage|Camouflaged Mirage]] ([[User talk:Camouflaged Mirage|talk]]) 10:42, 12 November 2020 (UTC)

* Uh. Do we really need to discuss a configuration change for such a rare occurrence? Can't we just decide that interface admins can be added to the autopatrol group on sight? Let's not make things more complicated that they need to be. [[User:Nemo_bis|Nemo]] 20:27, 11 November 2020 (UTC)

* Oppose. 1) We should turn off the useless autopatrolling altogether. The feature and the associated group is superfluous. – 2) Per Martin Urbanec. – 3) Per Nemo, where's the big problem of giving interface-admins the autopatrol group as well. --<small>[[User:MF-Warburg|MF-W]]</small> 20:51, 11 November 2020 (UTC)

*:Re nemo point: My thinking is along the lines we grant global renamers, TAs autopatrol, read a discussion somewhere about adding. Just can't find it now. [[User:CM-Public|CM-Public]] ([[User talk:CM-Public|talk]]) 21:10, 11 November 2020 (UTC)

*:::Response to comment about AP itself. I find the patrol indicator useful for my viewing of edits here. &nbsp;— [[user:billinghurst|billinghurst]] ''<span style="font-size:smaller">[[user talk:billinghurst|sDrewth]]</span>'' 02:55, 12 November 2020 (UTC)

* {{comment}} They are independent and should continue to be independent, when one stops being admin do you then you think that they should be back to being patrolled. I would hope that if someone is being given the described rights that whomever just assigns autopatrolled at the same time. If you are pushing for a binary decision, {{oppose}} though based on a true need and a sanity of action. &nbsp;— [[user:billinghurst|billinghurst]] ''<span style="font-size:smaller">[[user talk:billinghurst|sDrewth]]</span>'' 02:50, 12 November 2020 (UTC)

* {{oppose}} use the right tool for the right job, there is absolutely no problem with someone being in multiple user groups, and needing a project-local customization for intadmin for this is a bit silly. — [[User:Xaosflux|<span style="color:#FF9933; font-weight:bold; font-family:monotype;">xaosflux</span>]] ^{[[User talk:Xaosflux|<span style="color:#009933;">Talk</span>]]} 16:27, 12 November 2020 (UTC)

* {{oppose}} per Martin, Xaosflux, billinghurst - they are orthogonal groups and I don't see a clear benefit to bundling autopatrol into intadmin. If we want to explicitly say that intadmins are presumed eligible for autopatrol, I won't object, but imo that's rules creep - if someone is trusted enough to be an intadmin I would certainly expect them to meet the criteria for autopatrol. [[User:GeneralNotability|GeneralNotability]] ([[User talk:GeneralNotability|talk]]) 17:08, 12 November 2020 (UTC)

* {{weak oppose}} I find Martin Urbanec's reasoning to be persuasive. <span style="background-color:#EEE; font-size: 1.2em; padding:.15em .45em;"><b>[[User:Quantocius_Quantotius|<span style="color:#800000;">&#119980;</span>]][[User_Talk:Quantocius_Quantotius|<span style="color:#800000;">&#120084;</span>]]</b></span> 22:23, 17 November 2020 (UTC)

* {{strong oppose}} <span style="background:linear-gradient(to right, #FFFF00, #FF0000);">[[User:Nieuwsgierige Gebruiker|Nieuwsgierige]] [[User talk:Nieuwsgierige Gebruiker|Gebruiker]]</span> ^{([[Special:CentralAuth/Nieuwsgierige Gebruiker|CA]])} 17:05, 24 November 2020 (UTC)

<syntaxhighlight lang="lua">

{{not done}} No consensus for system change as proposed, though there is clear indication that consideration be given to granting the right separately if someone is applying for the right, and that admins and 'crats should be considering this pro-actively. &nbsp;— [[user:billinghurst|billinghurst]] ''<span style="font-size:smaller">[[user talk:billinghurst|sDrewth]]</span>'' 06:36, 26 November 2020 (UTC)

-- Using separated /zh-hans, /zh-hant, /zh-hk, we no longer need to pass the language tag :params( lang_tag ) every time

tmb.new( mb_page_title, lang_tag ):t( message_key ):plain()

</syntaxhighlight>

With this change, every Lua module using translation bundles can be simplified:

== Close request ==

<syntaxhighlight lang="diff">

{{comment|Note}} this request is a cross-post from RFH; additional discussion is available <span style class="plainlinks">[https://meta.wikimedia.org/w/index.php?title=Meta:Requests_for_help_from_a_sysop_or_bureaucrat&oldid=20667037#Close_request,_or_in_fact_3_close_requests. here]</span>.{{pb}}Would an uninvolved contributor please consider closing the 3 discussions at [[Communications/Wikimedia brands/2030 movement brand project/Community feedback and straw poll]], thanks for your time.{{pb}}<span style="background-color:#EEE; font-size: 1.2em; padding:.15em .45em;"><b>[[User:Quantocius_Quantotius|<span style="color:#800000;">&#119980;</span>]][[User_Talk:Quantocius_Quantotius|<span style="color:#800000;">&#120084;</span>]]</b></span> 17:20, 15 November 2020 (UTC)

- :t( message_key ):params( lang_tag ):plain()

+ :t( message_key ):plain()

</syntaxhighlight>

Without this change, every Lua module using translation bundles need to:

== Some glitch on translations ==

<syntaxhighlight lang="diff">

I have done some translations for page [[Wikimedia Foundation/fi]] but it seems that my translations are not in its page history, these exists only in namespace Translation. [[User:Jnovikov|Jnovikov]] ([[User talk:Jnovikov|talk]]) 19:20, 15 November 2020 (UTC)

- :t( message_key ):plain()

+ :t( message_key ):params( lang_tag ):plain()

</syntaxhighlight>

Note: "translatewiki.net page translation model"/"Miraheze Meta page translation model" refer to the same translation model.

Whoa, now these are there! [[User:Jnovikov|Jnovikov]] ([[User talk:Jnovikov|talk]]) 19:22, 15 November 2020 (UTC)

-- [[User:Winston Sung|Winston Sung]] ([[User talk:Winston Sung|talk]]) 07:57, 30 July 2025 (UTC)

== Call for insights on ways to better communicate the work of the movement ==

The Movement Strategy recommendations published this year made clear the importance of establishing stronger communications within our movement. To this end, the Foundation wants to gather insights from communities on ways we all might more consistently communicate about our collective work, and better highlight community contributions from across the movement. Over the coming months, we will be running focus groups and online discussions to collect these insights. Visit the [[m:Movement communications insights|page on Meta-Wiki]] to sign up for a focus group or participate in the discussion.

[[m:User:ELappen (WMF)|ELappen (WMF)]] ([[m:User talk:ELappen (WMF)|talk]]) 18:56, 18 November 2020 (UTC)

<!-- Message sent by User:CKoerner (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Movement_communications_insights/Invitation/targets&oldid=20683714 -->

:LOL. Attempting to really communicate would be a good start, contrary to the [[Communications/Wikimedia brands/2030 movement brand project/Executive statement|Decision]]... [[:mw:GitLab consultation/Discussion summary|has]]... [https://lists.wikimedia.org/pipermail/cloud/2020-November/001325.html been]... [[Talk:IP Editing: Privacy Enhancement and Abuse Mitigation#Going forward: IP masking happening, where there's flexibility|made]]... attitude. All of the link being generated from 2020 event is saying something. &mdash;&nbsp;regards, [[User:-revi|<span style="color:green;font-family:Courier new, serif;font-variant:small-caps">Revi</span>]] 22:23, 18 November 2020 (UTC)

:: +1. --[[User:Base|Base]] ([[User talk:Base|talk]]) 15:49, 19 November 2020 (UTC)

::Agreed. --'''[[User:Rschen7754|Rs]][[User talk:Rschen7754|chen]][[Special:Contributions/Rschen7754|7754]]''' 02:35, 20 November 2020 (UTC)

:::{{ping|ELappen (WMF)}} courtesy ping to make sure you saw the responses [[User:DannyS712|DannyS712]] ([[User talk:DannyS712|talk]]) 03:45, 20 November 2020 (UTC)

:::: I did see it, thanks {{u|DannyS712}}. It didn’t feel like anyone was looking for a reply from the team so I didn’t want to butt in, but I will say this work is based on the recognition that we have a lot of room to grow. I totally understand that people are frustrated and disillusioned and may not want to elaborate, but if anyone wants to have a conversation about the specifics of what better, more consistent communication would look like to you, I’d be happy to have it on the [[m:Talk:Movement_communications_insights|project talk page]], or here if you prefer. Needless to say, I would also be happy to have any of you sign up for a focus group. --[[User:ELappen (WMF)|ELappen (WMF)]] ([[User talk:ELappen (WMF)|talk]]) 18:05, 20 November 2020 (UTC)

:::::{{ping|ELappen (WMF)}} Okay, I'll bite. In one sentence: ''When the community tells you no, then listen.'' For the last several years, the WMF has had a series of colossal failures where they proceeded against the wishes of the community and making excuses as to why they did so ("oh, it was just a vocal minority and the majority really agrees with us", "oh, our TOS requires this" (when it was more a matter of interpretation, for example). Visual Editor? MediaViewer/[[Superprotect]]? [[:w:en:WP:FRAM]]? And now WMF has the temerity to ask us what they are doing wrong (and expect editors to go join a synchronous Google Meet call), as if they can't learn from or understand their mistakes. WMF has since burned all their political capital (and thus not had it when they needed it, such as with global bans) and trust is at an all-time low. I think the fact that all three of us (Revi, Base, and I) are or were [[stewards]], and have almost half a million edits and 34 years of editing experience between the three of us should also say something. --'''[[User:Rschen7754|Rs]][[User talk:Rschen7754|chen]][[Special:Contributions/Rschen7754|7754]]''' 06:50, 25 November 2020 (UTC)

::::::+1 &mdash;[[User:MarcoAurelio|MarcoAurelio]] ([[User talk:MarcoAurelio|talk]]) 10:26, 25 November 2020 (UTC)

::::::@[[User:Rschen7754|Rschen7754]] and others, I think [https://meta.wikimedia.org/w/index.php?title=Talk:Movement_communications_insights&type=revision&diff=20692775&oldid=20692623&diffmode=source my reply] to a similar point applies here as well. Instead of copying it in full, I'll just say here that situations of strong disagreement and massive discussion make one type of communication problems, but there are many more. Of course your perspective as long term Wikipedians and Stewards is very important, it's just that there are many other perspectives in the movement that complement each other. Examples just to illustrate this point include where to find information about what is going on in our movement, how to promote activities to get more participants among Wikimedians or newcomers, how to share community news in multiple languages, how to collaborate effectively in social media outreach, how to collaborate to get more local press coverage, what type of documentation and training the communicators in our movement need, etc. Dozens of volunteers are signing up for the focus groups, some might want to discuss problems like the ones you describe, others might have other priorities. We want to capture everything. [[User:Qgil-WMF|Qgil-WMF]] ([[User talk:Qgil-WMF|talk]]) 18:17, 25 November 2020 (UTC)

:::::::{{ping|Qgil-WMF}} Quite frankly, the growing divide between the editor base (read: the people who write the content that motivates people to donate) and the WMF is the most pressing of these problems. In other words, I don't think there will be a movement or a WMF to communicate about in 5 years if the WMF proceeds to alienate the most experienced portion of its editor base like it is currently doing. --'''[[User:Rschen7754|Rs]][[User talk:Rschen7754|chen]][[Special:Contributions/Rschen7754|7754]]''' 18:30, 25 November 2020 (UTC)

::::::::Noted, and we agree that this relationship is an important problem to address. [[User:Qgil-WMF|Qgil-WMF]] ([[User talk:Qgil-WMF|talk]]) 22:05, 25 November 2020 (UTC)

: Pinging @​[[User:94rain|94rain]] @​[[User:乌拉跨氪|乌拉跨氪]] @​[[User:梦夕琳|梦夕琳]] ​@[[User:Allenwang6212a|Allenwang6212a]]、 @[[User:ASid|ASid]] @[[User:Cookai1205|Cookai1205]] @​[[User:Cwek|Cwek]] @​[[User:Ericliu1912|Ericliu1912]] @​[[User:Hamish|Hamish]] @​[[User:Heihaheihaha|Heihaheihaha]] @​[[User:Joycewikiwiki|Joycewikiwiki]] @​[[User:Kaganer|Kaganer]] @​[[User:KOKUYO|KOKUYO]] @​[[User:Kuailong|Kuailong]] @[[User:Lakejason0|Lakejason0]] @​[[User:LowensteinYang|LowensteinYang]] @​[[User:Minorax|Minorax]] @​[[User:Reke|Reke]] @[[User:SCP-2000|SCP-2000]] @​[[User:Shangkuanlc|Shangkuanlc]] @​[[User:Shizhao|Shizhao]] @[[User:SolidBlock|SolidBlock]] @​[[User:Stang|Stang]] @​[[User:SunAfterRain|SunAfterRain]] @​[[User:Supaplex|Supaplex]] @​[[User:Taiwania Justo|Taiwania Justo]] @​[[User:Tigerzeng|Tigerzeng]] @​[[User:Venuslui|Venuslui]] @​[[User:WhitePhosphorus|WhitePhosphorus]] @​[[User:Wong128hk|Wong128hk]] @​[[User:Xiplus|Xiplus]] @​[[User:YFdyh000|YFdyh000]] @[[User:人间百态|人间百态]] @[[User:魔琴|魔琴]] @​[[User:だ＊ぜ|だ＊ぜ]] -- [[User:Winston Sung|Winston Sung]] ([[User talk:Winston Sung|talk]]) 04:24, 5 August 2025 (UTC)

== Community Wishlist Survey 2021 ==

: As I didn't look into two models, is there any major difference? If yes, would you briefly describe the difference please? [[User:Hamish|<span style="background:White;border:1px #FFDAB9 solid;color:Pink;border-radius:999px">Hamish</span>]] 16:02, 5 August 2025 (UTC)

[[File:Magic Wand Icon 229981 Color Flipped.svg|thumb|48px]]

The '''[[m:Special:MyLanguage/Community Wishlist Survey 2021|2021 Community Wishlist Survey]]''' is now open! This survey is the process where communities decide what the [[m:Community Tech|Community Tech]] team should work on over the next year. We encourage everyone to submit proposals until the deadline on '''{{#time:j xg|2020-11-30|{{PAGELANGUAGE}}}}''', or comment on other proposals to help make them better. The communities will vote on the proposals between {{#time:j xg|2020-12-08|{{PAGELANGUAGE}}}} and {{#time:j xg|2020-12-21|{{PAGELANGUAGE}}}}.

: More briefly for the <code>zh</code> part: The old configuration can only translate into <code>zh</code> while the new configuration can translate into <code>zh-hans</code> (for <code>zh-Hans-CN</code>, <code>zh-Hans-MY</code>, <code>zh-Hans-SG</code>), <code>zh-hant</code> (for <code>zh-Hant-TW</code>) and <code>zh-hk</code> (for <code>zh-Hant-HK</code>, <code>zh-Hant-MO</code>). -- [[User:Winston Sung|Winston Sung]] ([[User talk:Winston Sung|talk]]) 08:27, 8 August 2025 (UTC)

The Community Tech team is focused on tools for experienced Wikimedia editors. You can write proposals in any language, and we will translate them for you. Thank you, and we look forward to seeing your proposals!

== Ready for translation: Education Newsletter July 2025 ==

[[m:user:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] 05:52, 20 November 2020 (UTC)

<!-- Message sent by User:SGrabarczuk (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=User:SGrabarczuk_(WMF)/sandbox/MM/En_fallback&oldid=20689940 -->

July 2025 education newsletter released for translation. Please help our readers to read education newsletter in their native language. The latest education newsletter is ready for translation: [[Education/Newsletter/July 2025|here]] Newsletter headlines link for translation: [[Education/Newsletter/July 2025/Headlines|here]], to read individual articles check out: [[:Category:Education/Newsletter/July 2025]]. Regards, [[User:ZI Jony|<span style="color:#8B0000">'''ZI Jony'''</span>]] [[User talk:ZI Jony|^{<span style="color:Green"><i>(Talk)</i></span>}]] 02:56, 1 August 2025 (UTC)

== Global bot policy proposal: invitation to a Meta discussion ==

: @[[User:ZI Jony|ZI Jony]], please also include link to [[Template:Education Navigation]] into your invitations. [[User:Kaganer|Kaganer]] ([[User talk:Kaganer|talk]]) 09:57, 6 August 2025 (UTC)

::Noted. Regards, [[User:ZI Jony|<span style="color:#8B0000">'''ZI Jony'''</span>]] [[User talk:ZI Jony|^{<span style="color:Green"><i>(Talk)</i></span>}]] 16:34, 7 August 2025 (UTC)

:::☁ [[User:Ray Butcher|Ray Butcher]] ([[User talk:Ray Butcher|talk]]) 09:22, 12 August 2025 (UTC)

:hridoy.khan57327@ [[Special:Contributions/103.242.8.180|103.242.8.180]] 09:49, 12 August 2025 (UTC)

== Need help from bot ==

<div class="plainlinks mw-content-ltr" lang="en" dir="ltr">

{{int:hello}}!

Hi!

I apologize for sending a message in English. {{int:please-translate}}. According to [[:m:Bot_policy/Implementation#Where_it_is_policy|the list]], your wiki project currently is opted in to the [[:m:Bot_policy#Global_bots|global bot policy]]. Under this policy, bots that fix double redirects or maintain interwiki links are allowed to operate under a global bot flag that is assigned directly by the stewards.

I need the help from a bot to apply the following algorithm:

As the Wikimedia projects developed, the need for the current global bot policy decreased, and in the past years, no bots were appointed via that policy. That is mainly given Wikidata were estabilished in 2013, and it is no longer necessary to have dozens of bots that maintain interwiki links.

<source lang="js">

const listOfPages = mw.getListOfPagesStartingWith( "Wiki Loves Living Heritage/" );

const replaceRegex = new RegExp(`<!--BEGINREPLACE.+<!--ENDREPLACE-->`, "s");

A [[:m:Requests for comment/Refine global bot policy|proposal]] was made at Meta-Wiki, which proposes that the stewards will be authorized to determine whether an uncontroversial task may be assigned a global bot flag. The stewards already assign permissions that are more impactful on many wikis, namely, [[:m:GS|global sysops]] and [[:m:GR|global renamers]], and I do not think that trust should be an issue. The stewards will assign the permission only to time-proven bots that are already approved at a number of projects, like [[:m:User:ListeriaBot|ListeriaBot]].

const backupRegex = new RegExp(`{{Wikidata list.+{{Wikidata list end}}`, "s");

for( page in listOfPages ) {

By this message, I would like to invite you to comment [[:m:Requests for comment/Refine global bot policy|in the global RFC]], to voice your opinion about this matter.

let matchingContent = page.wikitext.match( replaceRegex );

if( ! matchingContent ) matchingContent = page.wikitext.match( backupRegex );

if( ! matchingContent ) continue;

let contentToMove = matchingContent[0];

Thank you for your time.

let newSubPageName = page.pageName + '/list';

page.wikitext.replace( contentToMove, '{{:' + newSubPageName + '}}' ); //must be absolute path (for translation pages)

page.save();

mw.createPage(

Best regards,<br />

pageName: newSubPageName,

[[User:Martin Urbanec|Martin Urbanec]] ([[:m:User talk:Martin Urbanec|{{int:Talkpagelinktext}}]]) 11:49, 24 November 2020 (UTC)

pageWikitext: contentToMove

</div>

);

<!-- Message sent by User:Martin Urbanec@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=User:Martin_Urbanec/sand&oldid=20709229 -->

}

</source>

'''Aim''': moving Wikidata List to their own subpage, then transcluding the subpage, so what you see do not change.

== [[Meta:Bots]] ==

'''Point''': many of those pages are translatable. Each time the bot update the Wikidata list, a translation admin must mark the page for translation, which is uselessly time-consuming.

Since we are speaking of bots for the global bot policy, I found our meta bot policy is still marked as a proposal. Is there any objections if it becomes policy, tabling here for the community inputs. [[User:Camouflaged Mirage|Camouflaged Mirage]] ([[User talk:Camouflaged Mirage|talk]]) 16:58, 24 November 2020 (UTC)

* No objection from me. [[User:Ruslik0|Ruslik]] ([[User talk:Ruslik0|talk]]) 20:24, 25 November 2020 (UTC)

* {{comment}}: Meta is currently following [[Bot policy]], so does this proposal include discontinuing that and making [[Meta:Bots]] as policy or we gonna follow both? &#8208;&#8208;[[User:1997kB|1997kB]]&nbsp;([[User_talk:1997kB|talk]]) 04:02, 26 November 2020 (UTC)

*: {{ping|1997kB}} it reads as though it is meant to be complementary to global bot policy, and where there is dispute between the two policies that that the local wording will take precedence. &nbsp;— [[user:billinghurst|billinghurst]] ''<span style="font-size:smaller">[[user talk:billinghurst|sDrewth]]</span>'' 06:43, 26 November 2020 (UTC)

*::This is similar to the oversight and checkuser policies of meta vs global checkuser and oversight policies. This is more towards oversight policy as oversight policy we allow oversight of logged out editing here on meta where the global don't specify. I.e. we can add in more rules of how bots can be used rather than the global bot policy. It is also similiar to checkuser is that the local policy doesn't override the global one, i.e. global bots can operate still (as we the community agree on allowing global bots to run in meta). Hope this clarifies, might be a little confusing. [[User:Camouflaged Mirage|Camouflaged Mirage]] ([[User talk:Camouflaged Mirage|talk]]) 09:35, 26 November 2020 (UTC)

* okay with this being implemented, nothing controversial, and if we have a bot inactivity policy then something for on the way in makes sense. &nbsp;— [[user:billinghurst|billinghurst]] ''<span style="font-size:smaller">[[user talk:billinghurst|sDrewth]]</span>'' 06:45, 26 November 2020 (UTC)

* See no issues then. It will be useful to have a local policy. &#8208;&#8208;[[User:1997kB|1997kB]]&nbsp;([[User_talk:1997kB|talk]]) 01:42, 28 November 2020 (UTC)

*Don't get the point, is there anything in there that isn't in [[Bot policy]] (which seems to be the local policy, too)? If not, imo having two policies which don't add to each other is just confusing. [[User:ProcrastinatingReader|ProcrastinatingReader]] ([[User talk:ProcrastinatingReader|talk]]) 10:31, 2 December 2020 (UTC)

*:@[[User:ProcrastinatingReader|ProcrastinatingReader]] This proposal basically is to have a separate one for meta, as at times we might differ from the global bot policy and it's easier to list meta only proceedures/pages to apply for bots etc on a stand alone policy page rather than that of global. It's confusing I agree, but one must understand that while meta we host most of the global events, we had also a small community here related to meta so this is the local community bot policy. See [[Meta:About#Community]] for more details. [[User:Camouflaged Mirage|Camouflaged Mirage]] ([[User talk:Camouflaged Mirage|talk]]) 10:44, 2 December 2020 (UTC)

*::Hmm. But there are no specific local policy points currently, right, and currently it only seems to repeat the global one? Unless there's local terms, what's the point of creating a separate policy page? I fear it would just throw people off / confuse people trying to make meta bots at worst, or at best just add unnecessary reading.

*::On a tangential note, where is the local Checkuser policy anyway? I found [[Meta:CheckUsers]] but this seems to just be a page that "provides information" rather than anything supplementing [[Checkuser policy]] (indeed, it says to visit there for the policy). [[User:ProcrastinatingReader|ProcrastinatingReader]] ([[User talk:ProcrastinatingReader|talk]]) 10:51, 2 December 2020 (UTC)

Unfortunately, I have never set a bot up, and I have not enough time to learn. Can someone help?

== Wikidata descriptions changes to be included more often in Recent Changes and Watchlist ==

Pinging [[user:Susannaanas|Susannaanas]] for information.

<div class="plainlinks mw-content-ltr" lang="en" dir="ltr">

''Sorry for sending this message in English. Translations are available on [[m:Special:MyLanguage/Announcements/Announcement Wikidata descriptions in watchlist|this page]]. Feel free to translate it in more languages!''

-- [[User:Pols12|Pols12]] ([[User talk:Pols12|talk]]) 14:49, 12 August 2025 (UTC)

As you may know, you can include changes coming from Wikidata in your Watchlist and Recent Changes ([[Special:Preferences#mw-prefsection-watchlist|in your preferences]]). Until now, this feature didn’t always include changes made on Wikidata descriptions due to the way Wikidata tracks the data used in a given article.

:@[[User:Pols12|Pols12]]: What wanna you? As human, simple? What is problem? You write (in Aim) how wanna you implement, but i dont know what is the problem (example, if i would be a user, a none-technical user). [[User:Dušan Kreheľ|Dušan Kreheľ]] ([[User talk:Dušan Kreheľ|talk]]) 10:46, 13 August 2025 (UTC)

Starting on December 3rd, the Watchlist and Recent Changes will include changes on the descriptions of Wikidata Items that are used in the pages that you watch. This will only include descriptions in the language of your wiki to make sure that you’re only seeing changes that are relevant to your wiki.

::I explained it in the “point” item: each time a translatable page is updated, a translation admin has to “mark the page for translation” to validate the changes so they are applied to translation pages. Since those are [[d:template:Wikidata list|Wikidata lists]], [[User:ListeriaBot|the bot]] update the pages every day. This is really time-consuming for translation admins to review [[Special:Contributions/ListeriaBot|all of those bot changes]]!

::Benefits:

::* As a translation admin, this change would reduce my workload.

::* As a final user, I see the page up-to-date in my language as soon as ListeriaBot updates the page, I don’t need to wait for translation admin work.

::-- [[User:Pols12|Pols12]] ([[User talk:Pols12|talk]]) 12:14, 13 August 2025 (UTC)

:::@[[User:Pols12|Pols12]]:

:::'''Solution No. 1.:'''

:::How about getting pagetranslation rights for a bot?

:::'''Solution No. 2.:'''

:::I see that the page is a bunch of mini-pages. So I would put the translation into Lua modules (the module would load the translation according to the wikis and have some constant UI for the languages).

:::The page would be for example: <nowiki>{{Page widget box|en|dog;cat;rabbit}}</nowiki>

:::The modules would be:

:::* Page widget box

:::* Page widget box – item (description pulls according to wikidata and language)

:::* Page widget box – UI translate

:::[[User:Dušan Kreheľ|Dušan Kreheľ]] ([[User talk:Dušan Kreheľ|talk]]) 13:15, 15 August 2025 (UTC)

::::Your solution 1 is not conceivable. That action needs a special right because it needs a human review given the risks of making something wrong and for performance reasons. Besides, my solution only needs 1 bot passage ever for each page; whereas your solution 1 would need a daily passage (each time ListeriaBot edits the page) which would be uselessly resource-consuming.

::::I don’t understand your solution 2. I agree several unit would benefit to be included through a template since they are common to many pages. They are already some templates for that purpose, including [[Template:Wiki Loves Living Heritage/Placeholders]]. In any case, we want the page to be localizable, and the best way is to use Translate extension features, mainly for Meta-Wiki consistency. In most cases, only the page title will be manually translatable (no unit on the page), but that would enable Languages bar to change the page language.

::::Also, I don’t understand why you seem to want to avoid the solution I proposed.

::::Unfortunately, I will probably not find any more time to work more on this in the coming weeks, sorry if I can’t follow your next answers here.

::::--[[User:Pols12|Pols12]] ([[User talk:Pols12|talk]]) 23:47, 16 August 2025 (UTC)

== Display problem ==

This improvement was requested by many users from different projects. We hope that it can help you monitor the changes on Wikidata descriptions that affect your wiki and participate in the effort of improving the data quality on Wikidata for all Wikimedia wikis and beyond.

When I successfully mark pages for translation, the check icon on the left side of the notice squeezed. Probably not the only instance. I don't know where to post it, so I'll leave it here. —— '''[[User:Ericliu1912|Eric Liu]]'''_{（'''[[User talk:Ericliu1912|Talk]]'''）} 15:47, 14 August 2025 (UTC)

:@[[User:Ericliu1912|Ericliu1912]] does it appear similar to [[:phab:T398529#11048062]]? [[User:Johannnes89|Johannnes89]] ([[User talk:Johannnes89|talk]]) 13:52, 15 August 2025 (UTC)

:: Yes! Glad to see there was already a Phab task filed. —— '''[[User:Ericliu1912|Eric Liu]]'''_{（'''[[User talk:Ericliu1912|Talk]]'''）} 14:22, 15 August 2025 (UTC)

== Missing {{int:communitywishlist-support}} ==

Note: if you didn’t use the Wikidata watchlist integration feature for a long time, feel free to give it another chance! The feature has been improved since the beginning and the content it displays is more precise and useful than at the beginning of the feature in 2015.

Missing message in {{int:⧼communitywishlist-support⧽}}. Go to [[Community Wishlist/Focus areas/Media formats, editing, and display]] for example, scroll to blue button and push "Support focus area", the popup's main blue button that appears has this <code>{<nowiki/>{int:}}</code> in it. [[User:Waddie96|Waddie96]] ([[User talk:Waddie96|talk]]) 06:49, 17 August 2025 (UTC)

If you encounter any issue or want to provide feedback, feel free to use [[Phab:T191831|this Phabricator ticket]]. Thanks!

*Ping to {{ping|User:MusikAnimal (WMF)}} who I think is the staffer coordinating that. MA, looks like there are 2 problems:

#Missing label at [[MediaWiki:communitywishlist-support]] as reported above.

#This button loads a custom pop-out editor, which is missing licensing agreement verbiage (which should be, or be functionally similar to [[MediaWiki:wikimedia-copyrightwarning]])

*Would you look in to both of these? Thank you, — [[User:Xaosflux|<span style="color:#FF9933; font-weight:bold; font-family:monotype;">xaosflux</span>]] ^{[[User talk:Xaosflux|<span style="color:#009933;">Talk</span>]]} 12:34, 17 August 2025 (UTC)

*:The missing message is now fixed. Adding the copyright warning is a bit more involved, I'm afraid. We have a new MediaWiki extension that is going to replace the gadget version relatively soon, and we'll get the copyright warning added there.

*:Thanks for letting us know about these issues! :) [[User:MusikAnimal (WMF)|MusikAnimal (WMF)]] ([[User talk:MusikAnimal (WMF)|talk]]) 19:22, 20 August 2025 (UTC)

*::@[[User:MusikAnimal (WMF)|MusikAnimal (WMF)]] Thanks! [[User:Waddie96|Waddie96]] ([[User talk:Waddie96|talk]]) 23:28, 21 August 2025 (UTC)

== site name changed from Meta to Meta-Wiki ==

[[:d:User:Lea Lacroix (WMDE)|Lea Lacroix (WMDE)]] 14:38, 30 November 2020 (UTC)

</div>

<!-- Message sent by User:Lea Lacroix (WMDE)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=User:Lea_Lacroix_(WMDE)/wikis&oldid=20728482 -->

Per the prior discussion and [[phab:T399843]], our sitename has been changed. The database name has not been changed. If you see any problems, please let us know. — [[User:Xaosflux|<span style="color:#FF9933; font-weight:bold; font-family:monotype;">xaosflux</span>]] ^{[[User talk:Xaosflux|<span style="color:#009933;">Talk</span>]]} 13:34, 18 August 2025 (UTC)

== Test Wikimedia Commons ==

What is the interwiki prefix for Test Wikimedia Commons? Can't seem to find one at [[Special:Interwiki]]. [[testcommonswiki:]] doesn't work, nor does [[testcommons:]]. --[[User:AJ1m3,zsd.|AJ1m3,zsd.]] ([[User talk:AJ1m3,zsd.|talk]]) 21:18, 30 November 2020 (UTC)

:@[[User:AJ1m3,zsd.|AJ1m3,zsd.]] There's none (intentionally), as the site is/was a single-purpose one, and probably will be destroyed one day. [[User:Martin Urbanec|Martin Urbanec]] ([[User talk:Martin Urbanec|talk]]) 23:01, 30 November 2020 (UTC)

== Possibility of using UTRS / OTRS to handle block appeals ==

Hello, per [[Special:diff/20711072|this]], there is a discussion of the possibility of using UTRS on meta to handle appeals. I don't quite know what the system is but if I think it as OTRS queue, it seems attractive. We had countless users who should have either email / talkpage access revoked but we didn't for either one is due to the fact we wanted to leave them a possiblity to appeal. Currently the framework is that blocked users can appeal on talkpage, if talkpage is blocked they can do so via emailing one of us (typically they will have a link to the blocked admin). This isn't desirable for some who have no decency to keep email secrect, and us replying to them using our emails risks us being exposed by them and subsequently likely outing and etc. There is also another group of users who spam emails and hence got their email access revoked and mostly TPA too. In addition, the emailing of single admins isn't the most transparent ones, no one can track how many admins they emailed, neither can the appeal process being reviewed by other admins. A consolidated system seems attractive to me, and hence, I will suggest we change the appeal process for revoked TPA users to a queue, either via admin mailing lists / OTRS queue / UTRS (?) [[User:Camouflaged Mirage|Camouflaged Mirage]] ([[User talk:Camouflaged Mirage|talk]]) 16:32, 1 December 2020 (UTC)

:[[:en:WP:UTRS|UTRS]] is a totally different thing than [[OTRS]]. I think both will be ok for the intended task, but please let's not use both for that at the same time. --[[User:Krd|Krd]] 16:54, 1 December 2020 (UTC)

:I think block appeals should stay as on-wiki as possible. UTRS may come useful however for cases like IP hardblocks where appealing on-wiki would mean publicly disclosing the user's IP address. For everything else {{tlx|unblock}} seems to work just fine. Thanks. &mdash;[[User:MarcoAurelio|MarcoAurelio]] ([[User talk:MarcoAurelio|talk]]) 18:38, 1 December 2020 (UTC)

:::@[[User:MarcoAurelio|MarcoAurelio]] Yeah, I am just thinking of those exceptions, as well as cases where we don't want the user to have onwiki talkpage access as if they appeal, they may continue the libel / etc. I am just thinking of a way (one avenue only, to clarify @[[User:Krd|Krd]] point above) to handle appeals for users with TPA revoked. These cases can be very few but at least we have something to give them, although they may not deserve this avenue, rather than needing them to email us individually. [[User:Camouflaged Mirage|Camouflaged Mirage]] ([[User talk:Camouflaged Mirage|talk]]) 18:49, 1 December 2020 (UTC)

::Another useful case is handling appeals of global locks. Though here is not the proper place to discuss such issue.--[[User:GZWDer|GZWDer]] ([[User talk:GZWDer|talk]]) 18:45, 1 December 2020 (UTC)

:::@[[User:GZWDer|GZWDer]] For global locks, they can already email stewards<nowiki>{{at}}</nowiki>wikimedia.org. There is already this rather than emailing individual stewards, I am just proposing such an infrastructure for meta. [[User:Camouflaged Mirage|Camouflaged Mirage]] ([[User talk:Camouflaged Mirage|talk]]) 18:51, 1 December 2020 (UTC)