Task | Description | Depends On Tasks | Type | Associated Outputs | Primary Team | Collaborating Teams | Start Year | Duration | Risks | Contingencies | Benefits | Assumptions | Implications | Notes |
---|
Refactor Parsoid to support porting | Refactor Parsoid to facilitate future port or integration efforts | | Development | Output 1.4 | Parsing | | 0 | 3 | | | This 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 Parsoid | Prototype portions of Parsoid in PHP or a PHP-extension supported language to inform parser unification effort | Refactor Parsoid to support porting | Development | Output 1.4 | Parsing | MediaWiki Platform | 0 | 3 | | | | | | |
Standardize on a single parser | Unify Parsers into one implementation, deprecating the existing PHP parser. | Create a multi-purpose key/value storage component, Prototype and test PHP implementation of Parsoid, Write Architecture Spec | Development | Output 1.4 | Parsing | MediaWiki Platform | 0 | 12 | | | | | | |