Wikimedia Technology Goals, FY2017–18, Q3 (January–March)

Introduction

Purpose of this document

Goals for the Wikimedia Technology department, for the third quarter of fiscal year 2017–18 (January–March 2018). The goal owner in each section is the person responsible for coordinating completion of the section, in partnership with the team(s) and relevant stakeholders.

Goals for the Audiences department are available on their own page

Legend

Tech Goal categorizes work into one or more of these quadrants:

A Foundation level goals	C Features that we build to improve our technology offering
B Features we build for others	D Modernization, renewal and tech debt goals

ETA (Estimated Time of Arrival) fields may use the acronym EOQ (End of Quarter).

Status fields can use the following templates: In progress, To do, N Postponed, Done or Partially done

Technology departmental programs

Program 1: Availability, performance, and maintenance

Overall goal owner: Mark Bergsma

Owner for Outcome 1: Mark Bergsma
Owner for Outcome 2: Ian Marlier
Owner for Outcome 3: Nuria Ruiz
Owner for Outcome 4: Bryan Davis
Owner for Outcomes 5 and 6: Greg Grossmeier

Annual plan outcome	Annual plan objective(s)	Quarterly Work (or Goal)	Primary Team(s)	Dependencies	Tech Goal	ETA	Status
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)	Upgrade Varnish from v4 to v5 on all remaining Traffic clusters	TechOps (Traffic)	Analytics (varnishkafka)	D	EOQ	Done
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)	Generate consistent logical backups in CODFW Finish the generation script with the addition of the following features: Add orchestration of multiple hosts Consolidate backups into a small number of files Implement a retention policy Ensure exact data consistency of the new backups with the live core DB servers Failover existing eqiad backup system to this new system	TechOps		D	EOQ	Done
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)	Modernize Puppet configuration management Complete Puppet 4 agent upgrade on Ubuntu trusty hosts Upgrade PuppetDB to version 3.2 or newer Upgrade Puppet master infrastructure to Debian stretch Investigate landscape of PuppetDB frontends, and provision one Port Cumin to work with a newer PuppetDB API Investigate challenges and plan Puppet 5 upgrade	TechOps		D	EOQ	In progress
Outcome 1: All production sites and services maintain current levels of availability or better.	Objective 3: Maintain data center infrastructure and equipment lifecycle from procurement through break-fix to decommissioning	Hardware refresh and expansions Complete outstanding backlog of refresh/expansion migrations Migrate to new etcd/zookeeper servers (conf) in eqiad Deploy new ores eqiad+codfw to production Finish new MediaWiki appservers refresh in eqiad Migrate to new loadbalancer (lvs*) servers in eqiad Migrate to new access switches in ulsfo Finish outstanding core db refreshes and fully decommission <=db1050, <db2030, labsdb1001-1003 Complete the following Q3 refresh/expansions: Expand media storage/Swift capacity in eqiad and codfw Refresh MediaWiki appservers in codfw Refresh tendril database monitor server Refresh servers tin and bast1001 Bring new eqiad row A-C access switch stacks online and available for active server connections	TechOps	Scoring Platform, Analytics, WMCS	D	EOQ	In progress
Outcome 1: All production sites and services maintain current levels of availability or better.	Objective 3: Maintain data center infrastructure and equipment lifecycle from procurement through break-fix to decommissioning	Procure and turn up at least two transit links and at least one transport link Fully configure SG hardware, software, and network for live service Begin testing and validation of production service from SG Enable live production service from SG for at least some Asian countries' live users Gather metrics for before/after comparison of user impact	TechOps (Traffic)	Finance (network link procurement Legal (network link contracts) Partnerships (WP Zero issues) Performance (metrics)	A	EOQ	Done
Outcome 1: All production sites and services maintain current levels of availability or better.	Objective 3: Maintain data center infrastructure and equipment lifecycle from procurement through break-fix to decommissioning	Cleanup esams and refresh servers and infrastructure Remove all decommissioned hardware Prepare racks OE14, OE15 and OE16 with new infrastructure Setup new access switches Procure and install new PDUs Complete router migration from cr1-esams to cr3-esams Install RIPE Atlas Anchor Procure and install LVS and miscellaneous servers	TechOps (DC Ops, Traffic)		D	EOQ	stalled
Outcome 2: All our users consistently experience systems that perform well	Objective 1: Maintain a comprehensive toolset to measure performance of our platforms	Measure performance from Asia both pre- and post- Singapore data center coming online. Evaluate the performance impact, and publish that evaluation. Review performance of CentralNotice, and identify areas for improvement. Build out private wiki support in Thumbor implementation	Performance	FundTech (help with CentralNotice) Traffic (coordination around Singapore) FileImporter team TechOps (Thumbor private wiki support will require puppet changes)		Jan 31 (Singapore-related) EOQ (others)	Corresponding to each bullet point under goals: In progress In progress Done
Outcome 2: All our users consistently experience systems that perform well	Objective 2: Catch and address performance regressions automatically through automation	Continue to develop on-demand performance testing infrastructure Enhance performance testing infrastructure using the Chrome Trace log	Performance			EOQ	Corresponding to each bullet point under goals: In progress Done
Outcome 2: All our users consistently experience systems that perform well	Objective 3: Modernize our Performance toolset. We will measure performance metrics that are closer to what users experience.	Review current research on performance perception Choose a limited, clearly defined set of performance metrics that can be applied across all Foundation projects. Begin reporting on those metrics on a weekly basis.	Performance			EOQ	Corresponding to each bullet point under goals: Done In progress To do
Outcome 3: We have scalable, reliable and secure systems for data transport.	Objective 1: Consolidation of analytics Kafka infrastructure to tier-1 requirements, including TLS encryption	Port most (if not all) Kafka clients from Analytics to Jumbo, with TLS where appropriate In progress Shutdown plain text production of webrequest data, allow tls only. In progress STRECH: decom analytics Kafka cluster To do	Analytics	TechOps	C: Improving our offering D: Tech debt	Q4	In progress
Outcome 3: We have scalable, reliable and secure systems for data transport.	Objective 2: Maintenance and expansion of current Hadoop cluster to support new use cases that require more computational resources	Upgrade cluster java 1.8 Done Put in service 8 new hadoop nodes Done STRETCH: Upgrade Druid to version 0.10 To do	Analytics		C: Improving our offering	Q4	Partially done
Outcome 3: We have scalable, reliable and secure systems for data transport.	Objective 3: Software, hardware upgrades, and maintenance on analytics stack to maintain current level of service	Hardware refresh jupyter notebooks Done Hardware refresh eventlogging box Done Refresh zookeeper nodes on eqiad To do	Analytics	TechOps	C: Improving our offering	EOQ	Partially done
Outcome 4: Wikimedia Cloud Services users can leverage a reliable and public Infrastructure as a Service (IaaS) product ecosystem for VPS hosting.	Objective 1: Maintain existing OpenStack infrastructure and services	Setup wikitech, horizon, and striker on new labweb hardware	WMCS	TechOps DBAs (migrate db to S3)	C: Improving our offering D: Tech debt	EOQ	Done
Outcome 4: Wikimedia Cloud Services users can leverage a reliable and public Infrastructure as a Service (IaaS) product ecosystem for VPS hosting.	Objective 2: Pay down technical debt and allow upgrading of the core OpenStack platform to modern, supported releases by replacing the current network topology layer with OpenStack Neutron, which has become the standard for most OpenStack deployments.	Build out Nova Network test environment and convert it to Neutron	WMCS		C: Improving our offering D: Tech debt	EOQ	Partially done
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: Upgrade webdriverIO to version 4.9 Investigate replacing nodemw with mwbot Video recording for Selenium tests in Node.js	Release Engineering	All developers	B: For others offering	EOQ	Done Done Partially done
Outcome 5: We have effective and easy-to-use testing infrastructure and tooling for developers.	Objective 1: Maintain existing shared Continuous Integration infrastructure	Draft requirements for a Kubernetes based solution for CI - task T183513 Migrate MediaWiki PHPUnit tests to Shipyard (docker-based CI) (~40% of Nodepool usage) - task T183512 Unify production and CI docker image build process - task T177276	Release Engineering	TechOps	C: Improving our offering D: Tech debt	EOQ	Corresponding to each bullet point under goals: Partially done To do (swapped with the now completed Q4 goal) Done

