Scrum of scrums/2019-06-05

From MediaWiki.org
Jump to navigation Jump to search

2019-06-05[edit]

Callouts[edit]

Audiences[edit]

Readers[edit]

iOS native app[edit]

Android native app[edit]

Readers Web[edit]

  • Updates:
    • Summary: planning for desktop refresh, Wikimania, and next year's technical projects; continuing ongoing development for the advanced mobile contributions.
    • Responsive website (MinervaNeue / MobileFrontend / Related Articles):
    • QuickSurveys support
    • Planning
      • Desktop refresh design and planning
      • Wikimania proposal planning

Readers Infrastructure[edit]

Multimedia[edit]

  • Updates:
    • still working on qualifiers for depicts on commons ... integrating new feedback
    • next: other statements, delayed until after qualifiers release

Technology[edit]

Fundraising Tech[edit]

Core Platform[edit]

  • Blocking:
  • Updates:
    • Actor table is write-new everywhere
    • Parameter validation in REST API and Action API
    • Kask deployed
    • Proton is only PDF renderer
    • Off-site June 17-23

Release Engineering[edit]

Research[edit]

Search Platform[edit]

Site Reliability Engineering[edit]

Wikidata[edit]

German Technical Wishlist[edit]

  • Blocked by:
  • Updates:
    • Not putting it to Blocked By yet, but we've been struggling with Jenkins recently. Maybe Release Engineering would be interested in hearing those thoughts?
      • There have been multiple tests flapping, which are included in gated skins and extensions. These are annoying and a waste of CI resources since the usual response is to just 'recheck' an inappropriate number of times. We would like to see some way of increasing the visibility of these failures and encouraging either skipping or fixing.
      • The CI and Zuul dashboards in Grafana don't seem to include failure metrics--We'd be especially interested in tracking how often a patch gets V+2 and then tests fail during gate-and-submit.

SoS Meeting Bookkeeping[edit]

  • Updates:
    • Deb volunteered for backup facilitator 🎉 (still looking for one more)
    • The meeting starts at 15:35 UTC. If 15:40 UTC would be a better starting time, let me know.