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:
- 5 minutes – lightning talk 1
- 5 minutes – short Q&A 1 (clarifications only)
- 5 minutes – lightning talk 2
- 5 minutes – short Q&A 2 (clarifications only)
- 5 minutes – lightning talk 3
- 5 minutes – short Q&A 3 (clarifications only)
- 60 minutes – general discussion
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 internals edit
This category is for clusters that are completely about the server code.
Configuration edit
Proposals that involve moving away from global variables as the standard way of configuring core and extensions
Debugging edit
Storage services edit
Linking edit
Media backend edit
Parsing architecture edit
Proposals that involve big changes to how we think about parsing and wikitext
Parser changes edit
Smaller changes to parsing
Performance edit
Refactoring edit
SQL abstraction edit
APIs/Interfaces/Protocols edit
This overall category is for concerns that cut across front-end and backend, and how they interact with each other. This area typically haves an Ops heavy component, because things in this area muck with things like caching infrastructure and load balancers.
CentralNotice edit
HTML templating edit
Proposals that involve adding an abstraction layer for server-side and/or client-side HTML skin/user interface generation
- MVC framework (talk)
- OutputPage refactor (talk)
- HTML templating library (talk)
- Template engine (talk)
- Parsoid roadmap: DOM templating
Metadata edit
Interacts with: #Wikidata.
Mobile edit
Parsed output access edit
Service-oriented architecture edit
Thumbnail handling edit
URLs edit
- URL shortener service for Wikimedia (talk)
- URL shortener (talk)
- Clean up URLs (talk)
- Drop actions in favour of page views and special pages (talk)
Wikidata edit
Interacts with: #Metadata.
Frontend edit
Multimedia frontend edit
UI/UX: styling edit
Software management edit
This is for proposals that involve code for managing MediaWiki
Backend code modularity frameworks edit
Proposals that involve organizing our backend code to be more modular
- MediaWiki libraries (talk)
- Third-party components (talk)
- Extension release management (talk)
- Distribution and deployment (talk)
Installation edit
- Opt-in site registration during installation (talk)
- Extension manager (talk)
- Extension management with Composer (talk)
- Extension release management (talk)
MediaWiki management edit
- Overthrow Bugzilla (talk)
- MediaWiki Foundation (talk)
- Bugzilla taxonomy (talk)
- MediaWiki.org Main Page tweaks (talk)
Release process edit
Software for/from third parties edit
Functionality edit
These have end-to-end implications, but are typically more about functionality than architecture.
Crosswiki edit
Topic cluster, not really for implementation most likely.
- Regex-based blacklist (talk)
- Global scripts (talk)
Structured data push notification support for recent changes (talk)- Publishing the RecentChanges feed (talk)
General MediaWiki functionality edit
- Removing hit counters from MediaWiki core (talk)
- Update our code to use RDFa 1.1 instead of RDFa 1.0 (talk)
- Retained account data self-discovery (talk)
- Nonlinear versioning (talk)
- Localisation format (talk)
- Disable raw HTML on wikimediafoundation.org (talk)
- Scoped language converter (talk) (possible ideas beyond the Parsoid plans in bug 41716)