MediaWiki

Scrum of scrums/2018-01-31

< Scrum of scrums

2018-01-31 edit

Callouts edit

Audiences edit

Readers edit

iOS native app edit

Android native app edit

Reading Web edit

  • Blocked by:
  • Blocking:
  • Updates:

Reading Infrastructure edit

  • Blocked by:
  • Blocking:
  • Updates:
    • Dev Summit / All Hands, not much else happened
    • Trying again to get the summary switched over this week, probably more gradually by not forcing rerenders at first.
Maps edit
  • Blocked by:
  • Blocking:
  • Updates:

Multimedia edit

  • Thanks to WMDE and Search (and others) for meatspace availability last week, it was very helpful
  • Beta commons login issues related to expired sessions seem persistent on beta cluster - specifically on UploadWizard, not sure what's happening there - https://phabricator.wikimedia.org/T186133

Discovery edit

  • Blocked by:
  • Blocking:
  • Updates:

Community Tech edit

  • Blocked by: Waiting on security review for GlobalPreferences
  • Blocking:
  • Updates: Beginning to work on ping users from edit summary wish; Close to wrapping up work on Grant metrics tool; Investigating other wishes

Contributors edit

Editing edit

  • Blocked by:
  • Blocking:
  • Updates:

Parsing edit

  • Blocked by: Parsoid clients (VE, CX, Flow) needing to review and approve https://gerrit.wikimedia.org/r/#/c/402455/
  • Blocking:
  • Updates:
    • Had originally planned to replace Tidy on an additional 200+ wikis including 4 large/medium wikis today (Jan 31). (https://phabricator.wikimedia.org/T185945, https://phabricator.wikimedia.org/T184656 ) But, this has been postponed to Feb 6 because this week is a no M/W train, no SWAT week.
    • Would appreciate DBA input on https://phabricator.wikimedia.org/T173943#3933570 .. Kunal has added the #DBA phab tag already and so this SoS notification is just an FYI.
    • Question to everyone: Every once in a while, Parsoid makes changes that requires downstream clients to update / approve changes. Longer-term, once Parsoid HTML is used for everything, we have a formal content-negotiation process that includes content versioning and version headers, but for now, when our clients are all internal and the contention negotiation support is not yet in place in the Parsoid + RESTBase stack, something quicker and simpler for faster change deployment is what we need. We have followed a combo of gerrit / phab / irc / email / SoS for this so far, but suggestions welcome for of how best to get everyone's attention and action in a timely fashion. Or is our combo process the best way to make this happen?

Global Collaboration edit

Collaboration edit
  • Mostly, our team is getting up to speed on Maps, our new assignment.
  • Collaboration and Language are now two separate teams again.
Language edit
  • Blocked by:
  • Blocking:
  • Updates:

UI Standardization edit


Technology edit

Analytics edit

  • Updates:
    • All-hands +I offsite this week - nothing to mention

Cloud Services edit

  • Blocked by:
  • Blocking:
  • Updates:

Fundraising Tech edit

  • Blocked by:
  • Blocking:
  • Updates:
    • Starting work on adding EventLogging to CentralNotice, initially along with existing impression tracking, but at a low sample rate
    • Upgrading our Civi instance to latest version
    • Continuing work on new API for main credit card processor
    • Fixing various vagrant issues relating to OS update

MediaWiki Platform edit

  • Blocked by:
  • Blocking:
  • Updates:
    • Developer Summit and All Hands
      • Audiences Technology Working Group meetings
      • Evolving the MediaWiki Architecture
      • Supporting Third-Party Use of MediaWiki
    • Filed "DiscussThis" RFC T185607
    • Multi-Content Revisions/Actor Table/Comment Table work on-going
    • TemplateStyles ready to deploy

Performance edit

  • Blocked by: Review of mcrouter puppet code (SRE knows)
  • Blocking:
  • Updates:
    • Offsite/DevSummit/All Hands
    • Adding perf monitoring of svwiki in preparation for release of TemplateStyles
    • Continued improvements to Thumbor based on new error logging

Release Engineering edit

  • Blocked by:
  • Blocking:
  • Updates:

Research edit

  • Blocked by:
  • Blocking:
  • Updates:

Scoring Platform edit

  • Blocked by:
  • Blocking:
  • Updates:

Search Platform edit

Security edit

  • Blocked by:
  • Blocking:
  • Updates:

Services edit

  • Blocked by:
  • Blocking:
  • Updates:

Site Reliability Engineering (formerly Technical Operations) edit

  • Blocked by: global collaboration on flow
  • Blocking: none
  • Updates:
    • slow week, due to AllHands

Wikidata edit

Retrieved from "https://www.mediawiki.org/w/index.php?title=Scrum_of_scrums/2018-01-31&oldid=4024144"