Plan:FY18-19/1: Difference between revisions
From platformevolution
No edit summary |
m (Text replacement - "|Description=" to "|Name=") |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{Outcome | {{Outcome | ||
| | |Name=Engineers have a clear understanding of our technology stack and the plan to better scale, maintain and test it | ||
|Targets={{Target | |Targets={{Target | ||
|Target Description=WMF Staff and volunteers can view and understand the current architecture, proposed architecture | |Target Description=WMF Staff and volunteers can view and understand the current architecture, proposed architecture, implementation plan as well as the parser unification plan | ||
|Measurement Method=Ensure the architecture and plan documents exists, are publicly accessible, and are announced on public communication channels | |Measurement Method=Ensure the architecture and plan documents exists, are publicly accessible, and are announced on public communication channels | ||
}}{{Target | |||
|Target Description=Engineers can confidently port specific individual components of Parsoid and verity its correctness and performance without requiring a full port to be ready | |||
|Measurement Method=Ensure that token transformers and DOM passes have unit tests and a unit testing framework with suitable mocks | |||
}} | }} | ||
|Plan=Plan:FY18-19 | |Plan=Plan:FY18-19 | ||
}} | }} | ||
Latest revision as of 23:23, 23 February 2018
| Outcome: | Engineers have a clear understanding of our technology stack and the plan to better scale, maintain and test it |
|---|
| Target Description | Measurement Method |
|---|---|
| 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 |
| 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 | Output | Primary Team | Collaborating Teams | Milestones |
|---|---|---|---|---|
| Outcome 1: Engineers have a clear understanding of our technology stack and the plan to better scale, maintain and test it | Output 1.1: Architecture Spec for the WMF technology stack | WMDE (Daniel) |
|
|
| Output 1.2: MediaWiki REST API Design | MediaWiki Platform |
|
||
| Output 1.3: Parser Unification Plan | Parsing |
|
