[14:58:31] is wmf office @ SF open to personal visit by wikimedians? [15:27:36] liangent: yes [15:28:08] although https://meta.wikimedia.org/wiki/Wikimedia_offices doesn't say it clearly [15:28:50] most offices just ask you to call beforehand [15:29:49] Nemo_bis: ok thanks [15:31:34] liangent: the monthly report says who visited the WMF office [15:32:00] official meetings are another matter but I doubt they'd throw the door on your face [15:32:24] *slam [15:32:59] Nemo_bis: any link to the reports? [15:34:14] liangent: https://meta.wikimedia.org/wiki/Reports [15:34:33] e.g. https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Report,_February_2013#Visitors_and_Guests [15:35:01] any bankers but also some wikipedian :D [15:35:04] *many [15:36:58] so are all visitors (required to be) listed? [15:37:39] no idea [15:37:49] probably not the head of the CIA when he visits Sue [15:52:13] andre__: Well, I'm idling... [15:53:08] DanielFriesen, oh great. Hi! [15:54:06] We might come back to you for some questions, and you are very welcome to comment :) [16:32:21] Hello Bug Squad! [16:32:44] /topic update? [16:33:02] Hi everybody! Welcome to the MediaWiki page and skin rendering Bug triage here! Everybody is free to join and help cleaning up and retesting bug reports. See https://www.mediawiki.org/wiki/Bug_management/Triage/20130402 for more info. [16:33:11] Heh... I've never been tempted to use this one before... [16:33:15] "Hello World!" [16:33:34] hehe. welcome :) [16:33:43] tyvm [16:34:10] So the goal is to triage some bug reports together, be talkative and verbose in what we're doing, so it's transparent and people can learn from each other [16:34:37] Info is at https://www.mediawiki.org/wiki/Bug_management/Triage/20130402 and we document process in http://etherpad.wmflabs.org/pad/p/BugTriage [16:34:52] there's also a list of tickets to take a look at [16:35:03] The_Anonymouse, hi and welcome! :) [16:35:12] Hi! [16:35:24] The_Anonymouse, now if my memory was better I wouldn't have to ask: Have you triaged bug reports before? :) [16:35:28] I think I've seen your name [16:35:49] I don't think so [16:36:09] (and MatmaRex and DanielFriesen are here as developers and could help a bit if we have questions) [16:36:27] The_Anonymouse, heh, okay. Are you familiar a bit with Bugzilla? [16:36:33] yes [16:36:45] oh lovely. So I assume you have an account :) [16:36:51] yes, I do [16:37:40] so basically there's http://etherpad.wmflabs.org/pad/p/BugTriage [16:37:46] and that has a link to the open bug reports [16:38:18] wow, nice UI! [16:38:18] and everybody can pick her/his favorite ticket, take a look, try to understand and check it if all is fine. That's the triage part and that is explained in https://www.mediawiki.org/wiki/Bug_management/How_to_triage [16:38:50] so we check if the description and the steps to reproduce are good, and try to reproduce it, etc. [16:39:08] and if we're unsure with something, we ask here on IRC. [16:39:39] Hi dan-nl, are you here for the bugday that currently takes place in this channel? [16:39:59] hi andre__, late, but i'm here :) [16:40:10] hi MatmaRex! Yay! Nice to see you! [16:40:14] well, "see" :P [16:40:14] andre__: yes, was just looking at the list just to see what i might be able to take on [16:40:21] dan-nl, oh awesome! [16:42:33] dan-nl, if you have any questions please feel free to ask here, and feel free to add you results to http://etherpad.wmflabs.org/pad/p/BugTriage [16:42:49] and in general I encourage everybody to add yourself to the list at https://www.mediawiki.org/wiki/Bug_management/Triage/20130402#Attendees :) [16:43:06] andre__: sounds good ... looking at https://www.mediawiki.org/wiki/Bug_management/How_to_triage right now [16:43:18] dan-nl, I'd love to know if something is unclear or so [16:44:24] because there's always some improvements possible. [16:44:33] Hi tempodivalse! Nice to see you around! Bugday? :) [16:45:39] good afternoon/evening, andre__ ! [16:46:03] Just popping in to see what's going on in office hours today [16:46:03] tempodivalse, I think I know who you are, if we had email contact a few months ago? Or am I wrong? :) [16:46:17] andre__, we share a first name, but I don't believe we've met :) [16:46:42] ahh, okay. Sorry then, looks like I mix up IRC nicknames :) [16:46:56] Me too, no worries [16:47:35] * andre__ looks at https://bugzilla.wikimedia.org/show_bug.cgi?id=13627 [16:48:22] Hmm, this got updated just a few days ago, by a developer. So it's still valid and there is not much to do. It has the design and easy keywords. So I think I'll just set Version from "unspecified" to the latest "1.22-git" for cleanup reasons, but nothing else to do [16:53:41] I'm looking at https://bugzilla.wikimedia.org/show_bug.cgi?id=41887 now [16:54:17] I've long wondered why the MovePage window isn't single-line [16:54:26] since line breaks are impossible in logs [16:55:10] tempodivalse, yeah, it's weird. I was wondering a bit whether to change "Major" severity to "Normal" because it didn't feel like major loss of function (see http://www.mediawiki.org/wiki/Bugzilla/Fields#Severity ) [16:55:21] but Nemo made a good point that it makes the interface really confusing [16:55:30] also based on what you're used to from other similar interfaces [16:55:37] I don't think it's very serious; after all, it's been that way for as long as I can remember it [16:55:44] <^demon> I'm going to find bugs related to old skins and mark them wontfix. [16:56:05] but for the sake of consistency, it probably should be changed [16:56:06] ^demon, oh that sounds awesome, plus you have the knowledge for that :) [16:56:22] <^demon> Since we deleted the old skins, we're not going to fix them :) [16:56:40] https://bugzilla.wikimedia.org/show_bug.cgi?id=41887 really sounds like a dup of https://bugzilla.wikimedia.org/show_bug.cgi?id=41974 plus is code in LQT and not in MediaWiki core, so I am going to mark it as a duplicate [16:56:42] <^demon> Anything relating to those skins can be wontfixed on site if they're not relevant to other skins. [16:57:07] ^demon: ideally you'd add them to some tracking bug just in case some weirdo wants to restore them in an extension and move them in an ad hoc component? [16:57:54] <^demon> *snort* [16:58:27] maybe move them to a separate product (Deprecated Skins?) and then mark INVALID [16:58:49] ^demon: no, lemme, lemme! [16:58:56] there *is* a trackingbug ;) [16:59:31] When people fight who's going to do some clean up, I should not complain. ;) [16:59:39] :D [16:59:41] <^demon> I'd rather encourage people to write a modern skin rather than bring back this garbage :) [17:01:44] dammit, ^demon. [17:01:56] there's no conflict detection when doing mass bug actions. [17:02:05] and i just actioned on five bugs you just actioned on. [17:02:18] :D [17:02:20] https://bugzilla.wikimedia.org/show_bug.cgi?id=42081 and deps [17:02:37] <^demon> "I'm going to find bugs related to old skins and mark them wontfix." [17:02:43] <^demon> I clearly said that. [17:02:53] <^demon> And my messages were nice and individualized to each bug I closed. [17:03:10] i clearly said to let me do that ;) [17:03:30] sorry if I'm not understanding something basic, but how does one change the status of a bug report? [17:03:35] <^demon> Well I won't bother then. [17:03:46] i think there were only those five. [17:03:47] wat. [17:03:51] sigh [17:04:09] The_Anonymouse: Oh, I guess you don't have permissions in Bugzilla then. Could you paste your email address in a private message? [17:05:08] hm, demon left irc. i hope he was just kidding [17:06:01] The_Anonymouse, can you try again? You should now have some dropdowns for the Status and Resolution that you can change :) [17:06:39] Heh yeah, WordPress' newest default skin's simplicity makes me feel tempted to make a nice simple skin based on the white shadowed area on the BG and lots of padding. https://dantmantest.wordpress.com/ [17:06:41] Wow, I see lots of more drop-down options! [17:07:40] The_Anonymouse, heh, yeah [17:07:42] https://bugzilla.wikimedia.org/show_bug.cgi?id=42081 now tracks all five of the RESOLVED INVALID legacy skins issues. [17:08:20] nice [17:10:38] DanielFriesen: I use Simple skin. It's scheduled to be deleted. Pleaseohpleaseohplease? [17:10:59] Simple was going to be delete too? [17:11:18] One of the first round cuts, from what I saw. [17:12:30] Pft... that change looks messed up [17:12:40] it got rid of simple but not cologneblue [17:12:44] Please don't tell me simple will be removed ... [17:12:48] one of my favourites [17:12:58] * tempodivalse is the ultimate minimalist [17:13:09] andre__: is there an easy way of creating the buglist.cgi?1243,125,124 links? [17:13:15] andre__: I mean, from a page like https://bugzilla.wikimedia.org/buglist.cgi?f1=keywords&f2=keywords&keywords=platformeng&keywords_type=allwords&o1=changedto&o2=changedafter&query_format=advanced&resolution=---&v1=platformeng&v2=-28d&order=changeddate%20DESC%2Cbug_id&list_id=191142 [17:13:46] https://bugzilla.wikimedia.org/buglist.cgi?bug_id= [17:13:50] DanielFriesen: We're letting CB stay because it has an active maintainer who's fixing the issues with it. [17:13:54] greg-g, hmm, none that comes to my mind right now [17:14:18] DanielFriesen: If you desperately want to take on one of the skins and move it over to be a Monobook-based skin and maintain it, then we should talk. [17:14:19] greg-g: you can paste multiple bug numbers into the search box, if that's what you'relooking for [17:14:21] James_F: That can still be done in an extension [17:14:38] James_F: Simple wasn't a legacy skin [17:14:41] DanielFriesen: Also, yes, our skins system sucks and needs fixing. Knock yourself out. :-) [17:15:07] andre__: looks like changing the Product field in bugzilla doesn't update the Component dropdown. I was going to change https://bugzilla.wikimedia.org/show_bug.cgi?id=38334 to the LQT extension. [17:15:10] Last I checked simple had better support of all our features than colognblue does even after upgrades [17:15:11] James_F: easier to scratch and start over, if you're talking about the skin system. [17:15:22] Amgine: Exactly. [17:15:23] DanielFriesen: when did you check that? [17:15:25] And if you're talking about skin system improvements [17:15:35] MatmaRex: useful to know, but I was hoping to "convert" that page of bugs that is time-dependent (ie: it might change the next time I load it) to something permament to save.... automagically [17:15:50] https://www.mediawiki.org/wiki/User:Dantman/Skinning_system [17:15:51] andre__: thanks anyways! [17:16:10] greg-g: want a bookmarklet to do that? :) [17:16:51] MatmaRex: sure, I'll take it :) [17:17:11] give me two minutes [17:17:18] MatmaRex: thanks! :) [17:17:59] andre__: btw, I had to disable your greasemonkey bz scripts, with the number of bugzilla tabs open it was slowing down my browser too much. [17:18:04] ok, back on topic now.... [17:18:42] greg-g: to get a comma-separated list of bugs: javascript: alert( Array.prototype.slice.call( document.querySelectorAll('.bz_id_column a') ).map( function(e){ return e.firstChild.nodeValue } ).join(', ') ) [17:21:23] MatmaRex: nice, most of the way there! thank you [17:21:52] Yeah... simple is basically just MonoBook's template. It has complete support for all of our built in features. [17:22:05] hi Guest27683! [17:23:21] greg-g: and to paste them into the search box and search (giving you a nice permalink): [17:24:26] MatmaRex: nice, it works, not as clean as I hoped (the resulting search url) but it gets the job done [17:25:09] javascript: (function(){ var a = Array.prototype.slice.call( document.querySelectorAll('.bz_id_column a') ).map( function(e){ return e.firstChild.nodeValue } ).join(', '); document.getElementById('searchInput').value = a; document.getElementById('searchform').submit(); })() [17:25:19] hmmm, well [17:25:24] MatmaRex: Yeah... I guess I should actually write down an RFC with my standard for what a core skin should require. But by those CologneBlue still looks like it should be in an extensions instead of core. [17:25:37] greg-g: let me try something [17:25:53] waldir, no, Bugzilla is from ten years ago when it comes to AJAX-shiny automatically refreshing component lists [17:26:07] waldir, instead you'll get another dialog in between... [17:26:16] greg-g: URLs like https://bugzilla.wikimedia.org/buglist.cgi?quicksearch=45944,37880,20533,17693,37879,7736 also work [17:26:32] andre__: I wonder if there's a bug for that upstream. /me looks [17:26:55] waldir, I bet [17:27:01] greg-g: javascript: window.location.href = 'https://bugzilla.wikimedia.org/buglist.cgi?quicksearch=' + Array.prototype.slice.call( document.querySelectorAll('.bz_id_column a') ).map( function(e){ return e.firstChild.nodeValue } ).join(',') [17:27:14] greg-g: I never said I knew anything about writing performant code in JavaScript. :P But pity, I guess I should rewrite the GS scripts at one point, once I've grown up and have become a developer ;) [17:27:37] waldir, https://bugzilla.mozilla.org/show_bug.cgi?id=227611 [17:27:38] DanielFriesen: what exactly is CB missing? [17:27:39] andre__: :P [17:28:12] andre__: cool, thanks! [17:29:22] waldir, heh, sure [17:30:58] Hello Bug Squad! [17:31:19] I don't have much time now, but I did some homework yesterday night and I will try to find more time later this week [17:31:38] Focusing on semi-forgotten enhancement requests, as usual. [17:32:07] qgil was very active yesterday. Thanks for that :) [17:32:36] MatmaRex: It's not that things are missing. It's about how things that are part of core shouldn't break from the patterns built into the skin system (eg: navigation lists) and have their own done in a different way than the other skins. It doesn't disqualify the skin from being a fine skin. But doing things out of step should mean the fine skin should be an extension instead of inside the core software. [17:32:51] * andre__ sets the priority field for https://bugzilla.wikimedia.org/show_bug.cgi?id=46486 and adds the "accessibility" keyword, as this is an issue for people with disabilities [17:33:48] DanielFriesen: you mean the sidebar? i made is more standard and compatible with e.g. addPortletLink() or the hook for adding entriesto it thew E:Collation uses [17:34:02] adding entries to it that E:Collection uses* [17:34:47] MatmaRex: If it makes you feel better... By that standard... until content_navigation was built into SkinTemplate ;) I would have disqualified Vector as a core skin. [17:40:04] Compatibility with extensions adding things with standard hooks IS one of the requirements there. But complete customizability/(lack of hardcoding) is also important. [17:40:45] Enough theorizing, DanielFriesen. [17:45:54] what's that, who's volunteering to totally redo skins? :) [17:46:23] brion: nobody plans to redo anything, we're just trying to maintain the mess of bug reports here! ;) [17:46:29] :D [17:46:53] why is https://bugzilla.wikimedia.org/show_bug.cgi?id=45535 filed under skins? [17:47:10] dan-nl: any questions on the triage documentation, or do you need help to get started somehow? I'm curious :) [17:47:15] MatmaRex: The sidebar is fine (though I can't see where the personal, etc... are being added to the sidebar). It's that I still see hardcoded cologneblue specific navigation lists at the top and bottom. Doing things in unique way is fine, it can make great skins. But that should be done outside of core. [17:47:48] waldir: that component used to be called "Interface", which by itself has a lot of meanings [17:47:58] waldir, because the component was called "Interface" before [17:48:02] meh. MatmaRex was faster :D [17:48:02] andre__: have been looking at the full list of reports ... for now i need a bit of help on deciding what to look at ... took a look at https://bugzilla.wikimedia.org/show_bug.cgi?id=38213 and this looks like a mobile strategy approach question rather than a "single-take-care-of-everything-bug" ... so i'm not sure what to do with it [17:48:19] so I suppose that needs to be changed now. To what? [17:48:54] waldir, hmm, language links.... maybe Internationalization then? [17:48:59] waldir: Probably because that's directly the list we output into language_links and it's basically asking for a way for extensions to add links to that list in the skin. [17:50:08] dan-nl, hmm, let's see. so the "mobile" keyword is set already, that is good. [17:50:14] andre__: the docs are straight forward enough ... i think it's more about how do i decide what to look at ... the "full list of reports" is overwhelming so i just need a hint as to where to start ... high, normal, etc. i like the idea of enhancements so i started there ;) [17:51:32] dan-nl, I think I would ask if the bug report refers to the "standard" view (e.g. https://en.wikipedia.org ) on portable/mobile etc. devices (which I assume), or if the reporter refers to the mobile frontend (e.g. on https://en.m.wikipedia.org ), and *in case* that the reporter did not know about the mobile frontend, if s/he could give it a try [17:51:38] For some reason the preferences page tabs don't work anymore on my checkout of core [17:51:51] dan-nl, plus adding a link to http://www.mediawiki.org/wiki/Extension:MobileFrontend for more info [17:51:57] dan-nl, does that make sense to you? :) [17:52:16] Error: Unknown dependency: jquery.collapsibleTabs [17:52:40] [17:52:43] dan-nl, yeah, it's always a chicken and egg problem. Lots of choice and lots of bugs in open source projects, and I'm really really bad in telling people "Here. Start with this!" because I'm more like "Hey, do what you want and have fun" [17:53:08] too wiki, andre__ [17:53:20] andre__: the approach mentioned in that bug is imho not the right approach, but it brings up the strategy of the wiki - it's not responsive ... i see what you mean about pointing them in that direction .. will take a look ... one moment [17:53:45] dan-nl: Re "too much choice", we should probably prepare a list of bug reports for starters for the next bugtriage [17:53:58] ...which is in two weeks [17:54:05] Amgine: :) [17:54:41] andre__: that would be a good approach ... a short list just to get started and familiar with the process [17:55:43] dan-nl, yes, on the list for next time. I'm learning. :) [17:56:49] andre__: yes the m. site makes sense. the reporter of the bug will probably not like the answer though ... the site is not responsive, so the text stays "small", although the page contains a vieport meta statement [17:57:36] DanielFriesen: woot? collapsibleTabs is not in core [17:57:37] dan-nl, that sounds worth to add as a comment to the report, in my opinion [17:57:51] i'll will try that now [17:58:07] dan-nl, but in general, if you're not sure with a bug report and spend too much time thinking about it, it's always good to ask others (like here in this bugday), or to even leave it untouched in the end and leave it to those people that will have to take a look at it at some point. Like... me. :D [17:58:08] DanielFriesen: it's in Vector, https://gerrit.wikimedia.org/r/#/c/55524/ is aiming to move it to core [17:58:09] dan-nl, cool, thanks! [17:58:24] dan-nl, feel free to add it to the bottom of etherpad.wmflabs.org/pad/p/BugTriage after doing so [17:59:54] Ok... the Vector extension I had required was breaking it [18:00:02] wondering whether https://bugzilla.wikimedia.org/show_bug.cgi?id=46225 is in the right component. Feedback welcome before sending bugmail. [18:00:48] qgil, not the right component [18:00:52] James_F, in fact https://bugzilla.wikimedia.org/show_bug.cgi?id=46225 looks like a VisualEditor plugin candidate [18:00:59] Updating it works. [18:01:13] the component was called "Interface" before and I slowly understand the reasons why it was renamed to "Skin and page rendering" [18:01:17] I need to keep these extension repos up to date. [18:01:25] qgil: Possibly! [18:01:45] qgil, oh well, on the other hand it is about a graphical tool [18:01:48] James_F, should I move it to VE to see if it gathers more attention there? [18:01:59] qgil, see http://en.wikivoyage.org/wiki/Wikivoyage:Roadmap/Improved_editing_interface linked from there [18:01:59] James_F, I don't see any MediaWiki core development for this [18:02:17] Heh... Interface. I still need to talk to sumana about that section of the maintainers page. [18:02:28] andre__, this is exactly why I think it might belong to VE scope [18:02:31] qgil, "Page editing" ? [18:02:36] yeah. heh. :) [18:02:47] I'll move it at least. [18:02:53] andre__, but wait [18:03:01] okay. So you'll move it. :D [18:03:43] andre__, if moving to Page edting will bring nothing because no Wikivoyage specific development will be done... I'd rather give it a better chance as VE plugin [18:03:45] qgil: It won't get "more" attention, but if that's the right direction to go with given their timeframe, sure. [18:03:58] James_F, ok [18:04:21] Tch, I forgot the difference between mysql's binary and utf8 binary that Tim explained to me. [18:06:46] dan-nl, thanks for the comment on that report! [18:07:32] andre__: np, sorry i can't be of more help this time. need to get some other work done now ... good luck with the rest of the session [18:08:29] dan-nl, oh thanks a lot for joining, really! [18:08:34] dan-nl, see you around! [18:10:46] hi valeriej & welcome! [18:11:01] Hello! [18:11:22] The usual links: https://www.mediawiki.org/wiki/Bug_management/Triage/20130402 and http://etherpad.wmflabs.org/pad/p/BugTriage [18:12:02] * valeriej nods [18:12:11] Going through the bug list now. :) [18:12:42] The_Anonymouse: anything that I/we could help with (in case you're still looking at Bugzilla a bit)? Just curious :) [18:12:51] valeriej, there's enough bugs for everyone. But you know that very well. :D [18:13:27] I'm doing OK [18:13:42] thanks :) [18:14:09] Since this is my first time, I'm just trying to learn how this all works :) [18:16:08] The_Anonymouse, oh sure. Don't hesitate to ask here if something is unclear :) [18:16:17] * andre__ got to grab some dinner, will be back soon [18:16:23] OK, thanks! [18:20:16] qgil: BTW, have created bug 46803 as a tracker. [18:20:49] James_F, good, thanks! [18:24:49] * valeriej wants to test bug 23475. However the link to a screenshot doesn't work. Will ask for a retest. [18:29:20] Should I change bug 23475 to UNCONFIRMED as well? [18:34:22] qgil: I think 22463 was left open because we still have a separate hook and poweredbyico. We're not properly deprecating them mapping footericons stuff into them or killing the hook or killing them all like we should. [18:38:48] DanielFriesen, ok... difficult to guess all that by looking at the bug report. :) Feel free to reopen, although the functioality requested by the reporter seems to be fulfilled nowadays. [18:39:08] Sort of [18:39:23] It's fulfulled, but it doesn't work in skins that haven't updated. [18:40:02] * qgil welcomes feedback: does https://bugzilla.wikimedia.org/show_bug.cgi?id=41363 deserve to be listed at http://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Raw_projects ? [18:40:12] That said, I'm starting to be tempted to make it so that deliberately there are no icons displayed on old skins like that [18:40:26] DanielFriesen, you are the domain expert, I'm just a volunteer bug triager :) Do as you see fit. [18:40:54] DanielFriesen: you could also make it so that they work. [18:40:55] qgil: Only if it's done differently than https://www.mediawiki.org/wiki/Extension:CreateRedirect [18:41:00] DanielFriesen: also, old skins have just been removed. [18:41:04] so please be specific [18:41:10] because right now you're just being annoying. [18:41:13] end rant. [18:41:51] DanielFriesen, thanks for the link! This is enough progress for now ref redirects UI [18:41:58] MatmaRex: ;) I am specific... you're talking about what I call "Legacy" skins. "Old" skins are simply skins written before feature the current topic is on. Namely 3rd party skins. [18:43:18] ugh, all right. [19:12:04] valeriej, https://bugzilla.wikimedia.org/show_bug.cgi?id=25234 - where can I find that link? I fail to understand how to reproduce [19:13:17] andre__: https://www.mediawiki.org/wiki/User:Valeriej Check the left toolbar under 'Toolbox'. There should be a link to 'Email this user' [19:13:50] After you send a message using the form, it offers to return you to my user page. [19:14:04] ah, thanks a lot! [19:14:21] No problem! [19:16:24] Hello Bug Squad! [19:17:59] hah! hi Edokter! [19:18:06] and welcome! [19:18:12] thanks [19:18:48] Edokter, triaged bug reports before? :) [19:19:04] yes, twice before [19:19:17] just browsing the list now [19:19:26] oh awesome! so there's not much to explain to you, you know what you're doing. :) [19:19:39] Are there any left? [19:19:41] free choice, enough bugs for everybody [19:19:43] heh, oh yeah. [19:23:00] Edokter, but if I/we can help you somehow, please don't hesitate to ask here :) [19:23:54] Hey Edokter! [19:24:05] hi valeriej [19:24:15] hmm, does anybody have an old Internet Explorer 6/7 to test the testcases in https://bugzilla.wikimedia.org/show_bug.cgi?id=24515 ? [19:24:49] I have IE8 with compatibility mode [19:25:05] andre__: Why not bring up scout or browserstack? [19:25:14] andre__: i tested that recently ,see the latest comment [19:25:16] browserstack [19:25:17] +1 [19:26:13] I guess I shoould finally take a look at it, yeah [19:26:18] MatmaRex, oops, thanks [19:26:51] andre__: hm, well, maybe not that recently ;) [19:43:02] * andre__ tries to triage https://bugzilla.wikimedia.org/show_bug.cgi?id=12693 as part of the bugday [19:49:43] not much I can do here, added 2 comments. [19:51:07] have to go, until next time [19:51:33] Bye Edokter! [19:51:40] Oop, too late. [19:54:11] Oh, andre__, what do you think about changing bug 23475 to UNCONFIRMED? [19:54:11] hmm, still nice of Edokter! [20:05:13] I still cannot reproduce https://bugzilla.wikimedia.org/show_bug.cgi?id=42193 so I've pinged the reporter. Will close it in a few weeks without answer... [20:06:13] same for https://bugzilla.wikimedia.org/show_bug.cgi?id=33586 actually [20:12:46] Would https://bugzilla.wikimedia.org/show_bug.cgi?id=8171 be under History/Diffs instead of Skin and Page Rendering? [20:15:32] valeriej, yeah I agree, sounds like a better place for this. [20:16:02] andre__: Thanks, will move. [20:20:52] qgil: That bug is indeed about the Listings extension functionality that Wikivoyage has. And yes, it was filed against core, but wrongly. [20:21:39] James_F, ahm [20:23:13] Listings?: https://bugzilla.wikimedia.org/enter_bug.cgi?product=MediaWiki%20extensions&component=Listings [20:24:24] James_F, sorry, I had missed the fact that you had moved the report to that extension already [20:24:27] andre__, https://bugzilla.wikimedia.org/show_bug.cgi?id=46225 [20:24:37] qgil: No worries. :-) [20:24:45] andre__: Yeah, that's the extension. [20:25:13] Bah, James_F is faster than me. As usual. :P [20:25:19] * James_F grins. [20:28:57] * andre__ closes https://bugzilla.wikimedia.org/show_bug.cgi?id=11687 as worksforme - no answer from reporter to previous questions [20:30:53] Oh oh, our bugday here is slowly finishing. :) [20:31:27] Still a bug week to go, though. [20:31:47] Yes, definitely! [20:32:20] The triaging continues, and you can find the usual suspects (mostly me) on IRC if you have questions :) [20:32:30] So I'd like to thank everybody who joined, helped, commented, watched, or prepared some coffee for me today. See you around! [20:32:43] :-) [20:32:50] thanks andre__ valeriej & co [20:34:11] Oh, it's done? Thanks everyone! [20:34:57] valeriej: hehe, yeah! You're free! :D [20:35:15] * valeriej flies away :P [20:35:39] Hah, I'll triage some more reports throughout the week. :) [20:35:46] same plan here :)