[14:22:50] Project WiktionaryMobile - Nightly builds build #45: SUCCESS in 10 sec: https://integration.mediawiki.org/ci/job/WiktionaryMobile%20-%20Nightly%20builds/45/ [14:22:50] sheaclare: Removing more dead code for Near Me feature [16:22:12] YuviPanda: do you have admin rights on the WIktionaryMobile repo? we need to add siebrand and Nikerabbit for translations [16:22:24] pfhayes: let me check, but i doubt it. [16:23:17] pfhayes: *You* have admin rights. [16:23:26] Amgine: I don't believe I do [16:23:45] I don't [16:23:46] Tfinc was planning on making sure you do. Check? [16:24:00] Amgine: i just checked and I don't. i'll email tfinc [16:24:05] thanks YuviPanda [16:24:07] kk. [16:33:18] jdlrobson, hi [16:33:22] YuviPanda, ^^ [16:33:26] MaxSem: hi [16:33:29] jdlrobson: hi! [16:33:35] yo YuviPanda MaxSem [16:33:53] jdlrobson: so, the HTML returned by action=parse&mobileformat=html is quite different in structure than the one that MF uses [16:34:05] how so? [16:34:20] jdlrobson: specifically, sections aren't in divs, so that means that sectioning code won't work [16:34:24] as won't quite a lot of other stuff [16:34:43] is this in reference to the history api stuff i was experimenting with? [16:34:46] we need to standardise on this [16:35:10] app and MF should use the same calls [16:35:44] jdlrobson: this is in reference to moving the app to action=parse&mobileformat=html [16:35:54] which does *not* do per-section ajax requests [16:36:01] ok [16:36:33] * jdlrobson refamiliarises himself with api [16:37:02] YuviPanda, I still think that extra stage "using the API, but not per-section" is wrong [16:37:33] MaxSem: i think that both should be available. [16:37:40] high latency + multiple requests -> ugh [16:39:05] YuviPanda, jdlrobson, can you unify your requirements to the format sections are being served in? [16:39:17] should we always wrp them in divs? [16:39:23] s/wrp/wrap/ [16:39:25] I think so. [16:39:26] bandwidth usage vs. latency + multiple requests; shouldn't we fault to lower bandwidth? [16:41:00] so YuviPanda forgive me but can you start from the beginning about what you are trying to achieve. This is rewriting loadPage to use the api yet? [16:41:15] jdlrobson: yes. [16:41:17] so given a title of a page you go to the api and essentially you want to ask for all the sections for that page [16:41:31] jdlrobson: no, given the title of a page you go to the API and ask for the contents of the page [16:41:40] or better still ask for anything at the beginning plus the section names (1 level down) [16:41:42] * preilly — review https://gerrit.wikimedia.org/r/4105 [16:41:53] jdlrobson: wait, let me show you the exact API call [16:42:27] jdlrobson: http://en.wikipedia.org/w/api.php?action=parse&format=json&page=Mumbai&prop=text&mobileformat=html [16:42:42] compare that to html from http://en.m.wikipedia.org/wiki/Mumbai [16:44:39] and this: preilly * /branches/wmf/1.19wmf1/extensions/ZeroRatedMobileAccess/ZeroRatedMobileAccess.body.php: 1.19wmf: MFG Change-Id: I8eea04193a9fa3c7361e3124981bf55704988030 [16:45:30] so YuviPanda at the moment MFE parses the html and adds the sections itself [16:45:50] so what would be better in my opinion is rather than requesting the entire html requesting all the sections [16:48:10] jdlrobson: hmm, so you're in favor of moving to multiple requests per page too? [16:48:47] well for the time being all im suggesting is calling the api to get a more structured response from which we can build the sections [16:49:07] it also means later we could just request the summary at the top of the article and load sections on demand [16:50:01] i'm confused. [16:50:39] well so essentially you'd do something like http://en.wikipedia.org/w/api.php?action=mobileview&format=json&page=Mumbai§ions=all&mobileformat=json [16:51:31] which would return you an array of all the sections, then you'd iterate through putting each section into containers so the output is like in MFE (
) [16:52:06] going forward you'd do something like ...sections=0... which would just load the initial summary and then load sections 1...n when the user clicks a show button [16:52:37] jdlrobson: that request does not give me entire page's contents [16:52:56] just the lead section [16:53:00] i know but it could [16:53:05] MaxSem: ^ ? [16:53:32] jdlrobson: but http://en.wikipedia.org/w/api.php?action=parse&format=json&page=Mumbai&prop=text%7Csections [16:53:35] already has section info [16:55:07] but the text is all in one big block [16:55:17] jdlrobson, I'll implement sections=all [16:55:40] i'd like to see {"toclevel":3,"level":"4","line":"Monorail","number":"7.3.3","index":"17","fromtitle":"Mumbai","byteoffset":80204,"anchor":"Monorail", text: ''}, [16:55:43] where text is not an empty string [16:55:49] ah [16:55:50] +1 [16:55:55] but is the html currently in json.sections['*'] [16:56:29] you don't need to see byteoffset, young jedi [16:56:52] greetings all [16:57:58] yep, ideally i should just be able to just loop through the api appending line and text of each section (using toclevel to work out what level headings to use) [16:58:02] greetings tfinc [16:58:12] hey jdlrobson [16:58:59] jdlrobson: linSmith is going to change to a once a week check in [16:59:00] +1 on jdlrobson [16:59:48] she'll just be checking in with us on mondays [17:00:13] tfinc: I sent you an email about adding siebrand and Nikerabbit as collabs on the WiktionaryMobile repo [17:00:13] ok cool [17:00:17] jdlrobson, text belongs to sections because this whole API is oriented towards per-section retrieval [17:00:18] pfhayes: i saw it [17:00:21] tfinc: cool [17:00:50] you can request sections=1,2,3,100 and should receive them in a sensible manner [17:01:17] YuviPanda: i think to mimic what MFE does you would just have to do something like if(toclevel === 1) add special markup to headings and wrap content in a section and then run MobileFrontend.toggle.init() after the loop to get toggling working [17:01:36] ok. lets do our stand up [17:07:39] preilly what is the problem you're experiencing with cookies? [17:08:04] MaxSem: but i would need to know how many sections there are? [17:08:59] YuviPanda: how are our reviews looking ? [17:09:32] tfinc: good, they bumped up to 4.5 after a small dip to 4.4 [17:09:35] jdlrobson, my planned API workflow was: prop=sections|text§ion=0 on first view then just request needed sections with prop=text§ions=foo [17:10:00] this way you can just count the number of sections in the array returned by the first request [17:10:15] tfinc: i see a bunch of issues that i've not been able to replicate - possibly network related ones [17:10:20] YuviPanda: excellent. just as i predicted [17:10:30] YuviPanda: i saw some issues related to small fonts [17:10:47] tfinc: i think they're on the galaxy nexus, where possibly our 'largest' size is still not large enough [17:10:50] (DPI issues) [17:10:58] YuviPanda: iOS is still under review :( [17:11:04] tfinc: no feedback whatsoever? [17:11:13] YuviPanda: apple doesn't give you any feedback [17:11:20] its other approved, waiting, or rejected [17:11:22] thats all [17:11:57] mumble grumble sigh [17:12:21] I had 2 Skype interruptions during the standup - did anyone else have them? [17:12:28] YuviPanda: 1.1.1 has over taken 1.0.3 :D [17:12:29] MaxSem: jdlrobson i think section=all would be a feature that'd make a lot of sense. [17:12:30] MaxSem: so yes but i think the first smallest step that would get us some momentum is to just load the entire content as we are now but do so via the api via screen scraping [17:12:52] +1 [17:12:54] i worry if we go straight to the load from api step we might run into lots of problems and it will be a slower process [17:12:59] as MFE doesn't do this yet either [17:13:48] +1 [17:13:51] * MaxSem goes to implement sections=all [17:14:06] tfinc: am looking through the errors being reported. A few don't make sense to me. [17:14:09] YuviPanda: i love how we can have a five star and one start review from the exact same phone [17:14:12] 17 reports of 'WikipediaApp not found' [17:14:13] star* [17:14:27] with one person saying it doesn't work and the other loving it [17:14:38] that makes no sense to me - WikipediaApp crashes because WikipediaApp is not found. [17:14:51] tfinc: hehe, I'm guessing network + what you have on it makes a lot of difference [17:15:26] so YuviPanda untested code but i was imagining something like this - http://pastebin.com/LW5dEHnx [17:16:07] jdlrobson: yes, I understand how things would work once we have section=all [17:16:09] * MaxSem notices that he starts typing some weird pythonish PHP [17:16:18] hehe [17:16:21] sure... just checking we are on the same wavelength :) [17:16:37] i was writing python over the weekend and started by writing 'function' instead of 'def' and wondering 'why no syntax highlight?' [17:17:09] YuviPanda: we need to clean up the error reports in the play market [17:17:31] clean up -> ? [17:21:50] tfinc: ^ [17:27:31] YuviPanda: mark them as old [17:27:36] as that we can focus on any new issues [17:27:47] right [17:31:28] https://bugzilla.wikimedia.org/show_bug.cgi?id=31591 < YuviPanda / tfinc this is a MobileFrontend bug yes? [17:31:43] yes [17:31:48] will change [17:32:02] New patchset: awjrichards; "Set 'contact us' title in the special page, add corresponding i18n message" [mediawiki/extensions/MobileFrontend] (contact-us-redesign) - https://gerrit.wikimedia.org/r/3964 [17:33:24] * jdlrobson needs to pop out for 30 mins back in a jiffy [17:37:12] * tfinc starts on email backlog [17:37:59] who's a vim user in here ? [17:38:05] i am [17:38:25] awjr: which vim plugins do you use ? [17:38:27] tfinc: vim ftw [17:38:42] tfinc good question - whatever comes with apt-get install vim-full [17:40:13] i've quite a collection [17:40:14] wait [17:40:33] tfinc: awjr https://dl.dropbox.com/u/8768784/vimrc [17:40:48] fancy [17:40:50] 22 plugins [17:41:13] though 4 of them are color schemes I switch around [17:41:49] wow [17:41:57] i mostly just take advantage of syntax highlighting [17:42:29] YuviPanda: what does extradite do on top of fugitive ? [17:42:47] tfinc: given a file, i can see all commits that touched *just* that file [17:43:11] err [17:43:16] *just* the commits that touched that file [17:43:38] nerdcommenter .. nice [17:43:41] awjr: this accumulated over 2 years. [17:44:01] tfinc: command-T is pretty damn awesome as well [17:44:33] YuviPanda: how does it compare to NERDTree ? [17:44:45] tfinc: it is quite different, actually. [17:44:46] YuviPanda i've some how managed to not accumulate much over years of vim use, i guess i've always kept it simple and when wanting something more robust, opted for an IDE [17:44:59] nerdtree is more 'exploratory' [17:45:09] this is 'i remember part of a file name, let's open it!' [17:45:26] + it takes up no space [17:45:44] awjr: ah, right. The only IDE I actually like is 2005+ versions of Visual Studio, so no luck. [17:45:51] hahaha [17:45:56] awjr: :) [17:45:59] VS . haha [17:46:02] i remember that [17:46:07] awjr: plus i spent about two years writing code on an atom netbook [17:46:10] :D [17:46:17] that was when I switched from 8 months of emacs to vim [17:46:27] and have been here since :D [17:46:35] tfinc: it *is* better than every other IDE out there. [17:46:46] that's more a commentary on how every other IDE I used sucked [17:46:55] it is also perhaps because C# is a nicer language than Jav [17:46:56] a [17:55:05] preilly: you mentioned on the checkin call that you were seeing issues with cookies still? [17:55:22] tfinc: are you 'moving' to vim? [17:55:39] YuviPanda: lola.. i've been on vim for years [17:55:43] lolz [17:55:59] every couple of years i reassess whats out there and see if something new has come out that i should use [17:56:01] ah, then why the sudden plugin love? [17:56:02] ah [17:57:12] New patchset: preilly; "Remove dismiss zero banner code" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/4112 [17:57:47] awjr: can you approve this change ^^ [17:58:02] awjr: yeah, I'm seeing some weird cookie stuff [17:58:16] awjr: but, I've not really investigated in too much [17:58:40] tfinc: that's why I had 'moving' in quotes :) [17:58:44] tfinc: do you have a vimrc somewhere? [17:59:52] preilly: can you open a bug with the issues you're seeing? i can take a look later. [18:00:18] awjr: I want to investigate a bit more before I do, but sure [18:00:43] New review: awjrichards; "(no comment)" [mediawiki/extensions/MobileFrontend] (master); V: 1 C: 2; - https://gerrit.wikimedia.org/r/4112 [18:00:45] Change merged: awjrichards; [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/4112 [18:00:52] preilly ok thanks [18:00:58] what the fuck, git [18:01:02] it's nice we have gerrit notifications in here ow [18:01:03] *now [18:01:28] awjr: yeah, I set that up on Friday [18:01:52] baller. [18:02:02] preilly: Ryan_Lane : this was my last delivery of kitkats http://sphotos.xx.fbcdn.net/hphotos-ash4/317841_10150337427318344_585593343_7984472_1964213197_n.jpg [18:02:21] awjr: can you release https://gerrit.wikimedia.org/r/4112 today? [18:02:43] preilly sure put it on the deployment page [18:02:57] awjr: what is the link to that page? [18:03:09] http://www.mediawiki.org/wiki/Extension:MobileFrontend/Deployments#2_April.2C_2012 [18:06:57] awjr: is this sufficient, "http://www.mediawiki.org/w/index.php?title=Extension:MobileFrontend/Deployments&stable=0&shownotice=1&fromsection=2_April%252C_2012#2_April.2C_2012" ? [18:07:16] preilly that's great [18:07:54] awjr: okay, thanks! [18:08:35] New patchset: MaxSem; "Support for action=mobileview§ions=all" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/4113 [18:09:13] YuviPanda: is it just me or is QSB always in english ? [18:09:40] we merged in code that made QSB respect settings [18:09:46] tfinc: what language are you in? [18:09:49] Polish [18:09:58] and i have a report of the same thing not working in Swedish [18:11:03] jdlrobson, YuviPanda sections=all ^^^ [18:11:09] tfinc: hmm, question. [18:11:27] anything else? [18:11:42] tfinc: can you set it to english in the app, and set it back to polish and try? [18:11:58] sure [18:12:21] MaxSem: will have a play [18:14:08] YuviPanda: that seems to fix it *except* for terms you've already searched for [18:14:12] those seem cached in QSB [18:14:32] tfinc: yeah, I think the bug is that you need to set it in the app. It doesn't pick the default locale [18:14:33] hmm [18:14:50] bug filed: https://bugzilla.wikimedia.org/show_bug.cgi?id=35650 [18:14:54] MaxSem: YuviPanda is there any way http://localhost/w/api.php?action=mobileview§ions=all&page=History%20of%20China could not including the headings (class mw-headline) in the response - I'd rather we got this from line [18:15:09] i'm going to respond to the user who reported it and see if the sw->en->sw fixes it [18:15:16] so that they can at least have the correct seeting [18:15:18] setting* [18:16:18] jdlrobson: can you pastebin the response, I don't have a MF install [18:16:24] sure 1 s [18:17:04] http://pastebin.com/pd8gMHAE [18:18:46] tfinc: wow [18:19:52] jdlrobson, "I'd rather we got this from line"? [18:20:14] so for example in ... http://localhost/w/api.php?action=mobileview§ions=all&page=History%20of%20China&format=json if you grep for line":"Prehistory" [18:20:23] text begins with '

