Architecture committee/2016-08-03

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)

Minutes

Intro section

10 minutes (starting 21:00 UTC)

• Action items
  • Last week
    • ACTION: Rob to figure out Security access for Daniel
    • ACTION: Tim: find wikitech-l post on captcha (done)
    • ACTION: Brion to comment on T128351 with alternatives (done)
    • ACTION: Rob to announce T128351 (done)
• Review last week’s RfC office hour
  • E237T128602: Create and deploy an extension that implements an authenticated key-value store
• Update attendee list
  • Daniel, Kevin, RobLa, Tim, Timo
  • Invited: Brion, Daniel, Gabriel, Kevin, Roan, RobLa, Tim, Timo
  • RSVP
    • yes: Daniel, Gabriel, Rob, Timo
    • no: Brion
    • maybe/unknown: Tim

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? T128351.  Rob will chair
• 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"?  Field narrowing
• Picking an RFC for next week:
  • How does ArchCom-RfCs board look?
    • Where should anything in the inbox go?
  • What is the most important thing each ArchCom member is shepherding? Anything blocked?
    • Brion Vibber...
    • Daniel Kinzler
      • Working on DB schema for MCR.  Bottom up instead of top down.  Next step:
      • ACTION: Daniel: write email to Brion and Jaime transform current schema to new schema with sample data
    • Gabriel Wicke...
    • Rob Lanphier.T128351..
    • Roan Kattouw...
    • Tim Starling…
      • T89331 is blocked on T141591 (security review)
      • ACTION: Tim to post T141591 to Z411
    • Timo Tijhof
      • T111588
        • Gabriel and I started drafting the spec for the composition server.
        • Gabriel and I have each started work on some of the lower-level libraries required for the composition server to deal with ServiceWorker-environments in Node.js, and supporting Mustache in a transform stream. See https://github.com/gwicke/mixmaster, https://github.com/gwicke/node-serviceworker and https://github.com/Krinkle/musti
      • T589 ACTION: Timo to mail wikitech-l and encourage further conversation about details of the oldimage schema changes, and migration plan.
  • Are responsibilities balanced well between ArchCom members?
    • ACTION: Rob to take T139300 shepherd role
  • Do we have an RFC selected for next week's meeting?
  • Blob storage interface?  ACTION: Rob: have an answer by EOD Thursday about need next week
  • Which RFCs are listed as "needs triage"?
  • Do we have an RFC selected for next week's meeting?
    • ACTION: Rob figure out agenda for Wed W32
      • First choice: ask Subbu about HTML spec (e.g. Specs/HTML/1.2.1 and “[Wikitech-l] Loosing the history of our projects to bitrot” thread, and Subbu’s draft page)
      • Second choice: credits file discussion (T139300)
      • Third choice: blob storage/MCR
      • Honorable mention:
        • T141490 (deploy improved FancyCaptcha)
        • T34695 - wikicaptcha (reCAPTCHA inspired)

Other business/planning

20 minutes (starting 21:30 UTC)

• DevSummit
  • ACTION: Rob: make sure we spend a few minutes each week discussing
• Next week's ArchCom