Task:0009: Difference between revisions
From atwg
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
|Name=Refactor MediaWiki Core into well encapsulated components, removing global state and circular dependencies between classes | |Name=Refactor MediaWiki Core into well encapsulated components, removing global state and circular dependencies between classes | ||
|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). | |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: | |Associated Outputs=Output:1.2 | ||
|Type=Development | |Type=Development | ||
|Primary Team=MediaWiki Platform | |Primary Team=MediaWiki Platform | ||
| Line 9: | Line 9: | ||
|Depends On Tasks=Task:0008 | |Depends On Tasks=Task:0008 | ||
|Notes=Primary candidates are those where LAMP stack needs are vastly different than WMF scaling needs such as: Storage and Event Propagation | |Notes=Primary candidates are those where LAMP stack needs are vastly different than WMF scaling needs such as: Storage and Event Propagation | ||
|Archived=No | |||
}} | }} | ||
Latest revision as of 08:46, 20 February 2018
| 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:1.2|]] |
| Type | Development |
| Primary Team | MediaWiki Platform |
| Collaborating Teams | WMDE, Parsing, Readers Web, Reading Infrastructure, TechCom |
| Start Year | 0 |
| End Year | |
| Duration (months) | |
| Depends On Tasks | Write Architecture Spec |
| 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 |