Prehistory<\/span><\/h2>' [18:20:40] yet i can work out that h2 by using toclevel and line keys [18:20:51] ah [18:21:06] (or grep http://pastebin.com/pd8gMHAE) [18:21:27] YuviPanda, what do you think^^^ [18:21:35] reading through it [18:21:39] it gives me more flexibility MaxSem - for example i might want to do 2 articles on a page (for some unknown reason) - in which case h2's might become h3s [18:21:42] etc [18:21:57] search suggestions in mobile frontend show redirected pages on the list differing from desktop version [18:21:59] +1 it's duplicated data. [18:22:00] is this intended ? [18:22:29] srikanthlogic: can you give an example? [18:22:45] jdlrobson: type "Madras" on enwp , en.m.wp [18:23:02] Madras redirects to Chennai and many other redirects are present as well [18:23:39] becomes an "issue" more so with new beta which shows more suggestions [18:23:49] because people might think there is a relevancy issue [18:24:38] srikanthlogic: do you mean that in the search suggestions the 1st option says 'Chennai' rather than Madras and thus it is not clear it is related? [18:24:48] jdlrobson: yes [18:25:16] * jdlrobson looks closer [18:25:19] desktop version shows Madras btw [18:25:49] I tried setting up opensearch and auto-suggest working on local (both for mobile / desktop) but I couldnt try to get it working :( [18:25:57] this seems like an oversight - MaxSem - is there any reason http://en.m.wikipedia.org/w/api.php?action=opensearch&limit=15&namespace=0&format=xml&search=Madr provides the redirected name? [18:26:33] It looks like a bug to me srikanthlogic - thanks for pointing it out I hadn't noticed.. [18:27:24] :) and its even more strange in those language wikis where they redirect foreign names crazily :D [18:28:19] it would be good MaxSem (maybe its possible already) to also be able to provide the original title that matched the search term in the api response [18:28:43] jdlrobson: how does the desktop one work ? [18:29:06] mhm [18:29:08] good thinking :) [18:29:27] "Madrid (, ) is the capital and largest city of Spain." [18:29:50] it uses json rather than xml [18:29:56] (on desktop site) [18:30:19] jdlrobson, that would break users relying on OpenSearch conformance [18:31:10] you mean if we added another element to Item in the xml response? [18:31:38] heads up that ops is adding search servers in EQIAD today … shouldn't impact us since its load balanced service but i'm told we've never ran search from there [18:32:56] srikanthlogic: in terms of your local instance what isn't working? [18:33:23] jdlrobson: I tried installing OpenSearchXml and run updateSearch.php [18:33:31] it couldnt write to the pos file [18:34:06] pdateSearch.php is for incremental updates [18:34:32] oh, so is there a place where I know steps to perform after installation ? [18:34:33] are you sure it's needed? [18:34:39] none [18:34:54] if you have ordinary search set up [18:35:05] I dont know, I just thought I might need to create an Index , updateSearch seemed like a match [18:35:07] which should work by default [18:35:11] you mean http://www.mediawiki.org/wiki/Extension:OpenSearchXml or are you trying to do something else? [18:35:18] yes, same [18:35:37] mine worked without doing anything more than the above [18:38:23] srikanthlogic: MaxSem https://bugzilla.wikimedia.org/show_bug.cgi?id=35651 [18:39:19] grr [18:39:34] I don't understand: http://en.wikipedia.org/w/api.php?action=opensearch&limit=15&namespace=0&format=xml&search=Madr vs. http://en.m.wikipedia.org/w/api.php?action=opensearch&limit=15&namespace=0&format=xml&search=Madr [18:40:06] no difference [18:40:33] http://en.m.wikipedia.org/w/api.php?action=opensearch&limit=15&namespace=0&format=xml&search=Madras MaxSem [18:40:39] brion: you around? [18:40:48] tfinc: yo [18:40:49] top result is Chennai rather than Madras [18:41:03] brion: can you respond to Gord please [18:41:08] jdlrobson: thanks, but I wonder how API can return such ways [18:41:22] where it should just change the format of response [18:42:13] MaxSem is the problem related to the 'Madras' article being a redirect? [18:42:22] tfinc: looks like it was failing to init the section toggle because he hadn't run the magic command to fetch the .js files for it [18:42:35] did we fix it so that's not needed anymore yet or is that makefile still needed? [18:42:39] YuviPanda: --^ [18:42:45] awjr: yes [18:42:48] perhaps there's something different on the desktop site that's aware that the 'Madras' article exists as a redirect even though it's not coming back in the opensearch respsonse [18:42:53] brion: got to love, "magic commands". [18:42:59] eh, I was looking for differences in API while report was about differences in overall UI behaviour [18:43:01] got it [18:43:02] heh [18:43:20] brion: nope. [18:43:44] brion: working on it - have a submodule that submodules MF from gerrit, should push it up when it is actually directly being used [18:43:51] funkay [18:45:15] YuviPanda: let me know when you have a free minute to talk about the mozilla marketplace [18:45:54] tfinc: we can do it now [18:46:14] thanks brion [18:47:05] whee [18:48:59] MaxSem: pm [18:50:06] YuviPanda: let me add you to the email chain with mozilla and then we can chat [18:50:12] tfinc: cool [18:50:14] hi all [18:50:27] YuviPanda have a question for you :) [18:50:33] Astagi: sure! [18:50:33] heya [18:50:47] I'm trying fixing the scrolltop issue when you save a page [18:51:31] the only problem I have is that I can modify the scrolltop property only using document.body.scrolltop YuviPanda [18:51:36] is it ok? [18:52:00] YuviPanda: ok .. cc'd [18:52:26] YuviPanda: so their store is really simple [18:52:31] Astagi: what's wrong with $("#content").scrollTop() [18:52:54] I don't know seems to not working YuviPanda :( [18:53:08] jdlrobson: i think we had a discussion about this, IIRC? [18:53:12] YuviPanda: apps in the mozilla marketplace are nothing more then manifests that point to somewhere on the web [18:53:13] scrollTop? [18:53:17] tfinc: ah! [18:53:22] making versioning almost non existent [18:53:23] which i like [18:53:26] now [18:53:36] that doesn't mean that you don't want to leverage offlien [18:53:54] in fact i think these kinds of apps will really push their os to do HTML5 offline in really interesting ways [18:55:10] yep YuviPanda I tried $("#content").scrollTop() but is not working :) I read something similar here http://stackoverflow.com/questions/4809106/webkit-scroll-bar-overflow-jquery-scrolltop-returns-always-zero [18:55:10] scrollTop YuviPanda ? I think one of the android versions didnt like scrollTop on anything other than the body? [18:55:14] i wish gmail had custom keyboard commands [18:55:32] for instance .. i use this all the time "in:inbox is:unread" and build off of it [18:55:35] jdlrobson: what was our fix? we showed and hid it, right? [18:55:45] Astagi: lookat doScrollHack in android/platform.js [18:56:50] tfinc: yes! [18:57:05] yep YuviPanda that we did [18:57:09] tfinc: infact, once we push to the API, it should be simple to do saved pages without having to use PhoneGap apis [18:57:12] that was the horrible hack that we must never speak of [18:57:17] jdlrobson: this is why I prefer comments inline with the code [18:57:19] haha [18:57:19] rather than elsewhere [18:57:27] it will be on the commit though no? [18:57:40] ok YuviPanda jdlrobson but I need to get the current position too :) [18:57:40] if you do a git blame on that line you can remember the context [18:57:49] not only set it.. [18:57:53] jdlrobson: ^ [18:58:10] jdlrobson: i can, you can. Astagi can't because he wasn't involved in the discussion :) [18:59:37] yuvipanda but that's what commits are for no? https://github.com/wikimedia/WikipediaMobile/commit/86ed7486ffb25ca1f3acf356aaafe9aafac378af [18:59:40] tfinc: just saw that. It looks very doable [18:59:54] and https://bugzilla.wikimedia.org/show_bug.cgi?id=35369 [19:00:56] jdlrobson: yes, but still... [19:00:56] no jdlrobson :) I'm fixing another bug: https://bugzilla.wikimedia.org/show_bug.cgi?id=35431 [19:00:59] less context switches [19:01:24] and for do that I need to save the scroll position and set it after page is saved [19:01:49] Astagi: jdlrobson is the best person to talk about that hack :) [19:02:47] so with that bug surely we just don't run the hack? (i guess it must be running somewhere) [19:02:47] nice :) [19:03:14] jdlrobson: ah, yes. that makes a lot of sense [19:03:42] i guess clicking savePage triggers it somewhere. [19:04:35] oh I see jdlrobson, so this is causing the scrolltop to 0 right? [19:05:11] yep the show hide trick is forcing a scroll to top [19:05:13] this make sense, I'll check where you call it, I didn't remember about this hack :) [19:05:23] So I guess somewhere in the code when you do a save it is running the code hack [19:05:38] * jdlrobson does a git blame [19:05:52] I see, thanks for showing me up jdlrobson YuviPanda :) [19:07:13] actually [19:07:24] if you are doing a hide of the content I think that is going to force the scrolling to the top [19:07:33] regardless of whether you are doing the scroll hack [19:07:40] so clicking saved pages will hide content [19:07:59] which will reset scrolling :-S [19:09:11] ive got a few MobileFrontend things to do but will be around till late if you have any issues :) plenty of things it **could** be cas [19:09:14] ..caused by [19:10:14] I have to avoid both behaviour so :) thanks jdlrobson :) later will work on it, thanks for now! [19:10:32] good luck [19:10:35] the scrolling stuff is horrible [19:10:56] * jdlrobson needs to sit down and understand the scrolling issues on ios sometime soon [19:11:34] I see :) thanks! [19:20:59] tfinc: are we committed to making the moz launch? [19:21:12] we haven't committed to anything [19:21:25] i wanted to discuss what it would take first [19:23:39] we would have to *host* the app somewhere [19:25:13] tfinc: yes [19:25:21] tfinc: and there are CORS problems there. [19:25:28] *especially* because of the way we do subdomains [19:25:40] can be proxied, but then the proxy becomes a bottleneck [19:25:59] jerith: ping [19:26:30] CORS ? [19:27:33] tfinc: cross domain requests [19:27:57] tfinc: so, if the app is at en.m.wikipedia.org, it *usually* cannot access de.m.wikipedia.org [19:28:06] right [19:28:11] tfinc: i guess the 'app' store has ways of getting around this though [19:29:10] we should ask and find out [19:29:28] tfinc: yes, i'm sure they have technical documentation up ther somewhere [19:29:45] YuviPanda: lets build our question list and send it out [19:30:02] tfinc: alright. [19:30:17] that way it doesn't distract us from 1.2 [19:32:33] tfinc: okay [19:33:54] Do we have a, "Access-Control-Allow-Origin" header right now? [19:37:47] preilly: nope [19:37:53] preilly: Pong. [19:38:01] preilly: hmm, so we don't need proxies if we can set that [19:38:09] anyway, will add it to list of questions to send moz [19:38:22] YuviPanda: thanks [19:39:24] YuviPanda: yeah, we just need to set that [19:39:29] YuviPanda: no, need for proxies [19:40:02] preilly: too used to doing requests against stuff I don't control :) [19:40:10] nobody does Access-Control-Allow-Origin: * [19:40:11] :D [19:55:47] New patchset: Jdlrobson; "update footer template to mimic desktop site html" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/4122 [19:56:48] srikanthlogic: did you see update on https://bugzilla.wikimedia.org/show_bug.cgi?id=35651 ? [19:56:52] makes a bit more sense now [19:59:40] time for food [20:00:50] New review: preilly; "(no comment)" [mediawiki/extensions/MobileFrontend] (master); V: 1 C: 2; - https://gerrit.wikimedia.org/r/4122 [20:00:52] Change merged: preilly; [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/4122 [20:07:42] jerith: any status on making a deb [20:08:36] preilly: Sadly not. Life got in the way a bit. ;_; [20:08:55] jerith: do you know when that might be done? [20:09:07] jerith: I've got to get this stuff installed on these boxes [20:09:37] preilly: I can't make any guarantees, unfortunately. [20:09:54] But I'll try get it started tomorrow evening, at least. [20:09:57] jerith: hmm, well I guess I'll need to figure something else out [20:10:56] preilly: Can you puppet-deploy stuff straight from git repos? [20:11:19] I don't think setting up a virtualenv full of dependencies is easy to puppet. :-/ [20:11:41] jerith: we should be able to [20:12:31] jerith: well, I'd like to use a deb, but that doesn't look like it will work out in the short term [20:12:46] jerith: unless, you really think you'll be able to make progress tomorrow [20:13:14] I won't really know until tomorrow. :-/ [20:13:42] (I'm really sorry about this. It's just that we have more tight deadlines than manpower at the moment.) [20:15:26] jdlrobson: yes. [20:15:47] jdlrobson: when is the new UI supposed to be live? [20:16:09] also that would be just for app, what about the mobileweb site? [20:18:15] jerith: I understand [20:18:25] New review: awjrichards; "Line 42 of api/ApiMobileView.php:" [mediawiki/extensions/MobileFrontend] (master); V: -1 C: -1; - https://gerrit.wikimedia.org/r/4113 [20:19:41] is MaxSem out for the day? [20:19:54] ? [20:19:58] nm :) [20:20:08] i can't keep all your nicks straight :p [20:20:37] this time it wasn't intentional, simply got disconnected [20:20:59] no worries [20:21:03] awjr, you wanted something? [20:21:12] i just −1'd one of your changests [20:21:29] just wanted to let you know in case it's something you wanted to have go out today [20:22:40] thx [20:22:47] New review: preilly; "(no comment)" [mediawiki/extensions/MobileFrontend] (master); V: -1 C: -2; - https://gerrit.wikimedia.org/r/4113 [20:22:54] awjr: any idea why when i do git review contact-us-redesign it tries to send all my commits so far rather than the first [20:22:55] is that a problem? [20:23:24] MaxSem: do you know when sections=all might hit production? [20:23:25] jdlrobson: i'm not sure i follow [20:23:27] an approximate timeframe? [20:23:38] YuviPanda: probably once it works [20:23:47] ;_; [20:23:47] ah :) [20:23:56] is that a crying cat smiley? [20:24:08] well when i type git review contact-us-redesign im told that it is going to send a commit that has already been merged [20:24:11] has left me a little confused [20:24:28] as i thought if i did a git pull it would update itself [20:24:38] (@_@) [20:24:50] jdlrobson: i think i experienced the same thing and it all just sort of worked out [20:24:58] ok ill try it [20:25:01] preilly: that looks like puking-rainbow-guy sans the rainbow [20:25:09] it seemed like git-review was going to send a bunch of new commits, but the only ones that showed up as new in gerrit were the actual new changes [20:25:11] ahh remote rejected [20:25:16] >_< [20:25:21] change 3924 closed [20:25:25] * YuviPanda heads back to Javaland [20:25:47] New patchset: MaxSem; "Support for action=mobileview§ions=all" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/4124 [20:26:55] So, are we not amending changes now? [20:26:58] New review: MaxSem; "Amend with TortoiseGit didn't work:/" [mediawiki/extensions/MobileFrontend] (master) C: 0; - https://gerrit.wikimedia.org/r/4124 [20:27:40] awjr, ^^ [20:28:06] MaxSem: can you abandon your old change [20:28:44] Change abandoned: MaxSem; "(no reason)" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/4113 [20:29:59] MaxSem: thanks [20:31:35] New patchset: Jdlrobson; "additional styling" [mediawiki/extensions/MobileFrontend] (contact-us-redesign) - https://gerrit.wikimedia.org/r/4126 [20:32:12] awjr: deleted branch and tried again - hoping that worked! seems to have.. [20:33:20] hehehe ok jdlrobson [20:33:35] jdlrobson looks like it [20:33:41] awjr: what time are we deploying today? [20:33:46] sorry if you said already [20:33:49] jdlrobson 3pm PDT [20:33:50] no worries [20:34:02] k thx.. [20:34:04] jdlrobson: http://wikitech.wikimedia.org/view/Software_deployments [20:34:57] thanks :D [20:36:39] do we want to try to get the RL for CSS work in today? [20:38:23] New review: awjrichards; "(no comment)" [mediawiki/extensions/MobileFrontend] (master); V: 1 C: 2; - https://gerrit.wikimedia.org/r/4124 [20:38:26] Change merged: awjrichards; [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/4124 [20:39:03] jdlrobson: do you have a few minutes to chat about contact us? [20:39:37] ummm i can do [20:39:49] i was just looking at resource loader and seeing if we could get common.css in before this deployment [20:39:56] ok let's talk later [20:40:16] i'm here for a while so no rush :) [20:40:37] New review: awjrichards; "(no comment)" [mediawiki/extensions/MobileFrontend] (contact-us-redesign); V: 1 C: 2; - https://gerrit.wikimedia.org/r/4126 [20:40:40] Change merged: awjrichards; [mediawiki/extensions/MobileFrontend] (contact-us-redesign) - https://gerrit.wikimedia.org/r/4126 [20:44:57] YuviPanda, sections=all has been merged - I think awjr can deploy it today [20:45:02] woo [20:45:04] hoo [20:45:17] wee [20:58:33] MaxSem, jdlrobson, preilly - do you guys have all your changes for the deployment merged to master? [20:58:58] * MaxSem checks [20:59:10] I do [21:00:36] looks ok [21:02:05] awjr: i have one more commit [21:02:10] give me 5 mins [21:02:14] jdlrobson: no problem. [21:02:19] minor styling change [21:03:55] YuviPanda: you used a milestone ! [21:04:08] tfinc: i've been using them for a while, no? [21:04:19] how do you like them vs tracking bugs ? [21:04:30] tfinc: https://bugzilla.wikimedia.org/buglist.cgi?cmdtype=runnamed&namedcmd=1.2&list_id=104508 [21:04:34] tfinc: well, am mixed. [21:04:42] There is no saved search named '1.2'. [21:04:45] I like the display, but I'm missing the ability to comment on the release itself [21:04:53] damn, that is just for me? [21:04:57] so this also sucks [21:04:59] harder to share [21:05:05] and the URL to actually share is huge [21:05:12] yeah, this is a personal search [21:05:17] so while semantically cleaner, I see no obvious advantages + a few disadvantages [21:05:40] unless someone tells me 'you have been missing these!', i think we should move back to tracking bugs for the next release [21:05:44] k, if it doesn't work out when can always let mark know and then revert back [21:05:46] let's use this for this cycle so we give it time [21:05:47] yeah [21:13:19] YuviPanda am I free to use window variable in my code? look here: https://github.com/wikimedia/WikipediaMobile/blob/master/assets/www/js/chrome.js#L320 [21:13:27] tfinc: strong feelings on https://bugzilla.wikimedia.org/show_bug.cgi?id=34673 [21:13:29] actually awjr i dont think i need to commit anything (unless i magically get resource loader working) [21:13:30] Astagi: checking [21:13:49] jdlrobson ok in that case im going to start merging to the deployment branch [21:14:09] I was talking with jdlrobson and he suggested to use chrome.doScrollHack(window) [21:14:13] Astagi: I think this particular fix I'll defer to jdlrobson. [21:14:17] in plase of that line [21:14:37] *place [21:14:50] Astagi: he'll also be the one who'll be reviewing this pull request, so convincing him would be enough in this case :) [21:15:21] ahaha he just said me to ask you YuviPanda :D [21:15:29] jdlrobson you're the boss now [21:15:35] YuviPanda: I'm still not confident I understand all the hackery going on with scrolling - i wanted a 2nd opinion [21:15:36] i'll defer to jdlrobson's decision on scrolling :) [21:15:49] jdlrobson: I don't either. brion was the one who first did our scrolling work [21:16:02] * YuviPanda looks for the spell to summon brion [21:17:31] jdlrobson: from what I understand, doScrollHack simply resets page scroll to top [21:17:41] jdlrobson: unless you're on iOS 4.3, in which case it uses iScroll4 to do the same thing [21:17:49] yes we should maybe rename to scrollToTop or something similar [21:18:05] yes [21:18:12] will do in my patch coming jdlrobson [21:18:13] also need to figure out if we still need doFocusHack [21:19:25] I meant not the rename, but using scroll hack in place of window.scroll [21:22:18] ok fixed :) [21:23:42] YuviPanda did you read about shortner url for wikipedia? [21:24:02] Astagi: Extension:ShortUrl would hopefully be deployed soon and 'fix' that issue [21:24:11] atleast the biggest part of that issue [21:24:13] (url encoding ) [21:24:51] nice :) would be great to encode any url we share in the app [21:27:44] New patchset: MaxSem; "Added an option to return sections without tags" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/4133 [21:28:05] YuviPanda, jdlrobson ^^^ [21:33:54] New review: Demon; "(no comment)" [mediawiki/extensions/MobileFrontend] (contact-us-redesign); V: 1 C: 2; - https://gerrit.wikimedia.org/r/3963 [21:43:37] preilly: how are the zero styling changes going ? [21:43:54] tfinc: they're all done [21:43:58] anything else pending before we can announce a launch ? [21:44:04] baring all the opera mobile bits [21:44:08] tfinc: for zero? [21:44:16] yeah [21:44:23] tfinc: well, we need to figure out the fonts issue [21:44:36] tfinc: I've asked Dan to talk to Amit and the carrier and figure it out [21:48:33] MaxSem: \o/ [21:49:03] jdlrobson, moar regexes, unfortunately [21:49:17] :/ are those getting expensive yet? [21:49:52] heatherw_: https://minus.com/mbrpnLZKWy/ [21:49:57] both the new imagery [21:50:13] heatherw_: not sure if the 'beta' is too blocking [21:50:23] also, to open another can of worms, 'beta' is always in english :P [21:50:23] no, but it's bad practice :| [21:50:41] regexing through html? what could possibly go wrong... [21:50:53] New patchset: awjrichards; "Fixing language handling in MobileFrontend.body.php to use appropriate language fetching method depending on mw 1.19 or mw 1.20 - previously threw strict errors" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/4138 [21:51:07] preilly, MaxSem can you please take a look at ^ [21:51:30] it fixes something i fixed last week in a better way so it doesnt throw strict errors [21:53:50] awjr, static call of a member function [21:54:50] no, my bads [21:57:02] MaxSem: that was the problem before [21:57:51] New review: MaxSem; "(no comment)" [mediawiki/extensions/MobileFrontend] (master) C: 0; - https://gerrit.wikimedia.org/r/4138 [21:58:13] New review: Jdlrobson; "mf-feedback.js needs to be updated as it depends on this id (more a todo note than a complaint)" [mediawiki/extensions/MobileFrontend] (contact-us-redesign) C: -1; - https://gerrit.wikimedia.org/r/3963 [22:00:11] MaxSem $wgContLang will do the trick there? [22:00:31] also how do you lea an inline comment? [22:01:11] YuviPanda: scrolling questions? [22:01:50] brion: if me and jdlrobson have it right, the *only* reason doScrollHack exists is to 'scroll to the top' with an appropriate method, right? [22:01:57] i.e. natively everywhere, iScroll on iOS 4 [22:02:16] MaxSem: which is better to use, $wgContLng or $wgLang? [22:02:26] YuviPanda: iirc it's primarily to set up scrolling with iscroll, and also to scroll to the top :) [22:02:47] ah, okay. [22:03:07] brion: same thing :) [22:03:12] :D [22:04:07] awjr, 1) double click on a line in diff [22:04:28] 2) both seem to do static stuff in 1.19 anyway [22:05:43] MaxSem getLanguageName is not a static method though in the Language class in 1.19 [22:05:52] preilly: whats the official launch date for digi malaysia sans indic languages on the main page ? [22:06:20] New patchset: awjrichards; "Fixing language handling in MobileFrontend.body.php to use appropriate language fetching method depending on mw 1.19 or mw 1.20 - previously threw strict errors" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/4138 [22:06:45] MaxSem i made the change to use $wgContLang ^ [22:10:08] jdlrobson: what ux changes are going out today? [22:10:18] "UX improvements to beta" [22:10:32] tfinc: hitting enter on search goes to first result [22:10:39] gotcha [22:10:41] the footer expands no matter where you click [22:10:50] awjr, getLanguageName() doesn't seem to throw wfDeprecated() on 1.20 - maybe it can be called indiscriminately for simplicity? [22:10:50] I think it scrolls into view better as well [22:11:06] sorry should have been more clear on deployment notes [22:11:31] tfinc: i was planning to review the coding exercises tomorrow... hope that's okay.. wanted to make most of time with team today [22:11:37] totally fine [22:11:44] monday is deployment day [22:11:52] and since your overlapping with us on hours it makes a lot of sense [22:12:07] have also just had an enquiry about Berlin and have cc'ed you [22:12:15] MaxSem you are right - in 1.20 getLanguageName() just makes the call of Language::fetchLanguageName [22:12:24] were good to go on that. i just need to mail our travel coordinator [22:12:35] err [22:12:37] as in you going [22:13:47] New patchset: awjrichards; "Fixing language handling in MobileFrontend.body.php to use appropriate language fetching method depending on mw 1.19 or mw 1.20 - previously threw strict errors" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/4138 [22:13:55] MaxSem ^ [22:14:37] New review: MaxSem; "(no comment)" [mediawiki/extensions/MobileFrontend] (master) C: 1; - https://gerrit.wikimedia.org/r/4138 [22:14:57] YuviPanda: how goes the api rewrite? anything to share? [22:15:10] ie. the rewrite to make app use the api [22:15:18] jdlrobson: blocked myself on the new stuff to go to production and worked on a few other bugs [22:15:31] k what hours are you working tomorrow? [22:15:36] would be good to overlap again [22:15:45] jdlrobson: I can do that. [22:15:47] what hours are you on? [22:15:51] preilly can you look at this real quick: https://gerrit.wikimedia.org/r/#change,4138 [22:16:36] preilly: jerith: how is the puppetization going ? [22:16:38] i'm on BST right now YuviPanda and tomo I was hoping to do something more sane... -> 7pm-ish [22:16:51] 7PM BST? [22:16:54] (when i wake up should be about 8/9am based on current experience) [22:16:59] it's like GMT but it's summerfied [22:17:05] ie. GMT+1 [22:17:06] i…m confused [22:17:09] okay [22:17:18] tfinc: Not very, at the moment. [22:17:24] so you're going to be up at 7 'PM' UTC? [22:17:40] * jerith gazes into his schedule. "My god, it's full of deadlines." [22:17:43] well right now it is 23:17 GMT+1 [22:18:05] i'll be working till 7PM GMT+1 tomorrow.. if all goes to plan [22:18:08] MaxSem: are you ableto approve and submit that? it's blocking getting code up on test [22:18:09] ah [22:18:10] got it [22:18:25] jdlrobson: i can come up by about 2PM GMT+1 [22:18:40] awjr, I can't +2 [22:18:57] perfect YuviPanda [22:19:03] MaxSem ok - I can do it but I always feel weird doing it to myself [22:19:10] jdlrobson: cool! [22:19:37] * MaxSem gives awjr his blessings [22:19:47] New review: awjrichards; "(no comment)" [mediawiki/extensions/MobileFrontend] (master); V: 1 C: 2; - https://gerrit.wikimedia.org/r/4138 [22:19:47] :D [22:19:50] Change merged: awjrichards; [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/4138 [22:20:48] MaxSem: sections=all going to prod today, I guess? [22:22:57] ask the deploying guy;) [22:23:11] why do you need it so urgently? [22:23:33] because otherwise he has to wait a week! [22:23:41] :) [22:23:55] or write things with action=parse, and then rewrite it [22:23:56] again [22:24:06] we have staging servers for this [22:24:35] or modify the wikipedia app so that it is not a complete pain to talk to other servers. [22:24:36] hmm [22:24:38] i think i already did that [22:24:40] let me check [22:24:46] I don't like quick deployments of API because they should be tested by you the users first [22:25:00] good API === stable API [22:25:33] preilly, jdlrobson, MaxSem: today's deployment changes are live on testwiki [22:25:39] tfinc also ^ [22:25:41] \o/ [22:25:47] woot! [22:25:52] did he resource loader changes make it in? [22:26:02] please test and let me know if you see issues [22:26:41] errrorrr awjr [22:26:47] MaxSem: the fact that the app expects domains to be in a particular form messes up me testing elsewhere. Will fix [22:26:55] aw crap [22:27:20] nope tfinc turns out that can't turn off skins with resource loader - preilly was exploring it earlier but it sounds like string replacing is the only way to do it :-S [22:28:55] k [22:29:16] New patchset: awjrichards; "Finishing fix in previous commit to get all cases of getLanguageName()" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/4140 [22:29:23] MaxSem, jdlrobson ^ [22:30:01] awjr: i'm getting 'ur servers are currently experiencing a technical problem' [22:30:16] also on my android it's redirecting to incubator.wikimedia.org - is that normal? [22:30:17] jdlrobson yeah, the commit above should fix it [22:30:23] k [22:30:25] jdlrobson: yes it is normal [22:30:30] cool :) [22:30:31] jdlrobson but it sucks [22:30:40] incubator != test [22:30:48] we have an RT ticket open to get that fixed [22:31:03] awjr: whats the rt ticket on it? [22:31:37] tfinc one se [22:31:38] c [22:32:22] tfinc oh wow maybe that ticket didn't actually get made - that or rt search sucks. [22:32:38] i couldn't find it searching [22:32:42] yeah me neither [22:32:56] i'll make one - if it's a dupe they can deal. [22:34:53] tfinc: #2756 [22:35:21] MaxSem can you double check this: https://gerrit.wikimedia.org/r/#change,4140,patchset=1 [22:37:26] awjr, no warnings for me [22:37:46] New review: awjrichards; "(no comment)" [mediawiki/extensions/MobileFrontend] (master); V: 1 C: 2; - https://gerrit.wikimedia.org/r/4140 [22:37:48] Change merged: awjrichards; [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/4140 [22:38:18] awjr: when this is done let me know when you want to talk contact form [22:38:47] jdlrobson definitely [22:39:38] jdlrobson, MaxSem, preilly please test changes on test [22:39:52] * jdlrobson nods [22:40:09] now im getting language issues [22:40:16] you may see weird wfMsg() related things on test - it's just because we can't easily refresh the language cache until we actually deploy [22:40:21] k [22:43:10] MaxSem, preilly, jdlrobson: let me know when you are satisfied things work correctly [22:43:14] then i'll push to production [22:43:34] it looks fine just can't test on my android due to the incubator redirect :/ [22:43:53] grr [22:44:04] my part looks ok [22:44:26] ok then just waiting on preilly [22:46:35] he said bbiab at 23:05 and haven't seen him since [22:46:51] hmm [22:47:08] he made some zero-rated changes but im not sure how to test them [22:52:14] mm [22:53:30] need me to find him? [22:53:45] tfinc i just sent him a text - is he in the office? [22:53:53] he's in today just not at his desk [22:54:05] right now [22:54:29] ok he hasnt responded to me yet so i think i might just revert his changes and deploy everything else [22:55:42] i'll give him another minute or two [22:55:58] i took a quick stroll and didn't see him [22:56:04] bet he's grabbing coffee [22:56:34] don't wait on him. he can deploy it after [22:59:39] ok i reverted his change in the deployment branch [22:59:41] running scap [23:01:26] time to go bed.. gnite all :) [23:09:53] YuviPanda: you here? [23:10:13] heatherw: yup [23:11:01] so, i don't know who made the beta W for the mobile beta, but i matched that (regarding covering too much W, etc) [23:11:23] heatherw: norm made it [23:11:25] jorm* [23:11:29] hah [23:11:32] norm [23:11:34] :D [23:11:43] colloquy does that to me all the time [23:11:57] tfinc: [23:11:59] oops [23:12:11] but yeah, he's the one who made it [23:12:13] tfinc: what do you think of the W's YuviPanda is referring to? [23:12:22] i have no clue what your talking about [23:12:24] whats the background [23:12:32] looking for the bug one sec [23:12:56] https://bugzilla.wikimedia.org/show_bug.cgi?id=35577 [23:13:06] ahh .. this [23:13:10] tfinc: https://minus.com/mbrpnLZKWy/ [23:13:12] Beta W for the Android app [23:13:12] is how it looks in the app [23:13:14] and the screen [23:13:21] (there are two images there) [23:13:55] all of those look like we have a censor bar [23:14:02] i see that i *did* end up giving you the smaller launcher, too [23:14:03] yeah [23:14:30] maybe i will go with a light bar on the darker search bar icon [23:14:49] heatherw: mozilla does a nice job of this https://play.google.com/store/apps/details?id=org.mozilla.firefox_beta [23:14:57] by just making it off centered [23:15:09] ahh cool [23:15:21] i was trying to match, but i can try something else, too [23:15:42] i think our current W beta icon breaks down when you magnify it for an icon [23:19:34] awjr: preilly is back [23:19:38] ok scap just finished [23:19:46] I was at lunch [23:19:50] all changes (except for preilly's) are live [23:20:02] awjr: why not mine? [23:20:22] preilly: didnt know how to test them and you weren't here to say they whether or not they were ok [23:21:10] awjr: what change? [23:21:32] preilly: https://gerrit.wikimedia.org/r/#change,4112 [23:21:47] (thinks a nice red β for the beta) [23:22:06] awjr: please push that change [23:23:45] preilly im getting the change back on test now [23:24:04] what do tfinc and YuviPanda think of a β? [23:24:33] heatherw: i'd have to see it on icon form. how universal will that be ? [23:24:38] tfinc: The puppet work is stalled for the moment [23:24:52] tfinc: jerith is going to try to work on the deb tomorrow night [23:24:58] that is something i do not know [23:25:54] tfinc: I'm also working on creating the puppet configuration around the new deb [23:26:19] preilly: that change is live on testwiki [23:26:28] lemme know if it looks ok and i'll sync-file it [23:26:50] heatherw: do note that the app will also be named 'Beta', so that might help. [23:27:58] awjr: it looks okay — please sync it [23:30:03] preilly syncing now [23:30:58] heatherw: how would you feel about presenting the mobile redesign during the monthly metrics and analytics meeting ? [23:31:22] ooh! scary and fun! [23:31:29] a short coupe of minutes would do [23:31:39] i think it would be great to have you showcase it [23:31:55] were trimming down the engineering portion of the meeting to 3-4 short presentations [23:32:07] i am good at being short :) [23:32:14] preilly done [23:32:15] and i think the mobile re-design is the best one for us [23:32:19] heatherw: you in? [23:32:23] yup! [23:32:36] tfinc: yay! [23:32:45] want to talk about the whole thing including parts that aren't implemented? [23:33:00] lets sync up about it later today [23:33:06] awjr: cool — http://en.zero.wikipedia.org/ looks right [23:33:15] okay tfinc perfect, thanks [23:33:16] preilly: bitchin [23:33:53] awjr: are you going to have someone clear the varnish cache? [23:34:03] preilly is it necessary? [23:34:13] awjr: I think we at least need it for the zero related changes this week [23:34:24] maplebed: do you mind clearing the varnish cache? [23:34:32] awjr: I'm asking maplebed to do it [23:34:32] preilly ok - i wonder if we should wait til the deployment funkiness gets resolved [23:34:37] a lot of hosts are out of diskspace [23:34:44] awjr: hmm [23:34:49] LeslieCarr and tim are coping with it in #wikimedia-tech [23:34:53] New patchset: Jdlrobson; "adapt select menu font size for smaller devices" [mediawiki/extensions/MobileFrontend] (contact-us-redesign) - https://gerrit.wikimedia.org/r/4146 [23:34:55] swish swash "clear varnish kaboom!" [23:36:18] preilly: the varnish cache is cleared. [23:36:32] !log cleared the varnish cache [23:37:01] tim's re-running scap now - it looks like they might have resolved the issue [23:39:21] tfinc jdlrobson: shall we talk about contact us? [23:40:50] from my perspective all that is left to do is get the form saving the new fields and doing error handling/success handling in the same form rather than redirecting [23:41:07] than adding some ajax enhancements to do the same error/success handling [23:41:22] jdlrobson: cool - i still need to build out the logic for mail routing and whatnot [23:41:24] (then probably some extra work to remove any jquery dependancy) [23:41:52] and am curious how we should handle the page redirection for the category that doesn't display the form [23:42:01] how does it currently work? does it save to a database? [23:42:12] which category was that? [23:42:13] jdlrobson currently it does nothing [23:42:30] well, it just blindly sends you to a success page [23:42:35] really? eek [23:42:49] so people on wikipedia mobile might be using the feedback form without saving anything? [23:42:57] jdlrobson: did you mean the existing feedback form or where i'm at in building the backend for the new one? [23:43:03] both [23:43:11] right now, on the current feedback form, it writes the mssage to a wiki page [23:43:17] ok cool [23:43:17] w [23:43:25] well can't we still do that for a first release of contact us [23:43:32] we can do fancy email routing later on [23:43:51] better to start capturing more useful information and storing it on wiki pages [23:43:58] that's fine with me, pending tfinc/phillinje [23:44:32] Yay [23:44:36] jdlrobson: the one category that is weird is 'article feedback - factual error' [23:44:40] Android 4.0.4 for Galaxy Nexus [23:44:56] that's the one that is supposed to redirect to a wiki page rather than show the form [23:45:17] yeh that is a bit odd [23:46:01] we still capture things on the wiki page though right? [23:46:04] no [23:46:14] well that doesn't seem very usable [23:46:54] * jdlrobson notices the contact page has changed some more [23:47:24] so what does it need to email? [23:47:35] jdlrobson the specs are still not very clear on the design page, but i think philinje had said that when you select that category, it should auto-redirect you after 5s or something and also display a notification to the user with the link. if, before redirect, the user selects a different category, then the redirect would get cancelled [23:47:37] this section form has changed a lot [23:47:40] basically it tells people that they are complaining to the wrong place [23:47:57] so as i understand it now we are now dealing with several forms [23:48:01] inside sections [23:48:24] jdlrobson one of the problems with that particular feature is that i dont think we know whether or not every wiki project has a similar page, let alone what the URL is for that page on all projects [23:48:31] it is no longer a button with a menu [23:48:39] it's just a list of choices [23:48:53] preilly: http://www.mediawiki.org/wiki/Mobile_design/Contact [23:49:19] we need to think in terms of non-javascript browsers as well [23:49:32] preilly: when the form is supposed to email someone the comment, it's supposed to send the user's email address, their comment, and user-agent [23:49:42] ++ jdlrobson [23:49:43] jdlrobson: agreed [23:49:52] my preference would be to serve all the forms on one page under separate headings [23:50:03] and then using the toggling code from the rest of the mobile site [23:50:11] http://www.mediawiki.org/wiki/File:Mobile_Contact_A1.png [23:50:16] which i think is what that is doing [23:51:06] mostly. it changes the page+title from Contact us to whatever is chosen [23:51:14] and if I click technical problem i get a form which sets an input 'subject' to 'technicalproblem' general I get a form which sets an input 'subject' to 'general', article feedback I just get text with links [23:51:44] jdlrobson: we could set it up so that the what happens when a particular category selected is configurable with one of two possible actions - redirect or send email [23:52:14] that will keep behavior flexible for us depending on which wiki project plus keep the extension usable by other people [23:52:32] philinje: they are discussing the mechanics of the contact us page [23:53:53] if I submit a form I'd expect to either be redirected back to the form or back to the page I was on [23:54:10] If I got redirected to the factual error page that would be a bit confusing [23:54:24] I'd prefer to click contact us > report factual error and be told there that I need to go elsewhere [23:54:32] jdlrobson: agreed [23:55:27] i think if we did a first iteration that just saved any contents of a form to a wiki page we can update that to do other actions instead e.g. mail someone [23:56:25] jdlrobson so in essence replicate existing functionality but with categories? we would need to take out the email address submission box - or just do nothing with that particular data [23:56:27] you don't get a form when you select factual error [23:56:46] yes awjr exactly [23:56:56] heatherw: according to the specs you still get a form [23:57:00] heatherw: so with factual error I'd expect clicking on the heading I get some copy text explaining the situation [23:57:47] right now (in theory) you go straight to this, yeah? http://www.mediawiki.org/wiki/File:Mobile_Contact_F2.png [23:57:54] no form first [23:57:54] jdlrobson: where abouts are you based? [23:58:11] london Reedy [23:58:23] do you mean you want to change that text, jdlrobson ? [23:58:42] so heatherw how do I get to this page? [23:58:43] heatherw: according to the specs "Article feedback - factual error - reveals a link in the comment box: http://en.wikipedia.org/wiki/Wikipedia:Contact_us/Article_problem/Factual_error in the language versions listed below, and if the language does not correspond to one of these pages, to this email address: info-XX@wikimedia.org, where XX is one of the language codes listed below, or EN if none of those languages provides a match" [23:59:00] well, that is wrong! :P [23:59:04] sorry [23:59:08] thought it had been updated [23:59:09] no worries [23:59:11] i will fix it [23:59:44] heatherw: so in terms of http://www.mediawiki.org/wiki/File:Mobile_Contact_F2.png I'm puzzled by 2 things 1) how do I get to this page in the first place - is it via a link in the contact page?