Topics from the past

Hopefully by now, everyone has submitted their request for offsite/hackathon travel (see email)
[wikitech-l] Deployment train will freeze for the weeks of April 17th and May 1st
- Datacenter switchover is happening tomorrow: https://wikitech.wikimedia.org/wiki/Switch_Datacenter
Quarterly Discovery checkin slides were written, presented, and posted

Announcements, Information, Questions

Offsite hotel is taken care of; a manifest will probably be circulated by travel within a couple weeks to provide visual confirmation
[SoS] safemode=1 URL parameter to not load user scripts and gadgets. Often these cause interference with extension JS, so this can greatly simplify troubleshooting.
FYI: Conference rooms in the office will soon require you to “check in” for your meetings, or you might lose the room
Updates on Product/Tech tune-up (the "tuna")
- No big new news

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