Refactor MediaWiki Core into well encapsulated components, removing global state and circular dependencies between classes
From atwg
| Description | Incrementallly refactor MediaWiki code into logical classes/components/libraries to isolate functions such as storage, parser, events and app logic. Prioritizing refactoring of code into components to allow: Easier testing (leading to faster development), more easily support both LAMP stack and WMF use cases that require scale and selective SOA, increased re-usability, enabling an API-first approach be de-coupeling the presentation layer. Removing global state also enabled full cross-wiki capability (e.g. loading and rendering content from multiple wikis in a single request). |
|---|---|
| Associated Outputs | [[Output:003|]] |
| Type | Development |
| Primary Team | MW |
| Collaborating Teams | WMDE, Parsing, ReadersWeb, Reading Infrastructure, TechCom |
| Start Year | 0 |
| End Year | |
| Duration (months) | |
| Depends On Tasks | E10,E11 |
| Risks | |
| Contingencies | |
| Benefits | |
| Assumptions | |
| Implications | |
| Notes | Primary candidates are those where LAMP stack needs are vastly different than WMF scaling needs such as: Storage and Event Propagation |
