Architecture committee/2016-07-13

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 timeline

• 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 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 (mw notes: 2016-07-06, E225)
• Review last week’s RfC office hour
  • Phab:E226
    • Phab:T136866: Improve the per-programming-language listings for our tools

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? (about T589: RfC: image and oldimage tables) Rob to chair, Timo: shepherd.  Field narrowing conversation
• Do we have anything that should enter "final comment period"?
• Is T589 likely to move into "final comment"?
• Picking an RFC for next week:
  • How does ArchCom-RfCs board look?
    • Inbox:
      • T139810 RFC: New CheckUser extension
        • ACTION: Tim will comment
        • State: backlog
      • Phab:T126641 [RFC] Technical implementation plan for a cross-wiki watchlist (back-end only)
        • ACTION: Gabriel to comment
        • Keep in inbox, move to backlog if still stalled next week
      • Phab:T107595 [RFC] Multi-Content Revisions
        • Under discussion
      • Phab:T105638 RFC: Streamlining Composer usage
        • Timo will comment
        • Move to “Needs shepherd
        • Stay in “Needs triage” until comment responded to
  • What is the most important thing each ArchCom member is shepherding? Anything blocked?
    • New! ArchCom-has-shepherd workboard
    • Update your section in Architecture committee/Status!
    • Brion Vibber
      • Update on MCR?
      • Reviving the installer ‘beacon’ option
    • Daniel Kinzler
    • Gabriel Wicke
      • getting back into content composition.
    • Rob Lanphier
      • Link to Kevin’s draft doc about ArchCom purpose and process: https://www.mediawiki.org/wiki/User:KSmith_(WMF)/ArchCom_thoughts
    • Roan Kattouw
    • Tim Starling
      • Met with CScott (Tidy RFC).  Talked with team about Parsoid things that aren’t yet in RFCs
    • Timo Tijhof
      • RFC discussed this week; wishlist: content composition
  • Are responsibilities balanced well between ArchCom members?
  • Which RFCs are listed as "needs triage"?
  • Do we have an RFC selected for next week's meeting?
    • MCR?  Security RFC?  T126641?
    • Next week’s nominee: T126641
    • ACTION: Rob: talk to Kaldari Niharika and figure this out

Other business/planning

20 minutes (starting 21:30 UTC)

• Next week's meetings (Planning: E234, Office hour: E235)

generated from Architecture committee/MeetingNoteTemplate