Output:1.4: Difference between revisions

From atwg
(Created page with "{{Output |Description=unified parser |Parent Outcome=Outcome:1 }}")
 
No edit summary
Line 1: Line 1:
{{Output
{{Output
|Description=unified parser
|Description=Unified Parser
|Parent Outcome=Outcome:1
|Parent Outcome=Outcome:1
}}
}}

Revision as of 19:27, 11 February 2018

Output Unified Parser
Parent Outcome Infrastructure for Wikimedia projects can be more easily scaled due to increased modularization, re-use, maintainability, and testability of the technology stack
Primary Team
Collaborating Teams
TaskDescriptionDepends On TasksTypeAssociated OutputsPrimary TeamCollaborating TeamsStart YearDurationRisksContingenciesBenefitsAssumptionsImplicationsNotes
Refactor Parsoid to support portingRefactor Parsoid to facilitate future port or integration effortsDevelopmentOutput 1.4Parsing03This 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 ParsoidPrototype portions of Parsoid in PHP or a PHP-extension supported language to inform parser unification effortRefactor Parsoid to support portingDevelopmentOutput 1.4ParsingMediaWiki Platform03
Standardize on a single parserUnify Parsers into one implementation, deprecating the existing PHP parser.Create a multi-purpose key/value storage componentPrototype and test PHP implementation of ParsoidWrite Architecture SpecDevelopmentOutput 1.4ParsingMediaWiki Platform012