Release new version of Canasta for MediaWiki 1.43

[yaronkoren]

Now that MediaWiki 1.43 has been released, it's time to release the corresponding Canasta version, which would presumably be Canasta 3.0. I think this will be a much simpler upgrade than any previous release - mostly it should just consist of getting the files extensions.yaml and skins.yaml updated: adding and removing extensions (and maybe skins), getting rid of or updating patches, and of course updating the commit/revision ID for possibly every extension and skin.

Below are the relevant "issues" for extension addition/removal.

Extension additions with consensus:

• Add Extension:OAuth #237
• Add Extension:QuickInstantCommons #238
• Add Extension:Paragraph-based Edit Conflict Interface #239
• Add Page Schemas extension #348
• Add InlineComments extension #362

Extension additions without clear consensus - discussion required:

• Add PagePermissions extension #176
• Add Moderation extension #203
• Add ManageWiki extension #350
• Add EditNotify extension #354
• Add Extension:ParserMigration in next LTS #387
• Re-add WikiForum extension #480

Extension removals:

• Remove TinyMCE extension #359
• Remove Semantic Breadcrumb Links extension #360

Extension removals without clear consensus - discussion required:

• Remove Semantic Tasks extension #473
• Remove Semantic Forms Select extension #474
• Extensions to verify for MW 1.43 version #477 (list of another 16 (!) "questionable" extensions)

In addition, the extensions DiscussionTools, Echo, Linter, LoginNotify and Thanks are bundled into MediaWiki 1.43 but were not in 1.39; conversely, Renameuser was removed from the set of bundled extensions after MW 1.39. (Its functionality was merged into core.) There is no change to the set of bundled skins, as far as I can tell.

For Canasta, this means that the DiscussionTools and LoginNotify extensions need to be added to extensions.yaml (with "bundled: true"); the Echo, Linter, and Thanks extensions need to be changed in extensions.yaml to just have "bundled: true"; and the Renameuser extension needs to be removed.

Some of the extension patches need to be updated as well. Here are my thoughts about the five patches currently in Canasta:

• For Semantic Watchlist - still needed? It's not clear if "composer update" (and thus this patch) was ever actually needed for this extension in the first place
• For Semantic Breadcrumb Links - should be removed if Semantic Breadcrumb Links is removed
• For Semantic Compound Queries - no longer needed, after the SCQ developers finally accepted this patch a few days ago (!)
• For Semantic Result Formats - still needed, but in modified form
• For Semantic Scribunto - seems to no longer be needed, after this change

The only remaining type of patch involves removing the Semantic MediaWiki "requirement" in the composer.json files of SMW-based extensions, since it messes up Canasta's Git-based download. Unfortunately, it appears that more of the SMW-based extensions include such a line in their composer.json files than last time. I created an issue for this on the main SMW repository. If there's general agreement that these lines should be removed (and we can get PRs accepted for each of the extensions), then it could be that the next Canasta version will have no extension patches; on the other hand, if there's no agreement, there might be as many as seven of these tiny patches required. then 1-3 patches would be required. (I didn't think about it fully before - I'm pretty sure the SMW requirement is actually only a problem for extensions that also need a composer update.)

Other extension issues that it would be good to fix up (then use the latest version) before the next Canasta release:

• Cargo code currently not passing validation, and thus new patches getting blocked - see https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Cargo/+/1103408
• OpenIDConnect code DB issue - see https://phabricator.wikimedia.org/T378904

The only other issues that seem to make sense to resolve/handle with the new Canasta version are the following:

• Update to Debian 12 Bookworm #377
• Figure out ideal mailing approach for Canasta #446

[yaronkoren]

@jeffw16, @tosfos - your thoughts on all of these are welcome, but especially your views on the "iffy" extension additions and removals. Personally, I think the two additions that there's the strongest case for are OAuth and EditNotify, but I'm biased in the case of EditNotify.