Topics from the past edit

Announcements, Information, Questions edit

[Engineering] You can now write Selenium tests in Node.js! (Željko)
Product/tech tune-up proposals have been posted on office wiki: https://office.wikimedia.org/wiki/Product_and_Tech_consultation
- Erika will put together a doc which will become an office wiki page, with ideas for Discovery future

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-03-14. 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