Wikimedia Discovery/Meetings/Checkin/2017-04-04

= Topics from the past =
 * Book your offsite/hackathon travel (see email)
 * Should we clean up who is “voiced” in the discovery IRC channel?
 * We did

= Announcements, Information, Questions =
 * [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

= Scrum of Scrums = 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.)
 * None
 * None
 * None

Discovery News

 * See https://www.mediawiki.org/wiki/Discovery/Status_updates

= Quick Quarterly Goals/KPI Update (if needed) = 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.

FY 2016-17 Q4 (Apr-Jun) goals: https://www.mediawiki.org/wiki/Wikimedia_Engineering/2016-17_Q4_Goals#Discovery
 * 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

= FYI =
 * April 5: Work-centric unmeeting
 * April 5: CREDIT showcase
 * Signup: https://etherpad.wikimedia.org/p/CREDIT
 * April 12: Work-centric unmeeting
 * April 14: WMF Holiday(!)
 * May 14-18: Discovery offsite in Vienna (right before the hackathon)
 * May 19-21: Hackathon in Vienna (right after the offsite)
 * July 18: Next All-Discovery retro
 * July 24-August 4: WMF staff encouraged to work remotely