Page MenuHomePhabricator

[Self-Hosting] Improve Installation - 09.06.2026
Closed, ResolvedPublicGoal

Description

Long Term Goal:
Wikibase self-hosting operations are more accessible, robust and easier to manage.

Goal Q1 & Q2:
The ease of self-hosting improves, as measured against the baseline metric and target defined in Q4 2025.

We defined time for installation as a metric to measure the ease of self-hosting. We have chosen this metric due to the low adoption rates of Wikibase Suite assuming most dropouts occur during installation. The average installation time is 120 minutes (!) with a target to reduce this to 60 minutes at least.

The working doc to track current state and further improvements

Details

Due Date
Jun 9 2026, 11:00 AM

Event Timeline

Leif_WMDE triaged this task as Medium priority.Jan 14 2026, 4:49 PM
Leif_WMDE changed the edit policy from "All Users" to "Task Author".Jan 14 2026, 5:03 PM
Leif_WMDE set Due Date to Jun 9 2026, 11:00 AM.
Leif_WMDE renamed this task from [Self-Hosting] Improve Installation to [Self-Hosting] Improve Installation - 09.06.2026.Jan 14 2026, 5:11 PM
Leif_WMDE raised the priority of this task from Medium to High.Jan 20 2026, 3:46 PM
Leif_WMDE added a subscriber: Deepesha_WMDE.
Leif_WMDE changed the subtype of this task from "Task" to "Goal".Feb 3 2026, 2:53 PM

I don't know what approach are you working in but lately I'm thinking probably we need to use a different repo than https://github.com/wmde/wikibase-release-pipeline for just the current «deploy» content since AFAIK there is no need for the immense amount of users for the pipeline code. Probably this change will have minor impact but would reduce the complexity a bit. Also, naming, neither «wikibase-release-pipeline» or «deploy» are meaningful. So, this new repo would have a better naming as «wikibase-suite-something» or similar.

My 2¢.

Another point related in my point of view. Now we have a set of minimal properties ready to be imported in a empty WB with the needed tools. See wikibase-bootstrap and T391815.

Thanks @Olea, we will definitely take that into consideration :)