Wikimedia Release Engineering Team/Roles

This page outlines roles and their responsibilities in the context of the Wikimedia Release Engineering Team.

Tech Lead
The Tech Lead for a project is responsible for overall direction setting, determining short-term plans, and being aware of the project's health.

A Tech Lead is assigned for every project that has a quarterly goal (see Goals) and is continuous for the quarter. Changes to the Tech Lead happen at the start of new quarterly goal work, usually around the time of quarter switch over.

Responsibilities

 * Arranging, scheduling, preparing, miscellaneous wrangling, and leading of any meetings needed for the successful completion of the project.
 * Communication of project status update during weekly Release Engineering Team meeting (eg: what recently happened, what the current near-term plan is, and anything anyone is blocked on).
 * Project workboard maintenance
 * Delegation and prioritization of tasks necessary to reach the project goal
 * Balancing maintenance tasks associated with the project with new work
 * "Public" project communication – notes/docs/wikipages/changelogs/mailing list things – communicating priorities and direction to the world outside of RelEng.
 * Performing new software releases and upgrades, interfacing with opsen where appropriate.

Train Conductor
The Train Conductor is responsible for all aspects of rolling out the latest production deploy of MediaWiki and extensions (the bulk of Wikimedia's user-facing code).

A Train Conductor is assigned via 2 week rotations within the Wikimedia Release Engineering Team.

Responsibilities

 * Perform the train release, see Heterogeneous deployment/Train deploys
 * Revert when issues arise, (quickly) assign people to fix issues when needed.
 * Address Logspam by:
 * Identifying new logspam and reporting it in Phabricator.
 * Nudging relevant parties to address said logspam. With increasing assertiveness.
 * Comment on relevant task AND the weekly train deployment blocker task.
 * Review old logspam tasks and either:
 * verify resolved, or,
 * nudge relevant parties with increasing assertiveness.
 * Phase 1: Get the group0 log dashboard to zero log messages.
 * Phase 2: Keep the group0 log dashboard at zero log messages.