[00:00:09] many thanks for this invitation ^^ [00:01:01] Astagi: yup, that was last years [00:01:17] 2012 is still in its early planning stages [00:01:21] but i wanted to give you a heads up [00:01:25] since it would be great to have you there [00:02:12] :D nice! [00:05:18] tfinc yuvipanda_ have a question about an improvement to do.. [00:05:52] Astagi: rule 13 of IRC: 'never ask to ask' :) [00:05:56] just aks! [00:05:57] *ask [00:06:21] I was trying to work on search now: when I type a key to search usually results comes even after the page is loaded, or sometimes happens that there are old results shown for a moment, then all back ok.. this seems to happen only on low devices and/or with a low speed connection.. imho we should implement some concurrent mechanism to make it work better, for example cancel all the previous requests when you type [00:06:21] the last letter.. can I start working on something for it? [00:06:28] folks, if we will release the Android UA in 1.03, should we also "squeeze in" links from browser and Google search on home screen? [00:06:59] yuvipanda_ you're right I was introducing my long question ^^ [00:07:08] sorry ^^ [00:07:52] Astagi: ah yes, serialize access and cancel previous ones [00:07:58] Astagi: go ahead, that's a nice enhancement to have [00:08:14] philinje: UA change is a very minor one, google search is not [00:08:31] i could get you links from browser, if you really want [00:09:23] nice yuvipanda_ so bug about sprite and search improvement ;) will start working on now! [00:09:30] Astagi: :D nice [00:28:05] same piece of code [00:28:11] like *absolutely* same piece of code [00:28:22] works and doesn't work according to its whims and fancies [00:30:26] preilly: do you have your ICS phone with you? Can I borrow for testing? [00:32:41] yuvipanda_: nope [00:32:48] yuvipanda_: I sent it in for repair [00:37:23] [WikipediaMobile] yuvipanda created js-url-cache (+1 new commit): http://git.io/NuS_9A [00:37:23] [WikipediaMobile/js-url-cache] Initial commit for js based urlCache - YuviPanda [00:39:45] Project WikipediaMobile - Nightly builds build #157: SUCCESS in 10 sec: http://integration.mediawiki.org/ci/job/WikipediaMobile%20-%20Nightly%20builds/157/ [00:42:02] okay, i'm giving up on the urlCache stuff for until brion comes back. I think it should be easily usable on iOS, but painful on android [00:42:17] in which case we can continue using urlCache plugin in android + js implementaiton in iOS [00:44:37] nice [01:10:36] jerith: ping [01:11:08] * preilly notes that it's currently 3:10am Tuesday (SAST) - Time in South Africa [01:41:58] full of fail http://communities-dominate.blogs.com/brands/2012/01/how-many-lumia-sales-as-nokia-and-microsoft-ashamed-to-reveal-number-lets-count-and-compare-to-n9-me.html [01:42:03] not surprised at all [01:42:59] wow [01:45:24] tfinc: i expect people in India (where Nokia has a super-strong brand) to not buy the Lumia 710 at least, since it looks similar to the incredibly crappy Nokia 5800 [01:45:37] that phone got very popular, and then turned out to be very crappy [01:45:54] so in general, you'll get laughed at if you're using a nokia touch screen phone [01:46:05] while a 'normal' nokia is still 'cool' [01:46:40] * yuvipanda_ goes back to doing things he has a clue about [01:52:51] [WikipediaMobile] yuvipanda pushed 1 new commit to master: http://git.io/qmuZjw [01:52:51] [WikipediaMobile/master] Hitting search button actually searches now - YuviPanda [01:54:45] Project WikipediaMobile - Nightly builds build #158: SUCCESS in 8.6 sec: http://integration.mediawiki.org/ci/job/WikipediaMobile%20-%20Nightly%20builds/158/ [01:54:45] yuvipanda: Hitting search button actually searches now [02:41:21] http://thatcoolguy.github.com/gridless-boilerplate/ [02:49:46] hey yuvipanda_ ^^ [02:49:57] I made this https://github.com/4ndreaSt4gi/WikipediaMobile/commit/400101c973c319fa7aa5d309050dfd976a6041ed [02:50:35] is just an initial improvement, I use just a counter and works without any problem of concurrency... [02:50:57] Astagi: well, there's network.stopCurrentRequest that should work just as well, no? [02:51:55] uhm didn't see it [02:52:13] my function is able to don't make any ajax request [02:52:28] and don't render any useless information [02:52:55] Astagi: on keypress, cancel current request if it is still in progress. [02:53:00] doesn't that accomplish the same thing? [02:54:04] sorry I didn't see it.. anyway we call it if we have inprogress call... uhm doesn't seem a good solution [02:54:18] *class sorry [02:54:42] why not? [02:54:56] that's what we want to do, right? [02:55:05] cancel old requests and make sure there's only one... [02:55:31] Astagi: currently the search API doesn't use the network.* calls [02:56:34] uhm [02:56:56] so that cancel request is useless? [02:58:53] yuvipanda_ we can remove it so.. [02:58:59] err [02:59:15] my point is we should move search to use network.* calls [02:59:19] and then use that call to remove stuff [03:00:54] yuvipanda_ ok [03:01:11] s/remove/stop/ [03:01:27] ? [03:02:23] as in, we can then use that method to stop the current request [03:03:28] Astagi: and then in the *next* step, have it use the objects $.ajax returns so we can cancel the *Correct* one instead of just a random one [03:03:28] ok [03:03:33] err, not random - last one [03:03:47] Astagi: that's similar to your 'threadId' idea, but built- into jquery [03:05:58] uhm wait I'm confused ^^ [03:05:59] so [03:06:09] I have to use network api [03:06:24] passing it the url, data and a success callback [03:06:39] that's ok for the moment yuvipanda_? [03:07:14] Astagi: the basic idea [03:07:21] is to have all network requests ($.ajax) [03:07:29] use network. calls [03:07:31] instead of $.ajax [03:07:34] ok [03:08:04] and render only the last one, right? [03:08:35] yes [03:08:51] Astagi: also, branch off current master, I touched search code a *tiny* bit in the last commit [03:10:13] nice ^^ so in case the ajax request is aborted the success callback is not thrown, in the other case render the success callback only if I'm the last thread.. so in this case I just have to substitute ajax requests with network requests [03:10:35] will branch off yuvpanda_ thanks ^^ [03:11:46] my summary is correct? :D [03:13:25] Astagi: sortof [03:13:30] Astagi: there are no 'threads' in js [03:13:42] i've been burnt by 'thread' level thinking before ;) [03:14:00] ideally, i'd want to move all code to http://api.jquery.com/category/deferred-object/ [03:14:03] instead of callbacks [03:15:16] sorry yuvipanda_ you're right :D I meant async calls.. [03:15:20] :) [03:15:33] deferred objects are a great solution.. [03:15:35] Astagi: so instead of using manually maintained 'threadId's, $.ajax returns deferred objects [03:15:46] (a minor variant of them, but they're deferred) [03:15:50] so we should move to them [03:16:01] I can try ^^ [03:16:09] never used before [03:16:30] :D [03:16:39] Astagi: takes a bit to understand first [03:16:43] so take your time :) [03:17:32] thanks yuvipanda_ ^^ [03:17:35] :) [03:17:37] will try tomorrow [03:17:43] now is too late for me ^^ [03:17:48] have to go to bed! [03:17:57] cya on tomorrow! [03:18:05] bye! [03:18:08] bye all! [03:18:34] Astagi: gnite :) [03:18:41] Astagi: and thanks for contributing :) [03:19:32] glad to do that yuvipanda_ ^^ good night ^^ [03:42:52] [WikipediaMobile] yuvipanda pushed 1 new commit to v1.0.3: http://git.io/uGs91Q [03:42:52] [WikipediaMobile/v1.0.3] Bump version numbers - YuviPanda [03:43:06] Project WikipediaMobile - Nightly builds build #159: SUCCESS in 7.5 sec: http://integration.mediawiki.org/ci/job/WikipediaMobile%20-%20Nightly%20builds/159/ [03:43:06] yuvipanda: Bump version numbers [04:07:26] yuvipanda_: http://dumps.wikimedia.org/android/WikipediaMobile-1.1-alpha1.apk [04:21:46] [WikipediaMobile] yuvipanda pushed 1 new commit to master: http://git.io/pCJiEg [04:21:46] [WikipediaMobile/master] Bumped version to v1.1-alpha. Added CHANGELOG - YuviPanda [04:21:55] Project WikipediaMobile - Nightly builds build #160: SUCCESS in 8.4 sec: http://integration.mediawiki.org/ci/job/WikipediaMobile%20-%20Nightly%20builds/160/ [04:21:55] yuvipanda: Bumped version to v1.1-alpha. Added CHANGELOG [04:22:03] Project WikipediaMobile - Nightly builds build #161: SUCCESS in 8 sec: http://integration.mediawiki.org/ci/job/WikipediaMobile%20-%20Nightly%20builds/161/ [07:05:44] good morning [08:21:34] tfinc: still working? [08:22:00] yuvipanda: a little bit before i go to bed [08:22:04] hehe [08:22:12] gnite then! [08:24:38] yuvipanda: did you end up wandering around town ? [08:24:54] tfinc: union square, watched people race + stunt with bicycles [08:24:58] 827,236 total installs (users) :D [08:25:04] nice [08:25:16] tfinc: then got fries at McD (the place stinks!) [08:25:27] tfinc: then some more time at union square [08:25:31] so many better places then that [08:25:44] true, but wanted to try + couldn't actaully walk too far [08:26:16] it wasn't actually that bad, but super duper's fries were better [08:26:26] also, their 'large' was about 5 times the 'large' in india [08:26:27] which is good [08:27:08] was having a conversation with planemad about what happens after you die :D [08:30:35] tfinc: no alpha email? [08:30:59] yuvipanda: after i finish digging through my email [08:31:06] ah yes [08:31:07] :) [08:31:11] inbox (347) [08:34:03] Inbox (101) doesn't seem so crazy [08:42:43] (288) [08:50:35] (200) [08:51:40] \o/ [09:02:49] (142) [09:02:53] but i'm running out of steam [09:13:43] (97) :D [09:31:44] https://bugzilla.wikimedia.org/show_bug.cgi?id=33646 solved [09:31:45] "Bad title" error page returns HTTP 200 OK instead of an error code [09:31:54] the error page now output a 400 http status code [09:32:01] it was applied live a few minutes ago [09:36:37] sehr gut [16:54:25] hi yuvipanda [16:54:32] how are you? [16:55:33] ported search on using network.js https://github.com/wikimedia/WikipediaMobile/pull/130 [16:56:27] the only problem is that stop a request between the if{} seems to stop all. I think we should stop a request every time we enter the search function what about? [18:01:46] Hey Sheaclare [18:04:52] Sheaclare: have you updated the git repo? [18:07:08] :Amgine As recently as a few days ago [18:07:28] Okay, I'm trying to find the c/r. [18:08:22] Amgine I mean I fetched and merged Dale's changes. I haven't had anything to commit or push yet [18:08:59] Ok. Did you see that Wiktionary's mobile now has WOTD template displaying? [18:09:24] No I haven't. How long ago was that? [18:11:03] two days after we last chatted here. [18:11:36] Preilly got it working, I think. [18:13:01] Great. That should make things super easy on me. [18:13:50] … if it doesn't automatically implement the feature without me having to do anything. [18:13:57] Give me a sec and I'll try to find out [18:14:55] What it will do is automagically display the template on the home page. It won't do anything for making it available on other pages or from the menu. [18:16:36] Ok. I didn't realize we wanted to do that as well. Should it be a link displayed on each page or a button on the slide-up menu, or what? [18:17:42] I think it should be a button on the slide-up, and if we modify the page template to have the horizontal tab system we should add a tab for wotd. [18:18:42] So you should rough in a menu item for wotd, and then start looking at the accelerator to detect a shake (for the anagram feature) [18:19:42] Great! [18:20:02] [18:20:09] I'm looking at the commits: https://github.com/pfhayes/WiktionaryMobile/commits/master [18:20:19] I don't see a place for reviews there. [18:20:34] Do you know the url for code reviews? [18:21:55] No, I don't. I'll look and let you know if I find anything. [18:22:26] Oh, figured it out. If you click the hash button to the right you see the diff, and can add notes to it. [18:22:42] There don't seem to have been any additions in the past 5 days. [18:23:47] Ok, I see that now. Looks like you're right. [18:25:04] I wonder if everyone experienced what happened to me: since we spent three days without working on any other classes, I got a little swamped with catch-up last week. [18:25:15] That might explain the lull in commits [18:26:48] Probably. We need to get everyone regularly meeting, but Patrick and Dale both reported conflicts for this time frame. [18:28:53] Oh… by "commits" I mean commits to repositories, not time-commitments [18:29:21] But speaking of conflicts, I've got one starting in a half-hour [18:30:15] Okay. What does your schedule look like at ... [18:30:44] 1pm, or 2pm, or 3pm? (for the rest of term? [18:30:51] I'll email you an excel spreadsheet of my schedule. [18:31:05] kk. amgine@wikimedians.ca [18:33:04] done [18:37:56] Okay, I'm going to send an e-mail out, sheaclare, with some other tweaks to scheduling. [18:38:05] Have a good class! [18:38:31] Thanks, Amgine. [18:39:04] greetings all [18:50:31] preilly: anything left on https://github.com/wikimedia/wikipedia-iphone/commit/2f0b0d6c9b8c08e593b5830ab47e0e79d05cbf74 before i can push out 2.2.2 RC1 ? [18:56:04] preilly: --^ [18:58:14] tfinc: I think it's good [18:58:31] tfinc: did you test it? [18:59:29] testing now [18:59:45] i was doing Android V1.0.3-RC1 and V1.1-alpha1 last night [19:01:47] okay [19:02:42] preilly: looking good so far [19:02:47] i'll mail mobile-l [19:04:24] tfinc: okay, cool [19:08:13] did i ever mention how much i hate apples app signing/approval/everything process? [19:09:51] preilly: You pung me last night? [19:10:23] ok, IPA is signed. mailing out to mobile-l@ [19:10:43] jerith: yeah, give me a second and I'll ask you want I wanted to ask last night [19:12:24] actually .. let me test on device first [19:13:37] jerith: where is the wikipedia stuff on vumi-gw1? [19:13:55] preilly: /var/praekelt/vumi [19:14:06] jerith: okay [19:14:12] It isn't completely set up, though. I got a bit sidetracked. [19:14:24] jerith: ah, okay [19:14:33] jerith: when do you think you might have time to work on it? [19:14:53] is it all located in /var/praekelt/vumi/vumi ? [19:15:05] The vumi branch with the wikipedia app in it has diverged and is being recalcitrant. [19:16:10] I'm in the middle of pulling it out into its own repo so it stops being tied to all of vumi, but one of our clients wanted some audit data that I've just finished getting sorted. :-/ [19:16:46] jerith: okay [19:17:09] I even have a github repo for it and everything now. :-D [19:18:23] preilly: looks good on device. one i get yuvi's udid then i can mail this out. [19:18:30] once* [19:19:30] tfinc: cool [19:19:49] Give me a couple of minutes to finish lunch (well, supper now) and I'll finish setting up the repo and configuring vumi-gw1. [19:20:19] jerith: okay, sweet [19:20:23] jerith: no rush [19:20:31] jerith: enjoy your supper [19:20:51] preilly: The longer I leave it, the rustier it gets. [19:45:29] preilly: any caching issues with our UA change in Wikipedia (Android) V.1.0.3-RC1 ? [19:48:04] tfinc: not that I know of [19:52:56] hey pchang [20:05:50] hi all ^^ [20:06:42] hey Astagi [20:06:49] things are going to get a bit quiet in here over the next days [20:07:02] due to a lot travel to India and FOSDEM [20:07:40] yep np tfinc ^^ why do you go in India? [20:07:52] grrr, whatever indexes I try, the total row reads count don't drop [20:07:59] Astagi: http://www.mediawiki.org/wiki/Pune_Hackathon_Feb_2012 [20:08:25] oh nice ^^ [20:08:40] any MySQL jedi around? [20:08:55] MaxSem: binasher preilly [20:10:39] in which countries do you usually have hackathon tfinc? [20:10:49] MaxSem: can you paste an explain statement [20:10:50] in all of them [20:11:03] Astagi: we typically do one in Europe and one in the USA yearly [20:11:21] lately we've also added India to that rotation [20:12:22] nice ^^ [20:12:57] oh need an advice... ^^ [20:13:41] need an advice... I made a pull request to port search on using network.js...all works good but, as you can see here ( http://goo.gl/ebX7T ) I commented network.stopCurrentRequest(); cause something goes wrong. [20:14:02] My idea is to call it everytime performSearch is fired. what about? [20:14:48] the old request get cancelled and no success callback should be fired [20:15:01] this may improvement the search experience [20:15:09] preilly, https://gist.github.com/1712637 <-- this is against http://svn.wikimedia.org/viewvc/mediawiki/trunk/extensions/GeoData/GeoData.sql?view=markup [20:15:48] is just an idea anyway, later we will make something better using deferred objects.. [20:15:54] I tried different indexes like create index gt_geosearch on geo_tags(gt_lat,gt_lon,gt_globe,gt_primary,gt_dim); [20:16:09] rows count changed only superficially [20:19:33] tfinc: Not sure they will show up today. [20:19:40] Amgine: how come? [20:19:51] tomorrow will be my last day to do any easy sync up [20:19:54] then the crazy travel starts [20:19:57] so i'm eager to meetup [20:20:26] Me too. Just guessing that they may not. Sheaclare made it for 10am, and will probably be back. [20:20:55] I can send out a quick "okay, let's meet in 2 hours" note though. [20:21:24] Patrick cannot make it before 1630 though. [20:21:38] Amgine: you know my time window so just keep me updated [20:21:49] Will do. [20:22:59] someone in Android development have an idea? ^^ [20:23:43] Astagi: about what? [20:23:58] [12:13] need an advice... I made a pull request to port search on using network.js...all works good but, as you can see here ( http://goo.gl/ebX7T ) I commented network.stopCurrentRequest(); cause something goes wrong. [20:24:24] yep that tfinc ^^ thanks Amgine [20:24:47] <- irc daemon or smth> [20:25:43] Astagi: nothing jumps out at me but i'll try and take a in the afternoon here. Yuvi is traveling back to India today and won't be back up an running till Friday [20:27:07] ok tfinc thanks np ^^ [20:28:40] MaxSem: First MySQL has to scan the matching rows to determine how to retrieve them in sorted order, this is the extra filesort pass. Then it retrieves the rows in sorted order putting them into a temporary table because where else can it put them? The rows aren't sorted on the disk and there's no sorted index. If we had a sorted index then none of this would be necessary because all the values would already exist in memory in sorted order. [20:31:05] MaxSem: you want to have no temporary table or file sort and get matches from the index instead of the disk. [20:31:18] preilly, both of those funny things - "Using temporary" and "Using filesort" - are due to ORDER BY dist. since dist is a result of dynamic computations, it can't be indexed [20:31:34] this is expected [20:31:57] I just wanted to reduce the number of reads to retrieve the data to be sorted [20:32:53] MaxSem: I don't think this is possible [20:33:05] oh np tfinc I just made a test. I noticed that search is more responsive when we don't interrupt the previous searches ( ok I mean more responsive like seems is doing something :D ) ... anyway why worry about that? I think calling a search api doesn't generate an huge traffic, does it? [20:33:16] preilly: I'm back. Busy setting up the vumi-wikipedia app. [20:33:17] MaxSem: how many rows satisfy just the lat/long range in that query? [20:34:21] Astagi: give me the background on what you've been working on here. i'm not as up to date as yuvi has been leading your through this [20:34:33] what was the core issue we were trying to solve ? [20:34:51] ok tfinc ^^ [20:34:55] MaxSem: is this on your labs instance? [20:35:01] preilly, yes [20:35:09] on mobile-enwp [20:35:57] well tfinc yestarday talking with yuvi we decided to move all the search to network.js and think later on a future better management of ajax requests, using deferred objects... [20:35:58] binasher, 30 [20:36:17] now I ported search on using network.js [20:36:27] Astagi: was this a refactor or was there a bug somewhere ? [20:36:30] binasher: instance name mobile-enwp [20:37:34] no tfinc only a refactor... the real bug to solve at the end is making search better, sometimes when a page is loaded an old ajax request could come up and cover the page and this is bad ( but well they are async ^^ ) [20:38:16] eek .. ok [20:38:30] anyway that will make later... I'm studying deferred objects in my spare time but it's not so much now ^^ [20:38:46] nice so we have this piece of code [20:39:49] http://pastebin.com/Wtm9DKLj tfinc [20:40:28] k [20:40:38] I think that is bad decide to stop a request in that way [20:40:58] anyway this didn't work before cause search didn't use network.js [20:41:33] so I may do two things: remove it, let it to be fired everytime performsearch is fired [20:44:55] in the first case I get a more responsive search, I can see all the intermediate results, in the other case I get the search only when I stop writing and shows only the final result [20:45:20] what is the better way in your opinion tfinc? [20:47:40] * tfinc is getting distracted by a meeting :( [20:48:30] Heyla dlemieux [20:48:49] np no rush ^^ [20:48:52] Hi there! [20:50:32] Heyla Sheaclare [20:50:43] Hi Amgine: [20:50:54] Dale, you'll not be surprised that it is raining here still... [20:51:27] Hi :Da [20:51:37] I just replied to the email about an IRC meet up at two [20:51:38] Haha oh really? We have been getting covered in snow over here [20:52:28] I still think snow is easier to deal with / less cold than cold rain. [20:53:09] Hey sheaclare! [20:53:10] Actually, we were aiming for 2:30 PST/5:30 EST sheaclare. [20:53:11] MaxSem: the number of rows read == the number of rows that matched the range given on gt_lat [20:53:34] MaxSem: running - create index lonlat on geo_tags (gt_lon,gt_lat); [20:53:38] dropped the rows read to 175 [20:53:39] hi :dlemieux [20:53:52] which == the rows that match the total lat/long range [20:53:55] :Amgine I'll be there/here [20:53:57] those rows need to be read [20:54:00] to match the other conditions [20:54:05] there's no way you're going to read less [20:57:56] MaxSem: the query optimizer can only cover one range scan with an index. if you always scan lat and long, only one of those can benefit from an index, so there's no benefit from a compound index. and if there's just a compound index on (lat,lon) - only lat can ever use that index [20:58:14] so it'd be better to have separate indexes on lat and lon, neither compounded [20:58:32] and use whichever one should cover the smallest range [21:00:08] binasher, so there's no point in creating huge indexes like CREATE INDEX gt_geosearch ON geo_tags(gt_lon,gt_globe,gt_primary,gt_dim) to try to cover a lot of conditions? [21:00:36] you might want to compute the density of all ranges on each by some degree, have a lookup table, and force index based on which should be smallest. mysql won't always pick the right one on its own [21:01:38] MaxSem: probably not.. unless you were always going to search by longitude range only [21:04:09] hmm, lookup makes sense - I wanted to have it eventually to figure out maximum search radius [21:06:57] binasher, do you have any objections against using the stored function on WMF cluster? [21:10:41] preilly: Almost done, I think. (I hope.) [21:30:55] preilly: Apparently lucid's version of redis too old for our session magic.. [21:31:29] I'll fiddle with it some more tomorrow. [21:47:17] tfinc I made my decision so ^^ cancel previous request on every new one.. [21:48:30] ok [21:53:05] tfinc just a thing, and sorry for annoying you today ^^ usually during code review is there some talk here in IRC between developers? [21:55:08] Astagi: no worries at all. i just wish i had more devs for you to talk with [21:55:59] ^^ [22:17:32] jerith: is it working? [22:18:11] hey all, i'm a dev at a little design/dev agency in baltimore and we're working on an app that uses the wikipedia api [22:18:28] we'd love to get some feeback / be pointed to the best place to get feedback for the app from within wikimedia [22:18:49] if that's at all possible [22:18:56] thwop: have you asked in #wikimedia-dev [22:19:50] i haven't yet, i'll give that a go. figured it would be worth a shot to try here first with a mobile app :) [22:19:54] thanks though [22:20:16] thwop: well, at this time we don't really have a mobile specific api [22:20:47] preilly: we've been able to use the api well enough [22:21:10] thwop: greetings, whats the app ? [22:21:17] thwop: I read app as api my bad [22:21:24] we're just mostly looking for feedback from someone in wikimedia because we want to donate from the proceeds [22:21:40] oh no problem [22:22:23] thwop: what sort of feedback? [22:22:24] it's called Wikiweb, and we're drawing the relationships between articles on Wikipedia as lines between nodes [22:22:51] thwop: cool. is there a version that we can play with? [22:23:05] and we have a simplified, typeset article reader that goes with it [22:23:23] there is, but it's iOS only at the moment so we need UUIDs [22:23:54] we designed it with the tablet in mind, but it works on phones as well [22:24:04] * tfinc sighs about the iOS distribution model [22:24:11] agreed [22:24:19] Amgine: are we all set to meet in 5 min ? [22:24:37] Yes. [22:24:52] Skype/irc/phone ? [22:25:09] We have not yet set up skype/phone, so IRC. [22:25:15] preilly: we're hoping to get both interaction feedback and feedback about how it feels/aligns with the ideals of wikimedia [22:25:23] I won't be able to answer as many detailed questions as brion/yuvi but i'll do my best to point you guys in the right direction [22:25:44] dlemieux, sheaclare, and TonyC_ are already present and accounted for. [22:25:50] nice [22:26:50] :Amgine I think I've got "reload WOTD" feature working. Two issues. [22:27:10] Go ahead Shea [22:27:18] bb in a minute [22:27:47] 1. Should I use an icon in the menu (and if so, which one), and how deep in the menu should the option be? [22:28:15] Mmm, TonyC_? you are most familiar with the menu. [22:28:42] 2. The most recent code I've got off of git has a problem. When you click "back" to the WOTD page, the spinner freezes and never goes away. [22:29:12] I think there's a problem with onPageLoad(). [22:29:20] sheaclare: are you using eclipse? [22:29:26] well the menu basically just a list of menu options where the top 6 (i believe) have spaces for icons, if you put in your option at the end, it would just fine with no icon [22:29:29] … well not with onPageLoad(), per se, but something that uses it [22:29:38] ok .. back [22:29:43] yeah, I'm in Eclipse [22:30:09] You should be able to watch the logs to see what error is probably occuring [22:30:12] Amgine: so in a traditional stand up we'd have each dev talk about what they've done and what their doing next, and what their blocked on [22:30:16] preilly: we love wikipedia and we want to give back, and we want to make sure that what we creates invokes the same excitement in what wikipedia offers in you as it does us [22:30:39]