[00:01:01] thanks Brooke [00:03:27] New patchset: Tim Starling; "Use the normal WikiPage parser options when saving to the cache" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/27382 [00:11:57] Change merged: MaxSem; [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/27382 [00:12:35] jcmish, are you back? [00:25:58] awjr: sorry it took so long they were late coming out from practice at Dimi's school [00:26:01] anything I can help with? [00:26:59] jcmish: one minute, just wrapping up a mtg [00:27:06] no prob [00:28:30] New review: Tim Starling; "Brion tested it." [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/27382 [00:28:59] jcmish i think we're all set for today; i've got to wrap up a few things before i have to sign off in ~30 minutes [00:30:19] jcmish if there's anything you need or any questions you have for me now im happy to help, otherwise we can pick up tomorrow after you're done with chris :) [00:30:31] sounds great [00:30:34] sorry I had to leave [00:31:57] jcmish: no worries. pro-tip: block out time in your google calendar for things like that when possible so we know not to schedule meetings with you during those times, or we can figure out why you're MIA if we're looking for you for something :) [00:32:30] hehe yup! [00:32:37] will do [00:36:47] jcmish, how did that deployment look from your perspective?:) [00:37:12] hehe [10:26:30] any mobilefrontend guru around ? [10:26:44] We apparently redirect the new firefox mobile to the desktop website : https://bugzilla.wikimedia.org/show_bug.cgi?id=40919 [10:27:11] ping YuviPanda MaxSem [10:27:44] mmmm [10:28:45] apparently we look at the user-agent to contains Android [10:28:54] and they removed it from their ua [10:28:55] and it makes sense [10:29:02] so we should look for "Mobi" apparently [10:29:05] "If FirefoxOS lies and sends a user agent with "Android" in the title" [10:29:15] so don't fucking lie:P [10:29:40] it's a wontfix imho [10:29:59] i have no idea what FirefoxOS is hehe [10:30:10] ahh [10:30:12] that is an OS [10:30:15] replacing Android [10:30:41] http://lawrencemandel.com/2012/07/27/decision-made-firefox-os-user-agent-string/ [10:30:50] apparently: Mozilla/5.0 (Mobile; rv:14.0) Gecko/14.0 Firefox/14.0 [10:30:56] whereas on Android there is: [10:31:02] Mozilla/5.0 (Android; Mobile; rv:14.0) Gecko/14.0 Firefox/14.0 [10:31:02] Mozilla/5.0 (Android; Tablet; rv:14.0) Gecko/14.0 Firefox/14.0 [10:31:10] so yeah, should probably check for Mobile string [10:31:52] MaxSem: I will let you comment on https://bugzilla.wikimedia.org/show_bug.cgi?id=40919 :-] [10:31:55] stepping out myself [10:37:10] added the user agents above in https://bugzilla.wikimedia.org/show_bug.cgi?id=40919 [16:59:29] awjr: joining us ? [16:59:35] tfinc yep sec [17:00:32] MaxSem: standup! [17:11:41] awjr: were going to continue putting up the mingle screen for stand ups . it's helping to raise questions very quickly [17:11:50] tfinc im glad to hear it :) [17:17:42] awjr: so the bug with nokia's seems to be cache related AGAIN [17:17:42] appending debug=true fixes the problem [17:18:01] hmm [17:18:13] i dont know if that necessarily means it's cache related [17:18:19] there could be something weird with load order? [17:18:45] i don't know - but whatever it is it's happening far too frequently [17:18:50] and it's really random [17:19:11] right now on one device none of the stylesheets are loading at all [17:19:17] Nokia E63 Opera Mobile [17:20:21] jdlrobson: is there a relaible way to debug with opera mobile? [17:20:27] no [17:20:42] ok [17:20:49] and this is device specific? [17:21:04] there may be a new debugging tool I haven't seen though so i'll have an explore [17:21:16] So far problems reported on Nokia and Blackberry's [17:21:25] but not consistently [17:21:40] Also browsers it wasn't working on yesterday are now working today [17:22:06] can we flush the cache like we've done in the past to see if that fixes it? [17:22:25] jdlrobson: the varnish cache was flushed shortly after deployment yesterday [17:23:14] oooh it seems opera now has remote debugging [17:23:19] jdlrobson: are there specific resources that are not getting loaded? [17:23:30] awjr: yes burt sometimes in the past it's seemed we've needed to flush again for some reason [17:23:39] awjr: some phones nothing is getting loaded (no js or css) [17:23:43] some phones some js is loading [17:23:50] and all css [17:24:08] jdlrobson: if i'm thinking of the same issue, it's not actually flushing the varnish cache that helps; it's touching the specific resources files and redeploying them that helps [17:24:19] i see [17:24:27] do we touch the resource files? [17:24:33] (as part of deployment?) [17:24:53] not explicitly; theoretically we shouldn't need to [17:25:20] can you touch them to see if this fixes the problem i can currently replicate? [17:25:31] jdlrobson: i need to know which resources specifically [17:25:41] all i'm guessing [17:25:56] let me try opera dragonfly brb [17:27:45] "No request made. All data was retrieved from cache without accessing the network." [17:27:48] that's what's going on [17:27:59] the thing being cached is a bad resource loader file [17:27:59] exception 'MWException' with message 'ResourceLoaderFileModule::readScriptFiles: script file not found: "/usr/local/apache/common-local/php-1.21wmf1/extensions/MobileFrontend/javascripts/application.js"' in /usr/local/apache/common-local/php-1.21wmf1/includes/resourceloader/ResourceLoaderFileModule.php:564 [17:28:29] jdlrobson: Where are you getting that error? [17:28:37] jdlrobson: that path doesn't exist anymore [17:28:43] MobileFrontend/javascripts/application.js [17:28:43] Krinkle: I have an Opera Mobile emulator [17:28:49] Nokia E63 [17:28:55] I have enabled remote debugging via dragonfly [17:29:05] and it shows me that I'm downloading css/javascript with those errors [17:29:09] from cache [17:29:16] jdlrobson: is this error live now? [17:29:26] ok [17:29:27] yes [17:29:42] should resource loader throw a 500 or 404 in these cases to avoid this problem? [17:29:54] No, and that wouldn't make a difference anyway [17:30:10] It sets state:error [17:30:12] it would - the browser wouldn't cache it [17:30:16] the response is 200 OK [17:30:24] jdlrobson: timestamps [17:30:36] jdlrobson: as long as the module still has the same timestamp, the error will still be there too [17:30:36] Well Opera Mobile is ignoring that Krinkle [17:30:40] I'm telling you "No request made. All data was retrieved from cache without accessing the network." [17:30:47] and the bit that has been cached is the stack trace [17:30:52] jdlrobson: no it isn't, it is incapable of ignoring that [17:30:54] it is in the url [17:31:01] Yes [17:31:08] Which means the module still has the same timestamp [17:31:16] Krinkle: so we've dealt with similar problems in the past by touching the resource file on fenari and re-syncing it [17:31:30] http://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=mobile%7Cmobile.references&only=scripts&skin=mobile&version=1349820291&* is the url requested [17:31:33] that has been cached [17:31:38] the question is, why does the module still have the same timestamp eventhough it changed? [17:31:42] but in this case, it's looking for a resource that doesn't exist anymore (it's been moved) [17:32:11] jdlrobson: Yes, at the that timestamp the file didn't exist, and if a purged client still requests the same, it means the startup module is still giving it the same timestamp, nothing changed, no need to not use cache. [17:32:20] then the module timestamp should've been refreshed. [17:32:27] before deployment [17:32:38] Krinkle: perhaps a race condition during deployment [17:32:52] has it been at least 5 minutes since deployment? [17:33:01] Krinkle: yeah, it's been like 16 hours :p [17:33:08] then it isn't a race condition [17:33:24] awjr: did you update the module timestamp? [17:33:24] ttl for those resources is 5 mins? [17:33:47] no, i believe that happens automagically [17:35:04] Krinkle: touching one of the resources and re-syncing should update the timestamp, right? [17:35:43] awjr: automatically indeed. the startup module is upto 5 minutes (if it changed) [17:35:47] seems to be set here - https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/MobileFrontend.git;a=blob;f=includes/skins/SkinMobile.php;h=36e378d26d73a9216553cbf37c3d7b8b63bd07ef;hb=HEAD#l219 [17:36:16] w... why is that in mobilefrontend? [17:36:30] its the same as in rl though [17:36:34] that logic is fine [17:36:43] and that timestamp is for something different [17:36:45] (well, there is a known bug in it, but htat aside) [17:36:51] jdlrobson: that timestamp is for the event logging you put in [17:36:52] * jdlrobson shrugs https://gerrit.wikimedia.org/r/#/c/7670/ [17:37:06] awjr: no it [17:37:07] ' [17:37:12] awjr: no it's not [17:37:31] * Krinkle meeting [17:37:46] well the only thing called timestamp in that file you sent is [17:37:57] jdlrobson: was there something else you were looking at? [17:38:30] anything inside php files from mobilefrontend is unrelated and has no influence on what the mw.loader client does (other then the module registry) [17:38:43] the cited code there is what MF uses (or used to use) to hardcode the timestamp in the html [17:38:55] awjr: are you looking at L219 [17:38:55] right, the RL timestamp gets generated by RL [17:39:11] yep, and sent to mw.loader through the startup module [17:39:35] so Krinkle to refresh the timestamp, touching one of the resources and resyncing should do it… right? [17:39:37] touch any file in that module and sync it, that should fix it in < 5 minutes [17:39:54] there is nothing we can do on the short term for what already happened [17:40:00] (other than the above) [17:40:07] Krinkle: the paths to those resources changed during our deployment yesterday [17:40:26] there is a bug likely related to this, will tell more later [17:40:27] meeting now [17:40:27] brb [17:40:34] Krinkle: k [17:40:52] ok awjr can you touch those files to see if the problem goes away? I'm guessing this should be part of our deployment process [17:41:01] i'd suggest touching application.js and common.css [17:41:11] sorry mf-application.js and mf-common.css [17:41:11] jdlrobson: no - the cached files do not exist anymore [17:41:14] so i am unsure what to touch [17:41:36] from what timo just said it sounds like there might be a RL bug behind this [17:41:44] can we symlink in the meantime? [17:42:01] ie. make those files exist again as symlinks? [17:42:32] jdlrobson: im actually unsure how (if) that would work in the context of how changes get synced [17:42:45] jdlrobson: my preference would be to get a little more clarity around this before trying random stuff in production [17:42:53] mm - can you own this awjr so I can work on login ? [17:43:03] jdlrobson: absolutely [17:43:05] i'm here if you need any further debugging [17:43:06] thanks [17:43:10] jdlrobson: is there a bug open in bugzilla yet? [17:43:20] no.. i'm not sure what the bug should say [17:43:37] i guess the bug is something like "resource loader not updating after deployments" [17:43:41] jdlrobson: i'm going to wait to sync up again with Krinkle before i do anything; there's a genearl MW deployment about to happen so we'll have tow ait anyway [17:43:46] we've had this issue for some time now [17:43:54] jdlrobson: i'll file the bug [17:43:58] thanks [17:43:59] np [17:44:04] it's nothing to do with sections as i first thought [17:44:15] it's simply returning old cached versions which break shit like sections [17:47:33] d'oh [17:54:29] hi Maryana [17:54:32] question: https://mingle.corp.wikimedia.org/projects/mobile/cards/113 [17:54:38] what is 'the appropriate icon'? [17:54:54] the icon heather designed [17:55:05] Maryana: where is it? [17:55:12] that's a very good question [17:55:17] :) [17:55:17] hi [17:55:18] awjr: i've got that one ready to merge [17:55:23] it didn't merge due to a path conflict, lemme find it [17:55:30] heatherw^ home icon? [17:55:33] https://gerrit.wikimedia.org/r/#/c/26570/ [17:55:33] awjr: jdlrobson: the bug in RL is that max(timestamps(files)) remains the same if an old(er) file is removed from the set. [17:55:36] brion: just the icon or the language fix as well? [17:55:41] https://gerrit.wikimedia.org/r/cat/26570%2C2%2Cstylesheets/common/images/menu/home.png%5E0 [17:55:44] that's just the icon [17:55:48] (and the other icons also updated) [17:55:58] which we intend to fix by adding the hash of the registry as an invisible property to the registry [17:55:59] ahha ok [17:56:06] :) [17:56:14] all cleared up? [17:56:14] brion cool then i'll go ahead and update the language and then the changes will merge and it will be glorious [17:56:19] whoever came up with firefox's clever "show transparent images on a white background on top of the dark background' feature should be slapped around with white-on-transparent icons until they give up [17:56:28] lol [17:56:34] yes [17:56:37] Krinkle: is there a short-term workaround? [17:56:51] so, i was playing with ribbon & language selector today, and it was kinda buggy [17:56:53] just fyi [17:56:54] awjr: jdlrobson: however the reason for it to be rare, is that if a file is removed, in general it is reasonable to assume other files change to accomodate for it. If not, and it was standalone, it should've been in its own module [17:57:17] Krinkle: there was a wholesale updating of paths for resources [17:57:24] awjr: No, other than making sure the timestamp does increase, by making an insignificant change to other files [17:57:39] awjr: updating of paths is not a problem, rl is fine with that [17:57:50] Krinkle: ok, so even touching one of the new files should do the trick? [17:58:09] awjr: yes. [17:58:13] Krinkle: great thanks. [17:58:31] awjr: btw, when you say 'even', did you mean to emphasise 'new' files? I mean, what other files would you touch instead? (maybe I'm missing something) [17:59:03] if there are any new files, then no touching is needed, max-timestamp will naturally be higher [17:59:26] Krinkle: correct, i meant to emphasize new files. you are not missing something; i wasn't sure what else i would touch in the module since all the paths had changed [17:59:36] Krinkle: but apparently that did not work since all of the paths are new [18:00:37] ok, so there are more advanced systems in place for css and messages, but for javascript it can be simplified as: max(timestamps(files)) should be higher after every change. If a file was actually changed, then that will naturally be the case. [18:00:54] grr https://bugs.launchpad.net/git-review/+bug/1046881 [18:00:56] If only files moved, but no changed, then there is no need to force a cache refresh (existing cache is fine, new cache will be fine too) [18:01:16] Krinkle: i get that, but that does not seem to be what happened in this case [18:01:22] no wait i'm in the wrong directory [18:01:23] * brion slap [18:01:33] if files were only removed: make sure one of the other files gets touched, only files added: make sure that new file is last modified after the existing files were last modified. [18:01:41] New patchset: Brion VIBBER; "Switch out sprited nav icons for higher-resolution ones, using data: URI embedding. Switch "W" icon out for more generic "home" icon." [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/26570 [18:01:56] Krinkle: yeah i'll give that a try after the MW general deployment is done [18:02:02] awjr: alright [18:02:09] Krinkle: thanks for your help! [18:02:15] awjr: you're welcome [18:02:28] New review: Brion VIBBER; "Updated/rebased to resolve path conflict." [mediawiki/extensions/MobileFrontend] (master); V: 0 C: 0; - https://gerrit.wikimedia.org/r/26570 [18:02:37] awjr: sorry I can't be of more help at this time, it is a bit overflow of info, but hopefully something useful is in there. [18:02:44] Krinkle: totally :) [18:02:50] New review: Brion VIBBER; "Sneaking in a +2 since someone else previously +2'd this. ;)" [mediawiki/extensions/MobileFrontend] (master); V: 0 C: 2; - https://gerrit.wikimedia.org/r/26570 [18:02:50] Change merged: Brion VIBBER; [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/26570 [18:06:58] New patchset: awjrichards; "Update nav to say 'Home' instead of '{{SITENAME}}'" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/27433 [18:09:07] New patchset: Brion VIBBER; "Use 'Home' instead of sitename for the home link in the left nav." [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/27434 [18:09:38] uhoh biron [18:09:39] er [18:09:40] brion [18:09:41] jinx [18:09:48] hah [18:09:53] PATCH FIGHT [18:09:59] to the death! [18:10:19] brion: there's already a mf message for 'Home' [18:10:25] :) [18:10:27] let's take yours, it uses a preexisting message awjr [18:10:35] victory is mine! [18:10:36] \o/ [18:10:47] a worthy foe, brion vibber [18:10:51] brion: https://gerrit.wikimedia.org/r/#/c/26432/ < is +2 but not merged - any reason? [18:10:56] New review: Brion VIBBER; "Uses preexisting already translated message -- you win this patch fight, awjr!" [mediawiki/extensions/MobileFrontend] (master); V: 0 C: 2; - https://gerrit.wikimedia.org/r/27433 [18:10:57] Change merged: Brion VIBBER; [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/27433 [18:11:10] does https://gerrit.wikimedia.org/r/#/c/26432/ require MaxSem approval? [18:11:19] jdlrobson: we can remove MaxSem's disapproval or he can reverse it [18:12:03] my point is that we should get rid of this hack of using mobileview for tokens [18:12:09] MaxSem: any strong opinions on it? existing hack, just being tweaked [18:12:13] can we do that in a followup later? [18:13:08] Change abandoned: Brion VIBBER; "awjr did the same but using an exsiting already trnslated message that makes sense in context" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/27434 [18:13:31] woo-hoo, merge conflict [18:13:42] jdlrobson: merge conflict (which gerrit indicated before pressing Rebase change) [18:13:50] jdlrobson, Your change could not be merged due to a path conflict. [18:13:54] gerrit leaves the comment in the wrong order [18:14:00] whee [18:14:06] press submit: gerrit leaves merge conflict order, then the comment about "+2" [18:15:46] New patchset: Jdlrobson; "remove override parameter from query string" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/26432 [18:15:58] ^ MaxSem brion [18:16:19] say what you will about the Kindle Fire; the bad boy keeps a charge in sleep mode for weeks, while my nexus 7 and galaxy tab die in days [18:16:53] i pushed the +2 button [18:16:56] let's see if it merges [18:17:25] Change merged: Brion VIBBER; [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/26432 [18:19:16] \o/ [18:40:47] * tfinc ponders lunch before the team hangout @ 12 [18:40:51] jdlrobson: brion --^ [18:41:43] aye we should get some foodstuffs [18:41:55] * jdlrobson goes to scavenge for food [18:45:58] awjr, i'm still catching bugs in ribbon nav & sticky cookies. should i just accept the cards from iteration 1 anyway and write new cards for improving these features? [18:47:52] Maryana: if the acceptance criteria is fulfilled as written, then the cards should be accepted. either create new cards to address the issues if it's something not behaving the way it now seems it should, or open a bug if it's something defective. if the acceptance criteria, as written, is not met, then the card is not complete [18:48:15] ok, gotcha [18:48:17] thx [18:49:55] k, accepted those. not sure what to do w/#171, tho [18:50:14] have we removed the "src" atribute on s in collapsed sections? [18:55:27] Maryana: since #171 is a spike, it's done if the questions it asks were addressed/answered [18:56:12] #171 is a little weird, the questions are not totally clear and i think the narrative might be a bit confusing, but that's ok if you feel like jon's response satisfies the goals of the spike [18:57:12] i don't see a response. just questions. i'll ask him after lunch [18:58:18] hangout time! [18:58:26] linkie? [18:58:57] MaxSem: looks like the office folk are running late [19:04:23] MaxSem: i set up a hangout, but not sure when the others will join - https://plus.google.com/hangouts/_/09cdcfa4525b5a6164f92d1a5a0ee18423c7fa2d?pqs=1&authuser=0&hl=en [19:07:48] lunch hangout etherpad: http://etherpad.wikimedia.org/MobileTeamHangout [19:11:34] brion: http://etherpad.wikimedia.org/MobileTeamHangout [19:11:42] tx [19:15:51] brion https://plus.google.com/hangouts/_/09cdcfa4525b5a6164f92d1a5a0ee18423c7fa2d?pqs=1&authuser=0&hl=en [19:25:48] http://www.mediawiki.org/wiki/Bangalore_DevCamp_November_2012/Topics [20:07:10] jdlrobson: i just touched mf-application.js in prod and sync'd it out - can you dbl check if the problem persists on the nokia? [20:07:20] sure awjr [20:08:06] awjr: nope [20:08:07] not fixed [20:08:24] can you send me the busted link again? [20:08:48] jdlrobson: also, can you refresh the browser cache and try again? [20:09:05] jdlrobson: also, it might take up to 5 minutes for the change to take affect [20:09:15] due to the ttl for resource loader resources [20:09:30] ok i'll wait a bit - keen not to manually refresh browser cache as that won't help the average person [20:09:35] agreed [20:13:10] ok jdlrobson can you try again? [20:13:34] nope still nothing [20:13:57] ahaha [20:13:57] fixed [20:14:01] ! [20:14:04] let me reach out to the users on twitter [20:14:37] awjr: hello. Someone from Mozilla opened a bug about our frontend redirecting FirefoxOS browser to the desktop version of our site : https://bugzilla.wikimedia.org/show_bug.cgi?id=40919 [20:15:14] mail sent [20:15:15] awjr: so just pinging you to make sure you are aware of this bug :-] It is related to the user agent not containing "Android" anymore since that OS is not Android but FirefoxOS (they don't even ship the OS description hehe) [20:15:25] thank you hashar [20:16:02] we'll get it in the backlog :) [20:16:04] awjr: Maryana can someone write a story for the above [20:16:18] jdlrobson: one step ahead of you [20:16:43] ah, thanks awjr [20:17:04] jdlrobson: do these questions have answers? https://mingle.corp.wikimedia.org/projects/mobile/cards/171 [20:17:12] just a stub pointing to the bug for now: https://mingle.corp.wikimedia.org/projects/mobile/cards/214 [20:17:14] if so, i will officially accept, to much trumpets and fanfare [20:17:43] awjr: thanks :-] have a good day! [20:17:49] you too hashar! [20:26:02] jdlrobson, poke again [20:26:24] * Maryana steals jdlrobson's hat [20:30:36] * Maryana puts down jdlrobson's hat and pokes brion instead [20:30:59] waah [20:31:03] :D [20:31:12] so, there are still 2 story cards in iteration 1 [20:31:17] both of them dealing with images [20:31:32] one is a spike, so as long as we have reasonable answers to the questions that are listed, it's ok to sign off [20:31:40] https://mingle.corp.wikimedia.org/projects/mobile/cards/171 [20:32:08] does this still seem murky and mysterious to you, brion? [20:32:12] 171 we have partial time logging infrastructure in place to help us determine which method is fastest etc when we actually do the spike [20:32:20] 132 is done and waiting for someone to +2 and merge it :) [20:32:33] aha! [20:32:37] excellent [20:32:59] mwahahahahaha….. most excellent >:D [20:33:13] * Maryana puts jdlrobson's hat on brion [20:33:27] aw, we made him leave [20:33:30] * brion puts on a jaunty accent to match [21:14:01] brion would you slap me if i asked for phpunit tests for https://gerrit.wikimedia.org/r/#/c/24115/14 ? [21:14:52] awjr: the parser test cases don't end up including any srcset items at present… could probably rig one up that does [21:15:00] there is also a quint test for some of the JS bits [21:16:32] yah [21:16:48] if jon's happy with the js my inclination is to go ahead and merge the changes lest it languish any longer [21:17:31] \o/ [21:17:35] i'll whip up that test [21:17:41] w00t! [21:18:50] brion: and another thing! can you add to the 1.21 release notes? [21:19:03] sure [21:19:09] hrm [21:19:25] it looks like parser tests disable server-side image scaling or something [21:19:40] ruhroh [21:20:15] maybe i can… change that mwahahaha [21:22:14] awjr: can i have permission to edit cards please? [21:23:21] heatherw: sure - if you add new work please make sure to ping someone so they know it's been added to the backlog; and please don't update any cards that are ready for dev, in dev, ready for testing, etc, at least not without chatting with someone from product [21:23:53] heatherw: done [21:24:03] all i really want to do it be able to add the assets [21:24:11] rather than emailing to jon and brion [21:24:25] perfect, that's where they should be added in case someone else picks up the card :) [21:24:41] :) [21:25:07] thanks! [21:26:27] what, you mean we can have things in our cards other than bulleted lists and confusing prose? [21:26:36] head splody [21:26:48] tehe [21:27:03] what is this, trello? [21:27:23] we have to maintain our dry text-only format. zero fun at all times. [21:30:58] retro! [21:31:08] here's the etherpad: http://etherpad.wikimedia.org/mobilenav-sprint1-retro [21:31:11] hangout link is in the invite [21:31:19] IRL hangout is in r31 [21:31:41] tfinc, ping ping ping [21:31:51] tfinc, Maryana, MaxSem, brion [21:31:57] all hands on deck [21:32:01] howie/jdlrobson too, who im not seeing on the internets [21:32:07] howie's here [21:32:08] wot [21:32:18] no jdlrobson or brion yet [21:33:31] jcmish around? [21:34:43] http://etherpad.wikimedia.org/mobilenav-sprint1-retro [22:46:44] good work team - https://twitter.com/OnomatoSteveUh/status/256160434212700160?uid=16467495&iid=am-182297469113499083815882123&nid=27+233 [23:04:57] awjr: do we already have on wiki recommendations for it for video equipment ? [23:05:07] tfinc: somewhere [23:05:08] one sec [23:08:21] tfinc: i thought it was more specific, but this is what i was thinking of:https://office.wikimedia.org/wiki/Office_IT/Projects/Telepresence [23:08:38] k [23:10:59] New patchset: Jdlrobson; "repurpose css files as less files" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/27480 [23:11:00] New patchset: Jdlrobson; "fix syntax error in background-size and introduce mixin in the process" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/27481 [23:11:00] New patchset: Jdlrobson; "add new css files generated via less" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/27482 [23:11:14] ^ brion [23:11:32] whooops [23:11:34] abort [23:11:35] error in that [23:12:14] heh [23:12:18] looking over em [23:14:52] New patchset: Jdlrobson; "fix syntax error in background-size and introduce mixin in the process" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/27481 [23:14:52] New patchset: Jdlrobson; "repurpose css files as less files" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/27480 [23:14:52] New patchset: Jdlrobson; "add new css files generated via less" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/27482 [23:17:30] Change merged: Brion VIBBER; [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/27480 [23:17:38] Change merged: Brion VIBBER; [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/27481 [23:17:58] New review: Brion VIBBER; "Output styles look correct!" [mediawiki/extensions/MobileFrontend] (master); V: 0 C: 2; - https://gerrit.wikimedia.org/r/27482 [23:17:58] Change merged: Brion VIBBER; [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/27482 [23:19:07] awjr: up for a chrombox test ? [23:19:17] tfinc: can't right now, im working with michelle [23:19:29] MaxSem: --^ [23:19:48] sure [23:19:59] join the hangout for the friday standup [23:21:47] thanks brion [23:21:52] whee [23:23:21] ok, looks like i need to go a couple more rounds with the responsive images stuff -- adding the parser test cases in turned up a couple cases where it comes out wrong [23:23:28] hangout test success! [23:23:35] yay! [23:23:35] now with usb audio in and out [23:23:41] we'll try this out on friday for the standup [23:24:30] brion: now the final piece is how to start up the hangout [23:24:38] each of us could just log in . load our calendar and click hangout [23:24:50] should work [23:24:56] which works but id love for the unit to be aware of its space and to show you the corresponding meeting [23:24:58] whoever gets there first gets to click the button [23:25:02] then you just hit join and it works automatically [23:25:10] oooooooh fancy [23:25:18] google has something similar from what preilly tells me [23:26:04] i'll mail this out but for friday whoever is there first will log into the chrome box and can start up hangout [23:26:16] sweet [23:27:10] ok, i'm going to escape for now and continue with the images thing when i'm freshly fed later. hungry brion make code SMASH [23:27:17] and smashed code doesn't do so good on tests [23:34:48] arrggg .. but it doesn't work consistently … gah! [23:46:13] ok. i think i've figured out its quirks [23:53:23] awjr: we'll be fully running off of the chrome box for the friday stand up [23:53:44] booyakasha! [23:54:22] awjr: and i have it setup so that on login both calendar and mingle get pulled up for my account [23:54:24] its pretty sweet [23:54:37] login, click, click , and i'm good to go [23:55:22] nice!