Scrum of scrums/2016-03-30

From MediaWiki.org
Jump to navigation Jump to search

2016-03-30[edit]

Technology[edit]

Analytics[edit]

  • Blocking: none
  • Blocked: none
  • Updates:
    • Unique Devices data released, pageviews data officially released, pagecounts-raw, pagecounts-all-sites deprecated, dumps.wikimedia.org/analytics has details
    • Request Breakdown reports from Hadoop are ready, they replace the old Wikistats squid reports, some UI improvements coming shortly

Release Engineering[edit]

  • Blocking:
    •  ???
  • Blocked:
    •  ???
  • Updates:
    • scap 3.1 will be in production on Tuesday April 5th, now with large binary support! (via git-fat (what trebuchet used for feature parity))
    • Code freeze week of April 18th (DC switchover)

Research[edit]

  • Blocking:
    • none
  • Blocked:
    • none
  • Updates:
    • Deployed ORES swagger & v2 paths. Can now ask for feature lists and do feature injection when scoring. Announcement coming.

Services[edit]

Technical Operations[edit]

  • Blocking:
    • noone
  • Blocked:
    • by noone
  • Updates:
    • changeprop is live, worked with Marko from Services team
    • working on ORES and scap3 integration with Amir

Product[edit]

Discovery[edit]

Editing[edit]

Collaboration[edit]

  • Blocking:
    • External store work
  • Blocked:
  • Updates:
    • Working on support for Flow notifications being properly hidden on moderation
    • Work on the Echo special page

Language[edit]

Parsing[edit]

  • Blocking:
    • None
  • Blocked:
    • None
  • Updates:
    • VE team and CX teams already knows about the tasks I've filed against them for setting user-agent headers, accept headers. I've filed a ticket against Flow as well to set user-agent header in your request. Not urgent, but good to get it done sooner than later.
    • Work ongoing to move data-mw out from an inlined attribute .. CX, VE, Flow: please start thinking about what this means and how you will process data-mw and html from separate api requests. The Parsoid and RESTBase side work will be done in 2-3 weeks time (which includes performance evaluation and impact of supporting old versions, etc.). We'll not turn this on in production (3-4 weeks away at least) without consulting with all affected clients, but the accept: header is your way of getting the old version till you are ready to switch, but we prefer that the switch not be delayed inordinately. I've already filed tickets against these projects, but this is just a heads up.

Fundraising Tech[edit]

  • Blocking:
    • None
  • Blocked:
    • None
  • Updates:
    • More DonationInterface refactoring
    • Investigating ActiveMQ replacement options
    • More work towards mass (reversible) contact de-duping in CiviCRM
    • Scoping work to update PayPal integration


Reading[edit]

Android[edit]

  • Updates:
    • Content Service is rolling out successfully. (25% of Android production app as of Monday evening)

iOS[edit]

  • Blocking:
    • None
  • Blocked:
    • None
  • Updates:
    • 5.0.1 Deployed last week
    • 5.0.2 Being deployed this week

(Just decided this on Monday - we received a call from Apple that there is an OS bug causing our app to crash and we needed to work around it)


Web[edit]

  • Language switcher overlay being deployed

Reading Infrastructure[edit]