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.

Requests

 * 1) Rob Lanphier; Wikimedia Foundation; San Francisco
 * 2) * Role: Facilitating, probably some note-taking, quite possibly moderating at least some of the discussion
 * 3) * RFCs commented: mainly Architecture guidelines
 * 4) * RFCs to discuss: Parsoid/Roadmap, ,
 * 5) * How I'll help: moderation, facilitation, and and note-taking primarily
 * 6) Tomasz Finc; Wikimedia Foundation; San Francisco
 * 7) * Role: Highlighting mobile development needs
 * 8) * RFCs commented: mainly internal team discussions
 * 9) * RFCs to discuss:
 * 10) * How I'll help: Providing perspective for features based initiatives
 * 11) Mark Holmquist; Wikimedia Foundation; San Francisco
 * 12) * Role: Representing Multimedia team's needs, wearing front-end developer hat
 * 13) * RFCs commented: None really, but participated in offline discussions
 * 14) * RFCs to discuss:, , likely others as discussion plays out
 * 15) * How I'll help: Could do note-taking and help with prototyping maybe.
 * 16) Tyler Romeo; N/A; New York
 * 17) * Role: Discussing RFC designs, commenting on current proposals, ensuring security is taken into account
 * 18) * RFCs commented:, , maybe others
 * 19) * RFCs to discuss:, , ,
 * 20) * How I'll help: Prototyping solutions, editing RFCs for clarification
 * 21) Gabriel Wicke; Wikimedia Foundation; San Francisco
 * 22) * Role: Discuss Parsoid, storage services, HTML only wikis, ESI caching, packaging, ...
 * 23) * RFCs commented: Parsoid/Roadmap,, , , , ,
 * 24) * RFCs to discuss: Parsoid/Roadmap, User:GWicke/Notes/Storage (RFC in development), ,
 * 25) * How I'll help: Present current implementation status and prototypes, discuss next steps and long-term vision, provide feedback on RFCs and help edit them.
 * 26) Dan Garry; Wikimedia Foundation; Manchester, United Kingdom
 * 27) * Role: Representing the platform engineering team, in particular MediaWiki Core. Discussing platform projects with people from other teams.
 * 28) * RFCs commented: None at present. Tim made me aware of the RfCs recently, and has asked me to get involved.
 * 29) * RFCs to discuss: Unsure at present. See above.
 * 30) * How I'll help: Will do a talk giving an overview of platform and each project that's being worked on.
 * 31) Howie Fung; Wikimedia Foundation; San Francisco
 * 32) * Role: Observer
 * 33) * RFCs commented: None
 * 34) * RFCs to discuss: None
 * 35) * How I'll help: Happy to help out in whatever capacity the team needs.
 * 36) Daniel Kinzler
 * 37) * Role: Senior Developer at the Wikidata project
 * 38) * RFCs commented: -/-
 * 39) * RFCs to discuss:
 * 40) * How I'll help: Provide insight into the best practices and experiences at the Wikidata project.
 * 41) Nik Everett; Wikimedia Foundation; Raleigh, North Carolina
 * 42) * Role: Developer
 * 43) * RFCs commented:, (via IRC I think), ,  (my baby),
 * 44) * RFCs to discuss: I have none at this point.
 * 45) * How I'll help: Hopefully insightful comments.
 * 46) Chad
 * 47) * Role: Developer
 * 48) * RFCs commented: ,
 * 49) * RFCs to discuss: ,
 * 50) * How I'll help: I'm opinionated :)
 * 51) Bryan Davis; Wikimedia Foundation; Boise, Idaho
 * 52) * Role: Developer, "Outsider" perspective
 * 53) * RFCs commented: -/-
 * 54) * RFCs to discuss: (author)
 * 55) * How I'll help: Comments, Questions, Other duties as assigned
 * 56) Jon Robson; Wikimedia Foundation; San Francisco
 * 57) * Role: Developer
 * 58) * RFCs to discuss: January is a while away so it's hard to say but Styling in templates and RL template support (to be written up)
 * 59) Chris Steipp; Wikimedia Foundation; San Francisco
 * 60) * Role: Security perspective, platform's needs, developer
 * 61) * RFCs commented: Allow styling in templates, Alternative Commons Domains
 * 62) * RFCs to discuss:, , ,
 * 63) * How I'll help: Contribute to the conversation
 * 64) Brad Jorsch; Wikimedia Foundation; North Carolina
 * 65) * Role: Developer
 * 66) * RFCs commented: Architecture guidelines,, , , various others
 * 67) * RFCs to discuss: Architecture guidelines,
 * 68) * How I'll help: Contribute to discussion, write code, hopefully provide some useful "enwiki community" perspective too
 * 69) MZMcBride
 * 70) * Role: serial commentator and sassmaster; heavily involved in bug triaging, process, and meta-process; somewhat involved in user support, end-user documentation, and code/project development; rarely involved in writing code
 * 71) * RFCs commented: http://p.defau.lt/?Jeej070LOvSBRQlt7RQsOA
 * 72) * RFCs to discuss: no idea
 * 73) * How I'll help: providing institutional memory, providing first-hand experience of the RFC process, note-taking, &c.; side note/humblebrag: I'm the reason the RFC process still exists (there was a past effort to merge it into the older review queue that I nixed ;-)
 * 74) Aaron Schulz; Wikimedia Foundation; San Francisco
 * 75) * Role: platform's needs, developer
 * 76) * RFCs commented: Architecture guidelines, thumbnail cache
 * 77) * RFCs to discuss:, , Architecture guidelines
 * 78) * How I'll help: Contribute to the conversation
 * 79) Sean Pringle; Wikimedia Foundation; Australia
 * 80) * Role: DBA
 * 81) * How I'll help: Contribute to the conversation
 * 82) Siebrand Mazeland; Wikimedia Foundation, translatewiki.net; Netherlands
 * 83) * Role: keep an eye i18n/L10n needs
 * 84) *RFCs commented: Not that many
 * 85) *RFCs to discuss: Updated i18n format, MediaWiki independent i18n (mostly for frontend)
 * 86) * How I'll help: Keep forward momentum
 * 87) Mark Hershberger; Release manager
 * 88) * Role: Tarball construction, working with third parties, supporting MW users, occasional bug fixes
 * 89) * RFCs commented: Not that many
 * 90) * RFCs to discuss:
 * 91) * How I'll help: Make sure small user's needs are considered, working with orgs like CPanel and VirtualMin
 * 92) Markus Glaser, release manager; Germany
 * 93) * Role: release manager, working with 3rd party users (mainly in enterprise context), BlueSpice, Wikimedia Germany
 * 94) * RFCs commented: Cirrus_search, Login Security, Site registration, Extension release management
 * 95) * RFCs to discuss: Parsoid, MediaWiki Foundation, Configration database
 * 96) * How I'll help: note taking, bring in view of 3rd party users, alternative funding models, integration with other software
 * 97) Greg Grossmeier
 * 98) * Role: Release Manager @ WMF
 * 99) * RFCs commented: -
 * 100) * RFCs to discuss: -
 * 101) * How I'll help: notes and organizational help
 * 102) Steven Walling: WMF product mis-manager, San Francisco
 * 103) * Role: Primarily observer, may contribute some
 * 104) * RFCs commented: LESS (co-author), Workflow, Clean up URLs, Grid system
 * 105) * RFCs to discuss, in order of priority: Support for user-specific page lists in core, Grid system, Password requirements
 * 106) * How I'll help: I'll do all non-technical scutwork as needed, including note-taking, product/design review as desired, etc.
 * 107) Niklas Laxström
 * 108) * Role: mainly i18n and things affecting LangEng team development work
 * 109) * RFCs commented: LESS, CirrusSearch, Grid system, MediaWiki Foundation, Configuration database
 * 110) * RFCs to discuss: Grid, l10n file formats (to be written), Isolate custom jQuery libraries, Vertical writing support (maybe)
 * 111) * How I'll help: Continue the many year effort making sure that our i18n support stays on the leading edge (should not be taken for granted). Knowledge of many pieces of MediaWiki. Being and working with 3rd party users. Can write blog posts.
 * 112) Sam Reed; Wikimedia Foundation; United Kingdom
 * 113) * Role: WMF (Software|Release) Engineer
 * 114) * RFCs commented:
 * 115) * RFCs to discuss:
 * 116) * How I'll help: Fixing and/or breaking things.
 * 117) (you)
 * 118) * Role:
 * 119) * RFCs commented:
 * 120) * RFCs to discuss:
 * 121) * How I'll help:

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.