Basic Information Section

Brief description

• The ParserMigration extension helps previous rendering differences between the legacy PHP parser and the new Parsoid parser on production wikis. It was deployed in 2017 then undeployed in 2018 after that particular migration was complete. We have updated the extension and would like to redeploy it to production.

Do you have a project/product/program plan or documentation?

• Parsoid homepage: https://www.mediawiki.org/wiki/Parsoid
• Parser unification project: https://www.mediawiki.org/wiki/Parsoid/Parser_Unification
• Parser migration extension: https://www.mediawiki.org/wiki/Extension:ParserMigration
• Using the parser migration extension: https://www.mediawiki.org/wiki/Help:Extension:ParserMigration

Primary Contacts

• @cscott, @ssastry

What Security Team services do you anticipate needing?

Application Security Reviews (I think?)

What is the 'go live' date for deployment of this project

ASAP. Within 1 month, ideally.

Privacy Information Section

Will any sensitive data to be collected, stored or exposed?

No.

Technical Information Section

Do related discussions exist in Phab, on wiki, or in an RFC'?

T333179: (Re)deploy ParserMigration extension to production (and tasks which it is blocking, which we'll fill in on phab)

Technology Stack

• PHP

Security Readiness Review Section

• Below is only relevant if this Project has reached maturity and requires a Readiness review.
• You can fill this in later if you are still in the Preview or other early phases :)

• https://www.mediawiki.org/wiki/Security/SOP/Security_Readiness_Reviews

Code

• https://gerrit.wikimedia.org/r/q/project:mediawiki/extensions/ParserMigration
• Primary changes since last deploy are at https://gerrit.wikimedia.org/r/c/mediawiki/extensions/ParserMigration/+/904855 and https://gerrit.wikimedia.org/r/c/mediawiki/extensions/ParserMigration/+/905333

Originally deployed in https://gerrit.wikimedia.org/r/c/operations/mediawiki-config/+/344276 (April 3, 2017)
Undeployed starting with https://gerrit.wikimedia.org/r/c/operations/mediawiki-config/+/478726 (Dec 10, 2018) at which point commit b42af282e2491e867cfa0b3007c5b4bf7b7e3d69 of the ParserMigration extension was live.

So an incremental review would probably compare b42af282e2491e867cfa0b3007c5b4bf7b7e3d69 of ParserMigration to the current head of the main branch, which is e696126271ca7bcd2c199363483a9a1b88f6e826 -- with most of the intervening commits automated dependency or localisation updates. However, given that the code involved is fairly small and the original security review was done under different norms and processes, it may be easier just to undertake a de novo review.

Post-deployment

• Content-Transform-Team (already listed at https://www.mediawiki.org/wiki/Developers/Maintainers )

Working test environment

Described at https://www.mediawiki.org/wiki/Extension:ParserMigration#Installation and https://www.mediawiki.org/wiki/Help:Extension:ParserMigration:

• Start with a working installation of mediawiki-core
• Unpack the ParserMigration extension in $MW/extensions/ParserMigration
• Add wfLoadExtension( 'ParserMigration' ); to LocalSettings.php
• Enable parser migration tool in your preferences
• Use the 'edit with migration tool' link in the sidebar 'tools' menu on any article page.