Come up with a porting plan for the Listing extension
Closed, DeclinedPublic
Actions

Assigned To

None

Authored By

	cscott
	Nov 30 2023, 3:33 PM

Description

This task is for initial triage of the Listing extension as used on hewikivoyage, since that is one of our possible phase 1 targets:

First, we should examine how it is used on hewikivoyage (how many pages, etc) and the importance of a port -- also, given that this is a non-english wiki, is our port likely to have other i18n issues? If there are only a small # of pages, can we allow/block list them instead of porting?

Assuming we decide that we need to port this extension, we should determine a porting plan:

full port to use the Parsoid extension API, or
just use the existing core hooks in a more Parsoid-compatible manner (if possible)

Finally come up with a time estimate for this work and use this to determine whether we want to sink that time now, or else revisit the decision to target hewikivoyage in phase 1.

Related Objects
Search...

Status	Subtype	Assigned	Task
Open	Release	None	T84936 Release VisualEditor-MediaWiki as "1.0"
Open		None	T50429 [Epic] Support editing parts of a page in VisualEditor-MediaWiki
Open		None	T54365 Explore performance gains from progressive (JIT?) de-alienation in VisualEditor
Open		None	T174303 Copy-pasting linked ISBN numbers from view mode HTML into VisualEditor inserts wikitext links to Special:BookSources (it should turn them into magic links?)
Open	Feature	None	T54091 The read HTML should have hinting to allow full DOM copying (as opposed to just rich copying) from read mode into VE surfaces
Open		None	T55784 [EPIC] Use Parsoid HTML for all page views
Open		None	T258838 [EPIC] Ensure all extensions on the Wikimedia cluster that use Parser hooks or implement tag hooks are retargeted for Parsoid
Declined		None	T272937 Make Listings extension compatible with Parsoid
Declined		None	T352443 Come up with a porting plan for the Listing extension

Event Timeline

cscott created this task.Nov 30 2023, 3:33 PM

MSantos edited projects, added Parsoid (Tracking); removed Parsoid.Dec 7 2023, 3:22 PM

Restricted Application edited projects, added Parsoid; removed Parsoid (Tracking). · View Herald TranscriptDec 7 2023, 3:22 PM

MSantos edited projects, added Parsoid (Tracking); removed Parsoid.Dec 7 2023, 3:23 PM

I pushed a couple patches to gerrit to cleanup the Listing extensions code. See https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Listings/+/980959 and followup.

This should be fairly easy to port to use the ParsoidExtensionAPI after those patches are merged since it DRYs out some code.

That said, if we know for certain that listings don't use <ref> tags or links, etc. that might need Parsoid semantic markup, we can continue to proxy this to the legacy Parser. So, first order of business to determine this is to look at usage on wikivoyages and see what kind of wikitext is embedded inside listings.

Additionally, all wfMessage use in the listing extension are "inContentLanguage" so no i18n work is needed for it to work on non-english wikis. So, maybe it is simple to write a Parsoid compatible version rather than do any additional analysis or research.

@MSantos, looks like the listing extension is slated to be undeployed this year. So, I recommend declining this as well.

ssastry lowered the priority of this task from Unbreak Now! to Low.Jan 12 2024, 12:19 AM

It's even already undeployed, afaict: https://phabricator.wikimedia.org/T253216

ssastry closed this task as Declined.Jan 13 2024, 4:12 AM

Come up with a porting plan for the Listing extensionClosed, DeclinedPublicActions

Description

Related ObjectsSearch...

Event Timeline

Come up with a porting plan for the Listing extension
Closed, DeclinedPublic
Actions

Related Objects
Search...