Scrum of scrums/2015-04-22
2015-04-22
editSearch Team
edit- Ongoing preparations for Wikidata Query Service version 0.0.1
- [ ] truthiness
- [ ] Puppet scripts
- [ ] Labs infrastructure
- [x] packaging for distribution
- [ ] documentation
- Ongoing team structure/organization planning, interviews, etc. re: reorg
Wikidata
edit- What has your team done since we last met?
- Big thanks to Stas, Nik, Jason and Co for continuing to work on query service and RDF exports!
- What will your team do before we meet again?
- Begin to roll out usage tracking on next Tuesday on fr Wikisource and nl Wikipedia
- Is anything slowing your team down or getting in their way?
- No fatal logs: https://phabricator.wikimedia.org/T89169
- Changing a name in LDAP: https://phabricator.wikimedia.org/T85913
- Are you about to put something in another team’s way?
- not planned
Analytics
editDone: Welcoming madhu, new team member Fixing small EL data drops (1 hr in length) right now. Phabricator task: https://phabricator.wikimedia.org/T96082 Incident documentation: https://wikitech.wikimedia.org/wiki/Incident_documentation/20150409-EventLogging
Reworked cluster resource allocation, backfilled pageview files that had stalled Working on spark jobs to determine length of mobile sessions Work into our visualization platform: dashiki (limn replcement, currently hosting only vital signs, will host VE funnel viz)
Will do: Finish backfilling Work into visualization platform (dashiki) Pageview computations (new definition), communication and development
Parsing
edit- Erstwhile parsoid team, now under the editing department. Missed last week because of quarterly review.
- Continuing to deal with code cleanup and tech debt last 2 weeks. Should be done in a week's time, and focus entirely on VE goals.
- Added a new normalization pass to our HTML -> WT endpoints which clients can enable (pass "scrubWikitext=true" via POST or GET) for more aggressive normalization if desired. Added to support VE. Yet to be documented.
RelEng
edit- What has your team done since we last met?
- Stoping staging-work for the time being, moving forward on deployment tooling
- Continued work on Isolated CI instances, breaking up pool into smaller hosts
- Finishing by-team test history
- What will your team do before we meet again?
- Deployment research team meeting tomorrow
- Finish by-team test history (this week is the goal)
- Is anything slowing your team down or getting in their way?
- Nothing currently
- Are you about to put something in another team’s way?
- No plans
Services
edit- Done:
- RESTBase: security headers, generic cache module, various small fixes
- Services:
- Work with ops on streamlining the deployment process (ongoing)
- Deployment of graphoid (ongoing)
- To do:
- All ongoing stuff wrt deployment
- Work on deploying MobileApps service
- Meet with RelEng to continue the conversation about future deployment tooling
- Blockers:
- eployment of MobileApps
- test sec headers: https://phabricator.wikimedia.org/T96126
- write tests: https://phabricator.wikimedia.org/T96870
- eployment of MobileApps
Fundraising Tech
edit- Done:
- CentralNotice code cleanup
- Small DonationInterface fixes
- Doing:
- Astropay integration
- Use Mustache in donation forms
- Make queueing not ActiveMQ-specific
No blockers, no plans to block
Language
edit- CX in 17 more Wikis!
- Blocker: Mystery of failing package (apertium-dan) build,
https://phabricator.wikimedia.org/P481
- No other blockers
API Team (that doesn't exist any more)
edit- SUL finalization Done (mostly, a few things to button up before setting `$wgCentralAuthStrict = true` on the prod cluster)
- Logstash servers racked; bd808 will be working with ops on provisioning and adding them to the current cluster
Operations
edit- phab:T72068 Jenkins: Re-enable lint checks for Apache config in operations-puppet
- New patch by Legotkm, needs review.
- phab:T88798 Jenkins is using php-luasandbox 1.9-1 for zend unit tests; precise should be upgraded to 2.0-8 or equivalent
- No response since Alex's last response o March 30.
Security
edit- Coordinating with all teams for security priorities