T393500: Support page view graphs in Charts extension (Graphs parity request) is somewhat related (but not about the info action).

Should this be reopened, since (per T403753: Drop PageViewInfo's integration with the Graph extension on action=info, the extension is dead) action=info doesn't have page view graphs anymore? (Although it still has some pageview data.)

Since March 2024, I've been using the "Database report" template to automate the building of pages of in-project links for change patrol. So, I guess I no longer need this resolved as much as before. I still however think a system solution as indicated in the description is optimal.

My humble patrolRevisions.js script provides this button.

Not worth doing given the current status of Flow.

Boldly declining as all project tags are also archived.

Blocked on subtask T382995

Change #1107096 had a related patch set uploaded (by SD0001; author: SD0001):

[mediawiki/extensions/Gadgets@master] Add special page UI for configuring gadgets in JSON repo

https://gerrit.wikimedia.org/r/1107096

@Urbanecm_WMF hi! Do you think it would be useful to use CC for gadget managment? And is this possible? :)

I started implementing a UI for editing gadget definitions using HTMLForm. I considered Community Configuration as well but that doesn't seem to precisely fit the use case. Community Config would have been suitable if there were only one gadget to configure instead of several. But let me know if there are ways to work around that.

I wonder if we can actually start somewhere like with Fandom's Dev Wiki. Almost the entire contents of that wiki should be compatible with Wikimedia's content license. If we can build a template and module repository that Wikimedia (and other projects) can use, then we can open the door to global templates. It would allow for templates ported to be deletable unless if they are highly used on a project.

In T31398#9733653, @Krinkle wrote:

For those interested in implementing this, there is code for a Gadget Manager implementation already, and can be found in the RL2 branch of the mediawiki/extensions/Gadgets repo. This is from the 2011 prototype that @Catrope and myself worked on at the time.

It is however based on the deprecated jQuery UI. I suggest migrating it to HTMLForm instead.

In T125582#1993994, @TheDJ wrote:

Comments

• ...
• Gadgetmanager wise, I don't see many problems.
  • It's all jQuery UI, which we are trying to get rid off.. but it is fairly self contained, so I think that's ok for now, but is there a ticket for that ?

With MultiGadgetRepo, adoption will be gradual with users having full autonomy at the individual gadget level. This means adopting a JSON gadget is as easy as creating the appropiate page (JSON will have precedence over the entry from the legacy definition page). And switching back would involve deleting or moving said page, or changing its content model, so as to not be loaded.

For those interested in implementing this, there is code for a Gadget Manager implementation already, and can be found in the RL2 branch of the mediawiki/extensions/Gadgets repo. This is from the 2011 prototype that @Catrope and myself worked on at the time.

I just undid all reviews by WizardGamer775 (currently 747 edits and 3 months old) directly in the database due to a significant number of them being inaccurate (35%) and/or not having the proper actions taken (20%).

Change 981622 merged by jenkins-bot:

[mediawiki/extensions/Gadgets@master] Introduce MultiGadgetRepo to facilitate repo migration

https://gerrit.wikimedia.org/r/981622

Change 981622 had a related patch set uploaded (by Krinkle; author: SD0001):

[mediawiki/extensions/Gadgets@master] Introduce MultiGadgetRepo to facilitate repo migration

https://gerrit.wikimedia.org/r/981622

Done in the new CopyPatrol (hopefully to be released later this week). There's also "revdel" link for those with the requisite user rights.

We now query the database directly.

CopyPatrol has long had i18n support. This task is about the Copyvios tool.

Any recent progress on this? I recently came back from a hiatus, and I'm still having to manually regenerate a list of all a project's pages for project change patrol purposes. It would be nice to no longer have to do that.

If the community wants this and the WMF works out access to other provider APIs, then this could be reopened.