We should deprecate and remove the VueTest extension in favor of CodexExample.

Background

When we were first getting started with Vue.js in MW, we created the VueTest extension as a test-bed and example to show to other WMF developers. Later, we also worked out a somewhat flaky way to get un-merged Codex code inside this extension to allow for testing of upcoming features inside a MediaWiki environment. Finally, we used this extension as a target for the Pixel tool to attempt to catch possible visual regressions caused by changes to Codex components.

However, the developer experience of maintaining this extension has always been poor, and the visual regression tests have suffered from a poor signal-to-noise ratio (making the tests essentially useless – we have too many warnings due to minor, unrelated changes to various other MW skins/extensions/core features). After Codex matured, we created a new stand-alone CodexExample extension that is a better showcase of how to use the features that DST is developing, and the Codex documentation site has also come a long way.

Acceptance Criteria

• Remove VueTest from any WMF-wide Pixel configuration that is currently (see here for an example of how VueTest was first added to Pixel)
• Remove VueTest from BetaLabs (https://en.wikipedia.beta.wmflabs.org/wiki/Special:VueTest/codex)
• Remove VueTest from the WMF branching script (https://gitlab.wikimedia.org/repos/releng/release/-/blob/0ecaf86d7a2176a6dd2c95a640634b500ae72f1c/make-release/settings.yaml#L206)
• Remove all documentation references to VueTest and update the links to point to CodexExample; this search is a good place to start
• Update the MW Page for this extension to indicate that it is no longer active (should probably point folks to CodexExample instead)
• Mark the Gerrit repo as archived/read-only, or even just delete it all together. **
• Remove the demo build in the codex-docs package Found no instance of VueTest in codex docs

Standard extension archival checklist

• On-wiki documentation
  • Archive documentation on mediawiki.org (https://www.mediawiki.org/wiki/Extension:VueTest): replace page contents with {{Archived extension|last revision id before archiving|task=T######}} (for extensions)/{{Archived skin|last revision|task=T######}} (for skins); replace T###### with this task's number.
  • If documentation page was translatable, remove <translate>, visit Special:PageTranslation, and click "remove from translation" (if you don't have the translation administrator right, ask a user who does).
  • Update Wikidata item (https://www.wikidata.org/wiki/Q124314643) associated with documentation page
    • add statement Abandonware (Q281039) to instance of (P31) together with qualifier start time (P580) = the YYYY-MM-DD date that you decided to archive extension/skin (generally per edit history)
    • add qualifier end time (P582) = the YYYY-MM-DD (same date as above) to instance of (P31) = MediaWiki extension (Q6805426)/MediaWiki skin (Q21996535)
• Phabricator
  • Mark all Phabricator tasks for the extension/skin either Declined or Invalid. Add a comment pointing to this task when doing so for reference.
  • Archive Phabricator project VueTest for the extension/skin.
  • Edit Phabricator project VueTest description for the extension/skin with a link to this ticket.
• Translatewiki.net/translations
  • If the extension is deployed on Wikimedia sites, but it is known that it's not going to receive significant feature updates or deployed to new wikis, make sure that its project ids (usually "ext-extensionname") appear in the groups/MediaWiki/WikimediaLegacyAgg.yaml file in the translatewiki Gerrit repository and not in WikimediaMainAgg.yaml, WikimediaAdvancedAgg.yaml, etc. (If it also has an api group, it should remain in WikimediaTechnicalAgg.yaml).
  • If the extension is no longer deployed on Wikimedia sites, remove it from all Wikimedia*Agg.yaml. (If it was ever deployed, by this time, it's most likely in WikimediaLegacyAgg.yaml or WikimediaTechnicalAgg.yaml.)
  • If the extension is going to be completely archived and no longer developed, remove it completely from translatewiki.net by making sure that its project IDs don't appear in any of the following files:
    • groups/MediaWiki/ExtensionsAgg.yaml
    • groups/MediaWiki/SkinsAgg.yaml
    • groups/MediaWiki/mediawiki-extensions.txt
    • groups/MediaWiki/mediawiki-skins.txt
    • repoconfig.yaml
    • mw-config/validation-exclusion-list.php
• Configuration/tests/integrations/etc.
  • Remove tests in integration/config (zuul/layout.yaml). 1223248*
  • Remove manifest/other references from mediawiki/vagrant if they exist. (Found no instance of 'vuetest' here).
  • Remove from https://doc.wikimedia.org/cover-extensions/ if present (requires Continuous-Integration-Infrastructure shell user to delete directly from the server).
• Repositories
  • Remove from mediawiki/extensions / mediawiki/skins (along with in .gitmodules).**
  • Mark the repository read-only in Gerrit (also edit description to prepend "[ARCHIVED]" and a reference to this task, remove all access lists and reparent on All-Archived-Projects): https://gerrit.wikimedia.org/g/mediawiki/extensions/VueTest **
  • Deactivate the Diffusion repository for the extension/skin: rEVTE extension-VueTest**
  • Delete the GitHub mirror: https://github.com/wikimedia/mediawiki-extensions-VueTest **

In review*
Perms required**