Wikimedia Platform Engineering/Wikimedia MediaWiki API Team/Meeting Minutes/2015-04-07

Status
(no discussion of items here, add to “To Discuss” if something needs discussion)
 * Brad
 * Working on unit tests for AuthManager.
 * Slightly stuck on the User-class/password question from the mailing list, more feedback would help.
 * Reviewing lots of code.
 * Gergo
 * looking for feedback on T74469/T94885
 * Sentry stuff: UploadWizard error logging goes live this week, need help on orchestration part from someone with more puppet/salt knowledge
 * Will discuss with Bryan
 * Kunal
 * SUL. A few patches need code review. Chris said he would look.
 * https://gerrit.wikimedia.org/r/#/c/201144/
 * Mark
 * Out
 * Bryan
 * Wrapping up Q3 review meeting prep for Platform
 * Working on logging config and backports (shhh don't tell anybody I'm coding)
 * Other

To Discuss

 * Agenda/Minutes
 * Ongoing agenda in google doc (which only the team can view, for security)
 * Kevin will copy a redacted version to a wiki page after each meeting
 * https://www.mediawiki.org/wiki/Wikimedia_MediaWiki_API_Team/Meeting_Minutes
 * Who’s our victim for attending Scrum-of-Scrums?
 * Bryan to cover this week. Ask Mark about future.
 * Do we care about keeping track of everyone’s vacations and other unavailabilities, and if so how should we do it?
 * Kevin will talk to Rob
 * Options:
 * In here, like MW Core did?
 * Officewiki page?
 * Get a team calendar set up?
 * Brad suggests we should try to make it a “strong suggestion” that we get asked to review new api.php modules, at least for code deployed to the cluster.
 * Having the API team as stewards of the api.php makes sense
 * devs: let them know via mailing list that API team is available to help (Bryan to draft email)
 * PMs in features area: Maybe informative email from Damon (Bryan to ghostwrite)
 * Should API team have representation on ArchCom? (Bryan to ask Robla, or delegate to Kevin)
 * Discuss patches for blocked issues: Are devs writing code for known-blocked tasks, or are tasks getting blocked after the code is written?
 * Some of each
 * Kevin just wanted to raise awareness of the issue. No action items.
 * Bryan may not be at next week’s meeting

SUL status (can we help?)

 * Just code reviews

What is Blocked on Core/API

 * https://phabricator.wikimedia.org/T78730
 * Kevin to switch from blocked-on-core to blocked-on-security

What is blocking us (which should go to Scrum-of-Scrums)

 * Maybe that AuthManager will need HHVM patch adc98c20 to work on HHVM, no idea what the timeline might be on getting that into our HHVM. We’re a good way from actually being blocked on it though.
 * Wikidata issue blocking a bunch of ours:
 * https://phabricator.wikimedia.org/T95168 (which is blocking T91073 which is blocking T76728 which is blocking 4 others, one of which is blocking 2 others, one of which is blocking one other)