[00:00:01] actually there was another related one too [00:00:41] nice job tackling that one. it was getting super annoying to see [00:01:06] 36528 [00:01:19] jdlrobson: i'm going to have to step up my game of giving you tough bugz :D [00:01:40] i'm starting to run out https://bugzilla.wikimedia.org/buglist.cgi?query_format=advanced&field0-0-0=bug_severity&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&type0-0-0=notequals&value0-0-0=enhancement&component=MobileFrontend&resolution=---&resolution=LATER&resolution=DUPLICATE&product=MediaWiki%20extensions&list_id=116003 ;-) [00:01:45] i think that's the shortest i've seen it so far [00:01:58] and a lot of those are unconfirmed [00:02:15] anyone able to test the following: [00:02:16] https://bugzilla.wikimedia.org/show_bug.cgi?id=36530 [00:02:22] https://bugzilla.wikimedia.org/show_bug.cgi?id=36455 [00:02:35] i can take a look at 36530 [00:02:45] https://bugzilla.wikimedia.org/show_bug.cgi?id=36383 [00:02:47] should all be fixed [00:03:10] (apart from maybe the last as I couldn't replicatE) [00:04:26] i'm heading to bed now as I need sleep [00:04:40] i can't test the others, but 36530 is indeed fixed [00:04:41] will continue to kill that list tomorrow [00:04:45] \o/ [00:04:51] jdlrobson: excellent work. sleep well [00:05:14] awjr: think of what we could get done if we could clone jdlrobson [00:05:56] tfinc perhaps i can work on my new cloning technology during my 20% time [00:06:21] i would welcome that [00:06:31] more clones mean more volunteer support [00:06:54] yeah, we shouldn't have any problems convincing sumana [00:07:59] awjr: send a tweet that we've resolved a lot of the android issues our users were seeing [00:08:49] tfinc where can i find the login info again? i was looking on office wiki earlier to respond to someone but my search foo was failing me [00:09:33] i'll pm it to you [00:09:37] ty [00:15:42] awjr: i keep it simple by just runnign tweetdeck. that way i input the pass once and never again [00:16:01] oo fancy [00:16:52] if your wondering how i seem to know whenever anyone speaks our name on twitter it because of i *always* have tweetdeck on [00:17:14] tfinc do you use the chrome app or desktop? [00:18:29] desktop [00:18:37] v0.38.2 [00:18:42] not the new shitty one [00:18:48] lol [00:18:49] k [00:19:03] nice .. alolita already retweeted us [00:19:40] its funny. i look at the mobile site so much that i've forgotten what the desktop version looks like [00:20:30] I think thats for the best [00:23:11] awjr: this deployment brought a lot of fixes that i had been waiting for [00:23:16] the site looks much better [00:23:24] yeah, it feels a lot more polished [00:24:05] awjr: which is perfect as we can now put it down and move full speed with nav, wlm, and core migration [00:25:32] awjr: hows the sibling project move going ? [00:25:40] we need to catch up on that [00:25:43] yeah [00:25:56] there has been little movement since i got the response from asher last week [00:26:16] i'm betting you'll need patrick/tim help with the c work [00:26:24] likely [00:26:40] i can take a stab at it but i dont really know c [00:26:52] preilly: do the c ^^ [00:26:58] do it [00:27:02] DOIT [00:27:07] awjr: no, lets let preilly or tim do it ;) [00:27:20] im sure i can make the c code more awesomer [00:27:24] or whatever [00:27:26] lolz [00:27:26] anyway [00:27:43] we need to figure out what to do about proejcts that dont have language subdomains [00:28:10] like wikimedia.org and mediawiki.org [00:28:17] as well as decide how to handle things like… commons [00:28:26] hmm [00:28:37] i imagine commons will not work nicely out-of-the-box with MobileFrontend [00:28:59] the first two can just be m. [00:28:59] can we just do m.wikimedia.org / m.mediawiki.org ? [00:29:13] but switching all of the other projects with language subs shouldn't be a big deal [00:29:21] commons is the absurd looking one [00:29:37] binasher that might require some code changes [00:29:58] also wikimedia.org already has a bunch of subs, like commons for instance [00:29:59] awjr: besides commons what else is an edge case? [00:30:19] probably any of the wikimedia subs like meta, collab [00:30:34] binasher: this would all be easy if you guys let us drop m. from the domain [00:30:35] incubator [00:31:11] office [00:31:20] those are the on wikimedia.org subs i know of but there might be more [00:31:44] there's also wikitech [00:31:50] and then just mediawiki.org [00:32:00] m.mediawiki.org would probably work fine [00:32:31] and we could probably do something like commons.m.wikimedia.org, meta.m.wikimedia.org, etc with no code changes [00:33:29] tfinc the other thing that binasher suggested in the email was coping with what happens when a user goes to just 'en.wikipedia.org' - the redirection to the main page happens at the proxy layer [00:33:44] he was suggesting that we try to fix the behavior in mediawiki [00:34:14] i think it was because the different projects have different main pages, which makes configuration for all the different cases a nightmare [00:35:26] actually i don't think that's quite right [00:35:34] binasher can you explain the issue with the / redirection? [00:36:06] if you hit / [00:36:29] mediawiki will redirect you to the mainpage, but not the mobile url for it [00:36:57] ah yeah fixing that on the MW side will require some things to be migrated to core [00:38:09] what im working on now is making MW core context aware, so that could go hand-in-hand nicely with getting the automatic redirection done for the sibbling projects [00:38:56] http://imgur.com/pOXX1 [00:46:18] it looks like doing just m.mediawiki.org would require a varnish config change [00:46:47] the matching regex is currently: if ( req.http.host ~ "^([a-zA-Z0-9-]+)\.m\.([a-zA-Z0-9-]+)\.org" ) { [00:48:52] awjr: do you have a full list of projects that we need to move over? [00:49:03] i'd love to take a look at the exhaustive list and see which ones are easy, hard, etc [00:49:09] and plan out the names [00:49:23] if not i'll spin up a quick spread sheet [00:49:42] tfinc: i dont have an exhaustive list but i've got one somewhere hang on a sec [00:50:31] tfinc: email subject "Switching all projects to use .m. domains" sent may 1 hast a list of the projects i was able to figure out [00:50:53] with their individual caveats [00:52:44] it would probably be good to get someone else's eyes on that list, but those were the projects i was able to glean form various configuration files, etc. i wasn't really able to find a centralized cohesive list of projects [00:54:41] awjr: i took those and threw them into a spreadsheet ... your shared on it [00:54:57] cool [00:55:25] awjr: i thought you had sent that out but i onlve looked at your last email thread [00:58:32] awjr: so really we have three types of sites [00:58:58] lang.m, wikimedia.org, seperate domain [00:59:02] 1) projects with language subdomains 2) projects that are subdomains of mediawiki.org 3) stand-alone [00:59:03] yeah [00:59:19] sorry #2 should be subs of wikimedia.org [00:59:31] and really only #2 is annoying [00:59:51] but its an important one as commons is a really good candidate for our next mobile specific focus [00:59:58] well, #2 and #3 are both annoying but for different reasons [01:00:21] holy crap tweetdeck is taking over my screens [01:01:00] awjr: haha [01:01:00] tfinc i think we should probably start with #1 since it's relatively low hanging fruit [01:01:08] agreed [01:01:38] #2 is going to be problematic from a layout perspective as well as logistics with the subdomains (although i dont think this is that big of a deal as varnish is already configured to handle things like commons.m.wikimedia.org) [01:02:25] tfinc we should probably spend some time looking at the mobile version of the sibbling projects in the #1 category and make sure things are formatted OK [01:02:28] before ew make the switch automattic [01:02:49] awjr: i bet you they wont be. the'll be things that are broken [01:02:56] no question about it [01:02:59] yeah that's what im worried about [01:03:14] we'll want to get that ironed out before making the redirect automattic [01:03:15] but the only way that were going to raise awareness is to get people to use it [01:03:24] that is true [01:03:33] MF is already enabled on those projects and they already have .m domains [01:03:37] we wont be able to iron out everything. a quick pass at best [01:03:48] so lets say a two weeks heads up [01:03:54] for the project after we take a pass through it [01:03:57] and then we switch [01:03:58] can we reach out to those communities and get people to start using them manually so we get some feedback as we're working on the other moving bits? [01:04:05] yeah [01:04:09] awjr: sure, philinje can help you with that [01:04:30] awjr: my proposed m. are in the spreadsheet now [01:05:00] awjr: i've also included other projects that we need to consider [01:05:07] like wikimania [01:05:12] just added wikitech as well [01:05:22] exatly [01:05:24] exactly [01:05:36] yeah, those look right and good to me [01:05:50] awjr: this is yoru best list http://en.wikipedia.org/wiki/Special:SiteMatrix [01:05:54] oh collab is missing [01:06:12] just use SiteMatrix [01:06:16] it'll tell you everything [01:06:18] holy god [01:06:26] minux wikitech since its disconnected [01:06:40] lolz https://exec.wikimedia.org/wiki/Main_Page [01:07:04] awjr: so lets make this easy on us. dont bother with private wikis for now [01:07:12] awjr: that cuts out almost half of them [01:07:24] wow [01:07:28] yeah [01:07:31] awjr: hi, on the new Contact page, where is the Technical problem form supposed to put comments? [01:07:32] and the others all seem to be subs of wikimedia.org [01:07:40] awjr: then drop all the chapters wikis [01:07:41] so sub.m.wikimedia.org [01:07:47] yup [01:07:47] phew [01:07:55] awjr: see ... not so bad at all [01:08:22] that actually gets us back down to basically the list we have now anyway, right? [01:09:39] except for outreach and strategy [01:09:49] yup [01:10:00] did i manage to both scare and save you from work ? [01:10:02] awjr: --^ [01:10:03] philinje: http://www.mediawiki.org/wiki/MobileFrontendFeedback [01:10:09] thanks [01:10:15] np [01:10:17] tfinc aye [01:10:24] awjr: then my job for today is complete :D [01:10:43] awjr: i added some more columns to make it easier to plan this out [01:10:53] i see that, beautiful. [01:11:17] awjr: seems like the posting bit is not working anymore from Technical problem [01:11:59] oh i forgot to test that in the beta after our deployment today [01:12:02] lemme take a look [01:12:07] awjr: also, red message pops up, but let's look at this later, just needed to confirm something for the lawyer [01:12:26] ?! [01:12:28] awjr: after were happy with this table we can move it over to a wiki [01:12:49] but i hate public collaborative editing [01:14:45] philinje it just worked for me [01:15:00] philinje were you wondering about where feedback from the non-beta contact form goes? [01:15:17] no, just the new form on beta [01:15:23] yeah it works fine [01:15:47] hmm, let me take a look tomorrow, thanks [01:16:16] k [01:18:35] awjr: ok ... i think its time for me to head out [01:18:40] so tfinc tomorrow i'll talk to phil about reaching out to the projects with language subdomains to help us identify some of the kinks [01:18:53] yes, the other piece that will have to be coordianted is main page creation [01:18:56] were you suggesting a 2-week window? [01:19:02] you'll notice its a column that i added [01:19:04] yeah definitely [01:19:19] tweetdeck has already taken over my life [01:19:21] its been challening to get those in place [01:19:23] ah yes [01:19:34] awjr: what did you add as search ? [01:19:50] I only use five [01:20:00] hahaha nothing yet! just my various account updates and the wikimedia mobile updates [01:20:07] i need to get a handle on notifications [01:20:47] i have ... Mentions : WikimediaMobile, Search: Wikipedia Mobile, Search Wikimedia Mobile, Search:Wikipedia App & Search:Wikipedia Offline [01:20:55] tfinc do you think two weeks is enough time to collect feedback/make fixes/get the redirect switched on? [01:21:09] we'll know after our first round now wont we :D [01:21:12] nice that seems pretty encompassing [01:21:25] its too many domain to dilly dally [01:21:26] tfinc indeed [01:21:30] were goign to sweet pretty quickly [01:21:32] expect noise [01:21:45] but that'll show that we need more resources to better server our sibling projets now wont it :D [01:22:24] sonuva ... its so late that people are only speaking in dutch [01:22:26] i'm outta here [01:23:09] lol [01:23:10] hasta [06:44:07] jdlrobson, hi [10:16:36] jdlrobson, around? [10:17:41] yup [10:17:43] whats up [10:18:41] MaxSem: ^ [10:23:13] * jdlrobson seems to have been a victim of http://en.wikipedia.org/wiki/Knock,_Knock,_Ginger ;-) [10:25:35] [WikipediaMobile] jdlrobson pushed 1 new commit to master: http://git.io/Bl5IlA [10:25:35] [WikipediaMobile/master] Handle links in reference reveal display properly - YuviPanda [10:26:37] jdlrobson, could you take a look at https://gerrit.wikimedia.org/r/7670 ? it could slightly change the delivery order and also moves jQuery to the bottom per our discussion [10:27:13] sure also YuviPanda can be bump https://github.com/wikimedia/WikipediaMobile/pull/210/files into this release - I'm wary its been open and since I'm on 20% time today I think it would be a good time to get it in [10:28:08] jdlrobson: I think we discussed this and set it to 1.3 milestone? [10:28:46] yeh we did... but rethinking it it doesn't seem such a big change - and it is quite useful [10:28:49] jdlrobson: https://github.com/wikimedia/WikipediaMobile/issues shows me that. [10:30:18] jdlrobson: Still wouldn't want to. Too close to a release (hopefully next week) [10:30:26] np [10:31:05] so MaxSem Uncaught ReferenceError: mw is not defined [10:31:46] jdlrobson: am going to use http://jquery.malsup.com/block/ for the 'large spinner' [10:31:56] rather than div myself and deal with the positioning issues [10:32:12] YuviPanda: why do you need a plugin for that? [10:33:26] jdlrobson, to try it you should also checkout the revision mentioned in commit message [10:33:37] hmm, on second thoughts I could just white out the entire screen with a div [10:33:48] why not just $.ajaxSetup{ beforeSend: function() { $("#spinner").show(); $("#content").hide(); }, complete: function() { $("#spinner").hide(); $("#content").show(); } [10:34:11] jdlrobson: nothing for ajaxSetup, this is for the saved pages one [10:34:28] just a generic example [10:34:42] ah ook MaxSem [10:36:02] jdlrobson: because it'd need to block the rest of the UI? [10:36:20] but yeah, I should be able to have an abs positioned div with a high enough z-index that covers the entir eUI [10:36:34] exactly [10:36:36] so I'll go with that unless I run into problems with inputboxes grabbing focus and not giving a shit about z-index [10:36:53] yeah, I was initially thinking of a centered one like how devgeeks showed, a full div makes more sense [10:37:02] if they can't use the UI, better not show them it anyway :) [10:43:21] YuviPanda: just have a class page-request on the html / body tag when performing the action and clear it at the end. If we have any issues with elements we can style them away whilst the page-request class is on [10:45:02] jdlrobson: I think having a div blanket the viewport would be a simpler option. Working on it, will show you in a bit [10:45:53] sure... but all I'm getting at is go with a css heavy solution rather than js [10:46:11] e.g. don't bother with .show and .hide 's all over the place [10:47:21] ok [10:53:01] New review: Jdlrobson; "Adding one inline comment." [mediawiki/extensions/MobileFrontend] (master) C: 0; - https://gerrit.wikimedia.org/r/7670 [11:13:46] jdlrobson, which settings appear twice? [11:13:51] settings.js [11:14:06] ah [11:16:26] New patchset: MaxSem; "Mobile script delivery via ResourceLoader" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/7670 [11:30:58] * jdlrobson goes out for lunch [12:42:41] New patchset: MaxSem; "Fix fatal reported in the mediawki-api ML." [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/7787 [12:45:17] New review: MaxSem; "The ext. prefixing convention is not universal, and we're going to move this directly into core soon." [mediawiki/extensions/MobileFrontend] (master) C: 0; - https://gerrit.wikimedia.org/r/7670 [13:16:05] New patchset: MaxSem; "Fix fatal reported in the mediawki-api ML." [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/7787 [13:32:51] MaxSem does ResourceLoader support loading javascript on demand? [13:33:11] yes [13:33:29] however, this part is not mobile-friendly [13:33:33] :( [13:33:50] it's heavy and relies on jQuery [13:33:57] I'm just thinking ahead - as nearby functionality for the mobile site will require a lot of javascript - and don't really want to load it until necessary [13:34:43] then plain ol document.write('