[01:38:56] * tfinc goes to see if Xcode has finished installing [01:40:01] YuviPanda: lola about us doesn't scroll on the tablet view [01:40:12] tfinc: android? [01:40:13] tfinc: iOS? [01:40:19] iOS [01:40:21] tfinc: i checked today morning, we had a scroller on tablet [01:40:28] oh wait [01:40:34] this is 3.1beta1 [01:40:37] let me update [01:40:43] let me go check again now [01:40:49] yes, beta1 had about scrolling issues [01:40:53] they were fixed just before the RC [01:41:01] so anything older will have scroll issues there [01:41:48] right [01:42:06] * tfinc watches Xcode finish installing [01:42:32] sigh .. we have a blocker for making the new ui changes default next week [01:42:42] we didn't port over a major feature [01:42:54] disabling of images are nowhere to be found [01:44:03] tfinc: from the older iOS app? [01:44:13] YuviPanda: this is on mobile web [01:44:17] ah [01:47:22] code signing errors in the new version of Xcode .. [01:47:25] i hate upgrading Xcode [01:47:59] tfinc: http://minus.com/mbiinjqp4U/ [01:48:03] see bottom right [01:48:23] nice [01:48:40] YuviPanda: is that on your phone? [01:48:43] tfinc: yes [01:48:57] nice. what did you have to change? [01:50:47] damn shitty internet [01:51:03] tfinc: nice. what did you have to change? [01:51:20] tfinc: a lot of obscureish config values and some package names. [01:51:36] tfinc: so when are we moving to a generic google account for managing the market? [01:51:55] tfinc: we should be able to push out betas once, twice a week (once https://bugzilla.wikimedia.org/show_bug.cgi?id=35577 is solved0 [01:52:02] after we see most people on 1.1 [01:52:07] i already have the account from IT [01:52:32] am blocking on seeing > 50% successful rollout [01:52:39] as moving the account requires manual work on googles part [01:52:43] and thats ripe for breakage [01:52:43] aah [01:52:46] indeed [01:52:53] which i don't want during a major push [01:52:56] so give it a week [01:53:01] a when rather then an if [01:53:07] sounds good [01:53:49] tfinc: i'm trying to figure out a build process for producing betas. [01:54:01] think i've something figured out, shall test! [01:54:49] Xcode key signing fixed [01:55:11] scrolling works [01:55:16] :) [01:55:32] near by is fine [01:55:45] it actually looks pretty awesome on a tablet [01:55:55] i know [01:55:59] awesomer than phone [01:57:29] the simulator continues to be broken though [01:57:34] making taking a screenshot really hard [01:58:43] before you were able to press power+home to screen capture on the device [01:58:55] tfinc: doesn't cmd-s take a screenshot? [01:59:30] i'm talking about on an ipad2 [01:59:38] i can't screenshot the simulator as it doesn't get a gps fix [01:59:57] actually its worse. it doesn't even get tiles [02:00:59] aahhh [02:01:14] tfinc: my iPad simulator does get a fix [02:01:20] though it is always in cupertino [02:01:24] + I get tiles [02:01:27] tfinc: want me to take screenshots? [02:01:34] yes please [02:01:46] mine is so broken after the upgrade that it doesn't even show the chrome for the phone [02:01:57] hehe [02:03:32] tfinc: http://minus.com/mhm7SAwnT/ [02:03:38] uploading, should be there in a few seconds [02:03:48] k [02:04:30] tfinc: should be there now [02:04:35] tfinc: what other screenshots do you need? [02:04:35] YuviPanda: trim the url you put on tweets next time. you picked up &feature=search_result#?blahblah [02:04:45] gah. okay [02:05:12] something that shows the save page/share/facebook popup [02:05:21] on an article page [02:05:44] its kind of funny that we shows those in map view ;) [02:05:49] as if you can save the map [02:05:59] :D [02:06:03] tfinc: we should be able to... [02:06:05] :) [02:06:24] YuviPanda: what happens when you tap the contact us link at the bottom? [02:06:25] though i'm not sure at all how such a feature would work [02:06:36] tfinc: that is essentially whatever Mobile Frontend sends us [02:07:20] YuviPanda: In order to save your changes, all iPad screenshots must be a .jpeg, .jpg, .tif, .tiff, or .png file that is 1024x768, 1024x748, 768x1024, 768x1004, 2048x1536, 2048x1496, 1536x2048 or 1536x2008 pixels, [02:07:32] o_O [02:07:36] did you not take the screen shot in side the simulator ? [02:07:45] oh wait [02:07:51] i wonder if it saved the thumbnail on me [02:07:53] tfinc: yes [02:07:58] that's possible [02:08:24] yup. thats what happened [02:08:32] so i see a white page when i tap on contact us [02:08:36] can you confirm [02:08:38] tablet iOS [02:08:40] checking [02:10:15] uh oh [02:10:19] tfinc: i see no contact page in iOS [02:10:21] err [02:10:23] in the tablet [02:10:28] so you see a white page like i do [02:10:32] no [02:10:35] the link itself isn't there [02:10:37] the footer's gone [02:10:45] thats odd .. i see it [02:10:47] also in iPhone [02:10:50] my android sees it [02:11:33] i moved to our v1.1 branch, still dont' see footer [02:12:04] tfinc: on android it takes me to a reasonably horribly formatted useless wiki page [02:12:29] tfinc: do you still see it? [02:13:34] let me see [02:14:47] it works just fine for me [02:14:51] tfinc: :| [02:14:56] i see the Wikipedia:Contact us page [02:16:43] tfinc: false alarm. [02:16:57] Last time I was using the simulator, I was checking out how the beta affected it [02:17:02] and noticed that the only effect was a missing footer [02:17:12] iOS decided to keep that cookie, so it was running from the beta :) [02:17:15] which had no footer. [02:17:25] and no, I also see Wikipedia:Contact us [02:17:45] woot [02:17:52] all is well [02:18:45] indeed [02:18:52] okay, more screenshots [02:20:09] YuviPanda: i took care of the share screen [02:20:15] ah, okay. [02:20:21] do you want any more? [02:21:39] [WikipediaMobile] yuvipanda created beta (+1 new commit): http://git.io/uft_TA [02:21:39] [WikipediaMobile/beta] Renames needed for marking this as beta - YuviPanda [02:21:43] no, I have enough [02:21:49] i also fixed my location issue [02:22:00] ah, cool! [02:22:07] Project WikipediaMobile - Nightly builds build #264: SUCCESS in 16 sec: https://integration.mediawiki.org/ci/job/WikipediaMobile%20-%20Nightly%20builds/264/ [02:23:18] [WikipediaMobile] yuvipanda pushed 1 new commit to beta: http://git.io/aGFMww [02:23:18] [WikipediaMobile/beta] Make search suggestions in QSB work with Beta - YuviPanda [02:25:11] were all good on info and screenshots now [02:25:17] \o/ [02:25:24] now we just have to wait for apple to approve it! [02:25:26] woot [02:25:33] great job getting these out yuvi [02:25:45] :D [02:26:06] soon we'll be able to delete https://github.com/wikimedia/wikipedia-iphone [02:26:19] or rather archive it somehow [02:27:46] right [02:28:07] YuviPanda: i'm wrapping up here [02:28:11] tfinc: 1.2 scheduled to go out on 12 April (2 weeks). [02:28:15] tfinc: cool. [02:28:24] need anything from me? [02:28:24] i should perhaps eat and then sleep. [02:28:25] k [02:28:34] tfinc: updates on Berlin? [02:28:38] YuviPanda: lets talk tomorrow about what the moving parts are of 1.2 [02:28:43] alright [02:28:49] i'll ask Erik tomorrow [02:28:51] tfinc: cya! [02:28:53] he hasn't gotten back to me [02:28:54] cya [02:28:55] tfinc: okay! [04:46:21] congrats on the iOS push. :) [14:24:53] MaxSem: http://mobile-geo.wmflabs.org/w/api.php?action=mobileview&page=History+of+China&format=json§ions=1 any reason this doesn't return the text of the http://en.wikipedia.org/wiki/History_of_China#Paleolithic section [14:25:23] looking [14:25:39] 2nd link should be http://mobile-geo.wmflabs.org/w/index.php/History_of_China [14:25:44] I might be misunderstanding how the api works [14:26:55] btw, http://en.wikipedia.org/w/api.php?action=mobileview&page=History+of+China&format=jsonfm§ions=1 [14:27:11] ahh i think i understand MaxSem - it's saying that this section has sub sections [14:27:47] I currently only care about toclevel 1 [14:28:05] and i was expecting the entire body of that section [14:29:25] * jdlrobson needs to rethink a few things [14:30:29] sorry:) [14:31:35] for the record in http://en.wikipedia.org/w/api.php?action=mobileview&page=History+of+China&format=jsonfm§ions=1 [14:31:45] I think that the section with id 1 should have text empty string [14:32:03] as I know the heading from line [14:34:41] that would be yet another difference from action=parse [14:34:56] YuviPanda, what do you think^^^ [14:35:07] section sublevels? [14:35:07] yes [14:35:22] yes what?:) [14:35:26] I think action=parse makes sense when you're doing 'full article at a time' [14:35:37] mobileview makes sense when you're doing per-section expansion [14:35:45] MaxSem: shouldn't it be called 'sectionview'? :P [14:36:04] no. it serves mobile content [14:36:28] MaxSem: in sections. [14:36:32] mobilesectionview, perhaps [14:36:55] too late [14:36:59] it's liv3e [14:37:35] :( [14:41:25] ALSO, IT'S SHORTER, HAHAHA [14:41:45] MaxSem: saving the tubes from clogging? [15:06:33] so MaxSem I think I've rewritten the section loading correctly so that's good [15:08:41] wee [15:55:14] * AncientEntity waves to tfinc [15:55:22] * tfinc waves back [16:27:17] awww no Max [16:27:50] YuviPanda: He's here, disguised as AncientEntity. [16:28:31] * AncientEntity runs away to invent a new nick [16:29:23] ah [16:31:45] YuviPanda: my favorite new comment "Suggestions made by users have been quickly implemented in the app. Well done, developer dudes" [16:31:54] tfinc: :D [16:31:54] saw that [16:31:55] :) [16:32:02] really positive responses [16:32:03] tfinc: i'm investigating the chrome bug [16:32:03] overall [16:32:11] which bug ? [16:32:17] mobile-feedback-l [16:32:25] i'm a bit worried about the guy who said he lost his saved pages [16:32:32] will file a bug when i get into the office [16:32:39] overall though its a really positive roll out [16:32:48] well, while that is expected in iOS (We should mention it as well?), I am not sure it should happen in Android at all. [16:32:50] and i'm already seeing 1.03 installs drop [16:33:01] agreed [16:33:03] ok .. time to commute in [16:34:07] AncientEntity: how much time did it take you to setup the labs instance with a subset of enwiki? [16:34:56] you mean, how slow is the import? very slow, DB IO on labs suck [16:36:25] AncientEntity: well, how long did it take you? [16:36:27] a day, two days? [16:37:48] 3-4 if I recall it right [16:38:18] just copy the DB files from the current instance [16:38:40] ah [16:38:42] okay [16:51:11] YuviPanda, what do you need an extra instance for? [16:51:46] AncientEntity: jwild and tfinc were talking about me deploying my GSoC stuff for them to test [16:52:32] just fo that on the same instance;) [16:52:41] s/fo/do/ [16:52:55] hmm, I don't trsut my code to not kill your instance :P [16:53:36] i should look at how geodata does stuff. This does similiar work [17:04:37] jdlrobson hi there - i have some changes for contact-us-redesign that i was trying to submit last night but have been wrestling with git [17:04:47] how so? [17:04:51] im going to try and figure out wtf i've been doing wrong and get them committed shortly [17:05:30] YuviPanda: did you learn any more about the bug we saw yesterday where the 'about' screen was drawn over the article? [17:05:45] was it present in wikipedia as well? or just wiktionary [17:05:53] pfhayes: Reedy checked the wikipedia app. works fine [17:06:02] jdlrobson well i created a branch off of our remote branch. first i was trying to bring changes from master into the branch, which i think worked. then when committing locally and trying to rebase/run git-review things started exploding [17:06:06] okay, will investigate. thanks YuviPanda, Reedy [17:06:12] pfhayes: :) [17:06:46] jdlrobson i think what im going to do is just copy the files i've changed, get rid of the branches, and try to start over [17:06:55] :/ [17:06:57] did you see my changes? [17:06:58] yeah :( [17:07:08] changes from today? [17:07:09] not yet [17:07:54] jdlrobson have they already been reviewed? i dont see any open changes in gerrit from contact-us-redesign [17:08:00] * YuviPanda pokes heatherw with https://bugzilla.wikimedia.org/show_bug.cgi?id=35577 [17:08:24] oh hai YuviPanda :) [17:08:38] ohai Storm [17:08:40] err [17:08:42] heatherw [17:08:43] :) [17:09:25] heatherw: we're going to have 'Wikipedia' and 'Wikipedia Beta' apps in the market soon. They can be installed side by side. Need some way to differentiate them in the icons (a 'Beta' label?) and in the app as well (a label for the 'W'?) [17:11:58] awjr: forgot to review [17:12:06] https://gerrit.wikimedia.org/r/3924 [17:13:10] so awjr what i'm hoping for is several things [17:13:17] 1) we move the contact page to a special page [17:13:26] jdlrobson that is what i will hopefully have committed shortly [17:13:27] 2) that special page can post to itself [17:13:50] jdlrobson i've made the feedback form a special page that pulls the HTML from the leave feedback template [17:13:57] it doesn't do anything on post yet [17:14:00] i'll be working on that today [17:14:00] jdlrobson: i'm going to get the new reference reveal code to work in the app. setting up submodules and stuff now. [17:14:04] but yeah, it iwll post back to itself [17:14:05] 3) when i post via ajax I can receive an error message or success message in the status [17:14:16] jdlrobson: I'm guessing that we'd want to make sure that we reuse 100% code with the app and the site. [17:14:35] YuviPanda: i tried the reference reveal code earlier [17:14:40] the problems you will hit are... [17:14:46] okay YuviPanda [17:14:48] jdlrobson is there a specific json format you'd like? or shall we work one out together? [17:14:51] the css for the reference reveal code is in beta_common.css [17:15:11] sorry awjr be right back with you in a bit [17:15:53] greetings all [17:15:54] also YuviPanda make sure the MFE code is at the bottom of the page [17:15:54] jdlrobson no worries - i'm actually doing my fundraising office hours right now anyway [17:16:17] jdlrobson: hmm, think it is possible to factor out the css into separate files? [17:16:22] that are then crunched into one for MFE deploy? [17:16:47] it could be YuviPanda [17:17:01] ideally we need to find a way to use resource loader in MFE [17:17:10] Reedy: I filed a bug for the error you saw here: https://bugzilla.wikimedia.org/process_bug.cgi can you leave steps to reproduce, and what device you see it on? [17:17:15] indeed. atleast for CSS to begin with [17:18:23] jdlrobson: https://bugzilla.wikimedia.org/show_bug.cgi?id=31675 [17:18:29] we have a meeting about it on 4/5 when roan gets back [17:19:08] tfinc: it'd also make code reuse between MFE and App easier [17:19:23] YuviPanda: i know. we need Roan here to actually think through it and makes changes to RL [17:19:27] the bug has more info [17:19:28] :) [17:19:31] and were chatting as soon as he gets back [17:19:32] yeah reading through i [17:19:33] t [17:19:35] so its already scheduled [17:20:06] cool [17:21:57] so awjr on subject of the feedback form - when you post via the browser it should redirect to the same page - and the template should print a message saying if it has been successful or not [17:22:10] when done via ajax I was hoping that the response could be just the message [17:22:35] e.g. "Thank you! Your comment has been sent." might be the response for a success [17:22:48] jdlrobson what about validation/error handling? [17:22:51] or "Please enter a valid email address" with an error http status code [17:22:56] jdlrobson: i have at least two blockers for the beta default launch next monday. do you have any others? [17:23:09] jdlrobson particularly in the event that there is more than one error [17:23:10] what are those blockers tfinc ? [17:23:29] mmm true awjr - I guess it could be a json string that I could parse [17:23:32] 1) we need to finalize on placement of Desktop | Mobile switcher - either at the top or on the footer [17:23:44] 2) we dropped disable images and didn't put it anywhere on the new design [17:24:26] jdlrobson i could return a pre-formatted error message with the possible errors, but if you want to do anything fancy like highlighting boxes that have failed, we'll need to think of the best way to get the needed info to the front-end. [17:24:46] oh i see tfinc - so this is to make the beta as the default ? [17:24:54] perhaps a mapping of field names or ids -> error message [17:24:55] jdlrobson: yup [17:24:55] true awjr [17:25:01] i'm eager to do that quickly [17:25:12] 3) finalize button designs [17:25:18] awjr: that would make sense. So 200 should just provide a message [17:25:21] s/buttons/touchable sections [17:25:21] 4) make footer not disappear in app :) [17:25:39] right. so with you out next week we may just be able to push the new changes and go default the week after [17:25:43] err [17:25:45] our tomorrow [17:25:46] error should provide { email: 'Invalid email address', body:'cannot submit empty form' } [17:25:46] out* [17:25:53] where the keys are names of inputs [17:26:19] oh YuviPanda another issue you will have with reference reveal is on iphone [17:26:35] the reference reveal will interfere with the footer for iOS [17:27:00] jdlrobson: hmm, I suppose we should have to figure out a way to make it pop up above the footer. [17:27:11] possibly with a css override (or a js override) [17:29:23] z-index might help no? [17:30:22] jdlrobson: we don't want it hiding the nav bar, no? [17:30:42] assuming that it does fixed pos (haven't checked code yet), setting bottom should work [17:30:56] true... grr that's annoying [17:31:11] it does fixed position but has hacks for browsers that don't support it [17:31:27] btw I don't completely understand the issues with scrolling in iOS [17:31:38] * tfinc notices our iOS app is still pending review. hates the review process [17:31:47] but is there any way we could stop using absolute positioning in favour of relative. I fear it makes everything messy -> e.g. https://github.com/jdlrobson/WikipediaMobile/tree/byebyeabsolute [17:33:45] jdlrobson: hmmm. absolute messes everything or moving to relative does that? [17:34:04] absolute positioning in my experience carries lots of weirdness [17:34:16] (along the lines of the gaps we are seeing at top of pages) [17:35:13] jdlrobson: hmm, okay. [17:35:27] i'm not sure, but I'm guessing it is not possible to just use flexboxes [17:35:37] scrolling won't really work easily, I guess [17:36:49] tfinc: google seems to be having trouble with market. Sigh. [17:36:53] (check mobile-feedback-l) [17:37:37] YuviPanda: the weird install error ? [17:37:47] another weird install error. [17:38:45] given that we've have 184,000 recorded updates in the last 24 hours [17:38:49] i'm going to blame it on google [17:38:55] :D [17:39:02] tfinc: version percentage split? [17:39:39] 3: 76k [17:39:43] 4: 1.43million [17:39:48] 10: 184k [17:39:53] stats are updated daily [17:40:10] 76k in 3 [17:40:11] hmmm [17:40:12] i expect 4 and 10 to criss cross in under a a week [17:40:36] YuviPanda: its 4.35% of our install base [17:40:44] 2: 26k (1.54%) [17:40:56] 1: 16,390 (0.95%) [17:43:04] preilly: how are our beta opt ins looking ? [17:44:14] tfinc: 13 in last 24 hours [17:46:53] Reedy: saw your comment, thanks [17:57:03] im popping out now [17:57:24] jdlrobson: later [17:57:45] feel free to leave me feedback on the coding exercise i'm working on for new mobile candidates - http://jonrobson.me.uk/codingexercise/index.html [18:59:25] jdlrobson i got my changes in to the contact-us-redesign branch: https://gerrit.wikimedia.org/r/#change,3928 [18:59:50] i'd still like to try and sync the remote branch to master but my previous efforts have been massive failures [19:15:57] hi tfinc [19:26:03] preilly, could you comment on https://bugzilla.wikimedia.org/show_bug.cgi?id=31510 ? [19:33:40] aude: heya [19:33:50] MaxSem: it's lunch time over here so preilly is out [19:33:59] not urgent [19:34:23] * MaxSem makes a sweep through our bugs [19:35:29] MaxSem: we need to cleanup MF bug layout to be clean like the app [19:35:34] what would you recommend ? [19:35:43] i keep wanting to do it like i did for the app but never get the time [19:36:09] "bug layout"? [19:36:21] for instance our bugs are split against two products [19:36:27] MediaWiki -> MobileFrontend [19:36:35] Wikimedia Mobile -> foo [19:37:59] tfinc: i know you're busy (always) but any suggestions on who we contact at Adobe (phonegap) regarding wikimania sponsorship opportunities? [19:38:10] aude: hmm [19:38:13] good question [19:38:19] or any other suggestions, aside from them? [19:38:21] well, MF is still a MW extension, but there are a few bugs that can be split into two: "app needs this" and "MF should do that in order for app to achieve the former" [19:38:26] how are you pitching them ? [19:38:56] MaxSem: the app is already layer out neatly in https://bugzilla.wikimedia.org/enter_bug.cgi?product=Wikipedia%20App [19:38:56] tfinc: i'm talking with AT&T and other techie companies, as it's an opportunity for them to be involved [19:39:02] with distinct components and versions [19:39:23] aude: can you send me the info that your sending them? [19:39:27] with phonegap, some tutorials would be great during the hackathon and maybe a table where people could come and chat with them [19:39:30] i can then forward to some peope [19:39:36] tfinc: ok [19:39:42] so you thinking them attending rather then sponsoring then [19:39:54] for AT&T, i know they can bring test devices and such for any mobile hackers [19:39:54] not adobe sponsoring the event [19:39:58] nice [19:40:06] tfinc: both, but i pitch it as an opportunity for them to be involved [19:40:17] right [19:40:19] that makes sense [19:40:19] but we can't give speaking slots [19:40:27] aude: has kul been helping you with this? [19:40:32] that attendees will be interested in them [19:40:38] kul has been a great help [19:40:45] because the deadline has passe [19:40:46] d [19:40:54] i wish we had reached out to them sooner then [19:40:56] tfinc, is everything for https://bugzilla.wikimedia.org/show_bug.cgi?id=31703 achieved from your submitter's POV? [19:41:12] well, if they have something in mind for the program, like a workshop, i think we could do that [19:41:17] MaxSem: thats a good question [19:41:34] MaxSem: lets keep it open and let YuviPanda resolve it after the 1.2 app push [19:41:34] and the hackathon is open, with multiple rooms and space for tutorials [19:41:45] * YuviPanda likes current layout [19:41:46] i'm sure we can balance it [19:42:07] tfinc, currently he plans to release 1.2 w/o per-section loads [19:42:25] just switch to the API, but load everything at once [19:42:53]