Architecture committee/2016-05-04

Agenda timeline

 * Intro
 * Agenda bashing and action item check 21:00 (5 minutes)
 * Last week+this week’s RfC office hour 21:05 (5 minutes)
 * RFC status update
 * Format / goal of public update 21:10 (5 minutes)
 * Architecture committee/Status
 * RfC inbox triage 21:10 (5 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 summary

 * 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 section

 * 10 minutes (starting 21:00 UTC)


 * Last week’s RfC office hour
 * T122942: RFC: Support language variants in the REST API

RFC status update
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? RobLa
 * Do we have anything that should enter "final comment"? T120164
 * Do we have a robust queue of RFCs to discuss at future IRC discussions? Needs work
 * For each upcoming meeting, do we anticipate the RFC moving into "final comment"? (RobLa need to rephrase that question, since he confused himself)


 * How does ArchCom-RfCs board look? Inbox is empty.  Backlog is full.  See E167#1881
 * What is the most important thing each ArchCom member is shepherding?
 * Daniel
 * Not aware of anything
 * Following up on SQ working group
 * Multi Content Rev Spec with Brion - soon but not yet
 * Interwiki T113034?
 * Tim
 * No update
 * Gabriel
 * updated wiki
 * Roan
 * need to talk to Timo (action: update status)
 * RobLa
 * Daniel asked about T120164
 * ACTION: RobLa to issue a Last call
 * ACTION: create a “Last call” column on the ArchCom-RFC board
 * Absent today: Brion, Timo
 * Anything blocked? Are responsibilities balanced well?  See status

Other business/planning
20 minutes (starting 21:30 UTC)
 * Security working group? Brian Wolff joined our conversation on this
 * What should be our process for Security-related RFCs?
 * ACTION: Brian/RobLa to discuss long term plan
 * Figure out when to make things public
 * ACTION: Brian/Tim - make sure ArchCom has access to the things they need access to


 * Next week's ArchCom: We settled on T113034 for next week at the end of the meeting

generated from Architecture committee/MeetingNoteTemplate