You are browsing a read-only backup copy of Wikitech. The primary site can be found at

Wikimedia site requests

From Wikitech-static
Revision as of 12:05, 21 February 2020 by imported>Aklapper (Add "Remove a namespace from being indexed by internet search engines")
Jump to navigation Jump to search

Wikimedia site requests are requests to configure a Wikimedia project. This page gives an overview of the process for volunteers handling them, and other concerned parties from operations side.

If you want to contribute technically, then this is a good way to get familiar and start contributing to software changes. You need very basic knowledge of PHP and follow mw:Gerrit/Tutorial to create your first software change (a so-called "patch"). When you work on these types of tasks you can also look at previous similar software changes. Often you do not even have to too much understanding of what is going on exactly. But still you can get familiar with code and especially processes!

Lifecycle of a request

A request generally follows this workflow:

  1. The local project discuss the matter, in the manner the most appropriated for this project.
  2. A task is filled on Phabricator, in the Wikimedia-Site-requests project (or Wikimedia-Extension-setup if the change is about enabling an extension). See meta:Requesting wiki configuration changes. Please check Limits to configuration changes before.
  3. A volunteer writes a change (patch) to change the relevant files in the operations/mediawiki-config repository, and proposes the patch in Gerrit. (If you follow Gerrit/Commit message guidelines, then the Phabricator task will automatically get updated about your patch in Gerrit.)
  4. Someone else will review your patch in Gerrit.
  5. If your patch is all good, the same volunteer - or if reluctant/absent/busy, another volunteer - schedules it for SWAT deployment on the Deployments page.
  6. The change is merged and deployed on the Wikimedia servers, usually within one week but sometimes also faster.


The requests are handled in a fast pace, using a one week cadence: we can deploy them three times per day between Monday and Thursday. There is no formal sprint.

Priority on Phabricator Description
Unbreak now! The change breaks normal production. You want a deployment right now or in the next hours. That also means you consider this task requests we set other requests aside.
High The change is needed very soon, ideally in the next SWAT, or if not possible, this SWAT week (Monday-Thursday).
Normal The change is helpful, we can do it this SWAT week or the next (so in max. 7-10 days). This is the priority assigned to most simple tasks.
Low The change isn't needed before two weeks.
Lowest The change can take as long as needed, or there is nothing actionable before a long time.

Common tasks

Disable throttling of account creations for an IP at events

Often requested by editors who are hosting an edit-a-thon, account creation throttle exception are one of the most common tasks which Wikimedia site requests deals with. Such requests should follow meta:Mass account creation#Requesting temporary lift of IP cap.

  • Make your changes in the file wmf-config/throttle.php in the repository operations/mediawiki-config
    • from UTC date/time of exception start
    • to UTC date/time of exception end
    • range IP range(s) the exception applies to
    • dbname wiki(s) this exception applies to
$wmgThrottlingExceptions[] = [ // T184579
	'from' => '2018-01-11T09:00 +5:30',
	'to' => '2018-01-11T18:00 +5:30',
	'range' => [ '', '' ],
	'dbname' => [ 'enwiki', 'mrwiki' ],
	'value' => 45 // 35 expected

Change the logo of a Wikimedia wiki

'avwiki' => '/static/images/project-logos/avwiki.png', // T48589

Add a custom namespace

Change a namespace

  • Make your changes in the file wmf-config/InitialiseSettings.php in the repository operations/mediawiki-config
  • If necessary, also alias old names under wgNamespaceAliases in the file wmf-config/InitialiseSettings.php in the repository operations/mediawiki-config
  • Past example: phab:T202347 and
  • After config change, namespaceDupes.php maintenance script

Change the translation of a namespace

  • Namespace localization must happen in the extension that the namespace belongs to.
  • Namespace localization can require separate patches in some repositories. See e.g.
  • To deploy a custom namespace only on Wikimedia sites (and not in the MediaWiki software for everybody), the file to change is wmf-config/InitialiseSettings.php in the repository operations/mediawiki-config. This file also allows you to change project namespace (wgMetaNamespace).

Change the linktrail

Update the interwiki cache

Change local group rights

  • Change/define the group's right under GroupOverrides in the file wmf-config/InitialiseSettings.php in the repository operations/mediawiki-config
  • Change who can grant the group using (Add|Remove)Groups(Self), otherwise, only the stewards will be able to grant/remove it.

Change user groups and restriction levels

Enable or disable extensions on a wiki

Change import sources

Add a website to CopyUploadsDomains (e.g. for GWToolset)

Convert digits (numbers) into a different script

Remove a namespace from being indexed by internet search engines

Areas in the MediaWiki code base itself

These tasks are about the general MediaWiki code base itself, and not about the configuration of MediaWiki on Wikimedia servers like the tasks above.

Replacing deprecated functions

These functions could be found by phan checks or a good IDE with static analytic code checks.

Upgrading dev libraries

This is sometimes done by a bot, but that is not always and not everywhere the case.

Alphabetize stuff

Useful links