In T334940#9479502, @Bugreporter wrote:

In T334940#9474601, @Stux wrote:

In T334940#9474209, @MMiller_WMF wrote:

Right now, I'm gathering the small group of staff members who will think about the possible solutions. It would also really help me to have some synchronous conversations with people who know this space well and want to have a hand in planning. If you (or anyone else watching this task) would be interested in talking about this, please let me know at mmiller@wikimedia.org. Thank you!

If you're looking for long-term solutions, why not leverage and improve existing technologies to solve this? What I mean specifically is: why not bring Inline SVGs to reality (either directly embedded on a page or automatically converted to PNG and cached)? With this, we could use templates, Lua Modules and/or extensions to build graphs and not have to worry about 3rd party software issues.

-stux

Please discuss the idea at T334372: Add support for inline SVG.

Implementing this would provide a relatively simple solution for T334940.

In T334940#9474209, @MMiller_WMF wrote:

Right now, I'm gathering the small group of staff members who will think about the possible solutions. It would also really help me to have some synchronous conversations with people who know this space well and want to have a hand in planning. If you (or anyone else watching this task) would be interested in talking about this, please let me know at mmiller@wikimedia.org. Thank you!

Thank you very much for your update and statement regarding the future of the core legacy parser.

Any updates on this item? Not being able to use these parser functions on smaller wikis may end up forcing some of them to stay on older versions of Mediawiki (having to replace all content pages would likely not be feasible). This is quite problematic from a security standpoint.