Page MenuHomePhabricator

Service Ownership and Maintenance
Open, NormalPublic


The number of services running in WMF production has been steadily increasing lately: OCG, Mathoid, Citoid, Parsoid, RESTBase, Graphoid, Maps, MobileApps, etc. The Services team does a fair amount of mentoring other teams during the initial development and deployment process.


Developers have found it easy to develop new services and implement changes iteratively. However, service ownership and maintenance currently falls on Services by default, which has several drawbacks:

  • Scalability. The team has 4 members which work in various areas. Hence, maintaining the status quo in ownership and maintenance while increasing the number of deployed services will not be feasible.
  • Feature know-how. Having a feature being implemented as a service does not mean that the Services team is capable of implementing urgently-needed changes to running software.


Let's try to find solutions to the following problems:

  1. Re-evaluate the ownership status of the deployed services
  2. How can services be efficiently owned by teams lacking back-end / production knowledge?
  3. What is the long-term strategy for services in production? What happens to services when their owners leave / give up / etc?

Event Timeline

mobrovac created this task.Jan 4 2016, 7:10 PM
mobrovac raised the priority of this task from to Needs Triage.
mobrovac updated the task description. (Show Details)
mobrovac added subscribers: mobrovac, Joe, dr0ptp4kt and 4 others.
Restricted Application added subscribers: StudiesWorld, Aklapper. · View Herald TranscriptJan 4 2016, 7:10 PM
Eevans awarded a token.Jan 4 2016, 7:46 PM
Eevans added a subscriber: Eevans.

Wikimedia Developer Summit 2016 ended two weeks ago. This task is still open. If the session in this task took place, please make sure 1) that the session Etherpad notes are linked from this task, 2) that followup tasks for any actions identified have been created and linked from this task, 3) to change the status of this task to "resolved". If this session did not take place, change the task status to "declined". If this task itself has become a well-defined action which is not finished yet, drag and drop this task into the "Work continues after Summit" column on the project workboard. Thank you for your help!

mobrovac triaged this task as Normal priority.Jan 20 2016, 8:14 PM
mobrovac set Security to None.
GWicke moved this task from Inbox to Under discussion on the TechCom-RFC board.
GWicke moved this task from Backlog to attic on the Services board.Jul 12 2017, 5:24 PM
GWicke edited projects, added Services (attic); removed Services.
mobrovac changed the task status from Open to Stalled.Aug 8 2017, 10:53 PM
mobrovac added a project: User-mobrovac.
Krinkle changed the task status from Stalled to Open.Jan 24 2018, 9:24 PM
Krinkle edited projects, added TechCom; removed TechCom-RFC.
daniel moved this task from Inbox to Backlog on the TechCom board.Mar 7 2018, 9:32 PM

I made similar questions at but they were out of scope there, but I guess they are similar to these.