Architecture committee/2016-07-27
Appearance
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)
See also TechCom-RFC workboard in Phabricator. (Private minutes)
Agenda timeline
[edit]- 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
[edit]- 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
[edit]- 10 minutes (starting 21:00 UTC)
- Last week's ArchCom planning meeting (W29, E234)
- Review last week’s RfC office hour (E235)
- T126641: [RFC] Devise plan for a cross-wiki watchlist back-end
RFC status update
[edit]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? E237
- T128602: Create and deploy an extension that implements an authenticated key-value store
- RobLa to chair
- Field narrowing? Potentially a candidate for “in progress”
- 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"?
- Picking an RFC for next week:
- Review the ArchCom-RfCs board
- Where should anything in the inbox go?
- Which RFCs are listed as "needs triage"?
- Review the ArchCom-has-shepherd board and discuss each member's assignments/priorities:
- Brion Vibber:
- Status updated (a little backlogged, will continue with MCRevs updates): Architecture_committee/Status#Brion
- Daniel Kinzler. (intermittent connectivity issues)
- Blob storage layer for MCR
- Jaime has been asking for DB layout experiments.
- Gabriel Wicke:
- Rob Lanphier:
- Status is updated: Architecture committee/Status#RobLa
- Security WG item (see Phab:Z411#6231 for context, see also T125132)
- ACTION: Rob to figure out Security access for Daniel
- ACTION: Tim: find wikitech-l post on captcha
- Roan Kattouw.
- Tim Starling:
- Scott has mostly been working on Parsoid tasks
- Deployment is slowly moving forward html5depurate
- Timo Tijhof:
- No update on old_image. Will talk to Tim and Jaime
- API driven front end. continuing work on that; status page updated just now
- CSP moved to “no activity”
- Brion Vibber:
- Do we have an RFC selected for next week's meeting?
- Review the ArchCom-RfCs board
Other business/planning
[edit]20 minutes (starting 21:30 UTC)
- Security WG item (see Phab:Z411#6231 for context)
- Next week's ArchCom