Task:0003: Difference between revisions
From atwg
No edit summary |
No edit summary |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{Task | {{Task | ||
|Name= | |Name=Design MediaWiki REST API | ||
|Description=Design and prototype a REST API that would enable the full functionality of the desktop web experience in MediaWiki Core (and "critical" extensions?) with cacheability and consistent parameters, property names and objects | |Description=Design and prototype a REST API that would enable the full functionality of the desktop web experience in MediaWiki Core (and "critical" extensions?) with cacheability and consistent parameters, property names and objects. Note that this highly depends on the overall design of information flow (see [[Output:1.1]]) | ||
|Associated Outputs=Output: | |Associated Outputs=Output:2.1 | ||
|Primary Team= | |Primary Team=MediaWiki Platform | ||
|Collaborating Teams=Services, Reading Infrastructure | |Collaborating Teams=Services, Reading Infrastructure | ||
|Start Year=0 | |Start Year=0 | ||
|Duration=6 | |Duration=6 | ||
|Depends On Tasks= | |Depends On Tasks=Task:0002; Task:0009 | ||
|Notes=Should be designed by a group consisting of members from the MW Platform team, Services, Readers and Contributors. This ensures that those who know the MW platform best, those who have experience designing REST services, and those who implement the clients all agree on the design | |Notes=Should be designed by a group consisting of members from the MW Platform team, Services, Readers and Contributors. This ensures that those who know the MW platform best, those who have experience designing REST services, and those who implement the clients all agree on the design | ||
|Archived=No | |||
}} | }} | ||
Latest revision as of 11:37, 21 February 2018
| Description | Design and prototype a REST API that would enable the full functionality of the desktop web experience in MediaWiki Core (and "critical" extensions?) with cacheability and consistent parameters, property names and objects. Note that this highly depends on the overall design of information flow (see Output 1.1) |
|---|---|
| Associated Outputs | [[Output:2.1|]] |
| Type | |
| Primary Team | MediaWiki Platform |
| Collaborating Teams | Services, Reading Infrastructure |
| Start Year | 0 |
| End Year | |
| Duration (months) | 6 |
| Depends On Tasks | Identify features that the REST API needs to support,Refactor MediaWiki Core into well encapsulated components, removing global state and circular dependencies between classes |
| Risks | |
| Contingencies | |
| Benefits | |
| Assumptions | |
| Implications | |
| Notes | Should be designed by a group consisting of members from the MW Platform team, Services, Readers and Contributors. This ensures that those who know the MW platform best, those who have experience designing REST services, and those who implement the clients all agree on the design |
