Problem: Module CS1 suite is currently maintained in EnWiki even though it's de facto used worldwide for citations. Keeping track of changes is difficult and this makes the continuous update process needed to run it pretty difficult in different wikis, especially small ones.
Who would benefit: All wikis, especially small ones.
Proposed solution: Globalize module CS1. Find a way to track updates in different Wikis, notify them when new updates are available and help them do the updates when they're available.
@Pigsonthewing: Thank you for that! Actually I am aware of that or even of the phab tasks of producing global modules. But the problem, as everyone knows, is that they're not progressing much as projects. If you read my original post (in More comments), you'll see that I propose another approach to handle this situation: We create a big dynamic table on here (Meta) that we use to keep track of all the Wikis that use the said module and how updated is their version of it compared to the default one. (Maybe we can name updates.) The table would also include specific wishes or changes they wish to make to the their version of the module compared with the default version of it (The EnWiki one). Then every time the default one gets updated, wikis are notified en masse in their village pumps automatically by Mediawiki Message Delivery, describing what has changed and what they need to do to "get the update". Some volunteers also get mentioned who said users can contact for help in their updating process. If things go well, we can have global bots to help us in this process. To keep the dynamic table updated and maybe even to help globally on the update of some pages of the module that don't need much change and could be handled in a copy-paste manner. The said module also has its maintenance, property and error categories and its help pages. A lot of small Wikis don't know how to actually solve the problems with pages that get sorted in these categories. This could be handled the same way as the update process I mentioned above. Some global bots could help solve some easy problems (I already have one doing that on SqWiki and SqQuote), some volunteers could set themselves up as contacts to help small Wikis solve them... All this process is sort of already happening, it's just that it's happening on EnWiki and the only volunteer helping is Trappist. I think if it (this process) could be Metafied, (what I described above and more or other ideas other people might have) it would provide an easier global infrastructure. I'm already ready to help to set something like this up but only me and Trappist can't really deal with just the information gathering to create the said table, let alone maintain it and help keep the whole process up to date. So we either need more volunteers willing to participate in this idea, or more technical ideas how to automatize tasks needed for a process like this. - Klein Muçi (talk) 21:23, 26 November 2020 (UTC)[reply]
If I understand your suggestion correctly, a thing like what you suggest already exists at mw:Multilingual Templates and Modules, with the DiBabel tool. User:Yurik can say much more about that.
From what I saw at the MW page, it does look like it dabbles with the same idea I'm talking about. But given that it is the first time I encounter that page (or that tool/bot), I'd really like some more in-depth explanations about it. I hope Yurik can help, even though I sort of believe the aforementioned conversation would be better held between Yurik and Trappist the monk to settle if the tool can somehow help with module CS1.
Yes, I think I'll show my support even to that idea. Even though it deals mostly with templates and I think it reaches my idea tangentially, I support everything that helps internationalization of templates and modules. I do believe CTT is really a powerful tool (thank you) and can be helpful in different ways. Actually, I've writen you on EnWiki in the past about it and the idea of extending its function to integrate some mw:Extension:BoilerRoom logic to be helpful for us in SqQuote, but I didn't get an answer. - Klein Muçi (talk) 11:41, 27 November 2020 (UTC)[reply]
Oppose This is just a facet of the larger problem of template globalization. That is a huge problem, but it needs to be tackled comprehensively, and to the extent that small workarounds detract from its urgency, they're an unproductive use of developer resources. {{u|Sdkb}}talk05:19, 9 December 2020 (UTC)[reply]
Support in spirit, though I agree this is just an aspect to template globalization. So consider this a support for template globalization. Given the super-mega-complexity of the w:en:Help:CS1 citation template system, I do not believe it is a good initial testbed. Start with smaller stuff, and work up to that monster. — SMcCandlish ☺☏¢ >ʌⱷ҅ᴥⱷʌ< 05:28, 15 December 2020 (UTC)[reply]
Support YFdyh000 (talk) 23:28, 8 December 2020 (UTC)
Oppose This is just a facet of the larger problem of template globalization. That is a huge problem, but it needs to be tackled comprehensively, and to the extent that small workarounds detract from its urgency, they're an unproductive use of developer resources. {{u|Sdkb}} talk 05:19, 9 December 2020 (UTC)