Program 2: MediaWiki

Goal owner: Tim Starling

Annual plan outcome	Annual plan objective(s)	Quarterly Work (or Goal)	Primary Team(s)	Tech Goal	ETA	Status
Outcome 1: Stakeholders in MediaWiki development will have sense of progress and direction in MediaWiki.	Objective 1: Develop a MediaWiki roadmap	Actively participate in the Audiences Technology Working Group to create a plan for the evolution of the technology stack	MediaWiki/Audiences	D Modernization, renewal and tech debt goals	EOQ	Done
Outcome 2: MediaWiki code quality will be improved.	Objective 1: Increase measured unit test coverage	Generate unit test coverage reports for extensions (T71684)	MediaWiki	C Features that we build to improve our technology offering	EOQ	Done
Outcome 2: MediaWiki code quality will be improved.	Objective 2: Break up large classes and source files	Namespacization (T166010)	MediaWiki	D Modernization, renewal and tech debt goals	Q4	In progress
Outcome 3: MediaWiki security and stability will be improved.	Objective 1: Address the backlog of action items that arise from security and downtime post-mortems	Execute scripts to cease using unserialize() for MediaWiki text storage (T181555)	MediaWiki	C Features that we build to improve our technology offering	Q4	In progress

Program 3: Addressing technical debt

