Architecture committee/2014-10-29

People present: Brion, Mark, Roan, Tim, Daniel

Pending action items

• brion: flesh out Graph rfc w/ Yuri
• Tim to write RFC on merging enhanced recentchanges with normal RC
• brion: catch up with jon robson about the html templating rfc blurb to update it to current changeset & upcoming plans
• [?] start putting approved RfCs into phabricator for tracking
  • -> start priotizing
• brion: start an Arch/RfC entry in Scrum of Scrums for cross-team asks
• Tim to ask S Page about "Need to merge Notifications and Watchlist or lack thereof"
  • You may wish to CC Danny Horn, he's the product manager for Echo/Flow
• brion: prep some agenda items for Summit in January: make sure we have some plans for how to deal with RfCs that are basically feature requests; bump them to functional teams for work once we've determined there's no arch problem?
• Tim to write RFC on merging enhanced recentchanges with normal RC
• Tim to Import all RFCs into phabricator

RFCs to triage

• https://www.mediawiki.org/wiki/Requests_for_comment/Content_API
  • Seems to have morphed into a RESTBase RFC. We should probably discuss RESTBase at some point.
    • Let's grab Gabriel and make sure he's available -- he's pushing for deployments? let's make sure we know what's what.
• https://www.mediawiki.org/wiki/Requests_for_comment/Ditch_crappy_API_formats
• https://www.mediawiki.org/wiki/Requests_for_comment/Clean_up_URLs
• https://www.mediawiki.org/wiki/Requests_for_comment/Storage_service
  • briefly discussed

RFC scheduling

This week (Oct 29)

• Core user preferences
• Redesign user preferences
• Isolate custom jQuery libraries

Next week (Nov 5)

• Content API and/or Storage service? (check with Gabriel)
  • let's make sure we understand the diff between the two RfCs -- one is internal, one is external-facing?

Other business

• Dev summit planning: https://etherpad.wikimedia.org/p/ArchitectureCommittee-DevSummit2015

New action items

• Tim to read RESTBase code
• Brion to also read RESTBase code