Wikimedia Technology/Goals/2017-18 Q1
![]() |
Wikimedia Technology Goals, FY2017–18, Q1 (July – September) | Q2![]() |
Introduction
editPurpose of this document
editGoals for the Wikimedia Technology department, for the first quarter of fiscal year 2017–18 (July 2017 – September 2017). The goal setting process owner in each section is the person responsible for coordinating completion of the section, in partnership with the team and relevant stakeholders.
Goals for the Audiences department are available on their own page
Legend
editAnnual Program/Outcome refers to items in the annual plan (draft).
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 fields may use the initialism EOQ (End of Quarter).
Status fields can use the following templates: In progress, To do, Postponed, Done or Partially done
CTO
editGoal setting process owner: Victoria Coleman
Annual Program/Outcome | Quarterly Objective | Tech Goal | Team Goal | Dependencies | Team Members | ETA | Status |
---|---|---|---|---|---|---|---|
Program 4: Technical community building
Outcome 5: Organize Wikimedia Developer Summit Objective 1: Developer Summit web page published four months before the event |
Decide on Dev Summit event location, dates, theme, deadlines, etc. and publicize the information | B | Technical Collaboration | EOQ | To do |
Goal setting process owner: Nuria Ruiz
The Analytics Engineering makes Wikimedia related data available for querying and analysis to both WMF and the different Wiki communities and stakeholders. We develop infrastructure so all our users, both within the Foundation and within the different communities, can access data in a self-service fashion that is consistent with the values of the movement. For next quarter we will have less resources (about 2 people less for most of the quarter) thus our commitments are smaller. The second tier of priorities is marked as STRETCH, we will start working on those once goals are almost completed.
Annual Program/Outcome | Quarterly Objective | Tech Goal | Team Goal | Dependencies | Team Members | ETA | Status |
---|---|---|---|---|---|---|---|
Program 7: Smart Tools for Better Data.
Outcome 1: Foundation staff and community have better tools to access data. Objective 1: Wikistats 2.0 redesign. |
|
A. Org Level Priority. B. Serving our Audiences. | Cloud Services | Not done | |||
Program 7: Smart Tools for Better Data.
Outcome 1: Foundation staff and community have better tools to access data. Objective 1: Wikistats 2.0 redesign. |
|
A. Org Level Priority. B. Serving our Audiences. | Ops, DBAs | ||||
Program 7: Smart Tools for Better Data.
Outcome 1: Foundation staff and community have better tools to access data. Objective 3: Experiments with real-time data and community support for new datasets available. |
Deprecate socket.IO RC feed and help clients migrate (by July 7th) task T156919 Done | B. Serving our Audiences. | Ops | Done | |||
Program 7: Smart Tools for Better Data.
Outcome 1: Foundation staff and community have better tools to access data. Objective 2: Better visual access to EventLogging data |
Spike: Provide top domain and data to truly test superset task T166689 Not done | ||||||
Cross Departmental: Privacy, Security And Data Management. Track 2: Technology.
Outcome 2: To protect user data and uphold movement values, the Wikimedia Foundation continues compliance with best practices for data management Objective 2 & 3: Better offboarding / onboarding for data access. Ensure retention guidelines are being followed Done |
|
C. improve our own feature set
D. Tech Debt |
Ops | ||||
Program 1: Availability, performance, and maintenance.
Outcome 3: Scalable, reliable and secure systems for data transport. Objective 1: Consolidation of Kafka infrastructure to tier-1 requirements, including TLS encryption |
|
C. improve our own feature set
D. Tech Debt |
Ops | Done | |||
Program 1: Availability, performance, and maintenance.
Outcome 3: Scalable, reliable and secure systems for data transport. Objective 3: Software, hardware upgrades, and maintenance on analytics stack to maintain current level of service |
|
C. improve our own feature set
D. Tech Debt |
Ops |
Goal-setting process owner: Bryan Davis
Work is in progress on choosing which tasks to designate as goals on phabricator.
Annual Program/Outcome | Quarterly Objective | Tech Goal | Team Goal | Dependencies | Team Members | ETA | Status |
---|---|---|---|---|---|---|---|
Program 1: Availability, performance, and maintenance
Outcome 4: VPS hosting Objective 2: Pay down tech debt by deploying OpenStack Neutron |
Create a detailed migration plan for implementing Neutron as our OpenStack SDN layer | C: Improving our offering
D: Tech debt |
EOQ | In progress | |||
Program 1: Availability, performance, and maintenance
Outcome 4: VPS hosting Objective 1: Maintain existing OpenStack infrastructure and services |
Define a metric to track OpenStack system availability | B: Serving our audiences | EOQ | Done | |||
Program 4: Technical community building
Outcome 1: Improve documentation Objective 2: Create tutorial content |
Plan contract documentation work | B: Serving our audiences
C: Improving our offering |
EOQ | Not done | |||
Program 7: Smart tools for better data
Outcome 3: Data services Objective 1: Provide reliable and available access to dumps |
Begin migrating customer-facing Dumps endpoints to Cloud Services | C: Improving our offering | EOQ | In progress | |||
Program 10: Public cloud services & support
Outcome 1: PaaS is easy to use Objective 2: Migrate workflows to Striker |
Manage shared tool accounts via Striker | C: Improving our offering | EOQ | Done | |||
Program 10: Public cloud services & support
Outcome 2: Rebranding Objective 1: Complete core rebranding |
Perform initial Cloud Services rebranding | C: Improving our offering | Q2 | In progress | |||
Program 10: Public cloud services & support
Outcome 3: Outreach Objective 1: Promote services and products |
Attend Wikimania to support and promote Cloud Services products with the Wikimedia communities | B: Serving our audiences | August | Done | |||
Program 10: Public cloud services & support
Outcome 4: First line tech support Objective 1: Provide first line technical support resources |
Hire first line technical support contractor | B: Serving our audiences | Q2 | Done |
Goal setting process owner: Katie Horn
Annual Program/Outcome | Quarterly Objective | Tech Goal | Team Goal | Dependencies | Team Members | ETA | Status |
---|---|---|---|---|---|---|---|
Product Program 7: Payment processor investigation and long-term strategy
|
Continue Ingenico intergration | Some MVP of Ingenico | Ingenico (external vendor) | EOQ | To do | ||
Product Program 8: Donor retention
|
Time box work on Civi duplicate records | Time boxed effort to resolve merge conflicts | Major Gifts feedback | EOQ | To do |
MediaWiki Platform
editAnnual Program/Outcome | Quarterly Objective | Tech Goal | Team Goal | Dependencies | Team Members | ETA | Status |
---|---|---|---|---|---|---|---|
Program 2: MediaWiki
|
|
D: Modernization, tech debt |
|
EOQ | In progress | ||
Program 2: MediaWiki
|
C: Improving our offering
D: Tech debt |
|
EOQ | To do | |||
Program 8: Multi-datacenter support
|
|
C: Improving our offering | Ops |
|
EOQ | In progress | |
Cross Departmental: Structured Data on Commons.
|
A: Foundation level goals
C: Improving our offering D: Tech debt |
Ops (DBA) |
|
EOQ | In progress |
Speed is Wikipedia's killer feature. ("Wiki" means "quick" in Hawaiian.) As the Wikimedia Foundation’s Performance team, we want to create value for readers and editors by making it possible to retrieve and render content at the speed of thought, from anywhere in the world, on the broadest range of devices and connection profiles.
Goal-setting process owner: Gilles Dubuc
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 level of availability or better --> Objective 2: Assist in the architectural design of new services and making them operate at scale |
|
B: Features we build for others |
|
|
EOQ | Done | |
Program 1: Availability, performance, and maintenance
-> Outcome 2: All our users consistently experience systems that perform well --> Objective 2: Catch and address performance regressions in a timely fashion through automation |
|
B: Features we build for others |
|
|
EOQ | Done | |
Program 1: Availability, performance, and maintenance
-> 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. |
C: Feature |
|
EOQ | Done | |||
Program 1: Availability, performance, and maintenance
-> Outcome 2: All our users consistently experience systems that perform well |
D: Tech debt |
|
|
EOQ | Done | ||
Program 8: Multi-datacenter support
-> Outcome 1: Our audiences enjoy improved MediaWiki and REST API availability --> Objective 1: MediaWiki support for having read-only "read" requests (GET/HEAD) be routed to other datacenters |
B: Features we build for others |
|
|
EOQ | Not done |
Goal setting process owner: Greg Grossmeier
#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 |
Goal setting process owner: Dario Taraborelli [ Wikimedia Research goals overview ] [Wikimedia Research annual plan overview]
Annual Program/Outcome | Quarterly Objective | Tech Goal | Team Goal | Dependencies | Team Members | ETA | Status |
---|---|---|---|---|---|---|---|
Program 12: Grow contributor diversity.
Outcome 1: We improve Wikipedia’s contributor diversity after designing and testing potential intervention(s). Objective 1: Identify the underlying (potential) causes of lack of representative contribution from certain demographics task T166083 Objective 2: Design frameworks to change the current socio-technical infrastructure to address at least one of the underlying causes of lack of representativeness |
|
|
|
EOQ | Done
The second stretch goal is under review and may move to the next quarter depending on its engineering needs. This latter goal is a nice-to-have that we can afford to drop if needed. | ||
Program 9: Growing Wikipedia across languages via recommendations.
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 the can provide more detailed recommendations to editors and editathon organizers on how to expand articles/family-of-articles |
|
|
|
Done | |||
Cross Departmental: Structured Data on Commons. Segment 4: Programs.
Outcome 2: Develop a better understanding of existing needs for Structured Commons (task T152248) |
|
|
EOQ | In progress |
Goal setting process owner: Aaron Halfaker See the epic task: Phab:T166045
Annual Program/Outcome | Quarterly Objective | Tech Goal | Team Goal | Dependencies | Team Members | ETA | Status |
---|---|---|---|---|---|---|---|
Program 5: Scoring Platform (ORES). | |||||||
Outcome 1: Tool developers and Product teams can innovate tools that use machine prediction to make wiki-work more efficient.
|
C Features that we build to improve our technology offering |
|
|
Q1 | Done | ||
Outcome 2: Volunteers are empowered to track trends in prediction bias and other failures of AI in the wiki.
|
|
In progress |
Search platform
editGoal setting process owner: Erika Bjune
Annual Program/Outcome | Quarterly Objective | Tech Goal | Team Goal | Dependencies | Team Members | ETA | Status |
---|---|---|---|---|---|---|---|
Product Program 1: Make knowledge more easily discoverable
|
Quarterly Objective 1:
|
C. improve our own feature set | Analytics, Operations, Community Engagement | Erik, David, Trey, Daniel (contractor) | EOQ | Done | |
Product Program 1: Make knowledge more easily discoverable
|
Quarterly Objective 2:
|
C. improve our own feature set | Analytics, Operations, Community Engagement | Erik, David, Trey | EOQ | Done | |
Product Program 1: Make knowledge more easily discoverable
|
Quarterly Objective 3:
|
C. improve our own feature set | Analysis team, Operations, WMDE | Stas, Guillaume | EOQ | Done | |
Cross-Departmental Program: Structured Data on Commons.
Segment 2: Search integration and exposure |
Quarterly Objective 1:
|
C. improve our own feature set | Operations, WMDE | Erik, Stas, Guillaume | EOQ | To do | |
Cross-Departmental Program: Structured Data on Commons.
Segment 2: Search integration and exposure |
Quarterly Objective 2:
|
C. improve our own feature set | Readers, WMDE | Erik, Stas | EOQ | In progress |
Goal setting process owner: Darian Patrick
Annual Program/Outcome | Quarterly Objective | Tech Goal | Team Goal | Dependencies | Team members | ETA | Status |
---|---|---|---|---|---|---|---|
Cross Departmental: Privacy, Security And Data Management.
Segment 2: Technology |
Update MediaWiki security release process and tooling
|
|
|
|
EOQ | To do |
Goal setting process owner: Gabriel Wicke
Annual Program/Outcome | Quarterly Objective | Tech Goal | Team Goal | Dependencies | Team Members | ETA | Status |
---|---|---|---|---|---|---|---|
Program 7: Smart tools for better data
Outcome 2: access to Wikimedia content and data with scalable APIs Objective 1: Revision storage scaling |
Start gradual roll-out of Cassandra 3 & new schema to resolve storage scaling issues and OOM errors. | B: Serving our audiences; D: Tech debt |
|
EOQ | Draft | ||
Program 8: Multi-datacenter support
Outcome 2: Backend infrastructure works reliably across data centers Objective 1: Reliable, multi-DC job processing |
Begin migrating job queue processing to multi-DC enabled eventbus infrastructure.
|
D: Tech debt |
|
End of Q1 | Draft |
Goal setting process owner: Mark Bergsma
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. |
Continue Asia Cache PoP procurement, installation, and configuration tasks
|
B. Serving our audiences
C. Improving our offering |
Finance, Legal, Partnerships | EOQ | Done | ||
Program 6: Streamlined service delivery
Outcome 1: We have seamless productization and operation of (micro)services.
|
|
D. Improve our own feature set | Release Engineering, Services | EOQ | Done | ||
Program 1: Availability, performance, and maintenance.
Outcome 1: All production sites and services maintain current levels of availability or better. |
Remove Salt from our infrastructure
|
C. Improve our own feature set
D. Technical debt |
Release Engineering, WMCS | EOQ | Done | ||
Program 1: Availability, performance, and maintenance.
Outcome 1: All production sites and services maintain current levels of availability or better. |
Prepare for Puppet 4
|
C. Improve our own feature set
D. Technical debt |
Release Engineering | EOQ | Done | ||
Program 1: Availability, performance, and maintenance.
Outcome 1: All production sites and services maintain current levels of availability or better. |
Improve database backups' coverage, monitoring and data recovery time (part 1)
|
D. Technical debt | EOQ | Done |