https://www.mediawiki.org/wiki/Scrum_of_scrums/2016-11-16

2016-11-16 = == Product == === Reading ===

==== iOS native app ==== https://phabricator.wikimedia.org/project/view/2220/ * Last week:

- * Fixed more remaining issues from persistance layer update, investigated better long term solution

- * Sped up testing & build chain, began consolidating to buildmini & Jenkins

* This week: * More 5.3.0 beta feedback & fixes (and release Friday or Monday) * Add announcement card to the news feed * Initial dynamic type implementation & assessment of scope

==== Android native app ==== * Last week: * Continuing Q2 goals for Wikidata descriptions * Moving to kanban-ish workflow * Next week: * More Q2 goals for Wikidata descriptions (mostly polish)

==== Mobile Content Service (MCS) ==== * Adding announcements feed endpoint

==== Reading Web ==== * Current sprint: https://phabricator.wikimedia.org/project/board/2336/ * Continuing work from the last week * Next sprint: https://phabricator.wikimedia.org/project/view/2342/ * Stopping Hovercards A/B tests in multiple wikis * More work on PageImagesAPI (returning images in lead section only)

==== Reading Infrastructure ==== * We're disappointed in the fact that T150454 wasn't caught by grepping for the removed function before merging into core. https://phabricator.wikimedia.org/T150454 * API error/warning i18n patches are up! ** *https://gerrit.wikimedia.org/r/#/c/321406/* https://gerrit.wikimedia.org/r/#/c/321406/ (and its parent patches) could use review, both codewise and for the output resulting when non-bc errorformat is used. ** The patches depended on by that change are next in importance. These are for OAuth, TitleBlacklist, GlobalBlocking, Translate, and ConfirmEdit. ** All other WMF-deployed extensions affected by this change have patches too, see *https://gerrit.wikimedia.org/r/#/q/topic:api-error-i18n/T47843* https://gerrit.wikimedia.org/r/#/q/topic:api-error-i18n/T47843. Non-WMF-deployed extensions are (mostly) not touched at this time, the worst that should happen to them is wfDeprecated warnings eventually.

=== Community Tech === * No blockers, not blocking * RFC for changing default category collation to uca with numeric: https://meta.wikimedia.org/wiki/Requests_for_comment/Switch_default_category... * Pageviews Analysis 2.0 out: https://tools.wmflabs.org/pageviews/ (Improved UI) * Script for populating fields in localuser table in CA due to run next week: https://phabricator.wikimedia.org/T148242 ** Long-running script - estimated 4-5 days ** Note: Global user account renaming will be disabled during the script run to prevent conflicts * Work continues on Programs Dashboard

=== Editing === ==== Collaboration ==== * Updates ** RecentChanges new filtering work (ERI) ** Flow exception fixes ** Echo Notifications special page improvements ** Flow caching rewrite for multiple data centers has been deployed. Keep an eye out on Flow issues, and let us know if you have any problems. * Blocked - None * Blocking - None

==== Language ====

==== Parsing ==== (Arlo / Scott will show up instead of Subbu) * Parsoid: Released debian 0.6.1 and npm 0.6.1 packages -- last release to support node 0.1x. * Parsoid: Deprecated support for node 0.1x, dropping all support March 31st 2017 (see wikitech-l announcement). * Working with Community Engagment to communicate Tidy replacement changes, prepare FAQs, what this means for editors, what kind of fixups would be needed, tools available, etc. * Work ongoing to get the Linter extension ready for deployment on the Wikimedia cluster -- could launch in the Dec 2016 - Jan 2017 timeframe.

=== UI Standardization === Still working on: * Align Minerva (Mobile Frontend) to overhauled color palette (T146799) * Review and integrate messages, alerts, warnings as WikimediaUI component (T127405, continued) * Changing visual language of styleguide Working on: * Improve form layouts in OOUI MW core forms for better user experience (T136790) * Align CX to overhauled WikimediaUI color palette (T150731) * Align blog primary colors to WikimediaUI color palette (T150057) Finished: * Variable naming in WikimediaUI Base (T147612)

