[00:14:19] Even == is allowed within a heading, no needed. [00:14:20] https://www.mediawiki.org/w/index.php?title=Project:Sandbox&oldid=3875925 [00:14:23] I would not have guessed that [18:51:00] legoktm: would it make sense to e.g. index Wikia/app and Wikihow/src somehow in Codesearch? [18:51:27] Of the two,, Wikia is obviously simpler :) [18:52:02] the former is at least on a public source repo, although I dunno if it makes sense to index it because it's the ancient 1.19 fork and the newer 1.33 fork isn't yet public (or rather, the Wikia/mediawiki repo is but their branch appears not to be) [18:53:01] Hn.. true. I still think it would be useful though. We don't require there to be 0 results when changing stuff. [18:53:14] but it's still usefil to know whether something was even considered used on older versions [18:54:01] For example, I'm making two SpecialVersion methods that are public now private. [18:54:14] but if Wikia has a use for extending that, I could consider that now. [18:54:29] indeed; personally I'm of course more biased towards wikiHow since they're on a more recent MW version and update regularly and intentionally don't implement huge core changes; but neither party seems overly interested in collaborating with upstream, which is kinda a problem [18:54:59] Yeah, I'm working on closing that gap though (from multiple angles). This is one of them. [18:55:16] :D [18:55:23] Bu yeah, for wikihow it's harder given there's no public version control they own. [18:55:34] I think you have a mirror somewhere, right? Or is that also including other modifications [18:55:53] I saw one at some point on lego's git [18:56:07] daily import from their tarballs or something? [18:57:19] I'd say ask TK-999 but he's not here [18:59:48] I have like almost all publicly released wikiHow source dumps (save for a couple from the MW 1.6 era or so), so building some kind of history should be possible; I just...haven't gotten started with that project yet; one major challenge is that since 2014-10-30 (!) the source dumps haven't included the skins/ directory at all [21:34:19] ashley: That'd be super awesome. I was thinking of https://git.legoktm.com/ashley/ShoutHow/commits/master [21:34:33] which seems to have some sort of semi-automatic cadence but yeah, not a pure wikiHow import [21:35:55] It doesn't have to be functional, it would just be a reference repo matching exactly their tarballs. [21:36:22] I could help with a script if you like. We could run it from a cron on toolforge or something [21:36:46] I don't know if git gogs has support for per-repo push tokens, if not we could put it on github somewhere for now [21:44:13] yeah, that's my pet project which attempts to be functional and usable and whatnot ;) it's definitely not *the* official wH source; sure, any and all help would be much appreciated :) it's probably easy enough to deal with the pre-2014-10-30 stuff since it's just basically untarring the .tar.gz and whatnot, but afterwards...the skins/ stuff is problematic, for sure; I have some old skins/ folders but maybe not quite enough to build a complete [21:44:13] history [22:21:49] ashley: perhaps a simpler one with just untarred stuff would be useful as its own repo? the skin stuff would stop at the 2014 there (implicitly removed) [22:22:21] Looks like your repo isnt' currently in codesearch either [22:23:29] aye and aye [22:27:09] https://phabricator.wikimedia.org/T253597