Wed, Jan 10
Sat, Jan 6
Oct 20 2017
Jun 11 2017
Isn't there already a task to rewrite CreateWiki's backend?
Jun 8 2017
Which wiki does configure work with? ShoutWiki Hub only? I'm surprised that it even works at all in its curernt state, given the fact that the documentation page says it's incompatible with MediaWiki 1.28
There's a reason a number of extensions in the repository are unused. For Configure it's a case of "works okay for one wiki, not 8800+."
I'd like to see Configure and FlaggedRevs in use
May 1 2017
Oops, moved upstream instead: https://phabricator.wikimedia.org/T164231
Mar 29 2017
Pretty much, yeah, although I'm not sure if the patch has been tested on wikis running both extensions. I think the reason I was keeping this open was due to my earlier comment about merging AutomaticBoardWelcome and HAWelcome, but we can create a separate task for that or something.
Mar 28 2017
Based on the fact that patch was filed... over half a year ago, we can safely assume it's been deployed. Can we close this as resolved?
Mar 14 2017
Feb 2 2017
Jan 12 2017
Dec 16 2016
Dec 8 2016
Dec 4 2016
Nov 19 2016
Nov 14 2016
Nov 13 2016
Now that Sports is a theme of Games, I've pushed that change live and undeployed Sports from Interface Messages Wiki, the only wiki where it was deployed on.
Nov 11 2016
Jul 30 2016
Jul 24 2016
Yes, it's FOSS, and yes, the usage of wfMsg might break it under MW 1.27, but that's the very least of this extension's problems. I mean, a literal s/wfMsg/wfMessage/g will work because of the existence of Message::__toString, so if someone really wants to run this under 1.27, it's not this issue really blocking that -- it's the fact that the extension's somewhat ShoutWiki-specific, requiring a core hack (for the CustomSpecialStatistics hook) and uses some other deprecated things, such as PHP i18n and setup files...not to mention the obvious lack of scalability (a known design issue at the time).
Jul 23 2016
We don't use this extension in production
This is correct, but that's also because we don't have that many overly technical wikis, and also because we've never advertised it. Granted, that hasn't stopped users in the past from requesting different kinds of unsupported extensions, but still.