Architecture committee/2016-07-06

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)

  • Action items
    • Last week
      • ACTION (Rob [optional, lower priority]): provide update on Phab:T89331 that conversation is happening (done; more-or-less)
      • ACTION (Rob): talk to Product and/or Usability about T128352 (partially done)
        • I had a brief impromptu conv with Abbey and Danny (noted in Phab)
      • ACTION (Rob): better board triage (done, for some value of "better")  :-)
  • Review last week’s RfC office hour
    • ArchCom-RFC office hour 2016W26: 2016-06-29: E224 (E66/41)
      • T137926 - Require 'curl' PHP extension for MediaWiki
        • Conclusion: Last Call
      • ACTION: Rob - remove the word “deprecate” from the status page
      • ACTION Krinkle - approve the last call

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? Tim will chair, Rob will shepherd
  • Conclude last week's "final comment period":
    • T137926 - Require 'curl' PHP extension for MediaWiki
  • 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:
    • How does ArchCom-RfCs board look? Where should anything in the inbox go?
      • T139300 Create formal process for CREDITS files
        • Move to “Needs shepherd”, normal priority
      • T139012 Use index on rc_this_oldid
        • High priority, Daniel will shepherd, under discussion
      • T16950 Support global preferences
        • T120385 - language team’s work
        • ACTION Tim - comment on this task
        • ACTION: Rob: move to Backlog
      • T589 RfC: image and oldimage tables
        • Next week’s discussion
        • Move it to “ready for discussion”
        • ACTION: Rob Announce this as our topic for next week
    • What is the most important thing each ArchCom member is shepherding? Anything blocked?
    • Do we have an RFC selected for next week's meeting? T589

Other business/planningEdit

20 minutes (starting 21:30 UTC)

  • In E224, Brion and RobLa agreed we should use this meeting to discuss a plan for having an installer beacon
  • Next week's ArchCom