Architecture Summit 2014/Attendees

January 23–24, 2014 SPUR 654 Mission Street San Francisco, California, United States

Schedule

 * Call for participants:
 * Application deadline: Tuesday, October 22, 17:00 UTC (10 a.m. PDT)
 * Participant announcement: By Thursday, October 31, 2013
 * Initial agenda: By Friday, November 22
 * RFC finalization: Friday, December 20, 23:00 UTC (4 p.m. PDT). RFCs not out of draft by this deadline may be cut from the main agenda (we may set aside some unconference time)
 * Summit: Thursday–Friday, January 23–24, 2014

Structure
The basic structure of the architecture summit would be:
 * Put out a call for RFCs for badly needed architectural changes.
 * Cherry pick the most important RFCs for discussion resolution
 * Spend a reasonable amount of time discussing each RFC, attempting to come to consensus about acceptance of the work, or at least about next steps.

Additionally, we may spend a portion of the meeting discussing the central architecture document itself, depending on its state come January.

Your feedback about the scope, goals and schedule of the summit are welcome on |the discussion page.

Attending
The target audience of this event are mainly project maintainers and other developers involved in Requests for Comment and, in general, the future evolution of MediaWiki and related software components. All participants must specify their current involvement in the MediaWiki project, the RFC(s) that are promoting and the main future topics they want to discuss.

We are tentatively aiming to have around 50–60 people and we have some budget to sponsor travel for accepted participants.

Request format
In order to request an invitation, please add yourself to the list below.

Tips:
 * Be selective and point to what really matters.
 * Link to the RFCs you are promoting or discussing.
 * If your topic doesn't have a RFC yet, please create it. Drafts are fine for a start.


 * 1) Your name; organization; location
 * 2) * Role: What role will you fill at the summit?
 * 3) * RFCs commented: What RFCs have you already commented on?
 * 4) * RFCs to discuss: What RFCs or other issues do you believe are the most important ones to discuss?
 * 5) * How I'll help: what volunteering tasks are you willing to take? (e.g. note-taking, shepherding follow-up discussions, prototyping). Please be specific.

Organization

 * Coordination: Rob Lanphier. He controls the budget and bootstraps the committee.
 * Committee: Mark Bergsma, Tim Starling, Brion Vibber, Arthur Richards, Roan Kattouw and maybe more. They accept participants and drive the schedule.
 * Logistics: Rachel Farrand and Quim Gil.