Hi all - I've been reviewing a list of extensions with Reading Engineering and Reading Infrastructure leads - props to James Forrester for promoting this discussion. Here's a list of extensions we believe currently falls under Reading for triage (n.b., not all extensions will get active development support).
https://www.mediawiki.org/wiki/User:ABaso_(WMF)/Extension_Responsibility Presuming no major issues with this, I think we should move the page to mw:Reading/Extension_Responsibility. One important outstanding question: Is MultimediaViewer appropriate for Reading given its consumption-oriented nature? Or is this actually better suited to Editing (where there exists a team named Multimedia)? Some other notes: * For skins with low utilization, we in time probably should coordinate handover to interested community members (or discuss with community members practical approaches for EOL). * Regarding the Nostalgia skin, we believe it's only used on https://nostalgia.wikipedia.org/wiki/HomePage, so maintenance would be updating for breaking skin changes or security issues only. * JsonConfig, ZeroBanner, ZeroPortal - we'll need to examine this more closely. Yuri (who has deepest PHP knowledge on extensions) is now over in Discovery, Jeff (JS & Lua) is in Reading, and now I'm managing instead of writing lots of code. * Collection probably belongs in Services
_______________________________________________ Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l
