In T411329#11418383, @Bugreporter wrote:

However different wikis use different timezone and it is not really easy to recognize the current time in UTC.

I have another idea, instead of something lile ~2025-37554-09, perhaps we can make the sequence more specific to date of the account created, something like ~2025-1201-37554 sp that the patroller could identify the account created at which date (in this case 1 December 2025)?

Owh I see, I misunderstood that the roll out would be done on Tuesday. Thanks for the information!

In T394603#10858270, @hashar wrote:

I ran mwscript-k8s --comment="T394603" --follow -- namespaceDupes mswiki --fix , the full output is at P76463 and the important bits are:

27 pages to fix, 26 were resolvable.
4528 links to fix, 3704 were resolvable, 824 were deleted.

One page could not be fixed:

id=1255216 ns=0 dbk=Portal:Masyarakat *** dest title exists and --add-prefix not specified

That is because there is a duplicate between the namespaces. I have thus renamed the dupe using --add-prefix T394603/:

$ mwscript-k8s --comment="T394603" --follow -- namespaceDupes mswiki --fix --add-prefix T394603/
id=1255216 ns=0 dbk=Portal:Masyarakat -> Gerbang:T394603/Masyarakat (alternate)
1 pages to fix, 1 were resolvable.

0 links to fix, 0 were resolvable, 0 were deleted.

Looks good!

Those are the pages:

https://ms.wikipedia.org/wiki/Gerbang:Masyarakat
https://ms.wikipedia.org/w/index.php?title=Gerbang:T394603/Masyarakat&redirect=no

