Prio Notes:

This task is to have a review system ready in time for the beginning of the Mobile Editing Project beginning in Q1 2025. Work should be focused on be prepared for this project and leaving this at a prototype/MVP status is enough to meet the needs

Some thoughts:

• We could either create one VM and serve both instances from there (needs less computation resources) or create two VMs, each serving a single instance (which would simplify the operation).
• I think for this we should use the mw cli (using --context it even allows running multiple stacks of all services).
• For surfacing which versions are running, it should be possible to either set something like $wgSiteNotice manually on deploy and/ or create a tiny extension that shows small excerpts of the git log of relevant extensions on a special page (or something like this).
• Maybe use git for the MW local settings (LocalSettings.php) (create them in a git repo somewhere accessible by the webserver's php) and create symlink to that file?

Note: my local test wiki setup might contain some useful pieces if we choose to go with mw cli.

Hi, folks! This is showing up in a list of Horizon bugs and I don't understand what it has to do with Horizon. Is it possible that when you say 'Horizon' you just mean cloud-vps? (Horizon is the name of the web interface for managing cloud-vps systems.)

In T380031#10446068, @Andrew wrote:

Is it possible that when you say 'Horizon' you just mean cloud-vps?

That’s correct, but I I would’ve thought this little imprecision should be harmless as long as we didn’t tag the task with Horizon...

good live test ticket is https://phabricator.wikimedia.org/T338483

I believe the solution now deployed to our cloudvps box meets the acceptance criteria:

• Overview page: https://wikidata-uxtest.wmcloud.org/
• Deployment environment #1: https://berlin-wikidata-uxtest.wmcloud.org/
• Deployment environment #2: https://marburg-wikidata-uxtest.wmcloud.org/

The admin scripts (restore-latest-master and stage-gerrit-change) are available to users logged into the host at special-new-lexeme-testing.wikidata-dev.eqiad1.wikimedia.cloud. Source code for the admin scripts is available at https://gitlab.wikimedia.org/arthurtaylor/uxtesting-wiki-admin, including documentation about how to use and update the tool.

In T380031#10447381, @Lucas_Werkmeister_WMDE wrote:

In T380031#10446068, @Andrew wrote:

Is it possible that when you say 'Horizon' you just mean cloud-vps?

That’s correct, but I I would’ve thought this little imprecision should be harmless as long as we didn’t tag the task with Horizon...

you're right! This came up in an unrelated search and I briefly panicked that I'd been ignoring something important :)

Code looks sensible to me, and it seems to work as expected.

proposal: Product Verification consists of using this solution to verify T338483 (or whatever the next UX-involved ticket is)

This is all working for me, but as we are making Vector 2022 the default and scoped type-ahead search will be in Vector 2022, would it be possible to make the default skin Vector 2022? Or is it just set to Wikidata's current default?

I can still access it using ?useskin=vector-2022 but would be easier to navigate and check without having to add it to every page.

I’ve edited both LocalSettings.php files (with sudo -e – curiously, sudo -u www-data -e didn’t work) to set $wgDefaultSkin to "vector-2022".