Wikimedia Release Engineering Team/Goals/201718Q2

Q1

Wikimedia Release Engineering Goals FY201718Q2 (October - December)

Q3

#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 workboard Resolve some scap & git-fat technical debt. Implement most-wanted features identified by users of scap.	D. Modernization, renewal and tech debt goals	Technical Operations	Lead: Mukunda Modell Chad Horohoe	Ongoing	To do
	Outcome 5: effective and easy-to-use testing infrastructure and tooling	Objective 1: Maintain existing shared Continuous Integration infrastructure	Work Docker-CI A generalized POC for a docker-based CI. MW Nightlies TBC	D. Modernization, renewal and tech debt goals	Technical Operations, Cloud Services	Lead: Antoine Musso	Ongoing	Done
		Milestone 1: Develop and migrate to a JavaScript-based browser testing stack	Goal Migrate majority of developers to JavaScript based browser test framework (webdriver.io) Port Selenium tests from Ruby to Node.js - T139740	C. Improve our own feature set D: Tech Debt	All developers	Lead: Zeljko Filipin	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 Ongoing maintenance and upgrades	D Modernization, renewal and tech debt goals	Technical Operations	Chad Horohoe	Ongoing	In progress
		Milestone 2: Maintain and improve existing shared project management platform (Phabricator)	Work on-going work to move to modern hardware and cross-datacenter resiliency	D Modernization, renewal and tech debt goals	Technical Operations (Traffic)	Mukunda Modell	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) - T174090	Goal Objective 1.	B: Features we build for others D: Tech Debt	Code Health Group	Lead: Jean-Rene Branna Greg Grossmeier	EOQ	Done
		Objective 2: Identify and find stewards for high-priority/high use code segment orphans - T174091	Goal Objective 2.	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 Objective 1.	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 Objective 2.	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 Complete build phase of release pipeline Build phase of the chart Build test variant Run test entrypoint w/developer feedback - services dependency Build production variant w/developer feedback - services dependency Tag production container Push to production docker registry - ops dependency - staging namespace	C. Improve our own feature set D: Tech Debt	Technical Operations, Services	Lead: Tyler Cipriani Dan	EOQ	Done