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

Topics from the pastEdit

  • Book your offsite/hackathon travel (see email)

Announcements, Information, QuestionsEdit

  • REMINDER: Friday (April 14) is a WMF holiday
  • [SoS] FR-tech's new job runner / cron complement script to replace our Jenkins instance is working like a charm. Anyone else want to use it for scheduled jobs?
  • [wikitech-l] Deployment train will freeze for the weeks of April 17th and May 1st
  • Quarterly Discovery checkin slides are being written now (by Deb)
  • Updates on Product/Tech tune-up ("org tuna")
    • Decision: Paul probably doesn’t need to attend tomorrow’s meeting w/Toby+Victoria+Anna
    • Discussion tomorrow probably won’t cover maps much
    • Future support for graphs (and Commons datasets) remains a question mark
      • Toby might have a plan; maybe multimedia
    • Side thought: Multimedia team is expected to be responsible for structured data on commons
    • Timeline at the bottom of the org tuna page has been updated with more details

Scrum of ScrumsEdit

Are we blocked?

  • None

Are we blocking?

  • None

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

Discovery NewsEdit

Quick Quarterly Goals/KPI Update (if needed)Edit

Discovery Roadmap FY2016/17:

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

FY 2016-17 Q4 (Apr-Jun) goals:

  • 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


  • April 14: WMF Holiday(!)
  • May 3: CREDIT showcase
    • Signup:
  • 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