Architecture committee/2016-07-20

The TechCom planning meeting is a weekly invite-only video discussion, generally held on Wednesday 13:00 USA Pacific Time.
See also TechCom-RFC workboard in Phabricator. (Private minutes)

Agenda timelineEdit

  • Intro
    • Agenda bashing and action item check 21:00 (5 minutes)
    • Review last week's RfC office hour 21:05 (5 minutes)
  • RFC status update
    • RfC inbox triage 21:10 (10 minutes)
    • Shepherd assignments 21:20 (5 minutes)
    • Queue for future RfC office hours 21:25 (5 minutes)
  • Wrapup
    • Other business 21:30 (10 minutes)
    • Next week’s ArchCom agenda 21:40 (10 minutes)

Agenda details/Meeting summaryEdit

This section equates to the "meeting summary" section in the meeting note template. It's collaboratively edited during the meeting and serves as the official public notes of the meeting. Attendees: Fill in the important details in this section, but try to keep this concise and NPOV (easy way: use questions).  Put any prep information in this section if appropriate

Intro sectionEdit

10 minutes (starting 21:00 UTC)

  • Last week's ArchCom planning meeting (W28, Phab:E227)
  • Review last week’s RfC office hour (Phab:E228)
    • T589: RfC: image and oldimage tables
      • Timo posted a summary: fd
      • Gabriel comment on the task

RFC status updateEdit

20 minutes (starting 21:10 UTC)

Spend roughly 20 minutes ensuring Architecture committee/Status is up-to-date. Checklist of the questions we should answer:

  • Who is chairing Phab:E235? Rob
  • Conclude last week's "final comment period"? nope
  • Do we have anything that should enter "final comment"? nope
  • For each upcoming meeting, do we anticipate the RFC moving into "final comment"? nope
  • Picking an RFC for next week:
    • Inbox of ArchCom-RfCs board
      • T128602 Create and deploy an extension that implements an authenticated key-value store
      • T107595 [RFC] Multi-Content Revisions
    • Individual updates to Architecture committee/Status
    • Are responsibilities balanced well between ArchCom members?
      • ACTION (Rob) ^^ add archcom-has-shepherd link to mtg template
    • Which RFCs are listed as "needs triage"?
    • Do we have an RFC selected for next week's meeting?
    • T128602 Create and deploy an extension that implements an authenticated key-value store

Other business/planningEdit

  • 20 minutes (starting 21:30 UTC)
    • Gerrit: Ori's pingback patch
      • Inspired by Brion’s suggestion for phone-home info?
      • ACTION: RobLa to ask Ori to send wikitech-l email about this
    • Next week's ArchCom
      • Minutes publication from the ArchCom planning meeting