== Technology == === Analytics === Blockers or blocking: None Updates: * Waiting for nodes to double storage capacity for Pageview API * Computing the first standard metrics with reconstructed edit history * Testing ClickHouse as a very fast serving layer of the edit data * Public Event Streams is on its way of being productionized Upcoming: * We'll meet with Editing team to give some examples on edit data use

=== Architecture / ArchCom ===

=== Release Engineering === Updates: * 1.28 rc.1 this week (for realz) * scap 3.3.1 to go out (already on Beta Cluster) * Phabricator update this week (Wednesday) with Calendar improvements (in support of DevSummit) Blocked: * labs: Request for CI staging project https://phabricator.wikimedia.org/T150772

=== Security === * All projects and and security reviews have been suspended while team focuses on incident handling

=== Discovery ===

- You can now search for file properties such as file size and and file type on Commons.

- https://www.mediawiki.org/wiki/Help:CirrusSearch#File_properties_search

- The Interactive Team's roadmap can be viewed here; it was finalized in Nov 2016 for FY 2016/2017.

- https://www.mediawiki.org/wiki/File:Interactive_Roadmap_2016-2017.pdf

- Tabular & map data on Commons announced

- https://commons.wikimedia.org/wiki/Commons:Village_pump#Launching_shared_map...

=== Services === * Blockers: none * Updates ** Node 6 update planning: https://phabricator.wikimedia.org/T149331

- *** All services ready and tested, kartotherian is on it's way

- *** Planned order: RESTBase -> Parsoid -> SCB -> Others

- *** Q for Ops: is node 6 rollout considered a deployment and is under deployment freeze next week? Alex: Yes. It is under the freeze

** Thumb API discussion, please participate: https://phabricator.wikimedia.org/T66214 ** Scap3 config deployments:

- *** Parsoid: done

- *** CXServer: https://phabricator.wikimedia.org/T147634

- **** Patches done. Ready to proceed Thurstay EU morning, no objections?

- *** MCS - Marko ready to proceed Thursday EU morning, no objections?

=== Technical Operations === * '''Blocked''': ** none * '''Blocking''' ** none * Updates ** kubernetes goal ongoing. working with packaging kubernetes and calico ** labsdbs10{09,10,11} provisioned, work ongoing ** varnish 4 text cluster upgraded finally! Achievement unlocked! ** working with performance on thumbor 100% deployment ** deprecation of precise ongoing, down to 7 boxes

=== Performance === * Blocked ** Consensus to unlock further work on active/active DC project (etcd, session storage, varnish, etc.). I encourage representatives of Operations/Traffic and Services to attend the next active/active meeting on Nov 23. That meeting can be moved later if it's too early for some. * Blocking ** none * Updates ** ?action=markpatrolled is now POST-based ** Live traffic investigation confirmed that a non-trivial amount of pageviews start off as hidden tabs (>8%, mobile included). ** Parser report format reverted, the new format introduced for PerformanceInspector was breaking a commong workflow (i.e. checking the parser report when previewing an edit) ** Comparing HTTP status codes from production image scalers and Thumbor revealed a dozen edge cases. We'll need to discuss with Operations at the next Thumbor meeting which ones are blockers for the launch.

== Wikidata == * Being a WMDE employee I again was not able to join the Hangout, without being manually added every time. * RevisionSlider is out of beta. * Final touches on Cognate extension (automatic interwiki links for all Wiktionaries). * Waiting for security review of the Cognate https://gerrit.wikimedia.org/r/320743 and InterwikiSorting extensions. * German Technical Wishlist team is working on a UI for the 2 PDF renderers. Would like to track/gather feedback for a while. But: https://phabricator.wikimedia.org/T150871

== Fundraising Tech == * Two weeks till Big English ** please tread very softly in core, especially anything that could affect CentralNotice (messages, caching, ResourceLoader) ** FR-tech would appreciate a heads up if there are significant changes * Improving signal to noise ratio in fundraising system logging and alerts * Tweaking mailing list export and offline donation import * Still looking at CentralNotice issues ** https://gerrit.wikimedia.org/r/320317 should have gotten us logging for client-side issue, but we're not seeing those in logstash (search for message key centralnotice, and you only get the server-side messages)