Architecture committee/2016-06-08

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


 * Action items
 * Last week
 * Gabriel: follow up on Phab:T102476 - RFC: Requirements for change propagation
 * RobLa: make proposal "Backlog" column
 * RobLa: update workboard based on W21 IRC session (E187)
 * Last week’s RfC office hour
 * Architecture committee/2016-06-01 (E197)

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?
 * Conclude last week's "final comment period"? Do we have anything that should enter "final comment"?
 * Do we have a robust queue of RFCs to discuss at future IRC discussions?
 * For each upcoming meeting, do we anticipate the RFC moving into "final comment"?
 * How does ArchCom-RfCs board look?
 * Inbox:
 * T124569 RFC: Data namespace blob storage on wikidata.org
 * See also T134426, and Yuri's 2016-06-04 email to wikitech-l
 * What is the most important thing each ArchCom member is shepherding? Anything blocked?  Are responsibilities balanced well?
 * Brion
 * Multi-content revisions (T107595) is interesting
 * Daniel
 * Software Quality working group?
 * Working on Multi Content Rev Spec with Brion
 * T113034 RFC: Overhaul Interwiki map, unify with Sites and WikiMap: checking in with Adam
 * T89733 (approved, with Stas driving implementation)
 * Gabriel
 * Working with BSitzmann on T132597 (no longer an RFC)
 * Action item from Phab:E197: follow up on Phab:T102476 - RFC: Requirements for change propagation
 * Roan
 * T108655 RFC: Standardise JavaScript interfaces: I need to start the second part, but the recent comments have me confused. I'll need to talk to Timo and figure out what the subject of part two should be.
 * RobLa
 * Working with DPatrick on Wikimedia Security Team issues in an attempt to be useful there.
 * T123753 Establish retrospective reports for Security and Performance incidents
 * In scope for this group?
 * Forming ArchCom-affiliated working groups
 * RFCs
 * T124504 Transition WikiDev '16 working areas into working groups and
 * T123606 RFC: Implement ArchCom-affiliated working groups (process inspired by Rust's "subteams")
 * Testing Conpherence use for means of piloting ArchCom working groups. Still using Z425 as asynchronous ArchCom-RFC triage channel.  A Security/ArchCom quasi-working group discusses some issues in Z411.  I started renaming "subteams" to "working groups" on Requests for comment/Governance (with Nemo's help).
 * Tim
 * T89331 (Replace Tidy in MW parser with HTML 5 parse/reserialize) - should meet to discuss migration rather than implementation plan
 * T114444 RFC: Introduce notion of DOM scopes in wikitext: (Update?)
 * Timo
 * Section anchors - will update T18691
 * CSP - T135963 - Will shepherd
 * Local storage abstraction T121646 working with Fundraising on this to move cookies into local storage; not an RFC yet, but may become one.

Other business/planning
20 minutes (starting 21:30 UTC)
 * Next week's ArchCom

generated from Architecture committee/MeetingNoteTemplate