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: