Architecture committee/2016-07-27

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)

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 the upcoming IRC meeting? E237
    • T128602: Create and deploy an extension that implements an authenticated key-value store
    • RobLa to chair
    • Field narrowing?  Potentially a candidate for “in progress”
  • Conclude last week's "final comment period"? Do we have anything that should enter "final comment"?
  • For each upcoming meeting, do we anticipate the RFC moving into "final comment"?
  • Picking an RFC for next week:
    • Review the ArchCom-RfCs board
      • Where should anything in the inbox go?
      • Which RFCs are listed as "needs triage"?
    • Review the ArchCom-has-shepherd board and discuss each member's assignments/priorities:
    • Do we have an RFC selected for next week's meeting?
      • Change propagation?
      • T128351 (moving Echo notification framework to core)?
      • ACTION: Brion to comment on T128351 with alternatives
      • ACTION: Rob to announce T128351

Other business/planningEdit

20 minutes (starting 21:30 UTC)