Goal owner: Jean-Rene Branaa

Annual plan outcome	Annual plan objective(s)	Quarterly Work (or Goal)	Primary Team(s)	Dependencies	Tech Goal	ETA	Status
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	Objective 2.	Release Engineering	All teams	C: Tech Debt	EOQ	Done
Outcome 2: Organizational technical debt is reduced.	Objective 2: Define and implement a process to regularly address technical debt across the Foundation	Objective 2.	Release Engineering	All teams	C: Tech Debt	EOQ	Done
Outcome 2: Organizational technical debt is reduced.	Objective 3: Promote and surface important technical debt topics at large gatherings of Wikimedia developers (e.g., DevSummit and Hackathon(s))	Objective 3.	Release Engineering	Code Health Group, Technical Debt SIG	C: Tech Debt	EOQ4	To do

Program 4: Technical community building

Overall goal owner: Bryan Davis

Owner for Outcome 1: Bryan Davis
Owner for Outcomes 2 and 4: Dario Taraborelli
Owner for Outcome 3: Cindy Cicalese
Owner for Outcome 5: Deborah Tankersley

Annual plan outcome	Annual plan objective(s)	Quarterly Work (or Goal)	Primary Team(s)	Dependencies	Tech Goal	ETA	Status
Outcome 1: Becoming a technical contributor to the Wikimedia movement by creating and maintaining 'tools' (bots, webservices, etc) and other innovative solutions is easier than it has been historically because documentation is easier to find, more comprehensive, and descriptive of start to finish steps needed to solve common problems. Cloud Services product users feel comfortable sharing their knowledge with others as part of a community with a culture of sharing via documentation and mutual support.	Objective 1: Collaborate with community to find volunteers willing to form a documentation Special Interest Group to update documentation of existing Cloud Services products	Carry over from Q2 Find volunteers interested in forming a SIG SIG holds at least one meeting to plan further actions	WMCS	Technical Collaboration	A: Foundation goal (Community) B: Serving our audiences C: Improving our offering	EOY	Done
Outcome 1: Becoming a technical contributor to the Wikimedia movement by creating and maintaining 'tools' (bots, webservices, etc) and other innovative solutions is easier than it has been historically because documentation is easier to find, more comprehensive, and descriptive of start to finish steps needed to solve common problems. Cloud Services product users feel comfortable sharing their knowledge with others as part of a community with a culture of sharing via documentation and mutual support.	Objective 3: Increase community awareness of volunteer developed Tools (Added for Q3; not in official plan)	Document audiences and use cases for a Wikimedia Tools catalog	WMCS	Technical Collaboration	A: Foundation goal (Community) B: Serving our audiences C: Improving our offering	EOY (carries over into Q4)	In progress
Outcome 2: The adoption of Wikimedia technology can be reliably measured.	Objective 1: ~~Design a set of formal KPIs (key performance indicators) to measure the growth and diversity of our technology audience (task T171220)~~ This goal has been declined.	~~Write up report of interviews, including identified audiences, current measurement practices, and recommendations (T183202)~~	Research	Tech Management	A: Foundation goal (Community) B: Serving our audiences C: Improving our offering	EOQ	N Not done
Outcome 3: Value-added vendors who provide services and support based on Wikimedia software and true 'third parties' who install and use software produced by the Wikimedia movement on their own computers are more confident in recommending, deploying, and extending Wikimedia FLOSS projects.	Objective 1: Establish canonical point of contact for third-parties by promoting the existence of a dedicated technical liaison for software projects with support for third-party users	Establish channels of communication with third-party developers (T184606)	MediaWiki	Technical Collaboration	B Features we build for others	Q4	In progress
Outcome 3: Value-added vendors who provide services and support based on Wikimedia software and true 'third parties' who install and use software produced by the Wikimedia movement on their own computers are more confident in recommending, deploying, and extending Wikimedia FLOSS projects.	Objective 2: Clarify the Foundation’s short- and long-term commitments to third-party users. Create, publish, and promote a multi-tiered, third-party support level system for Wikimedia software projects. Document the support level of existing FLOSS projects and ensure that the documented levels of support are delivered.	Expand the set of bundled extensions to achieve a default MediaWiki experience that's comparable to Wikimedia sites (T178349)	MediaWiki	Release Engineering	B Features we build for others	Q4	In progress
Outcome 3: Value-added vendors who provide services and support based on Wikimedia software and true 'third parties' who install and use software produced by the Wikimedia movement on their own computers are more confident in recommending, deploying, and extending Wikimedia FLOSS projects.	Objective 2: Clarify the Foundation’s short- and long-term commitments to third-party users. Create, publish, and promote a multi-tiered, third-party support level system for Wikimedia software projects. Document the support level of existing FLOSS projects and ensure that the documented levels of support are delivered.	Create RFC for improving extension management (T88596)	MediaWiki		B Features we build for others	Q4	In progress
Outcome 3: Value-added vendors who provide services and support based on Wikimedia software and true 'third parties' who install and use software produced by the Wikimedia movement on their own computers are more confident in recommending, deploying, and extending Wikimedia FLOSS projects.	Objective 2: Clarify the Foundation’s short- and long-term commitments to third-party users. Create, publish, and promote a multi-tiered, third-party support level system for Wikimedia software projects. Document the support level of existing FLOSS projects and ensure that the documented levels of support are delivered.	Develop strategy for MediaWiki for 3rd party usage Initiate a catalog of Wikimedia software projects frequently used by third parties Create and publish a multi-tiered, third-party support level system for Wikimedia software projects frequently used by third parties	MediaWiki		B Features we build for others	Q4	In progress
Outcome 4: The collaboration with research in industry and academics is further scaled and supported.	Objective 1: Organize and host the annual Wiki Research Workshop. (task T171118)	Invite speakers (task T181832) Oversee paper review process and announcement of results (task T183031) Devise and announce the details of the program for the workshop (task T183033)	Research	Workshop co-organizers	A: Foundation goal (Community) B: Serving our audiences	EOQ	Done
Outcome 5: Organize Wikimedia Developer Summit	Objective 1: A good representation of non-WMF stakeholders related to the main theme are invited and participate at the event (preferred) or online.	Program Committee evaluates submitted position statements; and selects invitees Invitations are sent and responses processed Program Committee identifies themes and defines sessions All necessary event planning takes place (venue, etc.)	CTO Team	Developer Relations Program Committee members	A: Foundation goals (Community) B: Serving our audiences C: Improving our offering	EOQ	Done
Outcome 5: Organize Wikimedia Developer Summit	Objective 2: Discussions start before the event with the involvement of all the relevant stakeholders, in order to identify the points that need to be addressed at the event.	For each theme or session (TBD), an online discussion is initiated	CTO Team	Developer Relations Program Committee members	A: Foundation goals (Community) B: Serving our audiences C: Improving our offering	EOQ	Done

