I guess someone importing it into git, and bringing it up to date would be a good start...

[Title does not describe a bug but a solution or feature / new functionality. Hence setting priority to enhancement.]

Not sure whether to mark this as blocking bug 26751 or not.

Since this exention I no more use Special:Recentchanges

I also pimped it a bit to display the current page view at the bottom.

This would also be a comfortable way to (additionally) browse a user's contributions.

Boldly removing from T28751 since this is very far away from being able to be considered for core integration. The task description currently currently juxtaposes two polar opposites:

It is no more maintained and should be added to core […]

Rough path before core integration can be considered:

• Extension in Gerrit.
• Extension compatible with latest MediaWiki and following latest code standards and design style guides.
• Extension actively maintained by two or more people.
• Extension desired by Wikimedia community and subsequently deployed on all WMF wikis without any exceptions or opt-outs.
• Extension desired so much that it is among the most preferred RC workflows.
• Extension bundled with MediaWiki tarball releases.

And after that, we'd have to look at technical requirements and trade-off/benefits to integrating in core. It seems at glance that this extension does not benefit being part of MediaWiki core.

The foundations and central interfaces relating to Recent Changes and patrolling (patrol flag, recent changes database and API, RCFeed, etc) are already in core. And this is an area where there are already, and likely will continue to exist, a diverse set of user interfaces and tools for the actual patrolling workflows. Keeping it in an extension means communities retain their choice and can uninstall/install something else.

I'll actually updated this task to instead be about bundling (otherwise I'd decline it). When we first started looking at "suggestions for integration" on mediawiki.org, we didn't distinguish much between "in core" and "bundled". I think continuing as bundling retains the spirit of the original intention.

This should be a subtask of T333405

Oh well, NOT setting a parent until at least basic steps in the checklist have been performed. I don't think anyone wants to take over maintainership of more stuff when already existing stuff lacks maintainers.