Scrum of scrums/2018-10-03

=2018-10-03=

Callouts
Switchover/Switchback dates reminder. It's next week!
 * Fundraising campaigns https://meta.wikimedia.org/wiki/CentralNotice/Calendar
 * Actively working to eliminate ongoing messages from the mediawiki-errors logging channel. Your team may be tagged on those, please take a look if/when you are.
 * SRE:

Switchback:

Traffic: Wednesday, October 10th 2018 09:00 UTC MediaWiki: Wednesday, October 10th 2018: 14:00 UTC Services: Thursday, October 11th 2018 14:30 UTC Media storage/Swift: Thursday, October 11th 2018 15:00 UTC


 * Release Engineering
 * Next week: No train next week, DC switchover

We would like to ask the Security Team how is the security review of "JsonConfig and Kartographer interaction" (T163827) going and if they need any help with that (It's not blocking anything, but we would like to know the current status)
 * Reading Infrastructure:


 * Research
 * [Services]: Setting up a connection from the recommendation API service to MySQL: https://phabricator.wikimedia.org/T205452


 * UI Standardization
 * OOUI v0.29.0 released yesterday with 8 possible breaking changes, among those PHP 7 requirement and removal of CapsuleMultiselectWidget
 * Please consider if these changes might affect your code https://phabricator.wikimedia.org/diffusion/GOJU/browse/master/History.md;v0.29.0


 * 5 Minute Demo - taking your sign-ups now! Next meeting on Oct 11
 * https://www.mediawiki.org/wiki/5_Minute_Demo#Recordings_and_Presenters

Services (Core Platform) and Parsing team deployed code this week that implements HTML version (content) negotiation protocol alongwith a major version bump of Parsoid HTML from 1.8.0 to 2.0.0 ( https://www.mediawiki.org/wiki/Specs/HTML/2.0.0 ). As part of this, RESTBase + Parsoid will enforce the HTML version requested in the Accept header. If a version is requested that is different (^ semantics) than what is available in storage, RESTBase will ask Parsoid to get the appropriate version. If Parsoid cannot do that, it will return a HTTP 406. What does it mean for Parsoid clients? If you are requesting a really old version in your Accept header, you are very likely going to get a HTTP 406. If you request an older version (1.7 or 1.8), you will see an additional latency to your requests while Parsoid downgrades the HTML from the more up to date version. So, Parsoid clients should provide an accept header with the most up-to-date version of Parsoid HTML you can handle. Subsequently, you should update your code to handle the newer versions in a timely manner. A longer announcement and wiki docs will be coming out soon.
 * Parsoid

Community Tech

 * Blocked by:
 * Blocking:
 * Updates:

Anti-Harassment Tools

 * Blocked by:
 * Blocking:
 * Updates:

Editing

 * Blocked by:
 * Blocking:
 * Updates:

Growth

 * Blocked by:
 * Blocking:
 * Updates:

Language

 * Blocked by: None
 * Blocking: None
 * Updates:
 * Content Translation v2 released! https://wikimediafoundation.org/2018/09/30/content-translation-version-two/

iOS native app

 * Blocked by:
 * Blocking:
 * Updates:

Android native app

 * Blocked by:
 * Blocking:
 * Updates:

Readers Web

 * Blocked by:
 * Blocking:
 * Updates:
 * Mobile website (MinervaNeue / MobileFrontend):


 * Invest in the MobileFrontend & MinervaNeue frontend architecture https://www.mediawiki.org/wiki/Reading/Web/Projects/Invest_in_the_MobileFrontend_%26_MinervaNeue_frontend_architecture
 * Add unit tests for util and mfExtend T203818
 * Bundle widgets and models with Webpack; enable headless Page and View tests T204867 T204786
 * Make test set up explicit T204885
 * Lint unsupported JavaScript in build products T203976
 * Move MainMenu click tracking schema from MobileFrontend to Minerva T204584
 * Merge skin option modules into a single ResourceLoader module and move enabled logic to client T167713


 * Page issues https://www.mediawiki.org/wiki/Reading/Web/Projects/Mobile_Page_Issues
 * A/B test in progress T204609
 * Lots of cross-wiki QA and A/B test discussions


 * Maintenance and bug fixes T205449 T202756


 * Advanced mobile contributions https://www.mediawiki.org/wiki/Reading/Web/Advanced_mobile_contributions
 * Design and product continuing special pages work in Minerva


 * PDF rendering (Proton) https://www.mediawiki.org/wiki/Reading/Web/PDF_Functionality
 * Remaining work tracked in T186748
 * Html2pdf route should return promise T201158 T204055 T181623
 * Consistently represent asynchronous code execution T204055


 * SEO: where should Schema property 'sameAs' live? T204070
 * The Performance team is going to be deploying a second set of sitemaps next week, they will also be testing the indexing on mobile in parallel. Mikhail has analyzed the data from the initial Italian sitemap launch and we haven't seen any conclusive evidence that they've helped referrals or increased pageviews.  We will repeat the analysis with the other wikis.


 * Management supporting Multimedia hiring processes


 * Product working on 3-5 year planning


 * Design exploring reference previews https://reference-previews.firebaseapp.com/

Readers Infrastructure

 * Blocked by:
 * none
 * Blocking:
 * none known
 * Updates:
 * Maps:
 * Loading OSM map into maps1004 T205462
 * Tilerator overloading proxy fixed https://wikitech.wikimedia.org/wiki/Incident_documentation/20181002-maps
 * MCS:
 * Now loading Parsoid HTML v2.0.0

Multimedia

 * Updates

Parsing
Services (Core Platform) and Parsing team deployed code this week that implements HTML version (content) negotiation protocol alongwith a major version bump of Parsoid HTML from 1.8.0 to 2.0.0 ( https://www.mediawiki.org/wiki/Specs/HTML/2.0.0 ). As part of this, RESTBase + Parsoid will enforce the HTML version requested in the Accept header. If a version is requested that is different (^ semantics) than what is available in storage, RESTBase will ask Parsoid to get the appropriate version. If Parsoid cannot do that, it will return a HTTP 406. What does it mean for Parsoid clients? If you are requesting a really old version in your Accept header, you are very likely going to get a HTTP 406. If you request an older version (1.7 or 1.8), you will see an additional latency to your requests while Parsoid downgrades the HTML from the more up to date version. So, Parsoid clients should provide an accept header with the most up-to-date version of Parsoid HTML you can handle. Subsequently, you should update your code to handle the newer versions in a timely manner. A longer announcement and wiki docs will be coming out soon.
 * Blocked by:
 * Blocking:
 * Updates:

UI Standardization

 * Blocked by:
 * Blocking:
 * Updates:
 * OOUI v0.29.0 released yesterday with 8 possible breaking changes
 * Please consider if these changes might affect your code https://phabricator.wikimedia.org/diffusion/GOJU/browse/master/History.md;v0.29.0
 * PHP 7 is now required
 * CapsuleMultiselectWidget is removed entirely (resulting in 8% decrease of widgets CSS after gzipping https://phabricator.wikimedia.org/T183299#4637565)
 * Continuous work on wikimediafoundation.org website accessibility support

Analytics

 * Blocked by:
 * Blocking:
 * Updates:

Cloud Services

 * Blocked by:
 * Blocking:
 * Updates:

Fundraising Tech

 * Blocked by:
 * Blocking:
 * Updates:
 * Big English mass emails have begun! Watching for errors and trying to keep donation infrastructure solid
 * Debugging some CI issues with CiviCRM
 * Following along with core and/or language teams' work on CentralNotice save slowness
 * Support for Endowment Gifts via donations pipeline
 * Fixing audit file downloads

MediaWiki Core Platform

 * Blocked by:
 * Blocking:
 * Updates:
 * Deployed content negotiation for Parsoid ( https://phabricator.wikimedia.org/T128040 )
 * result of a 2 1/2 year collaboration with Parsing
 * allows clients to request a specific version of the content-type (how the content would look if produced by a specific version of the software)
 * PHP7 profiler development work
 * Tech Conf session design

Performance

 * Blocked by:
 * Blocking:
 * Updates:
 * Identified performance issue with saving banners due to RevisionStore, working with several teams on a fix
 * Added some additional data points to NavTiming collection
 * Chrome 69 shows a regression in firstPaint, reported upstream
 * Investigating a memory leak in our front-end code: https://phabricator.wikimedia.org/T205127
 * Investigating memcache TKOs: https://phabricator.wikimedia.org/T203786
 * Actively working to eliminate ongoing messages from the mediawiki-errors logging channel. Your team may be tagged on those, please take a look if/when you are.
 * Investigating memcache TKOs: https://phabricator.wikimedia.org/T203786
 * Actively working to eliminate ongoing messages from the mediawiki-errors logging channel. Your team may be tagged on those, please take a look if/when you are.

Release Engineering

 * Blocked by:
 * SRE/Services review of: Support a literal body for POST requests in `fetch_url`
 * Blocking:
 * Updates:
 * Production Excellence: September 2018 https://phabricator.wikimedia.org/phame/post/view/119
 * Train Health:
 * Last week: There were a few blockers, but they were resolved quickly. No delays in train.
 * This week: no delays
 * Next week: No train next week, DC switchover
 * Log Health:
 * Code Health:
 * Code Health:
 * Code Health:

Research

 * Blocked by:
 * [Services] Setting up a connection from the recommendation API service to MySQL: https://phabricator.wikimedia.org/T205452
 * Blocking: None
 * Updates:
 * Retain CitationUsage and CitationUsagePageLoad data after 90 days: https://phabricator.wikimedia.org/T205272
 * Resolve redirects for the Recomendation API: https://phabricator.wikimedia.org/T203041

Scoring Platform

 * Blocked by: None
 * Blocking: None
 * Updates:
 * Working on improving logging and send more logs to logstash

Search Platform

 * Blocked by:
 * Blocking:
 * Updates:
 * Finished Wikidata reindex, now search also uses statement values
 * Fixed bug where search was gluing together words separated by HTML tags: https://phabricator.wikimedia.org/T195389
 * Enabled Kafka poller on WDQS: https://phabricator.wikimedia.org/T189458
 * Fixed timeouts on RecentChanges API caused by bad indexes: https://phabricator.wikimedia.org/T202764
 * Working on calculating examination probabilities for completion queries: https://phabricator.wikimedia.org/T205348
 * Working on improving data and creating models from autocompletion click data: https://phabricator.wikimedia.org/T205111
 * Working on improving Korean analyzers: https://phabricator.wikimedia.org/T178925
 * Working on running multiple Elastic instances on the same hardware: https://phabricator.wikimedia.org/T193654
 * Working on query parsing refactoring: https://phabricator.wikimedia.org/T185108

Security

 * Blocked by:
 * Blocking:
 * Updates:
 * https://phabricator.wikimedia.org/T200279 being worked on for this month

Services

 * Blocked by:
 * Blocking:
 * Updates:

Site Reliability Engineering

 * Blocked by:
 * None
 * Blocking:
 * None
 * Updates:
 * Switchback to eqiad happening next week, no train, only emergency deploys

Wikidata

 * Blocked by:
 * Blocking:
 * Updates:

German Technical Wishlist

 * Blocked by:
 * Blocking:
 * Updates:

Multi-Content Revisions

 * Blocked by:
 * Blocking:
 * Updates:
 * "read new" enabled on mediawiki.org on Monday
 * "read new" will be enabled on commons on October 15
 * "read new" may be enabled on several small/medium wikis in the interim
 * addressing gaps and regressions and beginning to address tech debt

SoS Meeting Bookkeeping

 * Updates: