Jump to content

Wikimedia Search Team/Meeting minutes/2015-04-23

From mediawiki.org

2015-04-23

[edit]

Status

[edit]
  • Nik
    • Spent time on reorg, job reqs.
    • Turned on checkstyle for java project, and adding javadocs to avoid warnings
    • Likely to focus on hiring, not code, for next few days
  • Stas
    • Worked on updating ontology for dumper and fixing small bugs. Mostly done.
    • Tested the updater. Found stability issues and a couple bugs. Mostly good. Needs to add a couple more bug tickets.
    • Noted that there are no tests for normalizer. Nik wouldn’t object to some being created.
  • James
    • Has been documenting how to interact with Blazegraph (e.g. SPARQL). Used old ontology so needs to be updated.
    • May convert some docs to tests. Stas will point him to existing tests (php).
  • Erik
    • Working on vagrant integration for cirrus search
    • Looking at solutions for tests that only sometimes pass
  • Max
    • Working on Maps. Some key components are not open source. Yuri is working the server for tile generation. Max is mostly working on postgis
    • Geo search is in Lucene, so not clear whether it could be used with Blazegraph.
    • Server hardware requirements are unclear. Nik needs some kind of guess; so he and Max will discuss.
  • Yuri
    • (silence)
  • Dan
    • Interested in dipping toes in technical stuff.
  • Kevin
    • Not sure if I will remain involved with this team or not...TBD this week
    • Nik and others would like me to stay on


Scrum of Scrums

[edit]
  • Are we blocked?
    • No
  • Are we blocking?
    • No

To Discuss

[edit]
  • New team
    • Erik created a ticket to create a Search Team mailing list
    • Erik created an irc channel: #wikimedia-search
    • For now, everyone can dump all tasks into the Search Team phab board
      • Kevin will move add Search Team project to Max’s geo tasks
    • Wikimedia-Search is up for deletion: https://phabricator.wikimedia.org/T96551
      • Kevin commented in phab, reiterating that this shouldn’t happen until we’re ready
  • Current work doesn’t align with new Search Team stated priorities
    • WikiGrok was original driver of WDQS, but it is on back burner due to WDQ limitations.
    • Wes: Initial WDQS release (0.0.1) makes sense. (Nik/Stas: No blockers preventing it.)
    • Dan will coordinate checking with WikiGrok
    • Need to set new goals, priorities. Create a short (couple-paragraph) story.
    • WDQS might contribute to improving relevancy of searches
      • Mobile team has already experimented with WD-driven info boxes in search results
      • WD team is building some “fetch a thing” features; We could pull in live data or even produce lists or graphs from WD.