Scrum of scrums/2019-05-22

2019-05-22

edit

Callouts

edit

Audiences

edit

Contributors

edit

Community Tech

edit
  • Blocked by:
  • Blocking:
  • Updates:

Anti-Harassment Tools

edit
  • Blocked by:
  • Blocking:
  • Updates:

Editing

edit
  • Blocked by:
  • Blocking:
  • Updates:
    • git #b6704010 - Automatically add a template when chosen from the autocomplete list (Hackathon project)
    • git #3285b7db - Initialize $restbaseHeaders to null (T223281)
    • Working on a model corruption issue related to selections in VE: (T202719)

Growth

edit

Language

edit

Readers

edit

iOS native app

edit

Android native app

edit
  • Blocked by:
  • Blocking:
  • Updates:
    • New Beta release with minor bug fixes and enhancements (and with updated logout behavior).
    • Continuing to build on the Suggested Edits feature (beginning work on editing structured captions on Commons).

Readers Web

edit

Readers Infrastructure

edit
  • Blocked by:
  • Blocking:
  • Updates:
    • Maps: node10js migration is finished for a couple of weeks and remains stable

Multimedia

edit
  • Blocked by:
  • Blocking:
  • Updates:
    • qualifiers for depicts statements now on test-commons, should reach commons itself later in the week
    • next release - other statements, within the next few weeks

Parsing

edit
  • Blocked by:
  • Blocking:
  • Updates:
    • About 75% of the core Parsoid PHP porting has been completed. Once this is done, we'll move onto QA and other test and tooling scripts.

UI Standardization

edit
  • Blocked by:
  • Blocking:
  • Updates:

Technology

edit

Analytics

edit
  • Blocked by:
  • Blocking:
  • Updates:
    • Team is at offsite next week, May 27 through May 31st
    • Time selector updated on Wikistats 2 along with other improvements, on track for beta release by the end of the quarter
    • Looking into Apache Kylin for big data OLAP cube creation
    • Working on moving reportupdater queries from repositories like limn-language-data to the analytics-reportupdater-queries repository to centralize reportupdater usage so we can more easily maintain and help with queries going forward

Cloud Services

edit
  • Blocked by:
  • Blocking:
  • Updates:

Fundraising Tech

edit
  • Blocked by:
  • Blocking:
  • Updates:
    • Looking at Perf team's patches to reduce CentralNotice overhead
    • CentralNotice bannmonitoring
    • Dedupe improvements for core CiviCRM
    • Anti-fraud improvements
    • Better-styled card entry form for main card processor

Core Platform

edit

Performance

edit

Release Engineering

edit

Research

edit
  • Blocked by:
  • Blocking:
  • Updates:

Scoring Platform

edit
  • Blocked by:
  • Blocking:
  • Updates:

Search Platform

edit
  • Blocked by:
  • Blocking:
  • Updates:

Security

edit
  • Blocked by:
  • Blocking:
  • Updates:

Services

edit
  • Blocked by:
  • Blocking:
  • Updates:

Site Reliability Engineering

edit

TechComm

edit
  • Blocked by:
  • Blocking:
  • Updates:
    • Hosted Office Hour at Hackathon
    • No RFC IRC meeting this week

Wikidata

edit
  • Blocked by:
  • Blocking:
  • Updates:
    • Many interesting session, meetings and loads of hacking time at Wikimedia Hackathon in Prague
    • Working with SRE on deploying SSR service to kubernetes: https://phabricator.wikimedia.org/T220402
    • EntitySchema a.k.a. Shape Expressions live on beta, going live on wikidata.org next week

German Technical Wishlist

edit
  • Blocked by:
  • Blocking:
  • Updates:

SoS Meeting Bookkeeping

edit
  • Blocked by:
  • Blocking:
  • Updates:
    • We're still looking for a backup facilitator. 👀
    • Please keep in mind that this page is copy/pasted to a wiki page. Text on this page will be rendered as wikitext. See this page for some common formatting errors. https://www.mediawiki.org/w/index.php?diff=3240805&oldid=3240802&title=Scrum_of_scrums/2019-05-15&type=revision&diffmode=source
    • If your team is blocking/blocked, please make sure you copy/paste the note from your team section to the other team's section.
    • We're still looking for feedback if this meeting is useful. If it is, is there anything we could do to make it more useful?
      • SoS is really useful to Release Engineering because we are frequently blocked by various teams because of train. We also frequently block other teams because we're in charge of continuous integration (CI).
      • Should we make the meeting notes as short as possible, so interested people could read all of it? One step in that direction could be removing teams that did not leave any updates.