Topics from the past

Updates on Product/Tech tune-up (tuna)
- C-level decision meeting postponed until May 9
- We no longer have permission to discuss the tune-up publicly
  - (And we are getting mixed messages about sharing anything with staff)
- Kevin is tentatively slotted into Technology (rather than Editing)
Upcoming WMF employee engagement survey (May 8-20)
- HIGHLY recommended you fill it out today or tomorrow
Offsite
- Draft agenda has been updated:
  - https://docs.google.com/document/d/1LZ8sTAcHVhsuxW3XPnhomPq173sLEWO5sg3V6P3uLp8/edit#

Announcements, Information, Questions

Offsite/hackathon travel information and manifests have been posted on office wiki
- https://office.wikimedia.org/wiki/Travel/Vienna_Offsites/Hackathon_Travel_Information
- Discovery manifest/roster has been updated; if you are comfortable adding a mobile number that will work during the event, please add it
  - https://docs.google.com/spreadsheets/d/1ksM47C57EX4xb6OqvrvJ760nSSuKC-yGpp4gzMmABIc/edit#gid=0
SoS: Reminder: no train week of May 15th due to RelEng offsite (SWAT still on)
[wmfall] Friday, May 12th has been designated MediaWiki Documentation Day.
Staff annual reviews start May 22 (details to follow)
New map preview is up for feedback (info was sent to [Discovery], [maps], and is being posted on community village pump equivalents)
Offsite agenda: Will there be time to plan quarterly goals for the next fiscal year?
- During “new teams” section.
- QGoal format is different between Product and Technology
  - But maybe just how things are explained, not changes to what is important
- Erika plans to propose an unconference session
- Important to nail down how frontend and backend will coordinate
Not clear when Max will transition into his new role
- Partly depends on decisions by Toby around maps rollouts

Are we blocked?

Are we blocking?

Other dependencies (in either direction) which don’t need to be called out as “blocked” (e.g. are progressing smoothly, have no urgency, etc.)

Discovery Roadmap FY2016/17: https://docs.google.com/presentation/d/1ctlqdLA__0OxDuO7mJEIDLP-xt9a7E4jv4INMlZAHdQ

This status was last updated 2017-04-11. Completed/dropped goals are not shown.

Improve search by researching and load testing machine learning to automatically re-rank search results
- Research and develop new models to determine which ones work best
- Build out data munging and data pipeline to develop new models
- Deploy automated model which matches current performance of manually-configured search result relevance
- Begin performing load tests on new models to make sure they can be safely deployed to production
Improve search support for different languages by researching and deploying new language analyzers
- Perform research spikes to find new analyzers for different languages
- Test new analyzers to see if they are improvements
- Deploy new analyzers that are found to be an improvement
Refine and test new design of search results page with occasional deployments
- Test new functionality with at least 2 A/B tests
- Analyze tests and gather community feedback
- Roll out new functionality with small releases to production across all Wikipedias
Stabilize maps and graphs code base
- Stabilize and fix high priority bugs

Imminent OOO
- See also the Discovery May vacation/travel calendar sheet (and please update it)