Architecture meetings

These are the meetings we have had/are planning to have surrounding our Architecture guidelines and Requests for comment.

How scheduling works on a weekly basis:


 * 1) Monday: architects meet and decide the agenda for **next week**'s RfC meeting.
 * 2) Wednesday: RfC meeting hosted, the agenda for the next meeting is shared, confirmed, and announced.
 * 3) Friday: Heads up at the Roadmap and Deployments meeting.
 * 4) Next Wednesday: RfC meeting hosted as announced.

Current meetings
See Architecture committee.

Past meetings

 * 2014-08-13 — Wikimania followup and RfC discussion followup
 * 2013-05-24 — /Amsterdam Hackathon 2013 Day 1
 * 2013-05-25 — /Amsterdam Hackathon 2013 Day 2
 * 2013-08-08 — /Wikimania 2013
 * 2013-09-10 — /WMF Engineering All-Hands 2013
 * 2013-09-24 — RFC review 2013-09-24 (IRC) - URL shortener (discussion), Support for user specific page lists in core (discussion), Retained account data self-discovery (discussion)
 * 2013-10-02 — RFC review 2013-10-02 (IRC) - CentralNotice Caching Overhaul - Frontend Proxy, DataStore
 * 2013-11-06 — RFC review 2013-11-06 (IRC)
 * 2013-11-20 — RFC review 2013-11-20 (IRC)
 * 2013-12-04 — RFC review 2013-12-04 (IRC)
 * 2013-12-18 — RFC review 2013-12-18 (IRC)
 * 2014-01-02 — RFC review 2014-01-02 (IRC)
 * 2014-01-15 — RFC review 2014-01-15 (IRC)
 * 2014-01-23/24 — Architecture Summit 2014
 * 2014-02-05 — RFC review 2014-02-05 (IRC)
 * 2014-02-14 — RFC review 2014-02-14 (IRC)
 * 2014-02-21 — RFC review 2014-02-21 (IRC) on HTML templating and service-oriented architecture
 * 2014-02-27 — RFC review 2014-02-27 (IRC) on UI/UX styling
 * 2014-03-05 — RFC review 2014-03-05 (IRC) on TitleValue and passwords
 * 2014-03-12 — RFC review 2014-03-12 (IRC) to get quick next actions on multiple RFCs
 * 2014-03-19 — RFC review 2014-03-19 (IRC) - MVC Framework and structured logging
 * 2014-03-26 — RFC review 2014-03-26 (IRC)
 * 2014-04-02 — RFC review 2014-04-02 (IRC) -- scoped language converter & square bounding boxes
 * 2013-04-09 — RFC review 2014-04-09 to get quick next actions & validity checks on multiple RfCs
 * 2013-04-16 — RFC review 2014-04-16 on reducing image quality for mobile
 * 2014-04-23 — RFC review 2014-04-23 on Requests for comment/Associated namespaces
 * 2014-04-29 — RFC review 2014-04-29 on Requests for comment/MediaWiki libraries and Requests for comment/Third-party components
 * 2014-05-14 — Discussion of Performance guidelines draft
 * 2014-05-21 — Discussion of Typesafe enums and Square bounding boxes
 * 2014-05-30 — Discussion of Requests for comment/Extension registration
 * 2014-06-02 — Discussion of Requests for comment/Grid system
 * 2014-06-11 — Discussion of several RfCs (lightning round)
 * 2014-06-13 — Discussion of security guidelines draft
 * 2014-06-20 — Discussion of revamping MediaWiki's skin systems: Trevor Parscal's "Redo skin framework" and Bartosz Dziewoński's "Separating skins from core MediaWiki" work
 * 2014-06-25 — Discussion of frontend and UX standardization
 * 2014-07-10 — Frontend standardization discussion focusing on Requests for comment/Redo skin framework
 * 2014-07-16 — RfC discussion focusing on Requests for comment/Vertical writing support
 * 2014-07-23 — RfC discussion focusing on Requests for comment/Composer managed libraries for use on WMF cluster
 * 2014-07-30 — RfC discussion focusing on Requests for comment/CentralNotice Caching Overhaul - Frontend Proxy
 * (missing the logs of many, they can be fished out of [http://tools.wmflabs.org/meetbot/wikimedia-office/2014/ here)
 * 2014-10-01 - RfC discussion focusing on Requests for comment/API roadmap

Update instructions
For new RfC review meetings: === Full log ===
 * 1) open a new page at [[Architecture meetings/RFC review 2014-??-??]
 * 2) From http://tools.wmflabs.org/meetbot/wikimedia-office/2014/ - copy the [timestamp.txt] text (the summary/highlights). Paste that, and fix the wikimarkup manually (bulletpoint-indents, etc).
 * 3) Add this underneath, and paste the [timestamp.log.txt] text in the middle. Then transclude the updates on the RfC itself.