Page MenuHomePhabricator

Review and update Huggle config for es.wikipedia
Closed, ResolvedPublic

Description

https://es.wikipedia.org/wiki/Wikipedia:Huggle/Config when compared to its enwiki counterpart looks like it could use some updating. If it indeed needs it, I can take care of requesting temporary unprotection so you can work on it.

Event Timeline

Petrb triaged this task as High priority.Jul 11 2017, 9:23 PM

Umph.. I don't really understand what you are asking @MarcoAurelio.
In the French community, our Huggle/Config page doesn't contain all new data and new functions. If a user wants to do the update and has time to do this, he can copy/paste its content from the English version.

Our config is outdated, included templates, which makes that, for example, the automatic warning system doesn't work (it does not identify if the user has been warned 1, 2, 3, x... times).

The config is outdated on almost every wiki except English one, we need to take a look in that, maybe even some kind of sanity test

Hmpf, so many cats here :)

Unrelated to this ticket but we also need to take a look to investigate why the warning levels on eswiki do not work correctly. I'll file a new task for that.

I guess that with the new YAML format we can start working on updating it based on the new config template.

You can but, be careful, huggle 3.3.0 will start using new YAML config page since moment you create it.

I was thinking on User:MarcoAurelio/Config.yaml and get back to you all before making it permanent :)

OK,

With latest nightly build you can use option --override-conf User:MarcoAurelio/Config.yaml to load that one instead of default.

Thank you @Petrb -- unfortunatelly I'm having personal/health issues at this moment. so this will have to wait, again. Sorry.

Petrb lowered the priority of this task from High to Low.Nov 20 2017, 8:53 PM

OK

If you wanted to do any of this, here is documentation for almost every key: https://www.mediawiki.org/wiki/Manual:Huggle/Deploying/DefaultConfig.yaml

I think I have some more time these days so I'll try to have a look at doing this, but no promises :-)

(thinking out loud: with MediaWiki supporting JSON content model pages, maybe we can think about migrating from yaml to json?)

or maybe not.

btw YAML is superset of JSON. So it really would be a huge step back.