[12:57:29] James_F: o/ [12:58:26] Hey. [13:00:16] James_F: So, process Q. I'm thinking I should start socializing the extension while I'm finishing up the minimal features and an initial unit test suite so that when it hits beta there's people waiting to test. [13:00:25] James_F: Makes sense to you? [13:01:08] Coren: Hmm. With whom? [13:01:11] It's hardly general interest, but there are a pile of template writers that are likely to be extra interested. [13:01:18] Well. [13:01:24] Prolly enwp VPT at first. [13:01:41] Maybe. [13:01:50] I worry about spooking the horses too early, as it were. [13:02:31] Historically, horses tended to get spooked worse when presented with a fait accompli ready to deploy than early in the deployment cycle. :-) [13:02:44] Well, sure. [13:02:54] But the point of "will we do this" is already in the past, right? [13:03:22] I think the point of "will we" is far in the past, but the "how" is very much still in flux. [13:03:45] Any fundamental issues with the approach are best found now than later, I think. [13:03:50] Hmm. [13:04:10] The majority of even expert template authors won't be able to give advice on that, though, will they? [13:05:05] James_F: On the implementation, probably not. On the end result, almost certainly. To be honest, I'm not worried that this will be preceived as a universally positive thing if explained right. [13:05:44] What kinds of change are you thinking they might suggest? [13:07:25] Well, if I knew for sure then I'd make those changes first! :-) But my expectation is that they collectively have a very good idea of what the uses cases are, and where the biggest gains are likely and might raise a number of senarios where either an extra feature will make adoption a bigger win or tweaks in the behaviour that better match. [13:07:50] And they may well think of issues we haven't considered yet in odd edge cases. [13:08:01] * James_F nods. [13:08:11] Well, you have my blessing. :-) [13:15:23] Coren: I would wait until the extension is actually on Beta Labs, but yeah. [13:15:57] Leah: Ima spin up a mw instance with the extension as a playground. For me too. :-) [13:16:09] Neat. [13:16:26] Looks my test wiki is doing great: http://m4m.wmflabs.org/ [13:35:42] A user has asked me on Danish Wiktionary why he could not login this morning. Do you know why? You can see the message in the bottom of https://da.wiktionary.org/wiki/Brugerdiskussion:Sarrus (from 109.131.120.210) [13:38:37] Sarrus: they should file a bug in phabricator [13:38:47] there is a bug with their account https://www.mediawiki.org/w/index.php?title=Special%3ACentralAuth&target=Olelog [13:39:51] Hmmm [13:41:39] I don't know how that works, so I cannot explain them how they do that [13:42:14] actually, I will log it [13:42:29] good chance they can't log in at the moment [13:43:34] Will he be able to login again? [13:47:36] Sarrus: once the bug is fixed [13:47:40] Sarrus: https://phabricator.wikimedia.org/T132448 [13:48:40] Okay, I can tell him that link [13:51:06] Sarrus: You can even subscribe to the task for email updates on it (You can log in with your wiki account or Wikitech account) [13:51:22] I leave now but I still log the channel [14:08:13] Bleh. I don't *mind* most of the mw coding cenventions even though I use others normally - all but one. [15:22:57] * Coren attemps to please Jenkins and fails. [15:23:32] Coren: Run locally before pushing. :-) [15:31:10] * Coren goes for lunch and will return. [15:41:57] Oh, *there*'s what went wrong. Someone else merged a change in which I had not noticed. [16:29:07] * Coren reads up on ConfigFactory [16:30:11] bd808: I'm working on the tests right now; I wanted to get the parser in a stable enough state that I could actually match the output of a render() against expectations. [17:01:15] If anyone is interested, I'm playing with ideas about writing proper tests for Lua modules [17:01:35] There is a proposal at https://meta.wikimedia.org/wiki/Grants:IEG/Lua_libs_for_behavior-driven_development [17:01:54] * jeblad is fishing for endorsements [20:15:52] is the top icon on https://en.wikipedia.org/wiki/File:INTERIEUR,_OVERZICHT_-_Amsterdam_-_20295007_-_RCE.jpg a local enwp enhancement? [20:16:20] I don't see it on https://nl.wikipedia.org/wiki/Bestand:INTERIEUR,_OVERZICHT_-_Amsterdam_-_20295007_-_RCE.jpg for example [20:18:29] legoktm: which icon? the commons logo? [20:18:39] yes, in the top right [20:18:51] i see it on both links [20:18:57] just a bit smaller [20:19:34] does the Brussels banner mess with it somehow? [20:19:40] it's more to the right [20:20:08] hmm, I don't see it on nl.wp while logged in, but I see it logged out [20:20:09] weird [20:20:48] i was logged in [20:21:12] yea, so i think it's that banner [20:21:25] that icon jumps to the far right when the banner is finished loading [20:21:32] but i still see it , logged in or not [20:23:12] the placement is certainly messed up on nlwiki [20:24:18] on enwiki it's wrapped into the .mw-indicators div [20:45:31] i.e. https://www.mediawiki.org/wiki/Help:Page_status_indicators [20:46:39] I don't see it whilst logged in at nl, either. [20:50:03] ditto at frwiki (seen logged-out, not seen logged-in). https://fr.wikipedia.org/wiki/Fichier:INTERIEUR,_OVERZICHT_-_Amsterdam_-_20295007_-_RCE.jpg [20:50:25] but I do see a smaller version (both logged-in and logged-out) at Dewiki https://de.wikipedia.org/wiki/Datei:INTERIEUR,_OVERZICHT_-_Amsterdam_-_20295007_-_RCE.jpg