A succinct problem statement to give context for why the review was initiated.
The HtmlFormatter library is bundled inside mediawiki core and supports functionality in MobileFrontend that allows the mobile site to make some mobile-critical transformations to the HTML code - namely the removal of content that is not mobile friendly (removal of DOM nodes), lazy loading images and moving the infobox below the first lead paragraph (DOM traversal/manipulation).
It also supports TextExtracts which also has a code steward review at T256505
During a recent bug report to the library, it was clear that nobody is maintaining the library. The library is pretty stable but it would benefit from some clear ownership.
Recent chats with @Esanders suggest there will be wider adoption of this library to support the talk page project.
Entry in Developers/Maintainers with:
Number, severity, and age of known and confirmed security issues
Was it a cause of production outages or incidents? List them.
No known but there are several timeout issues likely due to the poor performance of the library on complex HTML.
Does it have sufficient hardware resources for now and the near future (to take into account expected usage growth)?
Is it a frequent cause of monitoring alerts that need action, and are they addressed timely and appropriately?
Given its a library, we should monitor issues on logstash and address them as needed.
When it was first deployed to Wikimedia production
Usage statistics based on audience(s) served
It is used in every mobile page view.
Changes committed in last 1, 3, 6, and 12 months
Reliance on outdated platforms (e.g. operating systems)
Number of developers who committed code in the last 1, 3, 6, and 12 months
5 in the last 1 years
Number and age of open patches
Number and age of open bugs
Number of known dependencies?
Is there a replacement/alternative for the feature? Is there a plan for a replacement?
Submitter's recommendation (what do you propose be done?)
This feels like a good fit for the parsing team, especially if we switch to Remex. I suspect their knowledge and expertise would provide a better supported alternative for all teams.