Wikimedia Release Engineering Team/Goals/201718Year
201718-Q1
[edit]#releng-201718-q1 (Phabricator project) -- All Technology team Q1 goals: Wikimedia_Technology/Goals/2017-18_Q1
Annual Program/Outcome | Quarterly Objective | Tech Goal | Team Goal | Dependencies | Team members | ETA | Status |
---|---|---|---|---|---|---|---|
Program 1: Availability, performance, and maintenance
Outcome 1: All production sites and services maintain current levels of availability or better Objective 1: Deploy, update, configure, and maintain production services |
|
D: Tech Debt |
|
|
EOQ | Done | |
Program 1: Availability, performance, and maintenance
Outcome 5: effective and easy-to-use testing infrastructure and tooling Milestone 1: Develop and migrate to a JavaScript-based browser testing stack |
|
C. Improve our own feature set
D: Tech Debt |
|
|
End of Q2 | In progress | |
Program 6: Streamlined service delivery
Outcome 2: unified pipeline towards production deployment. Objective 2: Set up a continuous integration and deployment pipeline |
|
C. Improve our own feature set
D: Tech Debt |
|
|
EOQ | Not done |
201718-Q2
[edit]#releng-201718-q2 (Phabricator project) -- All Technology team Q2 goals: Wikimedia_Technology/Goals/2017-18_Q2
Annual Plan Program | Annual Plan Outcome | Milestone/Objectives | Quarterly Work/Goal | Tech Goal | Dependency | Team members | ETA | Status |
---|---|---|---|---|---|---|---|---|
Program 1: Availability, performance, and maintenance | Outcome 1: All production sites and services maintain current levels of availability or better. | Objective 1: Deploy, update, configure, and maintain production services (Traffic infrastructure, databases & storage, MediaWiki application servers, (micro)services, network, and miscellaneous sites & services) | Work
|
D. Modernization, renewal and tech debt goals | Technical Operations |
|
Ongoing | To do |
Outcome 5: effective and easy-to-use testing infrastructure and tooling | Objective 1: Maintain existing shared Continuous Integration infrastructure | Work
|
D. Modernization, renewal and tech debt goals | Technical Operations, Cloud Services |
|
Ongoing | Done | |
Milestone 1: Develop and migrate to a JavaScript-based browser testing stack | Goal
|
C. Improve our own feature set
D: Tech Debt |
All developers |
|
EOQ | Done | ||
Outcome 6: Engineering teams can effectively plan, track, and complete their work. | Milestone 1: Maintain and improve existing shared code-review platform (Gerrit) | Work
|
D Modernization, renewal and tech debt goals | Technical Operations |
|
Ongoing | In progress | |
Milestone 2: Maintain and improve existing shared project management platform (Phabricator) | Work
|
D Modernization, renewal and tech debt goals | Technical Operations (Traffic) |
|
Ongoing | Done | ||
Program 3: Addressing technical debt | Outcome 1: The amount of orphaned code that is running Wikimedia “production” services is reduced. | Objective 1: Define a set of code stewardship levels (from high to low expectations) - task T174090 | Goal
|
B: Features we build for others
D: Tech Debt |
Code Health Group |
|
EOQ | Done |
Objective 2: Identify and find stewards for high-priority/high use code segment orphans - task T174091 | Goal
|
B: Features we build for others
D: Tech Debt |
Code Health Group, Current and future code/product stewards | End of Q3 | To do | |||
Outcome 2: Organizational technical debt is reduced. |
Objective 1: Define a “Technical Debt Project Manager” role that regularly communicates with all Foundation engineering teams regarding their technical debt |
Goal
|
B: Features we build for others
D: Tech Debt |
WMF Product Mangers (or similar) | EOQ | Done | ||
Objective 2: Define and implement a process to regularly address technical debt across the Foundation |
Goal
|
B: Features we build for others
D: Tech Debt |
End of Q3 | To do | ||||
Program 6. Streamlined service delivery | Outcome 2: Developers are able to develop and test their applications through a unified pipeline towards production deployment. | Objective 2: Set up a continuous integration and deployment pipeline to publish new versions of an application to production via testing and staging environments that reliably reproduce production | Goal
|
C. Improve our own feature set
D: Tech Debt |
Technical Operations, Services |
|
EOQ | Done |
201718-Q3
[edit]#releng-201718-q3 (Phabricator project) -- All Technology team Q3 goals: Wikimedia_Technology/Goals/2017-18_Q3
Annual Program/Outcome | Objective | Quarterly Work | Tech Goal | Dependency | Team members | ETA | Status |
---|---|---|---|---|---|---|---|
Program 1: Availability, performance, and maintenance
Outcome 5: We have effective and easy-to-use testing infrastructure and tooling for developers. |
Milestone 1: Develop and migrate to a JavaScript-based browser testing stack |
Specific improvements to the now canonical framework, see: task T182421, notably:
|
B: For others |
|
EOQ | To do | |
Objective 1: Maintain existing shared Continuous Integration infrastructure |
|
B: For others |
|
|
EOQ | To do | |
Program 3: Tech Debt
Outcome 1: The amount of orphaned code that is running Wikimedia “production” services is reduced. |
Objective 2: Identify and find stewards for high-priority/high use code segment orphans - task T174091 | Obj. 2 | C: Tech Debt | All teams |
|
EOQ | In progress |
Program 3: Tech Debt
Outcome 2: Organizational technical debt is reduced. |
Objective 2: Define and implement a process to regularly address technical debt across the Foundation | Obj. 2 | C: Tech Debt |
|
EOQ | In progress | |
Objective 3: Promote and surface important technical debt topics at large gatherings of Wikimedia developers (e.g., DevSummit and Hackathon(s)) | Obj. 3 | C: Tech Debt |
|
EOQ4 | To do | ||
Program 6: Streamlined service delivery | Objective 2: Set up a continuous integration and deployment pipeline | Build a functional PoC to verify the basic functionality of the 'production' image in the context of an isolated k8s deployment initially targeting mathoid. | C: Tech Debt
D. Improve our own feature set |
|
|
EOQ | In progress |
201718-Q4
[edit]#releng-201718-q4 (Phabricator project) -- All Technology team Q4 goals: Wikimedia_Technology/Goals/2017-18_Q4
Annual Program/Outcome | Objective | Quarterly Work | Tech Goal | Dependency | Team members | ETA | Status |
---|---|---|---|---|---|---|---|
Program 1: Availability, performance, and maintenance
Outcome 5: We have effective and easy-to-use testing infrastructure and tooling for developers. |
Objective 1: Maintain existing shared Continuous Integration infrastructure | Migrate away from Nodepool - task T190097
|
B: For others |
|
|
EOQ | |
Program 3: Tech Debt (aka Code Health)
Outcome 1: The amount of orphaned code that is running Wikimedia “production” services is reduced. |
Objective 2: Identify and find stewards for high-priority/high use code segment orphans - task T174091 | Broad role out of Code Stewardship model.
|
C: Tech Debt |
|
Lead: JR | EOQ | |
Program 3: Tech Debt
Outcome 2: Organizational technical debt is reduced. |
Objective 2: Define and implement a process to regularly address technical debt across the Foundation | Roll out of technical debt reduction approaches.
|
C: Tech Debt |
|
Lead: JR | EOQ | |
Program 6: Streamlined service delivery
Outcome 2: Developers are able to develop and test their applications through a unified pipeline towards production deployment. |
Objective 2: Prove viability of testing staged service containers alongside MediaWiki extension containers |
|
C: Tech Debt
D. Improve our own feature set |
|
EOQ |