Program 5. Scoring Platform (ORES)

Goal owner: Aaron Halfaker See phab tracking Epic: task T183198

Annual plan outcome	Annual plan objective(s)	Quarterly Work (or Goal)	Primary Team(s)	Dependencies	ETA	Status
Outcome 1: Tool developers and Product teams can innovate tools that use machine prediction to make wiki-work more efficient	Objective 1: Expand vandalism & good-faith detection models to more wikis (focus on Emerging Communities)	ORES Extension refactoring (task T183199)	Scoring Platform	Global Collaboration	EOQ	Done
Outcome 2: Volunteers are empowered to track trends in prediction bias and other failures of AI in the wiki	Objective 1: Develop best practices for using community input to improve/correct predictions	Blog about JADE, MW integration (risker's curation list), and social infrastructures (task T183200)	Scoring Platform	Communications	EOQ	Done
Outcome 1: Tool developers and Product teams can innovate tools that use machine prediction to make wiki-work more efficient		Deploy Draft Topic model for English Wikipedia (task T176336)	Scoring Platform		EOQ	Partially done
Outcome 2: Volunteers are empowered to track trends in prediction bias and other failures of AI in the wiki.	Objective 1: Develop best practices for using community input to improve/correct predictions	Deploy JADE MVP in Cloud VPS (task T176333)	Scoring Platform		EOQ	Done
		Annual plan proposal (FY19) (task T183203)	Scoring Platform	Talent and Culture (A. Stillwell)	EOQ	Done
Outcome 1: Tool developers and Product teams can innovate tools that use machine prediction to make wiki-work more efficient	Objective 1: Expand vandalism & good-faith detection models to more wikis (focus on Emerging Communities)	Existing ORES service support and stability	Scoring Platform	Operations	EOQ	Done

Program 6. Streamlined service delivery

Goal owner: Mark Bergsma

Annual plan outcome	Annual plan objective(s)	Quarterly Work (or Goal)	Primary Team(s)	Dependencies	Tech Goal	ETA	Status
Outcome 1: We have seamless productization and operation of (micro)services	Objective 2: Create a standardized application environment for running applications in Kubernetes	Serve one production service via Kubernetes Serve at least 50% of Mathoid via kubernetes Done Validate whether the (implemented) standardized application environment works as expected Done Utilize the deployment pipeline (stretch - finishing in Q4) In progress	TechOps		C	EOQ	Done
Outcome 2: Developers are able to develop and test their applications through a unified pipeline towards production deployment.	Objective 2: Verify deployment-pipeline 'production' image	Verify basic functionality of 'production' deployment and image (initially targeting mathoid) - task T183165: Functional PoC within integration in the deployment-pipeline Deploy to isolated k8s	Release Engineering	Tech Ops Services	C	EOQ	Done
Outcome 2: Developers are able to develop and test their applications through a unified pipeline towards production deployment.	Objective 3: Provide a lightweight integrated development environment	Develop tools allowing users to create, manage and test their services in minikube	Service Platfom		C	Q4	In progress

Program 7. Smart tools for better data

Overall goal owner: Nuria Ruiz

Outcome 1 owner: Nuria Ruiz

Outcome 2 owner: Marko Obrovac

Outcome 3 owner: Bryan Davis

Annual plan outcome	Annual plan objective(s)	Quarterly Work (or Goal)	Primary Team(s)	Dependencies	Tech Goal	ETA	Status
Outcome 1: Foundation staff and community have better tools to access data.	Objective 1: Wikistats 2.0 redesign	(CARRY ON) Daily and monthly pageviews per country. Visualization and reports task T90759 Done Mobile responsive-ness for most used pages based on piwik data task T176143 Done	Analytics		C: Improving our offering	Q3	Partially done
Outcome 1: Foundation staff and community have better tools to access data.	Objective 1: Vetting and release of new metrics that measure content consumption	More resilient backend for wikistats:task T177965	Analytics		C: Improving our offering	Q3	Partially done
Outcome 1: Foundation staff and community have better tools to access data.	Objective 1: Users see improvements on data computing and data quality.	Private geowiki data in new analytics stack task T176996	Analytics	Q4	Done C: Improving our offering D: Tech debt	Q4
Outcome 1: Foundation staff and community have better tools to access data.	Objective 2: Better visual access to EventLogging data	Productionize Eventlogging Refine task T162610 Done Purge refined JSON data after 90 days in hive task T181064 In progress	Analytics		C: Improving our offering D: Tech debt	Q3	Partially done
Outcome 2: Access to Wikimedia content and data with scalable APIs	Objective 1: Revision storage scaling	Complete the migration: Fully migrate to Cassandra 3 Improve Cassandra dashboards by leveraging Prometheus metrics	Service Platform		D: Tech debt	EOQ	Done
Outcome 3: Wikimedia Cloud Services users have easy access to public data.	Objective 1: Provide reliable and available access to Wikimedia database dumps by upgrading the hardware used and consolidating access by internal teams, Cloud Services users, external mirrors, and HTTPS downloaders to the new canonical location.	(Carry forward from Q2) Migrate customer-facing Dumps endpoints to Cloud Services	WMCS	Tech Ops (Dumps)	C: Improving our offering	Q3	Done

Program 8. Multi-datacenter support

Overall goal owner: Tim Starling

Outcome 1 owner: Tim Starling

Outcome 1, Objective 3 owner: Mark Bergsma

Outcome 2, Objective 1 owner: Marko Obrovac

Annual plan outcome	Annual plan objective(s)	Quarterly Work (or Goal)	Primary Team(s)	Dependencies	Tech Goal	ETA	Status
Outcome 1: Our audiences enjoy improved MediaWiki and REST API availability and reduced wiki read-only impact from data center fail-overs.		Re-examine the requirements and scope of TP8	MediaWiki	Performance, Services	C Features that we build to improve our technology offering	EOQ	Done
Outcome 1: Our audiences enjoy improved MediaWiki and REST API availability and reduced wiki read-only impact from data center fail-overs.		Install and use mcrouter in deployment-prep (Carried over from 2017-2018 Q2)	Performance	TechOps	D: Tech Debt	Jan 31	N Postponed
Outcome 1: Our audiences enjoy improved MediaWiki and REST API availability and reduced wiki read-only impact from data center fail-overs.	Objective 3: Integrate MediaWiki with dynamic configuration or service discovery, in order to reduce the time required for a master switch from one datacenter to another	Use EtcdConfig in production to allow automation of a datacenter switch Test EtcdConfig in different failure scenarios Prepare conftool for safely editing mediawiki-config values (additional validation, separate etcd credentials) Deploy EtcdConfig to production Allow use of EtcdConfig to configure slave databases (stretch)	TechOps	MediaWiki Platform	D	EOQ	Corresponding to each bullet point under goals: Done Done Done Postponed
Outcome 2: Backend infrastructure works reliably across data centers	Objective 1: Reliable, multi-DC job processing	Migrate at least two high-traffic jobs to the new infrastructure	Service Platform	Operations, Analytics	D: Tech debt	EOQ	Done

Program 9. Growing Wikipedia across languages via recommendations

Goal owner: Leila Zia

Annual plan outcome	Annual plan objective(s)	Quarterly Work (or Goal)	Primary Team(s)	Dependencies	Tech Goal	ETA	Status
Outcome 1: Surface relevant information about the articles to editors at the time of editing with the goal of helping editathon organizers	Objective 1: Build, improve, and expand algorithms that can provide more detailed recommendations to editors about how an article could be expanded. (task T171224)	Build a ground truth test set of section translation and synonym classifiers (task T183039) Build a section translation classifier (task T182211) Build a section synonym classifier (task T183037 Investigate section dependence and ways to model it (task T183038) Build a model to recommend high quality images for Wikidata items missing them (task T180013)	Research	External collaborators (Bob West)	B, C	EOQ	In progress In progress In progress To do Done
	Objective 2: Develop and gather design requirements for how the algorithms’ results should be exposed to the editors. (task T171225)	Explore the design of the interface for the section recommendation experiment (task T183041	Research	External collaborators (Bob West) Pau	B, C	EOQ	To do
	Objective 3: Evaluate the usefulness of article expansion recommendations for target users. (task T171226)	Run an experiment to evaluate section recommendations for less experienced editors (task T183042)	Research	External collaborators (Bob West, Tiziano Piccardi, Michele Catasta)	B, C	EOQ	To do
	Objective 4: Build Labs API(s) that can be used by researchers and developers to use and surface the recommendations in other products and research initiatives. (task T171227)	Build an API and/or a tool to surface section recommendations (task T183043)	Research	External collaborators (Bob West, Tiziano Piccardi, Michele Catasta)	B, C	EOQ	In progress

Program 10. Public cloud services & support

Goal owner: Bryan Davis

Annual plan outcome	Annual plan objective(s)	Quarterly Work (or Goal)	Primary Team(s)	Dependencies	Tech Goal	ETA	Status
No specific named goals in Q3 for Program 10.

Program 11. Improving citations across Wikimedia projects

Goal owner: Dario Taraborelli

Annual plan outcome	Annual plan objective(s)	Quarterly Work (or Goal)	Primary Team(s)	Dependencies	Tech Goal	ETA	Status
Outcome 1: Quantitative research is available to help Wikipedia and Wikidata contributors focus and prioritize their sourcing efforts.	Objective 1: Estimate what proportion of content in Wikipedia or Wikidata is unsourced and in need of citations. (task T171230)	Prototype models for detecting unsourced statements in need of citations in Wikipedia (task T178696)	Research	External collaborators (L3S)	B, C	Q4	In progress
Outcome 1: Quantitative research is available to help Wikipedia and Wikidata contributors focus and prioritize their sourcing efforts.	Objective 2: Collect and analyze clickthrough data for footnotes and external links to understand how readers interact with them (task T171231)	Finalize link instrumentation proposal and its implementation, pending security and privacy review.	Research	External collaborators (Lauren Maggio) Legal Security Analytics	B, C	Q4	Done

Program 12: Grow contributor diversity

Goal owner: Leila Zia

Note: We have decided to not to commit to official goals for this program in Q3. I would like for us to spend some time on a recent proposal for the experiment that we developed with the collaborators, flesh it out with interested communities and plan for an experiment in Q4. However, we cannot commit to doing this given the workload for Program 9 and knowing that some of our resources will need to be spent on Annual Planning in Q3 (not captured anywhere here:). --LZia (WMF) (talk) 21:52, 15 December 2017 (UTC)[reply]

Annual plan outcome	Annual plan objective(s)	Quarterly Work (or Goal)	Primary Team(s)	Dependencies	Tech Goal	ETA	Status

Product departmental programs

Note: When the draft annual plan was written, the Search Platform and Fundraising Tech teams were in Product. They were moved into Technology during the "tune-up" in June 2017.

Program 1: Make knowledge more easily discoverable

Goal owner: Erika Bjune

Annual plan outcome	Annual plan objective(s)	Quarterly Work (or Goal)	Primary Team(s)	Dependencies	Tech Goal	ETA	Status
Goal 1, Outcome 1: Through incremental Discovery improvements, readers are better able to discover and search for content.	Objective 1: Implement advanced methodologies such as “learning to rank” machine learning techniques and signals to improve search result relevance across language Wikipedias.	Create and test advanced parser features In progress Evaluate and build new features for machine learning pipeline (T162279) Done Begin to build relationships with external information retrieval researchers In progress Category search (keywords for sub-category searching) Done	Search Platform	Analytics, Operations, Community Engagement	C. Improve our own feature set	EOQ	Partially done
Goal 1, Outcome 1: Through incremental Discovery improvements, readers are better able to discover and search for content.	Objective 2: Improve support for multiple languages by researching and deploying new language analyzers as they make sense to individual language wikis.	Continue to investigate morphological libraries for ElasticSearch plugins. Partially done Implement Serbian, investigate Slovak Improve search by using fuzzy (phonetic) language matching (report, not implementation). Done Continue general language support (on-going work) In progress Investigate language analyzer config options (template created) Done	Search Platform	Analytics, Operations, Community Engagement	A. Foundation Goal: Reach, C. Improve our own feature set	EOQ	Done
Goal 1, Outcome 1: Through incremental Discovery improvements, readers are better able to discover and search for content.		Address technical debt: Elasticsearch 5.6/Logstash 5.6/Kibana 5.6 (ELK stack) To do Maintain APIs (on-going) Partially done Translation extension Done	Search Platform	Operations, Search Front-end	D. Technical Debt	EOQ	Done
Goal 2, Outcome 1: Through improvements to the user experience of search interfaces, users are better able to find content in an intuitive and easy way.	Objective 4: Investigate how to expand and scale Wikidata Query Service to improve its ability to power features on-wiki for readers	Acquire rack for six new servers for WDQS, (see T178548) Done Set up individual internal and external service endpoints with enhanced features for expert users In progress	Search Platform	Analytics, Operations, WMDE	C. Improve our own feature set	EOQ	Partially done

Program 7: Payment processor investigation and long-term strategy

Goal owner: Katie Horn

Annual plan outcome	Annual plan objective(s)	Quarterly Work (or Goal)	Primary Team(s)	Dependencies	Tech Goal	ETA	Status
Outcome 1: Advancement and fr-tech find a solution that lowers or does not increase current maintenance costs.	We are continuing with the Ingenico reintegration and scoping Contribution tracking	Get to "1 hour test" phase with ingenico	Fr-tech	Ingenio	D	EOQ	Partially done

Program 8: Donor retention

Goal owner: Katie Horn

Annual plan outcome	Annual plan objective(s)	Quarterly Work (or Goal)	Primary Team(s)	Dependencies	Tech Goal	ETA	Status
Outcome 1: In FY 16/17 four well-trained team members spent 106 hours on deduping related to the English campaign. One of those employees may not be available for this task next year and a new contractor may help. We still hope to reduce the hours spent.	Have we made a positive impact on Major Gifts manual work?	Measure impact and meet to retro work.	Fr-tech and Major Gifts	Major Gifts team	B	EOQ	Done

Cross-departmental programs

Community Health

Segment 3: Research on harassment