The second is a redirect to the first ( https://ms.wikipedia.org/w/index.php?title=Gerbang:T394603/Masyarakat&action=history ). I imagine it was temporary and that Gerbang:T394603/Masyarakat can now be deleted by @Hakimi97

In T394603#10854498, @Bunnypranav wrote:

In T394603#10854358, @Hakimi97 wrote:

Hi @Bunnypranav , thank you for the configuration of Portal: and Portal talk: namespaces. However, our Malay language community wonder if there is a possibility to make "Portal" as a redirect/alias to "Gerbang", and "Perbincangan portal" as a redirect/alias to "Perbincangan gerbang", perhaps through wgNamespaceAliases?

This is because we would like to avoid the situation whereby the [[:ms:Portal:Senarai]] could not be automatically redirected to [[:ms:Gerbang:Senarai]] and instead become redlinked.

Commit created, will backport hopefully on Monday.

Hi @Bunnypranav , I have searched through the mswiki to see if there is any existing links with format of "[[Perbualan Portal" or "[[Perbualan_Portal", and there were only 12 relevant pages, and I have changed all of them manually into "Perbincangan gerbang". The remaining 5 of the search results (refer to https://ms.wikipedia.org/w/index.php?search=insource%3A%22Perbualan+Portal%3A%22&title=Khas%3ACari&profile=advanced&fulltext=1&ns0=1&ns1=1&ns2=1&ns3=1&ns4=1&ns5=1&ns6=1&ns7=1&ns8=1&ns9=1&ns10=1&ns11=1&ns12=1&ns13=1&ns14=1&ns15=1&ns100=1&ns101=1&ns126=1&ns127=1&ns710=1&ns711=1&ns828=1&ns829=1&ns1728=1&ns1729=1&searchToken=3jph3h8c8lcsbxxyf0g1t2mkk ) will be left as it is.

Hi @Bunnypranav , thank you for the configuration of Portal: and Portal talk: namespaces. However, our Malay language community wonder if there is a possibility to make "Portal" as a redirect/alias to "Gerbang", and "Perbincangan portal" as a redirect/alias to "Perbincangan gerbang", perhaps through wgNamespaceAliases?

• I'm pretty sure you're not allowed to link to or even mention the brand names Telegram or Instagram or Google from a sitenotice. you can't from a CentralNotice, I don't see why a different policy should apply here. you can link to those pages from a page on your wiki and link from the sitenotice to that page on your wiki. but not directly from sitenotice to the external site. this is urgent, must be fixed immediately. (unless you can show us where someone said this is ok?)

Hi everyone,

In T392984#10781365, @Anoop wrote:

In T392984#10781299, @Hakimi97 wrote:

In T392984#10781211, @Anoop wrote:

In T392984#10780152, @Lucas_Werkmeister_WMDE wrote:

AFAICT it seems to be relatively common for Portal namespaces to be included in $wgNamespacesToBeSearchedDefault, and the same sometimes seems to be true for Work namespaces too; should they be searched by default on mswikisource?

@Hakimi97 , Current only main namespace gets displayed on search by default, if you want to add above namespaces to appear in search results along with main namespace I can add it.

Hi @Anoop , I will certainly appreciate if you could do so.

if you want let me know if you want any other namespace to render in search by default, i will add it

In T392984#10781211, @Anoop wrote:

In T392984#10780152, @Lucas_Werkmeister_WMDE wrote:

AFAICT it seems to be relatively common for Portal namespaces to be included in $wgNamespacesToBeSearchedDefault, and the same sometimes seems to be true for Work namespaces too; should they be searched by default on mswikisource?

@Hakimi97 , Current only main namespace gets displayed on search by default, if you want to add above namespaces to appear in search results along with main namespace I can add it.

Hi everyone,

Ping back @bd808 and @JJMC89 since the last response.

Our community at Malay Wikipedia has granted the event-organizer right for one month.

Hi @ifried and @vaughnwalters , may I know for how long do your team need the event organizer right?

Hi @bd808 and @JJMC89, it has been 34 days since the last response from @Aviator. @Aviator has updated the license information to the GNU General Public License 3.0 or later. Is it possible for the adoption process to continue by adding me as co-maintainer?

In T379340#10306370, @Aviator wrote:

Aviator here. The tool is indeed licensed under GPL. As for the binary, it was compiled from my own code that is written in C++ or Rust (I can't remember but I can dig my old files). I intended it to be in GPL as well. I just never released the source code.

Let me know if I should publish the code to ease the tool adoption process.

In T379340#10304722, @JJMC89 wrote:

The tool's software is not in compliance with the Cloud Services Terms of use as it is not licensed under an OSI approved Open Software license. Only @Aviator can fix this.

In T379340#10306182, @Chlod wrote:

@Hakimi97: If you or others from the Malay community need some help on this part, I can provide some engineering support. I think the hardest part of this, though, is the actual translation. Based on the code that @EmpAhmadK sent over back at Wikimania, it seems to be using some black-box binary that also doesn't seem to be open-source (or at least, I can't find the code for it to begin with). So that'll probably have to be rewritten, but I can't help much in that aspect because I'm not fluent in the language.

In T379340#10305075, @LucasWerkmeister wrote:

If you want to reimplement the tool (my very naive guess, without ever having seen the tool in action, is that it seems like a manageable task in principle – the existing source code I can see is some 200 lines of Python, 50 lines of CSS, and 120 lines of XML), I think we could still add you to the tool (after removing the old code), so that the rewrite can be reached under the same tool name. I can’t say whether this makes sense or not for this tool (whether a lot of users will want to continue using the same URLs, or whether it would be more confusing to users if a new implementation shows up there). Of course, you can also do a rewrite in a new tool.

As an active user of various Malay Wikimedia projects, as well as a native Malay speaker who has learnt the Jawi script from a very young age, I would like to support the effort made by @EmpAhmadK.

In T363250#10051641, @Pppery wrote:

Some local admin should remove

[[en:MediaWiki:Proofreadpage header template]]
[[fr:Modèle:Proofreadpage header template]]
[[it:Template:Proofreadpage header template]]
[[pl:MediaWiki:Proofreadpage header template]]

from https://ms.wikisource.org/w/index.php?title=MediaWiki:Proofreadpage_header_template&action=edit

That seems to be the cause of most of the remaining old interwiki links, and is cascading to cause unrelated works to interwiki to the proofreadpage header template of other wikis.

Hi, I would like to ask is there anything that we could do regarding "Clean up old interwiki links"?

In T368868#9952596, @Soda wrote:

I assume these have community consensus ?

In T369047#9947984, @Anoop wrote:

@Hakimi97 , I have created patch for namespace creation, aliases and proofread extension namespaces please check it & confirm , project talk namespace Perbincangan Wikisumber defined

NS_PROJECT_TALK     => 'Perbincangan_$1',

in https://github.com/wikimedia/mediawiki/blob/master/languages/messages/MessagesMs.php#L42

'wgExtraNamespaces' => [
	'mswikisource' => [ // T369047
		102 => 'Pengarang', // Author
		103 => 'Perbincangan_pengarang', // Author talk
		114 => 'Terjemahan', // Translation
		115 => 'Perbincangan_terjemahan', // Translation talk
	],

'wgNamespaceAliases' => [
	'+mswikisource' => [ // T369047
		'Translation' => 114,
		'Translation_talk' => 115,
		'Author' => 102,
		'Author_talk' => 103,
	],

'wgMetaNamespace' => [
	'mswikisource' => 'Wikisumber', // T369047
];

'wgSitename' => [
	'mswikisource' => 'Wikisumber', // T369047
];

Proofread extension namespace configuration have been merged, will be live on wiki on or after 10 July

/** Malay (Bahasa Melayu) */
$proofreadPageNamespaceNames['ms'] = [
	'page' => 'Laman',
	'page_talk' => 'Perbincangan_laman',
	'index' => 'Indeks',
	'index_talk' => 'Perbincangan_indeks'
];

This is currently on-going at T368868, just leave this page as a proof that the community on Malay Wikisource has discussed and agreed on the permanent configuration of logo and wordmark.

The logo change is currently on-going at T368868, but the namespace configuration is still not done and was not mentioned at any pages on Wikimedia-Site-requests, therefore this task should remain open.

In T363250#9917916, @Soda wrote:

In T363250#9917903, @Hakimi97 wrote:

Hi, our community from Malay Wikisource is curious about normally who will be in charge of the configuration for the namespaces, logos and wordmarks? Will the configuration of the namespaces, logos and wordmarks done after all the wiki import task done, or the configuration could be setup at anytime?

Nobody in particular is in charge. Y'all will need to follow the general steps outlined in Requesting_wiki_configuration_changes

Hi, our community from Malay Wikisource is curious about normally who will be in charge of the configuration for the namespaces, logos and wordmarks? Will the configuration of the namespaces, logos and wordmarks done together with other wikis created this year (and does it mean that we need to wait for all wiki import work to be done), or the configuration could be setup at anytime independent from the creation of other wikis?

Hello @Urbanecm, sorry to reopen the closed task regarding the implementation of intersection on Malay Wiktionary. However, I would like to consult a few matters here:

@elukey I have tried to run using Python for both Revert Risk Language Agnostic and Multilingual Revert Risk models, and both of them work well! Thank you for the support, I will let you know if there is any doubt later.

In T349968#9336577, @elukey wrote:

@Hakimi97 Hi! The ML team doesn't plan to support/expand revscoring-based models in the future, we and the Research team suggest to try the Revert Risk models instead. There are two variants:

• Language Agnostic - https://meta.wikimedia.org/wiki/Machine_learning_models/Proposed/Language-agnostic_revert_risk
• Multi-Lingual - https://meta.wikimedia.org/wiki/Machine_learning_models/Proposed/Multilingual_revert_risk

As far as I can see the Language Agnostic model supports the ms language, so would you be open to give it a try?

https://api.wikimedia.org/wiki/Lift_Wing_API/Reference/Get_reverted_risk_language_agnostic_prediction

For reference purpose:
https://meta.wikimedia.org/wiki/Research:Revision_scoring_as_a_service/Word_lists/ms

Actually, we previously attempted to convert from the Roman Malay script (also known as Rumi script) to the Arabic Malay script (also known as Jawi script) at https://ms.wikipedia.org/wiki/Wikipedia:WikiProjek_Jawi. A Malay Wikipedia user named Kurniasan assisted us in creating the code for conversion, as shown on the page: