Jump to content

Scrum of scrums/2015-03-18

From mediawiki.org

2015-03-18

[edit]

Language

[edit]

Wikidata

[edit]

Parsoid

[edit]
  • Good progress with VE Q3 blocker bugs -- almost done on the Parsoid end unless more bugs surface.
  • VE and Parsoid need to sync up with dealing with inter-page copy-paste.

Security

[edit]
  • Release Thurs or Monday (releng)
  • Training for fr-tech
  • Hovercard/Popups review in progress (design)
  • Initial gather review on Fri
  • T78730 temporarily on hold
  • Hiring

Multimedia

[edit]
  • SHA-1 patch needs AaronS and Gilles to coordinate for progress
  • Ops, heads up, we're requesting hardware for Sentry soon.

Analytics

[edit]
  • Event Logging throughput issues resolved for now

RelEng

[edit]
  • Staging environment slated for (near) completion by this quarter
  • Isolated CI project moving forward to be completed by end of Q4 (July)
  • Release MW 1.25 https://phabricator.wikimedia.org/T88709
  • Some improvements to MW-Vagrant regarding role settings, etc. to better accommodate heavy services
  • Blockage: Antoine would like to talk with Ops regarding isolated CI architecture https://phabricator.wikimedia.org/T92324

Services

[edit]

Editing

[edit]
  • Coordinating RESTbase roll-out with Services
  • Working on hittiing RESTbase directly once it's been rolled out
  • Citoid extension finally live on phase0 wikis, special thanks to Alexandros in ops for all the work getting the citoid service up
  • Mobile VE broken in wmf21 :( working on fixing

Mobile web

[edit]

Maps

[edit]
  • Kicking off in April, see email announcements

MediaWiki Core

[edit]


Fundraising Tech

[edit]


Operations

[edit]


Apps

[edit]
  • Bernd bringing existing services code from GitHub into Gerrit, noted that services on-call support will be important for breaking change hotfixes in the future
  • https://phabricator.wikimedia.org/T88633 Image-positioning service: team wanted to just raise the visibility on this ticket
  • Reminder: release new versions of apps on March 30
[edit]
  • Planning to get JavaScript Event Logging code submitted for Schema:Search sampled logging (i.e., 1 in x users will have the event logging running) in the next 1.0-2.5 weeks in order to get it running on desktop production for the last couple weeks of April