Task:0003: Difference between revisions
From atwg
(CSV import) |
No edit summary |
||
| Line 3: | Line 3: | ||
|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 | ||
|Associated Outputs=Output:010 | |Associated Outputs=Output:010 | ||
|Primary Team=MW | |Primary Team=MW | ||
|Collaborating Teams=Services, | |Collaborating Teams=Services, Readers Infrastructure | ||
|Start Year=0 | |Start Year=0 | ||
|Duration=6 | |Duration=6 | ||
|Depends On Tasks=E5, E12 | |Depends On Tasks=E5,E12 | ||
|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 | ||
}} | }} | ||
Revision as of 10:01, 11 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 |
|---|---|
| Associated Outputs | [[Output:010|]] |
| Type | |
| Primary Team | MW |
| Collaborating Teams | Services, Readers Infrastructure |
| Start Year | 0 |
| End Year | |
| Duration (months) | 6 |
| Depends On Tasks | E5,E12 |
| 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 |
