Task Table

	Type	Associated Outputs	Primary Team	Collaborating Teams	Start Year	Duration	Depends On Tasks	Risks	Contingencies	Benefits	Assumptions	Implications	Notes
Make REST Routing possible in MediaWiki	Development		MediaWiki Platform		0	6							Routing for external services should be handled outside of MediaWiki (Varnish). The MW routing should be done using a service runner that can be run separately from MW for WMF use, but could be run in the same process for small installs. Where a service lives, node, MW, or elsewhere should be transparent to clients. We should then figure out any necessary routing, mapping, proxying, etc without the clients needing to worry about this. This means we have an agreed upon REST url pattern that spans all services and routers. For MW APIs, thsse should be routed from Varnish to MW via some sort of configuration.
Identify features that the REST API needs to support	Research		Audiences Product and Design		0
Design MediaWiki REST API			MediaWiki Platform		0	6							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
Develop MediaWiki REST API	Development		MediaWiki Platform
Research Desktop Workflows to port to Mobile and/or Responsive (ARCHIVED)	Research		Readers Web		0	6							CSA: Added "re-evaluate technology tradeoffs"; perhaps split into a separate first-year research goal?
Port Desktop Workflows to Mobile and/or Responsive (ARCHIVED)	Development		Readers Web		0	18
Research architecture requirements and needs, identify and resolve trade-offs	Research		MediaWiki Platform		0	3
Write Architecture Spec	Documentation		MediaWiki Platform		0
Refactor MediaWiki Core into well encapsulated components, removing global state and circular dependencies between classes	Development		MediaWiki Platform		0								Primary candidates are those where LAMP stack needs are vastly different than WMF scaling needs such as: Storage and Event Propagation
Prototype page assembly	Prototyping		Performance		0
Simplify the RESTBase stack	Development		Services		0	3
Create a multi-purpose key/value storage component			Services		1	3
Isolate session data by creating a specialised session service			Services		0	3
Refactor Parsoid to support porting	Development		Parsing		0	3				This step is useful for improved maintenance, readability of the Parsoid codebase independent of the port. It also reduces the time spent doing the actual port.			The code cleanup and refactoring doesn't need to depend on the architecture document.
Prototype and test PHP implementation of Parsoid	Development		Parsing		0	3
Standardize on a single parser	Development		Parsing		0	12
Research 3rd party installations, uses, and contributions (ARCHIVED)	Research		MediaWiki Platform		0	3							Virtualization/Containerization/Cloud/Shared/Bare metal?
Define the default MediaWiki installation (ARCHIVED)	Research		MediaWiki Platform		0	3							These goals need to better stress "increase commonality between WMF and 3rd party installs", rather than treating 3rd party installs as a separate configuration target
Improve installation of default MediaWiki for WMF development, testing and production environments as well as 3rd parties (ARCHIVED)	Development		RelEng			6							I don't think we have full consensus on single-process LAMP vs node js helpers etc.
Improve installation and deployments of the "WMF Technology stack" for WMF development testing and production environments (ARCHIVED)	Development		Ops		0
Develop page assembly capability	Development		Performance
Create a purpose built developer portal for documentation	Development		Documentation		0
Document MediaWiki PHP service interface on portal	Documentation		Documentation
Document MediaWiki REST API on portal	Documentation		Documentation
Document system architecture, lifecycles, etc. on developer portal	Documentation		Documentation		0
Develop, publish and implement Code Standards that align with our new priorities around APIs, encapsulation and global state	Documentation		Documentation		0	0