Page MenuHomeMiraheze

Start planning for parsoid migration
Open, LowPublic

Description

With MediaWiki 1.41 (in about 7 months time), MediaWiki will offer parsoid for reading in some capacity.

This will be a huge migration.

SRE need to start coming up with a plan. A ParsoidMigration extension will exist with 1.41 for us to use.

It is highly likely that pages using DiscussionTools will be the earliest to move.

We'll also need to enable parsoid on all wikis. A PR has been opened at https://github.com/miraheze/mw-config/pull/5243

Known Issues

Related Objects

Event Timeline

RhinosF1 triaged this task as Low priority.

I'm going to do some research for you on what it will look like for non-wikimedia wikis.

RhinosF1 updated the task description. (Show Details)
RhinosF1 added a subscriber: Unknown Object (User).
Herald removed a subscriber: Unknown Object (User). · View Herald TranscriptJun 5 2023, 12:49

Can someone clarify what "completely broken" means? I'm experiencing no such issue running the master branch on 1.41-wmf-11?

Unknown Object (User) added a comment.Jun 5 2023, 15:44

Can someone clarify what "completely broken" means? I'm experiencing no such issue running the master branch on 1.41-wmf-11?

Parsoid will be enabled soon as the default parser and once that's done, PortableInfobox will completely break. It isn't enabled as the default parser for now on 1.41-alpha but will be done quite soon before 1.41 is released.

Can someone clarify what "completely broken" means? I'm experiencing no such issue running the master branch on 1.41-wmf-11?

You won't be running parsoid for read. It's not landed in master yet. If you follow the upstream tasks, they might have landed the query parameter. If not, they'll be a lot of gerrit patches about to be merged you can use.

RhinosF1 added a subscriber: Unknown Object (User).

I've spoken to the parsoid team to see what's likely to happen.

We probably will see parsoid for reads in some pages. This will likely be one's using discussion tools as a minimum which already heavily uses parsoid.

We'll also have the ParserMigration extension to deploy which will also users to see what changes will happen if they are any dirty diffs and rendering changes between the parsers.

It's not likely we'll be seeing parsoid everywhere in 1.41 so we do have some time. I've asked for an idea of what version we might see it land in.

Can someone clarify what "completely broken" means? I'm experiencing no such issue running the master branch on 1.41-wmf-11?

You won't be running parsoid for read. It's not landed in master yet. If you follow the upstream tasks, they might have landed the query parameter. If not, they'll be a lot of gerrit patches about to be merged you can use.

Cheers, I see it now.

Looks as though the problem with PI is that it's parsed into <p> tags instead of the expected output.

We're on MW 1.40 and our test wiki runs MW 1.41.

We're on MW 1.40 and our test wiki runs MW 1.41.

Can you install the parser migration extension?

With 1.41, users can see what's happening. Parsoid is opt in on a per user basis in 1.42.

Universal_Omega subscribed.

Upgrade will begin soon (tomorrow or next week) in phases.

We need to write some guides for user testing before 1.42

We need to write some guides for user testing before 1.42

Then this can be removed as a subtask for 1.41. It is not a blocker.