In the spirit of https://www.mediawiki.org/wiki/Everything_is_a_wiki_page
A page with a JSON backend using a storage structure similar to https://noc.wikimedia.org/conf/highlight.php?file=throttle.php would be a good first step. Once that's established, we could build a proper editing frontend.
This automatically adds API support, revision history, diffs, etc.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T202759 Ease the bottleneck in wiki account creation at in-person events | |||
| Open | None | T27000 Deploy ThrottleOverride extension to Wikimedia wikis | |||
| Open | None | T174895 Convert ThrottleOverride to use a wiki page for storage |
Is there some extension which might be used as a reference for storing data as json within a wiki page?
I'm personally only aware of extensions storing single strings per wiki page (like translations, a paragraph gets it's own page and each translation gets it's own page as well) but not of any storing structured data (e.g. json, yaml, whatever).
EventLogging is a good example, e.g. https://meta.wikimedia.org/wiki/Schema:MediaWikiPingback
Without any guarantees. I've just managed to get Special:OverrideThrottle to save to and read from Project:Throttle_overrides as a first step.
I propose declining this. I'm not a fan of store-the-config-in-random-NS_MEDIAWIKI-pages, and JsonConfig is no better.
Can we not look into using the core's Config interfaces instead?
https://doc.wikimedia.org/mediawiki-core/master/php/interfaceConfig.html ? From a quick glance, I don't see how to save anything into there, just how to read from it. How and where do you store the throttle data for in that approach?
I'd advocate for a special page for this better than a wiki page which it seems it is using already at https://www.mediawiki.org/wiki/Extension:ThrottleOverride#Usage right?