[00:05:36] wow wikipedia mobile is now a Phonegap featured app :D that's great! http://phonegap.com/app/wikipedia/ [08:29:03] [WikipediaMobile] yuvipanda pushed 1 new commit to master: http://git.io/8ypMVw [08:29:03] [WikipediaMobile/master] Removed dependency on Google APIs - YuviPanda [08:29:26] Project WikipediaMobile - Nightly builds build #177: SUCCESS in 13 sec: http://integration.mediawiki.org/ci/job/WikipediaMobile%20-%20Nightly%20builds/177/ [08:29:26] yuvipanda: Removed dependency on Google APIs [08:53:52] hi all! [08:54:19] [WikipediaMobile] yuvipanda pushed 1 new commit to master: http://git.io/J-Wnww [08:54:19] [WikipediaMobile/master] Remove Google Maps code - YuviPanda [08:54:34] Project WikipediaMobile - Nightly builds build #178: SUCCESS in 7.9 sec: http://integration.mediawiki.org/ci/job/WikipediaMobile%20-%20Nightly%20builds/178/ [08:54:34] yuvipanda: Remove Google Maps code [09:00:55] wee ... [09:01:00] yuvipanda: any ideas ? [09:01:11] tfinc: on that issue? [09:01:13] fixing [09:01:14] yes [09:01:16] k [09:01:17] for some reason it continues to work [09:01:34] for me, that is [09:05:09] [WikipediaMobile] yuvipanda pushed 1 new commit to master: http://git.io/W3V_2g [09:05:09] [WikipediaMobile/master] Removed more useless geonames references - YuviPanda [09:05:23] Project WikipediaMobile - Nightly builds build #179: SUCCESS in 7.7 sec: http://integration.mediawiki.org/ci/job/WikipediaMobile%20-%20Nightly%20builds/179/ [09:05:24] yuvipanda: Removed more useless geonames references [09:06:22] tfinc: check now [09:06:40] pulling [09:06:54] tfinc: okay [09:07:12] yuvipanda: that fixed the first error [09:07:18] but were still seeing SearchSuggestionsProvider.java:41 [09:07:28] cannot find symbol [09:07:31] hmm [09:08:29] yuvipanda: http://pastebin.com/gsS8PRYz [09:10:46] tfinc: try again [09:10:50] [WikipediaMobile] yuvipanda pushed 1 new commit to master: http://git.io/8-CRYA [09:10:50] [WikipediaMobile/master] Re-added HttpApi - YuviPanda [09:11:04] Project WikipediaMobile - Nightly builds build #180: SUCCESS in 7.8 sec: http://integration.mediawiki.org/ci/job/WikipediaMobile%20-%20Nightly%20builds/180/ [09:11:04] yuvipanda: Re-added HttpApi [09:11:45] tfinc: works? [09:11:52] checking [09:12:35] looks promising [09:13:26] yuvipanda: good build .. now just waiting on emu to restart [09:14:57] emu is up .. installing [09:15:53] yuvipanda: were good :D [09:16:02] you mean we're good :P [09:16:59] whatever version of english makes you happy :) [17:48:53] tfinc: heya [17:48:59] yuvipanda: sup [17:49:27] hey guys [17:49:34] you all appear to be night owls :) [17:49:49] tfinc: getting arun upto speed on the mobile app, he wants to try out some UI work [17:49:54] jdlrobson: that's one way to think about it :) [17:52:18] yuvipanda: nice [17:52:31] [17:52:34] tfinc: plans/bugs for tomorrow? [17:53:02] yuvipanda: haven't we already gone over this ? [17:53:24] we did and we ended up with just 2 bugs [17:53:38] with a 'lets see if we can break down a feature into smaller ones' [17:53:38] which two do you have [17:53:55] let me dig that up [17:55:21] tfinc: https://bugzilla.wikimedia.org/show_bug.cgi?id=31956 and https://bugzilla.wikimedia.org/show_bug.cgi?id=33283 [17:58:52] jdlrobson: hey Jon, welcome! [17:59:05] good timezone pfhayes [17:59:17] hello Amgine [17:59:26] we have our meeting now, right? [17:59:43] hello philinje! are you feeling any better? [18:00:11] no, a bit worse, but mostly just my throat - thanks for asking [18:00:25] pfhayes: So far it's just you, me, yuvipanda, and tfinc. And they're working on something else I believe. [18:00:42] Although I can introduce you officially to brion, if I haven't already. [18:00:52] sure [18:01:03] Brion, pfhayes is the other member of the UCOSP/WiktionaryMobile group. [18:01:07] :( at least you have the weekend to recover? [18:01:14] hello brion [18:01:30] tfinc: did you guys go through all the potential Android features? [18:01:52] philinje: how are our specs for new features? whats complete enough to jump into ? [18:02:03] * tfinc can dig through mail if you've already sent it out [18:03:15] tfinc: we are close on Beta opt-in and full-screen search [18:03:31] so nothing really for new android features [18:03:51] because all the really interesting android features need more speccing [18:03:52] http://meta.wikimedia.org/wiki/Mobile_Projects/features#Potential_features [18:04:02] in this list? [18:05:06] philinje: besides http://meta.wikimedia.org/wiki/Mobile_Projects/features#v1.1_candidates where else are you seeing android features in that list? [18:05:41] are you thinking of http://meta.wikimedia.org/wiki/Mobile_Projects/features#v2.0_candidates ? [18:06:12] further down, Potential features, bug 33855 [18:06:40] that is the list of what we were thinking is v1.2 , v1.3 [18:07:04] for example, Desktop view and Contact form are easy projects [18:07:40] maybe scroll indicator [18:08:26] I will pull some of those into a new list and create a new tracking bug [18:08:27] whats the bug # for desktop view ? [18:08:56] nm . found it [18:09:05] 31475 [18:09:28] let me put some of these on the Hackathon project page [18:12:27] yuvipanda: see any that you want to pickup from https://bugzilla.wikimedia.org/show_bug.cgi?id=33855 ? [18:17:35] yuvipanda: yes/no ? [18:19:45] take a look: http://www.mediawiki.org/wiki/Pune_Hackathon_Feb_2012/Topics#Mobile [18:20:25] If any are not easy or suitable, just remove them [18:21:01] tfinc: checking [18:21:55] tfinc: https://bugzilla.wikimedia.org/show_bug.cgi?id=31591 seems promising [18:22:16] yes, that is high priority too [18:23:26] thats pure content work [18:23:44] two column layouts currently suck [18:23:50] so we either break up the content [18:24:04] or work out how to incorporate two columns better [18:24:41] tfinc: we oculd do that [18:24:50] but the emulator for tablets is useless [18:25:22] yuvipanda: if it can't work on phones then it doesn't matter for right now [18:25:38] phones are our really audience right tnow [18:26:56] tfinc: err, was talking about that for 2 columns [18:28:01] philinje: whats the product plan .. trying to make it work for all existing contact or we going to make it drastically simpler ? [18:33:14] [18:44:57] am crashing [18:44:59] gnite everyone [18:55:44] tfinc: sorry, back now [18:56:12] contact form should be simpler, and it is really a design project [18:56:41] we could have Heather and Brandon work on it, but for now maybe there are folks at the Hackathon who are designers [18:56:52] yes, id like to slash the amount of complexity a ton there [18:56:54] arun is around [18:56:58] so we could get his thoughts [18:57:16] probably deserves a mini-spec like beta opt-in or full-screen search [18:57:29] let me reference those as models [18:58:05] philinje: in a broader context its how we deal with two column layouts [18:58:13] the contact page would be a subset of that [18:58:29] but i bet we can make this one easier by drastically simplifying ti [18:58:56] * tfinc does not like that he has to say up until 2AM to do an interview [19:01:54] tfinc: yes, we should start from a blank slate and show only the necessary stuff [19:02:34] i think the most basic form is fust a comments field with a little text on top and a submit button [19:02:41] just [19:03:28] here is a draft, could be good for Jon too: http://www.mediawiki.org/wiki/Mobile_Full_Screen_Search_Results [19:03:38] http://www.mediawiki.org/wiki/Mobile_Beta_Sign_Up_Call_to_Action [19:10:16] jorm, hey, had a chance to collect those glaucus assets? i'm dying to throw em in the mockup :D [19:10:18] both of these will be revised very soon based on a meeting yesterday [19:11:09] philinje: why do we say 'Please no deletion here.' http://meta.wikimedia.org/w/index.php?title=Mobile_Projects/features when its labeled as a whiteboard ? [19:11:20] whiteboards get erased all the time [19:11:24] DO NOT ERASE [19:11:24] especially for things we've already done [19:11:25] :) [19:11:29] brion: hush you [19:11:30] ;) [19:11:34] brion: feeling better? [19:11:42] much better than last week yes [19:11:53] excellent [19:11:54] this week? last week? i can't keep track. last week [19:12:08] i would rather archive than lose things, that page is meant to be the collecting place for all feature ideas [19:13:10] Changed to: This page is intended as a place to collect feature ideas and take a first step at organizing them. Please no deletion here. [19:13:17] philinje: k, i'm going to archive all items then [19:14:01] philinje: where did we put up the whiteboard breakdown that we did for howie ? the V1.0 V1.1 feature breakdown ? i would have expected it here http://meta.wikimedia.org/wiki/Mobile_Projects/roadmap [19:14:23] the roadmap page still has items that don't make sense to me [19:14:30] like Wikigome for Q1'12 [19:14:35] the Visual editor [19:14:42] etc [19:14:44] yes, I will revise that [19:15:15] the closest thing currently is the Wikipedia Navigation page, which has a sample timeline [19:16:16] http://www.mediawiki.org/wiki/MobileFrontend/Wikipedia_navigation [19:17:01] the roadmap will be a little more general than that for now, so maybe I will break that down by quarters [19:17:55] what is in Q1 is not really just Q1, it was a list of potential stuff that we had to decide on in terms of sequence and feasability [19:18:54] philinje: yes i know. but we all agreed that lots of things had to move out .. so lets get rid of them to confuse people less :) [19:19:27] sorry, working on other stuff right now, but will clean up the roadmap page today [19:19:46] did you have any thoughts about the timeline in the navigation page? [19:19:56] thanks [19:20:40] last time that i looked the timeline had the exact same tasks for multiple quarters .. has it been updated ? [19:24:08] it is a cumulative approach, because it shows how crowded the menus will get [19:24:25] each month there is another one or two features [19:25:02] we don't have any agreement on which features will in fact be done when, so it is a sample timeline [19:38:27] is any WML-only client actually able to use our API, or they don't know JS anyway? [19:41:15] tfinc, ^^ [19:41:43] good question [19:42:18] most will fail horribly [19:42:28] i'd suspect no useful js for those no [19:42:28] whats the use case ? [19:42:31] or very little [19:42:46] yeah, at best a J2ME app [19:42:54] that makes up for a shitty browser [19:43:51] so I wonder what should MF API do if someone requests a WML page [19:44:00] who may need it, at all? [19:44:29] sending WML wrapped in JSON (or other API formats) sounds sadistic [19:44:35] hehe [19:44:43] so what about a smarter J2ME app [19:44:46] how do we imagine that working [19:45:21] J2ME app*s*, I'm afraid :P [19:46:32] i suppose you could have an app that implements a partial wml browser, plus nicer search. ick! [19:47:20] sounds like "we should support Gopher":) [19:47:29] hehe [19:50:53] * aude waves [19:55:33] we may laugh but the majority of the worlds phones are still S40's [19:56:55] ok everybody except jorm that i need to check in with on stuff is either sick or in india [19:57:13] i think i'll just head home and fiddle with mockups, more of my devices are at home [19:57:36] tfinc, anything you want me to look into specifically on the app or on mockups/future plans? [19:57:37] you've got quite a bunch of them? [19:57:44] i've been collecting :P [19:57:59] i don't have the old devices though, those are all in tfinc's secret stash [19:59:15] mm, I've got a 2003 Siemens S55 [19:59:21] delicious! [19:59:28] brion: backup plan in case we can't get OSM in place in time for 1.1 [19:59:35] i'm a bit worried that there is still so much to do there [19:59:42] tfinc, two things we can do: [19:59:51] 1) use mapquest tile servers (check legal?) [19:59:59] 2) go back to the google maps native view [20:00:15] which would need some work to make it work with coordinate links [20:00:18] 1) is easiest [20:00:21] right [20:00:27] what would #2 look like for iOS ? [20:00:40] that would take us writing another native plugin i think [20:00:48] though there might be one we can make use of, .... [20:01:33] there is a mapkit plugin for ios [20:01:46] if you want i can fiddle with it [20:02:17] but my money's still on mapquest. either way we're giving peoples' approx locations to a third party [20:02:35] (a second third party -- already giving exact locations to geonames) [20:02:43] brion: can we cache [20:02:48] use squid as aproxy [20:02:51] to mapquest [20:03:17] in theory [20:03:28] but we'd still have to provision a server (on labs?) and figure out how to set it up [20:03:36] brion: ok [20:04:23] if we're going to use mapqest tile servers i'd say use them directly. if we want to use OSM master tileservers, then consider the cache [20:04:38] brion: they are using akamai [20:04:40] sp [20:04:44] so can handle the load [20:04:52] excellent [20:04:59] they = mapquest? [20:05:15] yes, mapquest is using akamai [20:05:18] k [20:05:19] for the tiles [20:05:29] so yeah that's the easiest and safest bet i think [20:05:36] ok [20:05:50] and then can work on our solution, with no time pressure [20:05:52] tfinc, want me to try switching over to the mapquest tiles and just see how it works? [20:05:59] ummm [20:06:15] but if you hard code the mapquest url, it's tricky to update it in the app [20:06:20] e.g. people have to update their app [20:06:38] shipping an update to the app for that is probably fine [20:06:44] whereas if we use a proxy, we can change the tile source behind the scenes [20:06:47] ok [20:06:48] brion: do it as a technical test [20:06:52] ok [20:07:13] ok anyhting else i should look at today? [20:07:47] don't stay up too late tfinc :) [20:08:00] yeah, it's friday [20:08:13] 2:00 AM - 2:45 AM interview [20:08:19] * tfinc hates the world [20:08:23] rofl [20:08:48] candidate for http://wikimediafoundation.org/wiki/Job_openings/Mobile_Partner_Development_Technical_Manager [20:09:03] ok i'll poke at the map stuff, keep poking jorm's menu demos when i get updated icons from him, and whatever else. [20:09:05] brion: i haven't been able to build the iOS app in a bit .. can you check its deps ? [20:09:18] tfinc, you may need to do the submodule dance [20:09:21] i think i doc'd it [20:09:27] link please [20:09:38] https://www.mediawiki.org/wiki/Mobile/PhoneGap/iOS_build_instructions#Get_source [20:09:43] ok [20:10:28] ok catch you on the flip side kids [20:10:33] brion: is there a way to hack on the iOS stuff with out a macbook? [20:10:36] e.g. ubuntu? [20:10:47] aude, you can hack the code, you just can't build it [20:10:52] * aude is noobish to phonegap [20:11:02] has played with the android phone gap stuff [20:11:06] brion-away: ok [20:11:18] but you can run the app itself in a browser. i'll see about making it easier to switch in the correct menus etc [20:11:30] add that to my list :) [20:12:15] * brion-away wanders off to productivity-land [20:12:47] ok! [20:15:32] [20:16:04] :) [20:16:13] * aude is at glamcamp [20:16:24] productive, i don't know [20:17:14] MaxSem: sorry to miss the discussion earlier about WML - we should degrade gracefully but that probably means alternate functionality, so it's a lower priority, but still important [20:17:20] hope that helps? [20:17:58] I asked from API's perspective [20:22:08] philinje: why are the "sister projects" showing up in Wikipedia 2.0 ? [20:22:14] their there own projects [20:25:10] tfinc: 2.0 is a placeholder, but we need to consider any relationship, and possibly the same app shell could open the other projects, etc. [20:25:26] but let's not get into that right now [20:25:31] philinje: except we've already decided not to do that right now [20:25:39] look at the work that ucosp is doing [20:25:50] oh, i see, yeah that's ok [20:26:07] someone filed that bug and it has to sit somewhere for now ;-)\ [20:26:19] ;-) [20:27:04] have to get some hot soup, be back soon [20:27:06] then put it in a future versions backlog .. having it under a tagged release is just confusing . i'm going to move it [20:27:49] ok. i trimmed the top of http://meta.wikimedia.org/wiki/Mobile_Projects/features pretty aggressively [20:28:54] Potential features is the backlog [21:42:34] Does anyone have further information about the possible mobile dev event April-June in Brazil? [22:13:48] * jorm yawns. [22:13:50] i am returned. [22:15:58] [22:20:32] * jorm am become death, destroyer of worlds. [22:20:42] * jorm am bizzaro #1 [22:36:22] hey fenta23 [22:36:36] wuha, long time ago, using irc:-) [22:36:44] are you still seeing the SSKeychain errors ? [22:36:47] we love it :) [22:36:50] irc that is [22:36:51] yes, [22:36:56] hmm [22:36:58] okay, what i did: [22:37:33] i forked the orignal git, and cloned it, i got the missing file error [22:37:49] then i did the update submodul stuff with a original clone [22:37:52] nothing [22:38:14] now i figured out: i dont have the file [22:38:26] fenta23: did it actually clone the submodule ? [22:39:12] yes, i cloned the Sumodules/ShareKit stuff [22:39:27] it took a while but nothing... [22:39:49] i can't find the file on disk [22:40:43] brion-away: if your around can you help fenta23 with the iOS build ? [22:40:50] * tfinc should sleep sometime soon [22:40:52] hmm [22:41:31] i tried to ad the file manually from the original shareKit Project, but i think its not the right way;) [22:41:46] you shouldn't have to do that [22:42:20] in what folder should the file be found? [22:42:45] Wikipedia-iOS/Submodules/ShareKit [22:42:50] okay, [22:43:23] funny, the file is not there... [22:48:05] fenta23: i'm seeing the error now [22:49:12] yeaaah, so i'm not alone:-) [22:49:51] fenta23: it was because my second update failed [22:50:00] after re-running it steps over that fine [22:50:23] now i'm running into a linker error though [22:50:24] hmm [22:51:02] someone crashed the car? [22:51:47] fenta23: i'm going to have to step out soon but hopefully brion-away gets back on. he should be able to help you out. otherwise i'll be up again in a couple of hours [22:51:53] set this channel on auto join :D [22:52:23] i'm way too tired to solve linker errors @ 4am [22:52:25] ah, i remember [22:52:40] it's 12pm;) [22:52:53] almost [22:54:01] okay, thank you tfinc... i will looking forward...