Plan:FY18-19/2

Outcome:

Target Description	Measurement Method
Engineers can use RESTBase storage without adopting RESTBase routing	Engineers develop a service that successfully stores objects in RESTBase storage but does not use the routing

Outcome	Output	Primary Team	Collaborating Teams	Milestones
Outcome 2: Engineers are able to access more functionality of the stack using well encapsulated components and well defined APIs	Output 2.1: MediaWiki REST API Infrastructure	MediaWiki Platform	Services Readers Web Reading Infrastructure Audiences Design Audiences Product	Milestone 2.1.1: Make REST Routing possible in MediaWiki Milestone 2.1.2: Begin development of one REST API
	Output 2.2: Modularized RESTBase	Services	MediaWiki Platform	Milestone 2.2.1: Refactor the RESTBase stack into logical components Milestone 2.2.2: Create a multi-purpose key/value storage component
	Output 2.3: Session Management system	Services		Milestone 2.3.1: Define an API that can serve use cases and be plugged into MediaWiki Milestone 2.3.2: Deploy the session service to production
	Output 2.4: Personalized and non-personalized content can be assembled into a page outside of the MediaWiki application	Performance	Traffic	Milestone 2.4.1: Prototype page assembly Milestone 2.4.2: Deliver page assembly capability
	Output 2.5: Initiation of Parser Unification	Parsing	MediaWiki Platform	Milestone 2.5.1: Begin development
	Output 2.6: TBD Refactoring Output (Scope pending architecture - potentially: Use Service Container throughout MediaWiki Core)	WMDE (Daniel)	TechCom WMDE MediaWiki Platform
	Output 2.7: Refactor presentation layer away from business logic code in MediaWiki	Readers Web	MediaWiki Platform Audiences Design Reading Infrastructure WMDE
	Output 2.8: Improved OOUI Library	Audiences Design	Readers Web	Milestone 2.8.1: Adopt OOUI on prominent special pages