You are browsing a read-only backup copy of Wikitech. The live site can be found at wikitech.wikimedia.org
Wikimedia site requests: Difference between revisions
Jump to navigation
Jump to search
imported>Alex Monk |
imported>MarcoAurelio No edit summary |
||
Line 6: | Line 6: | ||
# A task is filled on Phabricator, in the [https://phabricator.wikimedia.org/project/board/178/query/open/ Wikimedia-Site-requests project]. See [[meta:Requesting wiki configuration changes]]. | # A task is filled on Phabricator, in the [https://phabricator.wikimedia.org/project/board/178/query/open/ Wikimedia-Site-requests project]. See [[meta:Requesting wiki configuration changes]]. | ||
# A volunteer writes a change to edit the relevant files in the [https://phabricator.wikimedia.org/diffusion/OMWC/ operations/mediawiki-config] repository. | # A volunteer writes a change to edit the relevant files in the [https://phabricator.wikimedia.org/diffusion/OMWC/ operations/mediawiki-config] repository. | ||
#: Note: please check [[m:Limits to configuration changes|Limits to configuration changes]] before. | |||
# The same volunteer - or if reluctant/absent/busy, another volunteer - schedules it for [[SWAT deploys|SWAT deployment]] on the [[Deployments]] page. | # The same volunteer - or if reluctant/absent/busy, another volunteer - schedules it for [[SWAT deploys|SWAT deployment]] on the [[Deployments]] page. | ||
# The change is merged and [[How to deploy code|deployed]]. | # The change is merged and [[How to deploy code|deployed]]. | ||
== Prioritisation == | == Prioritisation == | ||
The requests are handled in a fast pace, using a one week cadence: we can deploy them twice per | The requests are handled in a fast pace, using a one week cadence: we can deploy them twice per day between Monday and Thursday. There is no formal sprint. | ||
{| class="wikitable" | {| class="wikitable" |
Revision as of 09:40, 14 April 2016
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.
Lifecycle of a request
A request generally follows this workflow:
- The local project discuss the matter, in the manner the most appropriated for this project.
- A task is filled on Phabricator, in the Wikimedia-Site-requests project. See meta:Requesting wiki configuration changes.
- A volunteer writes a change to edit the relevant files in the operations/mediawiki-config repository.
- Note: please check Limits to configuration changes before.
- The same volunteer - or if reluctant/absent/busy, another volunteer - schedules it for SWAT deployment on the Deployments page.
- The change is merged and deployed.
Prioritisation
The requests are handled in a fast pace, using a one week cadence: we can deploy them twice 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. |