Architecture Summit 2014/RFC clusters

The idea with this grouping is that we want it to be granular enough to consider batches of RFCs on this type of 90 minute agenda:
 * Lightning talk 1 - 5 min
 * Short Q&A 1 (clarifications only) 5 min
 * Lightning talk 2 - 5 min
 * Short Q&A 2 (clarifications only) 5 min
 * Lightning talk 3 - 5 min
 * Short Q&A 3 (clarifications only) 5 min
 * General discussion (60 minutes)

The idea is that a cluster contains RFCs that belong to each other. This means if we discuss RFC A and therefore RFC B needs to be discussed as well then those two RFCs should be in the same cluster. Clusters should also be small, probably not more than 3 or 4 RFCs per cluster.

Backend code modularity frameworks
Proposals that involve organizing our backend code to be more modular

Configuration
Proposals that involve moving away from global variables as the standard way of configuring core and extensions

Crosswiki
Topic cluster, not really for implementation most likely.

HTML templating
Proposals that involve adding an abstraction layer for server-side and/or client-side HTML skin/user interface generation

Installation

 * Requests for comment/Extension management with Composer
 * Requests for comment/Extension management with Composer
 * Requests for comment/Extension management with Composer
 * Requests for comment/Extension management with Composer

Metadata
Interacts with:.

Parsing architecture
Proposals that involve big changes to how we think about parsing and wikitext
 * Parsoid/Roadmap

Parser changes
Smaller changes to parsing

Wikidata
Interacts with:.