Plan:FY18-19/2: Difference between revisions

From platformevolution
No edit summary
No edit summary
Line 3: Line 3:
|Targets={{Target
|Targets={{Target
|Target Description=Engineers can implement a REST API in MediaWiki using our routing infrastructure
|Target Description=Engineers can implement a REST API in MediaWiki using our routing infrastructure
|Measurement Method=Engineers develop at least one REST service in MediaWIki
|Measurement Method=Engineers develop or convert at least one service to REST in MediaWiki
}}
}}
|Plan=Plan:FY18-19
|Plan=Plan:FY18-19
}}
}}

Revision as of 13:16, 23 February 2018

Outcome:
Target Description Measurement Method
Engineers can implement a REST API in MediaWiki using our routing infrastructure Engineers develop or convert at least one service to REST in MediaWiki
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
Output 2.2: Modularized RESTBase Services
  • MediaWiki Platform
Output 2.3: Session Management system Services
Output 2.4: Personalized and non-personalized content can be assembled into a page outside of the MediaWiki application Performance
  • Traffic
Output 2.5: Initiation of Parser Unification Parsing
  • MediaWiki Platform
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