| Outcome
|
Target Description
|
Measurement Method
|
| Outcome 1: Engineers have a clear understanding of our technology stack and the plan to better scale, maintain and test it
|
Engineers can confidently port specific individual components of Parsoid and verity its correctness and performance without requiring a full port to be ready
|
Ensure that token transformers and DOM passes have unit tests and a unit testing framework with suitable mocks
|
| Outcome 1: Engineers have a clear understanding of our technology stack and the plan to better scale, maintain and test it
|
WMF Staff and volunteers can view and understand the current architecture, proposed architecture, implementation plan as well as the parser unification plan
|
Ensure the architecture and plan documents exists, are publicly accessible, and are announced on public communication channels
|
| Outcome 2: Engineers are able to access more functionality of the stack using well encapsulated components and well defined APIs
|
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 3: Engineers better understand our current architecture and coding standards and where to find them
|
Engineers can view the WMF production architecture, the exposed APIs and the coding standards in a centralized documentation portal
|
Ensure this portal exists, is accessible by engineers inside and outside the organization, and is announced on public communication channels
|
