2016-03-30

Technology

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

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)

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

Blocking:
- /
Blocked:
- /
Updates:
- RESTBase
  - Redirects for File: titles active only for the native moblie apps
  - general availability blocked on VE - https://phabricator.wikimedia.org/T130757
  - bumped s-maxage for purged content to 1 week
- deployed the change-propagation service (via scap3)
- working on docs - https://www.mediawiki.org/wiki/Documentation/Services

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

Blocking:
- Not that we are aware of
Blocked:
- Quick Surveys:Not known to be blocked on anyone in SoS, but we might ask for help
- Existing: ops https://phabricator.wikimedia.org/T127014 and security https://phabricator.wikimedia.org/T127014
Updates:
- We are experimenting publishing weekly status updates: https://www.mediawiki.org/wiki/Discovery/Status_updates

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

Blocking:
- None
Blocked:
- None
Updates:
- Work on Parallel Corpora dump (will) need some time from Ops (Ariel), See: https://phabricator.wikimedia.org/T127793

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.

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

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

(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)