[00:02:24] binasher is there a downside to that approach? i'm trying to think if we'd need to change anything else in software [00:02:38] MaxSem: passing by reference isn't needed in this case but, I added it in a new patch set anyways [00:02:58] +1'd [00:03:08] * MaxSem kicks gerrit-wm [00:03:42] awjr: can you approve https://gerrit.wikimedia.org/r/#change,4379 [00:03:54] awjr: actually, i don't think it would work [00:04:03] :( [00:04:10] whynot? [00:04:33] since the desktop view link takes you to non-m wikipedia with &useformat=desktop [00:04:55] but you'd get redirected to m since the cookie hasn't been changed yet [00:05:29] this is obnoxiously challenging for such a seemingly trivial thing to do... [00:06:24] tfinc: i've got those MS folks coming in tomorrow, around 4:30 if anybody other than me's interested in seeing their metro goodies :) [00:06:42] binasher is it possible to make an acl that looks at the cookie AND the request query string? [00:06:45] brion: ask lindesy, heather, or brandon [00:06:51] jorm: --^ [00:07:02] mrh? [00:07:07] cannae. [00:07:14] well, maybe. i'll have to see. [00:07:14] np [00:07:15] jorm: Microsoft metro designers are coming in [00:07:30] or at least some of the people who worked on it [00:07:36] jorm: brion can tell you more [00:07:48] or at least folks who want us to make our app for windows 8 and are showing us the style :) [00:08:36] preilly approved. what happened to the bot? [00:08:42] preilly merged, also [00:08:58] * awjr pokes gerrit-wm [00:08:59] awjr: that is a zero thing bot isn't checking that yet [00:09:03] ohho [00:11:44] YuviPanda: http://www.geonames.org/img/charts/ws-credits8163-NhBKEPcu6P86DGxC7SYivA.png <-- Geo traffic [00:11:47] MaxSem: --^ [00:12:02] nice spike [00:12:06] tfinc: wow, [00:12:10] binasher it should be possible to make a squid acl that checks cookie an url query string, right? [00:12:17] we've used up 78% of our queries [00:12:19] but also quickly dropping [00:12:21] * tfinc goes to buy some more [00:12:43] awjr: i don't think its actually a good idea, since m. isn't intended for all url types [00:12:59] MaxSem: looks like 'oooh, let me play with this!' type initial look [00:13:02] binasher: what do you mean? [00:13:07] YuviPanda: exactly [00:13:11] i like to see things! brion [00:15:05] edit links, etc. if i have two wikipedia windows open, and get the mobile cookie, then click an edit link in the other window, i don't want it to open the edit page in the m domain [00:16:24] binasher i see what you mean but that usecase could also be acl'd, right? i mean, as it is now, if you try to edit a page on your mobile device, you go to the desktop version on .m to edit it [00:17:16] i guess my point is, that problem already exists in production [00:17:40] having to come up with a different acl for every case where we wouldn't want this new redirect to trigger doesn't seem like a good path to follow [00:17:57] tfinc: http://www.applestocks.net/wikipedia-drops-google-maps-in-favor-of-openstreetmap-for-use-in-its-mobile-apps/ [00:18:01] again we're a 'company' [00:18:01] sigh [00:18:08] things are already way more complex on the php side [00:18:21] binasher i agree, but that problem *Already* exists in production [00:18:42] tfinc: disregard last link, that was a splog with real source http://www.cultofandroid.com/8092/wikipedia-drops-google-maps-in-favor-of-openstreetmap-for-use-in-its-mobile-apps/ [00:19:22] i think the majority of people who are clicking on 'mobile view' are doing it on mobile devices that we're not detecting. i wish i had numbers to cite, but i would imagine that very few people on desktops are switching to mobile view, unless they're testing. [00:19:27] in my opinion desktop should only ever be visible on en.wikipedia.org and mobile should only ever be visible on en.m.wikipedia.org [00:19:54] +1 [00:19:58] preilly, binasher, in that case we'd need an acl to detect useformat= in the query string and redirect the request appropriately [00:20:12] it might also make sense to record to UA of the user when they click on mobile view [00:20:13] YuviPanda: now imagine being Jay and having to mange that for all of our communications ;) [00:20:20] preilly agreed [00:20:47] tfinc and i had chatted about that last week but im not sure of a sensible way to do that [00:20:49] tfinc: I'm guessing a lot of people think 'Wikipedia' is a company which writes this huge encyclopedia [00:20:53] would it make sense to step back a bit [00:21:04] like remove all of this logic [00:21:16] and attack it again with a clean slate [00:21:32] tfinc: do we try to get these people be right or let it go? [00:21:55] awjr: what is the context of, "tfinc and i had chatted about that last week but im not sure of a sensible way to do that"? [00:22:02] HeadAsplode: we focus on what were good at … dev .. not managing comm [00:22:03] preilly perhaps, but we still face the same useformat problem if we go back to how things were before we started down the stickycookie road [00:22:13] preilly: sorry - context was in regards to recording UAs [00:22:18] tfinc: by 'get these people be right' I mean do we poke jay about it or let it go [00:22:22] not send emails ourselves [00:23:18] awjr: what's the useformat problem? [00:23:51] lets not spend our time cleaning up the internet [00:23:52] let it go [00:24:03] ok [00:24:28] binasher using "useformat=mobile" ni the query string to toggle the view, so you'll see the mobile view on non- .m site if you do en.wikipedia.org/wiki/article?useformat=mobile [00:25:02] so en.wikipedia.org/wiki/article?useformat=mobile should redirect to en.m.wikipedia.org/wiki/article [00:25:37] just handle it like a canonical redirect [00:25:45] preilly redirect in php? [00:25:57] yeah [00:26:07] yes [00:26:10] that would work [00:26:10] that should be easy? [00:26:15] yeah it is [00:26:36] should we do the same thing for the action=edit cases as well? [00:26:46] like action=edit, action=history … not sure if there are others [00:27:58] it looks like useformat=mobile is ignored in those cases? [00:28:14] binasher correct, in those cases you will see the desktop version [00:30:23] so from the php side, don't redirect to .m. if there's a useformat=mobile and an action defined [00:30:45] i'm not sure what the correct behavior should be on mobile site [00:31:31] preilly would there be a problem if someone had useformat=mobile but shouldDisplayMobileView() === false and then got redirected to desktop site? [00:31:36] or vice versa? [00:32:16] binasher you mean like if someone's on the mobile site but then tries to edit an article? [00:39:00] awjr: how would that happen? [00:39:27] er wow that made no sense [00:39:35] ok if someone had useformat=mobile but action=edit [00:41:34] YuviPanda: can you pass me a link to 1.1.1 apk .. i want to send it to upload [00:42:01] tfinc: signed one? [00:42:04] yes [00:42:15] the exact same one you sent to the market [00:42:21] ok [00:43:33] tfinc: http://dl.dropbox.com/u/8768784/Wikipedia-v1.1.1.apk should be it [00:43:35] double checking [00:43:39] yeah, so useformat=mobile would trigger a redirect to the canonical mobile version of the url, unless there isn't such a thing (i.e. there's an action defined) [00:43:53] yup [00:43:55] that's it [00:43:57] tfinc: ^ [00:49:37] thanks. http://dumps.wikimedia.org/android/ is up to date now [00:49:46] cool :) [00:52:57] this release, saved pages is going to drive me nuts :D [00:53:11] YuviPanda: 1.1.1 or 1.2 ? [00:53:15] 1/2 [00:53:17] err [00:53:18] 1.2 [00:53:31] i'm trying to figure out the way I can get it to work with the least amount of code changes. [00:54:23] tfinc: ideally, i'd like to 'relegate' offline save pages functionality to someone else (Read It Later, etc). Thoughts? This would be on a much future release, wtih lots of advanced warning. [00:54:38] YuviPanda: thats a no go [00:54:44] but why [00:54:49] we can't build external dependancies [00:54:51] tfinc: ha ha [00:54:58] there are other apps that do this as their core competence [00:55:04] negative ghost rider [00:55:26] tfinc: we can let people pick whoever they want. [00:55:37] we're not having external dependencies. [00:55:53] if people want offline functionality, they will have an app that provides it for them. Why not integrate with those? [00:58:03] other services like evernote actually charge you to save things offline [00:58:08] http://www.evernote.com/about/premium/ [00:58:33] tfinc: there will be plenty of free ones. Android makes sure the choice is with the user, and not with the app developer [00:59:03] see https://readitlaterlist.com/ for a free one [01:00:12] YuviPanda: i know that list and i'm happy to integrate with more of them [01:00:21] tfinc: 'make the best app to consume (and eventually contribute to) wikipedia' is what we should be building. Saved pages is something we should leave to other apps. [01:00:32] YuviPanda: but unless we have a compelling reason i'm not going to remove a feature that people are actually using [01:00:53] tfinc: hmm, what would actually convince you to remove it? [01:01:04] YuviPanda: wouldn't you like to know ;) [01:01:09] indeed [01:01:21] ha ha ha [01:01:34] it's our last major platform specific code [01:01:57] and we're doing crappily what other apps are doing awesomely *and letting us use them* [01:02:14] why not integrate and free up time to work on awesomer stuff? [01:04:13] tfinc: our iOS app has 'save page' and 'save to read it later' right next to each other. I bet people would use RIL (or similar service) more than the actual save page. If they need to be reading stuff offline, they will already have an app. [01:04:25] if i had stats that showed a minority of users were using our native saving in favor of external services then we could have a conversation about it [01:04:58] i'll be happy to set up instrumentation to see how many people use 'save page'. [01:05:07] and ofcourse, that'll take about 9 months to set up servers for [01:05:24] given that a) we don't have that and b) people use the current functionality easily without any account level features. i'm not going to take it away unless I'm convinced that they don't need it [01:05:46] in summary - show me the numbers :) [01:06:05] how do you suggest I do that? [01:06:28] I can look into third party services that let me do analytics, and then watch as the community comes to my home with pitchforks [01:06:55] hmm, is there a way of using our pre-existing analytics stuff via an API? [01:07:08] YuviPanda: ask diedrik .. he'd know [01:07:30] time for me to head out [01:08:14] sigh [01:15:17] aaaah [01:15:28] i think i know a way to collect numbers on this particular thing [01:15:40] but first I need to make it work :D [01:36:38] YuviPanda: you might be able to abuse the clicktracking extension for that sort of means [01:36:46] Reedy: link? [01:37:04] Reedy: my other thought was that since i'm switching to the API, I can pass an extra parameter that goes unused, but is logged [01:37:14] that assumes that all API GETs are logged, which might not be true [01:37:20] but am guessing that'll be quite easy to measure too [01:37:22] https://en.wikipedia.org/w/api.php "Track user clicks on JavaScript items." [01:37:42] wooo, that's pretty much *exactly* what I need :) [01:37:49] err [01:37:56] https://www.mediawiki.org/wiki/Extension:ClickTracking [01:38:00] or [01:38:01] maybe not [01:38:09] it requires an edit token, which means I need to have a logged in user :( [01:38:35] Err [01:39:47] Edit token for anon is +\ [01:39:54] ah [01:40:02] sweet [01:40:42] Anons can edit with the api if they can edit via the gui [01:41:06] that never hit me. And I don't remember reading this in API:Editing [01:41:07] :( [01:41:21] Reedy: is there documentation on 'proper' usage of this? [01:41:30] Does Roan count? [01:41:30] ;) [01:41:49] I suspect users of the api are just even more likely to be logged in [01:42:08] i'm sure that someone can kidnap Roan and ransom the knowledge in his brain [01:42:10] There aren't going to be many casual users using the APi [01:42:21] agreed [01:42:55] AFTv5 uses ClickTracking (among others) [01:44:05] Reedy: where does data collected by this go to? [01:44:18] a database table [01:44:24] is that publicly visible? [01:44:36] nope [01:44:41] might be replicated to toolserver [01:44:44] ah [01:44:46] ok [01:45:19] Reedy: I think this should help me find the 'numbers' to (hopefully) kill Saved Pages in a few releases :) [01:45:21] thanks! [01:45:53] Reedy: is there anything you don't know? :) [01:46:11] Haha. Pi to a million places? ;) [01:47:00] i'm sure you could find a way around that :P [01:47:02] If you poke Dario/Howie they might be able to advise a bit better how they get access/use the data [01:47:14] 1415926535897932384626433832795028841971693993751058209 7494459230781640628620899862803482534211706798214808651 3282306647093844609550582231725359408128481117450284102 7019385211055596446229489549303819644288109756659334461 2847564823378678316527120190914564856692346034861045432 6648213393607260249141273724587006606315588174881520920 9628292540917153643678925903600113305305488204665213841 4695194151160943305727036575959195309218611738193261179 [01:47:14] 3105118548074462379962749567351885752724891227938183011 9491298336733624406566430860213949463952247371907021798 6094370277053921717629317675238467481846766940513200056 8127145263560827785771342757789609173637178721468440901 2249534301465495853710507922796892589235420199561121290 2196086403441815981362977477130996051870721134999999837 2978049951059731732816096318595024459455346908302642522 3082533446850352619311881710100031378387528865875332083 [01:47:16] 1415926535897932384626433832795028841971693993751058209 7494459230781640628620899862803482534211706798214808651 3282306647093844609550582231725359408128481117450284102 7019385211055596446229489549303819644288109756659334461 2847564823378678316527120190914564856692346034861045432 6648213393607260249141273724587006606315588174881520920 9628292540917153643678925903600113305305488204665213841 4695194151160943305727036575959195309218611738193261179 [01:47:16] 3105118548074462379962749567351885752724891227938183011 9491298336733624406566430860213949463952247371907021798 6094370277053921717629317675238467481846766940513200056 8127145263560827785771342757789609173637178721468440901 2249534301465495853710507922796892589235420199561121290 2196086403441815981362977477130996051870721134999999837 2978049951059731732816096318595024459455346908302642522 3082533446850352619311881710100031378387528865875332083 [01:47:17] 1415926535897932384626433832795028841971693993751058209 7494459230781640628620899862803482534211706798214808651 3282306647093844609550582231725359408128481117450284102 7019385211055596446229489549303819644288109756659334461 2847564823378678316527120190914564856692346034861045432 6648213393607260249141273724587006606315588174881520920 9628292540917153643678925903600113305305488204665213841 4695194151160943305727036575959195309218611738193261179 [01:47:17] 3105118548074462379962749567351885752724891227938183011 9491298336733624406566430860213949463952247371907021798 6094370277053921717629317675238467481846766940513200056 8127145263560827785771342757789609173637178721468440901 2249534301465495853710507922796892589235420199561121290 2196086403441815981362977477130996051870721134999999837 2978049951059731732816096318595024459455346908302642522 3082533446850352619311881710100031378387528865875332083 [01:47:20] 1415926535897932384626433832795028841971693993751058209 7494459230781640628620899862803482534211706798214808651 3282306647093844609550582231725359408128481117450284102 7019385211055596446229489549303819644288109756659334461 2847564823378678316527120190914564856692346034861045432 6648213393607260249141273724587006606315588174881520920 9628292540917153643678925903600113305305488204665213841 4695194151160943305727036575959195309218611738193261179 [01:47:20] 3105118548074462379962749567351885752724891227938183011 [01:47:22] ... [01:47:24] that's not a million [01:47:47] Reedy: i emailed diederik [01:47:55] as tfinc suggested [01:48:08] preilly: You missed the 3. ;) [01:48:18] and the rest of the million digits [01:48:19] YuviPanda: http://pastebin.mozilla.org/1555565 [01:48:34] still not a million [01:48:36] prepend the 3. [01:48:49] still not a million [01:49:04] damn it [01:49:04] http://www.piday.org/million.php [01:49:31] :D [01:49:36] "Computation timed out" on WA [01:49:45] :D [01:51:19] WA? [01:51:39] Reedy: ^^ [01:51:58] WolframAlpha [01:52:46] Reedy: ah [02:33:44] YuviPanda: so, what's the status on WCCCE? making reservations? [02:33:53] Amgine: i… don't know [02:33:55] i'd love to come [02:34:04] but i'd have to wait for response from tfinc or sumanah [02:34:41] Okay. The registration for the conference apparently costs money, and it will increase in price on April 12. [02:35:13] Only $25 more [02:36:22] I can't even find the dang registration page. [02:37:05] Amgine: getting into the conference is going to be easy. However, since all the teleportaiton devices in the world no longer work, getting me to Canada is going to be difficult [02:37:13] https://apps.cs.ubc.ca/WCCCE2012/frontpage.jsp [02:37:40] let's all chant: REEDY KNOWS EVERYTHING [02:37:49] 3rd result on google [02:37:50] srsly [02:38:03] chanting needs no reason [02:38:46] that actually dies for me, Reedy. [02:38:58] Weird [02:39:04] Are you on their network? [02:39:37] no, but I do use noscript. [02:39:52] apps.cs.ubc.ca seems a complete fail for this browser. [02:41:00] * Reedy blames Canada [02:41:10] Amgine: anyone of the students applying for GSoC? [02:42:25] I *hope* so. I have been pushing them to apply. I would love to see a GSoC to build the iOS/RIM or /other [02:43:01] RIM? Pffft [02:43:09] [02:43:11] * Mono[Away] was going to say that [02:43:45] No one I know has a Blackberry. Hopefully that will soon be true about Android. Some things should just die. [02:43:57] There's interesting stuff happening at RIM atm: executives flying out windows, but developers being bought up. [02:44:10] Doesn't sound like a CEO who is going to take apart the company. [02:46:04] Amgine: today is the last day, I guess [02:46:15] Android is adding millions of new users a day, it's not going anywhere for a while [02:46:18] O RLY? [02:46:19] Mono[Away]: hopefully that will soon be true of iOS. [02:46:20] * YuviPanda runs [02:46:31] Mono[Away]: 4.0 is *waaay* more polished than 2.x [02:50:18] YuviPanda: but most users are still on 2.3 [02:50:24] which makes the platform suck [02:50:27] for now [02:50:33] things get better :) [02:50:45] it's like the IE6 transition period [02:50:45] I read an article speculating that even Google would abandon it [02:50:48] :P [02:50:53] I hope not. [02:50:59] Except upgrading isn't even supported. [02:51:08] people buy new phones [02:51:11] Supposedly, to compete with the iPad and iOS platform, [02:51:36] they will launch 'Google Play' - a polished, Google-branded experience [02:51:52] 'and Android will become the cheap and open source option for the new generation of dumbphones [02:51:53] they have, and it is mostly slightly better crap than Android market [02:51:57] but sitll crappier [02:52:04] while also keeping their new glasses around [02:52:11] ah [02:52:20] I did not realize today is bash-the-google day [02:52:25] :) [02:53:01] At least I don't bash them for their privacy policy [02:53:16] YuviPanda: the article is at http://articles.businessinsider.com/2012-04-02/tech/31272944_1_the-android-android-marketplace-android-brand - it's an interesting read regardless [02:54:14] Just did. [02:54:17] speculation. [02:54:43] I, for one, prefer reading and writing code over speculation :) [02:55:50] of course. but it's a big deal for the industy [02:55:53] *industry [02:56:03] btw, who decided to go with MapQuest for tiles? [02:57:55] YuviPanda: ^ [02:58:48] Mono[Away]: I think it was a collective decision. Openstreetmaps.org didn't want the traffic, and MapQuest was okay with it, so we're with mapquest for now [02:59:49] Mono[Away]: aude plans on helping us set up our own tile server soon. [03:29:08] Which reminds me, aude, what kind of server would be needed for that? [03:47:28] Amgine: IIRC we were waiting on some gluster storage to come online with labs [03:47:32] and then git happened [03:47:41] woohoo, saved pages now work [03:47:43] sortof [03:47:49] \o/ [03:48:19] Amgine: we're in the process of decoupling the *data* of the mobile site and the app [03:48:24] while sharing more of the code [03:48:25] YuviPanda: Storage of the maptiles is different from generating maptiles. [03:48:38] Amgine: yes, but they are dependent on each other [03:48:52] i am setting up a small personal server of mine with tilestache, just for serving mbtiles [03:48:57] am sure that won't work for the wikipedia app :) [03:49:27] Yah, but I work with a host which has no throttle on bandwidth, but the storage on the server is limited. [03:50:16] We have some third party measures of 250GB transfer rates. [03:50:25] (rare peaks, but still...) [03:54:17] Amgine: :D [03:54:28] Amgine: the entire size of my tileset is about 5MB so I guess i'm good [03:55:50] [08:53:06] jdlrobson, do you see something on https://www.mediawiki.org/wiki/Special:Code/MediaWiki/114240 ? :P [08:53:16] * jdlrobson looks [08:54:26] looks like i'm closing a section before opening it ? :) [08:59:22] this function confuses me a lot MaxSem [08:59:47] yeah [09:00:14] gotta make a final push today to make it last a few weeks more:) [09:02:29] mmm so I'm not seeing where that div should be closed [09:55:59] MaxSem: I can't work out what's going on with those sections [09:56:12] I'll fix it later [10:00:54] much appreciated! giving me headaches.. [10:46:10] New patchset: Siebrand; "Fix some breaks." [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/4392 [13:49:52] New patchset: Jdlrobson; "hide clear search button when no text in input" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/4401 [13:49:53] New patchset: Jdlrobson; "hide references on touchstart or clicking outside the reference box" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/4402 [13:49:53] New patchset: Jdlrobson; "prevent jump when toggle" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/4403 [13:49:54] New patchset: Jdlrobson; "improve smoothness of expansion transition" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/4404 [13:49:55] New patchset: Jdlrobson; "on touchstart hide references instantly" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/4405 [13:49:56] New patchset: Jdlrobson; "prevent automatic text resizing for landscape mode" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/4406 [13:49:56] New patchset: Jdlrobson; "prevent page zooming when rotating to landscape" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/4407 [14:23:58] MaxSem: I've built new debs in a new PPA with much nicer packaging magic and less insane versioning. [14:24:04] The new PPA is https://launchpad.net/~jerith/+archive/vumi-snapshots [14:37:57] whee [14:39:26] MaxSem: The copyright stuff in vumi-wikipedia says "Praekelt Foundation and individual contributors". Do you know what WikiMedia does about that kind of thing? [15:00:56] ajerith, https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/core.git;a=blob;f=CREDITS;h=d0c4623d1a2ab63073b5a5ee6a0cd515a101db5e;hb=refs/heads/master [15:01:21] also https://en.wikipedia.org/wiki/Special:Version [15:02:59] MaxSem: Cool, thanks. [15:04:07] MaxSem: If and when you see preilly, can you point him at the new PPA? [15:04:23] sure [15:05:05] Everything installs fine on my VM, but that's the VM I built the debs on. [15:05:50] The vumi and vumi-wikipedia package names have changed, since they're more app-written-in-python than python-library. [15:06:21] Other than that, it's just version numbers and metadata and stuff that's changed. [15:07:00] That's a snapshots PPA, so we can pull updates from the dev versions of whatever to chuck in there as needed. [15:07:20] Once we have a proper vumi 0.4 release I'll build a releases PPA. [15:07:51] But now it's hometime. :-) [15:24:45] New patchset: Jdlrobson; "when initialising beta opensearch check whether search is already focused" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/4424 [15:24:46] New patchset: Jdlrobson; "prevent page zooming when rotating to landscape" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/4407 [16:27:49] New patchset: MaxSem; "Yet another fix for div fun. Looks like everything started with r114240" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/4432 [16:57:11] * YuviPanda looks around [16:58:12] preilly, https://launchpad.net/~jerith/+archive/vumi-snapshots [16:59:19] MaxSem: thanks! [16:59:33] MaxSem: do you know where the redis PPA is? [16:59:44] no idea [17:00:00] preilly, http://dpaste.com/727848/ [17:00:23] greetings all [17:00:30] lets do our standup [17:00:36] * tfinc notes the jon and arthur will be missing [17:00:45] MaxSem: ah, okay — thanks, for relying the message [17:01:03] * YuviPand_ checks logs [17:02:39] preilly: Ping? [17:04:01] i heard sonar again [17:04:09] jeroid: he's in a call, give him a few minutes [17:04:47] Cool, thanks. [17:06:06] jeroid, I've passed everything to him [17:06:26] interesting. connection works fine whenever tfinc or brion are speaking and kills itself when preilly is talking. [17:06:27] hmmm [17:09:36] MexSem, preilly: you want rwky/redis for the redis PPA. [17:10:12] MaxSem: Thanks muchly. [17:10:58] YuviPanda: what? [17:11:08] preilly: your voice kills my internet [17:11:11] jeroid: okay [17:11:11] :) [17:11:17] YuviPanda: NOT OKAY [17:11:56] It is probably scared and/or intimidated. [17:12:03] I'll calm it down, should be fine [17:12:19] I'm pretty much out for the evening, but I may check in later if there's a suitable gap in the proceedings. [17:12:27] YuviPanda: i saw diedriks response [17:12:39] tfinc: and Reedy found me a way to actually measure things :D [17:12:43] woot! [17:12:46] do tell [17:13:10] tfinc: api has a action=clicktracking [17:13:16] yes! [17:13:24] and since were a mw extension .. we can use that [17:13:33] plus since the feature requires internet [17:13:41] and save pages also requires internet [17:13:45] we can definitely use that [17:13:47] lolz [17:13:48] i like this [17:13:53] i'll be slipping it into the beta [17:14:03] don [17:14:04] t [17:14:08] we have to check with legal [17:14:21] Www [17:14:22] i'll slip it into a branch then. [17:14:27] jeroid: okay [17:14:29] actually .. let me talk with howie to see what they did for the other projects [17:14:30] after other beta stuff is done [17:14:31] Oops. [17:14:40] so that we can see what we have to tell our users [17:14:44] but assuming thats fine [17:15:11] I'd *definitely* want to get this out for 1.2, so either I can convince myself save page is useful or convince you that it is not :) [17:15:33] we can 1) add the analytics to see current usage … useful in its own right [17:15:52] 2) add more ways to save [17:15:54] 3) measure [17:15:57] 4) re-asses [17:16:17] yes, this would indeed be useful data. [17:16:23] reassess* [17:16:27] reassess [17:16:46] YuviPanda: that way we give users more options and can migrate them over [17:17:14] yes. Once we have the data we could figure out what we could do. [17:17:19] Rather than speculating [17:17:24] OMG WIKIPEDIA IS SPYING ON US ONEONEONE [17:18:01] just name the js file da_man_at_da_nsa.js [17:18:09] tfinc: I also have another way to measure saved pages, even without using clicktracking [17:18:22] it's definitely a hack though, but it'll work. But only for saved pages. [17:19:45] since i've moved to using the API for saving, I can just pass an extra parameter that'll be ignored by the API, but can be used for analytics [17:23:51] YuviPanda: I've taken your vimrc lead and disabled the arrow keys :D [17:24:05] jeebus .. the internet is still talking about our OSM move [17:24:09] :D [17:24:10] thats so yesterdays news [17:24:16] that's so two weeks ago news [17:24:23] we need to distract with something new and shiny [17:24:30] like a fresh UI [17:25:08] tfinc: the comments on techcrunch were quite nice.. [17:25:35] mostly about how it all still belongs to google [17:25:36] but sigh [17:25:49] people will read anything but think exactly what they want to think [17:26:22] its just noise [17:26:56] true [17:27:04] and honestly … anyone saying OSM looks like crap should look at http://stamen.com/ [17:27:04] also https://github.com/wikimedia/WikipediaMobile/issues/202 [17:27:09] you can't do any of that with google maps [17:27:20] all of their designs are done with OSM data [17:27:36] yes, devgeeks went 'waaah' after looking at it and is moving one of his phonegap apps off gmaps into leaflet :) [17:27:46] actually http://mapbox.com/ is sic [17:27:48] all the noise on the internet is generated by people who don't have anything better to do with their time [17:27:51] and one of their designers is going to be creating the design for our tiles [17:27:57] woah [17:28:00] so it gives a disproportionately poor impression [17:28:07] map box is beautiful too [17:28:15] because all the interesting and cool people are busy doing interesting and cool things [17:28:44] but really its the flexibility and choice with OSM [17:28:52] you get none of that with google maps currently [17:29:05] tfinc: do we have a timeline on our tileserver [17:29:05] and map box is a great example of how you can make OSM look fantastic [17:29:08] ? [17:29:54] tfinc: Foursquare is still willing to share tiles with us once we get tile server hardware provisioned [17:29:57] YuviPanda: i'm been working with ops to get the hardware purchased. lots of rt tickets open for that [17:30:13] sweet [17:30:18] erik needs to approve the last batch [17:30:25] OSM TAKING OVER THE WORLD WOOHOO. [17:31:38] tfinc: are we going to engage with apple fanboys at all? (https://github.com/wikimedia/WikipediaMobile/issues/202)? [17:32:37] yeah, i saw that last night [17:33:24] there are some valid points in there [17:35:54] plus were not doing well review wise so his comments aren't isolated noise [17:35:56] you guys should take the iphone seriously - 'apple fanboys' constitute a sizable percentage of dedicated smartphone users [17:36:33] Rolken: iOS Safari users compromise the majority of our users [17:36:36] Rolken: app traffic is tiny [17:36:45] but i agree that we need to fix the reported issues [17:36:56] that's because the Wikipedia Safari experience is better than the Wikipedia app experience [17:37:16] okay, that came out wrong [17:37:26] I was going 'how are we going to engage with them' rather than 'are we going to?' [17:37:31] ahh ok [17:38:03] do we work on making things more platform specific and tuned to the particular platform's styles? [17:38:28] yes, yes, very yes :P [17:38:57] (<-- iOS developer) [17:39:01] Rolken: ah :D [17:39:05] greetings Rolken ! [17:39:08] Rolken: hello! [17:39:08] hello! [17:39:11] is this your first time in here ? [17:39:14] yeah [17:39:24] Rolken: welcome :) [17:39:41] Rolken: excellent … as an iOS dev what would you suggest us attacking first to make it more iOS friendly ? [17:39:54] curious to get your thoughts vs others [17:40:35] well I took a look through the codebase yesterday and I'm not sure exactly how things get achieved within the context of that PhoneGap stuff [17:40:55] Rolken: think of it as a web app, except you can call into ObjC whenever you want [17:41:05] but the general theme is that a lot of things could stand to be more responsive, 'friendly', and consistent with general iPhone UI [17:41:20] things like- animations on screen pushes, when you tap the settings icon [17:41:34] scrolling doesn't feel like typical iOS scrolling [17:41:55] and for some odd reason, if, say, you set the page scrolling and tap on an icon, the icon will flash but won't respond with an actionsheet until the scrolling stops [17:41:55] Rolken: on which version of iOS does it feel unnatural? [17:42:06] Rolken: keep in mind apps like amazons kindle that don't follow ui convention but work just fine [17:42:07] I'm on 5.1 [17:42:15] jerith: are you still around? [17:42:27] animations can certainly be improved; we've not put a lot in yet. little things can be nice though. :D [17:42:30] well yeah there are apps that establish their own conventions [17:42:34] the Facebook app did a marvelous job with that [17:42:52] yup. so keep those in perspective before diving 100% in apple ui land [17:42:54] the settings dialog could be redone with native widgets on both android and ios, might be nice. but we haven't been in a huge rush to do it. [17:42:55] but responsiveness and intuitivity are key on iOS [17:42:56] but we can do much better then now [17:43:00] yes [17:43:23] other things we try to make look ios-y like the toolbar and use of native action sheets for expanded options on share and open [17:43:24] Package python-redis is not installed. [17:43:24] Package python-twisted is not installed. [17:43:26] Package python-tz is not installed. [17:43:27] Package python-wokkel is not installed. [17:43:27] Package rabbitmq-server is not installed. [17:43:44] Oops. [17:43:47] I mean, like the settings push-style page, that's not establishing new conventions, it's just behaving sort-of-like a typical screen push interface but weirdly [17:43:48] Sorry, for the spam [17:43:53] are we still fetching the sitemap data via ajax when opening the settings dialog? that'd be slowing us down [17:44:01] brion: nope [17:44:05] brion: it's shipped along. [17:44:08] oh good, that's a help then [17:45:02] Rolken, in part everything has to balance between making a good platform-independent app and making good platform integration [17:45:15] so there's always tradeoffs, but we can move those tradeoffs around over time [17:45:57] +1 [17:46:39] I think you're setting the bar too far toward platform integration as it stands though - I think that's something Firefox does really well actually [17:47:03] all the functionality is consistent between platforms, but they still adapt to the UI conventions of each platform at the same time [17:47:23] *nod* [17:48:01] and iOS is such a big platform that I think you'd be better served trying to get iOS-specific developers to build an app that works like the app on other platforms, but isn't hamstrung by cross-platforming [17:48:50] if you haven't, you should look at some of the other Wikipedia apps for iPhone [17:49:06] I use Articles, which does some wonderful things with the content [17:49:34] like intelligently reparse the infoboxes into a tappable icon that pulls up a table view [17:50:18] and mobile wikipedia looks really sparse on the iPad (especially the new one) [17:50:34] straight-up desktop wikipedia works pretty well there actually [17:51:47] Rolken: so one of the things we're trying to do is add APIs to mediawiki itself to support the things we want to do. [17:52:42] Rolken: so I guess we'll be able to add a 'tablet specific' formatter soon, which does much less stripping out than the current mobile view [17:52:46] MaxSem: tfinc ^ [17:53:58] Rolken: going back, what do you think would be a good first step towards making things more iOS friendly? [17:55:35] LIFI! [17:56:00] YuviPanda, gimme teh spec [17:56:04] tfinc: hehe, nice to know that your internet is spottier than mine :P [17:56:09] well, the #1 thing to appreciate about iOS is that the platform has succeeded through its design principles [17:56:14] YuviPanda: i had a quick chat with howie. he doesn't see any issues with click tracking saved pages [17:56:20] YuviPanda: no i just need to get legals ok [17:56:26] cooool [17:56:36] any time someone buys an iPhone instead of Android, they're voting for design over specs [17:56:38] but since we won't care about the individual pages saved … shouldn't be a problem [17:57:22] so- you don't have to embrace typical iPhone design conventions, but you have to understand them in order to break them properly [17:57:25] tfinc: I'd like to record that as well if legal doesn't object. [17:57:30] they're voting for emo! :P [17:57:40] were not recording what pages people save [17:57:53] why would we need to do that? [17:57:59] it's hard to boil that down to a single sentence except to say that the little things matter [17:58:10] because i'm a privacy hating data hog :P [17:58:15] troll [17:58:18] ;) [17:58:27] preilly: a bit [17:58:29] and iPhone users want an enjoyable experience more than they want effective access [17:59:27] anything that moves should animate, anything they touch should respond instantly, and everything else should be dropped if necessary in the pursuit of surprise and delight [17:59:38] that's the iPhone Way :P [18:00:08] (also, if you started an iOS project, I would contribute to it) [18:00:17] Rolken: :) [18:00:59] jerith: I've created a new VM called vumi [18:01:00] Rolken: its all going to have to balance with our priorities. articles which i agree is the most impressive third party app gets 0.007% of our total traffic [18:01:06] jerith: everything seems to have installed [18:01:33] preilly: \o/ [18:01:46] Rolken: pre 3.x the code base was all object c and nightmare to manage [18:02:01] I agree tfinc, but I think it's different when you put an official app out that now is representing the Wikipedia brand [18:02:06] agreed [18:02:14] you need to be able to stand 100% behind that app [18:02:31] (also, why was it a nightmare to manage?) [18:03:15] it was an inherited code base for the majority of us that crashed, was unstable, and generally didn't do us any favors [18:03:38] preilly: can tell you more since he worked with it more then anyone else to do some fixes [18:03:49] IIs there a Blackberry app? [18:04:06] if I were you, I would put up some kind of initiative website that overtly courts mobile developers to help build the future of Wikipedia [18:04:09] jerith: there is a playbook port [18:04:31] I mean, you get hella donations through charity drives every year [18:04:42] if what you need is mobile dev expertise, ask for that [18:05:57] +1 on "anything that moves should animate, anything they touch should respond instantly, and everything else should be dropped if necessary in the pursuit of surprise and delight" :) [18:06:42] I suddenly thought of it when I saw a million cousins with bbs. [18:07:50] part of it is also that I think just throwing up an encyclopedia app should only be the beginning - right now you're basically reliant on Google for an interface, but imagine if you had, like, the "Wikipedia zoo app experience," in which you provide an interactive exploration of animals (as an arbitrary field of study) [18:08:08] building out of the whole trove of information [18:08:16] and giving people new ways to interact with it [18:08:38] Rolken: our roadmap, IIRC, is to eventually have ways people can contribute back from the mobile, rather than just consume. [18:09:01] Rolken: so our focus as a whole for this year isn't that. its getting contributions into the site. i agree that improving the reader experience is integral but thats not our focus right now. others are welcome to contribute of course but contributions are key for us [18:09:04] +1 YuviPanda [18:09:39] contributions are at the core of any wikimedia project [18:09:44] and mobile should be no different [18:10:19] so wether its images, gps, micro tasks, content curation, etc … we need to do those so that mobile isn't a second class citizen within the wikimedia world [18:10:24] as its that way now [18:10:28] and it has to get fixed [18:10:39] I don't disagree- the point I was trying to make wasn't "you should build this starting tomorrow," but rather "so many possibilities will be opened by mobile technology and mobile should be a core focus" [18:10:56] +1 [18:11:16] mobile first architecture :D [18:11:25] and I think the elephant in the room is that HTML/JS/CSS isn't quite there yet on mobile [18:11:50] (or at least on the iPhone, I guess I shouldn't speak for other platforms) [18:11:58] Rolken: that depends on the platform [18:12:12] the exact some app on the android market is doing fantastically well [18:12:19] same* [18:13:09] people are less picky on android though ;) [18:13:16] yeah they are :P [18:13:33] we iPhoners are prissy primadonnas :) [18:13:38] ROFL [18:13:58] :)) [18:15:07] also we *do* have some bits that honestly look more androidy (the settings screen, the back icons) [18:15:15] yup [18:15:18] those can still be made more ios-look-n-feeling [18:15:55] Rolken, any complaints on the toolbar other than response times & having it show on screens where it possibly shouldn't? [18:16:17] the Settings back button flat out doesn't work sometimes [18:16:22] not sure what's going on there [18:16:23] that's built specifically for ios (though also will be used on blackberry playbook) [18:16:25] interesting [18:16:39] crap, of course i left all my iDevices at home today :P [18:16:53] brion: let me know if you need to borrow one [18:17:44] other than that, it's not so much 'problems' as a holistic notion of how things work on iOS [18:17:46] nah i'll check it out later if i can't get the simulator running [18:17:56] this is the nuts-and-bolts of my handwaving: http://watchingapple.com/2009/11/a-closer-look-at-iphone-transition-animations/ [18:18:22] brion: if you're going to be working on the app code, remember that there's going to be a biggish merge (API Move) soon. [18:18:38] should find jon on Monday and make him review it before merging [18:18:47] ooh fun [18:18:55] brion: no more dependency on MobileFrontend [18:18:56] :) [18:19:02] plus we get to use the new beta styles for content [18:19:12] I should also take a profiler to it [18:19:26] Rolken, ooh that's a nice link. will help in tuning the css animations once we add em [18:19:27] YuviPanda: keep in mind that those new styles won't go live for another week [18:19:38] tfinc: they don't need to [18:19:45] we're sharing code, but we're decoupled. [18:19:49] love it [18:20:03] so MF deployments will no longer break the app. [18:20:13] the way it should be [18:20:30] YuviPanda: aren't you glad i got max to come in to work on this ;) [18:21:02] :D [18:21:32] Project WiktionaryMobile - Nightly builds build #46: SUCCESS in 9.3 sec: https://integration.mediawiki.org/ci/job/WiktionaryMobile%20-%20Nightly%20builds/46/ [18:21:33] sheaclare: Fixes Android browswer --> Wiktionary VIEW bug [18:23:26] YuviPanda, does the ios app crash in the simulator for you too? i get a SIGABRT in main() :P [18:23:39] brion: master? [18:23:52] yeah [18:24:05] no... [18:24:16] weird [18:24:22] also, in the 'specific things to watch for' category, there are two conventional scroll deceleration rates on iOS, rapid decel for content (see: Safari pages) and low decel for lists and so forth (see: lists of music in Music) [18:24:32] well i'll fiddle with it tomorrow. i suspect small touch targets might be an issue with the back buttons [18:24:46] brion: yes, I think we need to figure out a way to make the targets bigger [18:24:53] I'd suggest using rapid decel on the Wiki pages and slow decel on settings etc [18:25:04] Project WiktionaryMobile - Nightly builds build #47: SUCCESS in 8 sec: https://integration.mediawiki.org/ci/job/WiktionaryMobile%20-%20Nightly%20builds/47/ [18:25:05] pfhayes: Fixes Android browswer --> Wiktionary VIEW bug [18:25:16] Rolken, scrolling is left up to ios/webview to handle, but because we've got those fixed toolbars we're using overflow scrolling for the content section [18:25:28] in theory that ought to behave like anything else, and if it isn't that's apple's fault :( [18:27:32] YuviPanda: brion : would it be easier if i organized a project around iOS improvements or would you prefer to have it be more adhoc for this part ? [18:28:01] i'm fine with adhoc but a project wouldn't hurt [18:28:15] at the least, let's make sure we get issues into the bug tracker [18:28:31] I think we should organize and make specific bugs that need fixing, and track them [18:28:31] and fix them per release [18:28:31] rather than go ad hoc [18:28:52] YuviPanda: k, i'll spin one up [18:28:57] \o/ [18:30:37] Rolken: I'm thinking that a 'good first step' would be to fix the tap-area-size issues and make the settings page a bit more iPhoney. [18:31:18] brion: you can set the 'decelerationRate' property to UIScrollViewDecelerationRateNormal or UIScrollViewDecelerationRateFast on any scrollview - each UIWebView in turn has a scrollView property (I have no idea how this intersects with the PhoneGap stuff though) [18:31:38] vi [18:31:40] oops [18:32:00] Sounds good YuviPanda :) [18:32:21] YuviPanda: did you see @Mistcrafter tweet [18:32:22] ? [18:33:15] tfinc: I responded to him from search. Looking at response [18:33:19] Rolken, basically we have one giant webview. the content is in a
inside that, with its own scrolling, while the top and bottom toolbars don't scroll. it's kinda funky :) [18:33:33] Rolken: we've webview scrolling off :) [18:33:54] tfinc: responding to him [18:37:03] Project WiktionaryMobile - Nightly builds build #48: SUCCESS in 7.1 sec: https://integration.mediawiki.org/ci/job/WiktionaryMobile%20-%20Nightly%20builds/48/ [18:37:04] * hy.cheng: added progress spinner when loading audio [18:37:04] * hy.cheng: added in-list spinner show and hide functions in chrome.js [18:48:04] tfinc: brion once the gerrit dust settles, we should also move there. While also accepting pull requests from Github. We can figure out details later, but I'm thinking end-april for this. Thoughts? [18:48:21] sounds doable [18:48:34] YuviPanda: with 1.1 out the door i'm fine with that. mail out a migration plan to mobile-tech and we can discuss [18:48:47] there's been some talk of a github pull request -> gerrit bridge, i don't know how easy that is :) [18:48:58] brion: that would be super nice [18:48:59] but we can certainly take them from there and bridge them manually if need be [18:49:13] yeah [18:49:19] but really we need to keep how easy its been for volunteers to send us pull requests [18:49:21] we can't lose that [18:49:27] yep [18:49:57] with git-review installed, submitting to gerrit is super easy, but that's not default [18:50:39] yes, am sure we can figure out an automatic/semi-automatic way [19:25:47] tfinc, around? [19:42:59] MaxSem: he is out at lunch [19:43:33] Project WiktionaryMobile - Nightly builds build #49: SUCCESS in 6.7 sec: https://integration.mediawiki.org/ci/job/WiktionaryMobile%20-%20Nightly%20builds/49/ [19:43:34] * pfhayes: Making order of menu items match wikipedia [19:43:34] * pfhayes: Adding icon for share [19:44:31] Project WiktionaryMobile - Nightly builds build #50: SUCCESS in 7.3 sec: https://integration.mediawiki.org/ci/job/WiktionaryMobile%20-%20Nightly%20builds/50/ [19:44:32] * pfhayes: Making order of menu items match wikipedia [19:44:32] * pfhayes: Adding icon for share [19:52:03] back from lunch [19:52:06] MaxSem: sup [19:52:47] tfinc, what shall I do next? [19:53:11] MaxSem: are you all caught up with the work that YuviPanda needed from you? [19:53:36] no further requests from him so far [19:53:42] YuviPanda: --^ [19:53:50] tfinc: yes, he was able to add the stuff we wanted (sections=all) [19:53:54] woot [19:54:13] MaxSem: and were all caught up with what jon needs? [19:55:10] yes, I think. last thing he wanted me to do is fix divs in output, which I did yesterday/today. he haven't seen my last commit though [19:56:01] MaxSem: nice. and you have all the changes that preilly needed for vumi ? [19:57:37] there's some more work to be done, but I really really want to see a review of what has already been done. je/rith will probably have time this weekend [20:12:43] MaxSem: ok [20:13:00] MaxSem: whats the status on getting GPS store/retrieval into production ? [20:13:47] so far I've been waiting for prototype app using it [20:14:01] it needs to be tried out [20:14:33] and are we finally getting that as part of 1.2 ? [20:15:11] I think Yuvi does not want it [20:19:59] thats fine. 1.2 is about decoupling from MF [20:20:05] and your api is not part of that [20:21:35] MaxSem: the rest of your contact has things like api throttling & access tokens which aren't really a priority for us [20:21:50] OAuth & Open ID would be fun :) [20:22:37] but thats going to take some coordination with the platform team [20:23:18] tfinc, there seems to be problems with the new wikipedia ios app [20:23:27] THO|Cloud: what are you seeing? [20:23:31] Project WiktionaryMobile - Nightly builds build #51: SUCCESS in 7.2 sec: https://integration.mediawiki.org/ci/job/WiktionaryMobile%20-%20Nightly%20builds/51/ [20:23:32] * pfhayes: Fixing onPageLoad, adding afterPageLoad [20:23:32] * pfhayes: Now expands first section only [20:23:33] * pfhayes: Updating timeout, adding better explanation [20:23:33] * pfhayes: Updating comment [20:23:43] I've not downloaded it myself but the reviews on the app store tfinc [20:23:48] quite a few 1 stars [20:23:55] about to download it now [20:23:59] Thehelpfulone: did you see our discussion about that earlier today? [20:24:06] ah nope [20:24:14] yeah, we've been discussing the feedback [20:24:23] and i'm going to spin up a project about polishing up the app [20:25:33] for example tfinc, when I click on the share button on the pane at the bottom [20:25:38] there's a delay opening up the options [20:25:47] Project WiktionaryMobile - Nightly builds build #52: SUCCESS in 6.6 sec: https://integration.mediawiki.org/ci/job/WiktionaryMobile%20-%20Nightly%20builds/52/ [20:25:47] * yuvipanda: Make default language for search be the system's default locale [20:25:48] * yuvipanda: Added migration code for PhoneGap database issues [20:25:48] * yuvipanda: Updated CHANGELOG and bumped version number [20:25:49] * yuvipanda: Added comments clarifiying data migration [20:25:49] * yuvipanda: Added clarification on language fix [20:25:50] * yuvipanda: Move WebKit settings to proper location. [20:25:50] * yuvipanda: Bumped version number for iOS [20:25:50] * jdlrobson: Fixed #35431 [20:25:51] * jdlrobson: Fixed sections bug [20:25:52] * jdlrobson: Some style fix according with styling guidelines [20:25:52] * niklas.laxstrom: Translation updates from translatewiki.net [20:25:53] * brion: bug 35710 - about page links now open in external browser [20:25:53] * brion: Bug 35734 - Update iOS splash screen images [20:25:53] * brion: Bug 35741 - iOS save/share menu should offer to open page in Safari [20:26:03] Thehelpfulone: please put in those bugs on bugzilla [20:26:06] as i'll be triaging them [20:26:08] ok [20:26:12] it'll be easier then sifting through the reviews [20:26:19] thanks inadvance [20:26:25] np [20:26:36] what version # is this tfinc? [20:26:48] might need to put an extra number on bugzilla [20:27:07] Project WiktionaryMobile - Nightly builds build #53: SUCCESS in 8.2 sec: https://integration.mediawiki.org/ci/job/WiktionaryMobile%20-%20Nightly%20builds/53/ [20:27:07] * pfhayes: Fixing onPageLoad, adding afterPageLoad [20:27:07] * pfhayes: Now expands first section only [20:27:08] * pfhayes: Updating timeout, adding better explanation [20:27:09] * pfhayes: Updating comment [20:27:12] Thehelpfulone: let me add one for iOS [20:27:17] well [20:27:20] its really 1.2 [20:27:32] platform iOS [20:27:35] the about suggests 3.1.1 [20:27:52] err [20:28:02] yeah, i'm thinking about how to manage that [20:28:06] let me add 3.1.1 of rnow [20:28:11] ok [20:28:54] Thehelpfulone: added [20:29:11] thanks [20:33:12] MaxSem: later today i'll have some api upload questions coming your way. but in the mean time take a look at http://www.mediawiki.org/wiki/Mobile_support_in_MediaWiki_core and let me know if your comfortable in picking up some of the first tasks [20:33:20] i still need to rev that page [20:33:38] preilly: do you need any help on zero from max ? [20:45:21] LIFI [20:45:37] MaxSem: did my last messages get through ? [20:45:46] yup [20:47:12] tfinc, "Move DOM Parsing mechanism into MediaWiki core - mid-May, 2012" - I already started a discussion on this in wikitech-l, but it quickly died [20:47:22] guess I'll have to Be Bold :) [20:47:33] don't pay attention to the dates on their .. their just place holders [20:47:41] be bold! [20:47:45] and then poke brion ;) [20:48:48] mmm, basically I wanted to move HtmlFormatter into core ASAP. MF will retain its descendant MobileFormatter for now [20:49:42] this way, we will be able to move page extracts functionality out of MF cause it doesn't really belong there [20:51:15] tfinc, I can start working on "Have current DOM parsing mechanism of MobileFrontend make greater use of memcached and the native parser cache" [20:51:38] it's really simple, but requires some stats [20:52:57] MaxSem: go for it and coordinate with preilly and awjr as needed [20:53:20] i know that we'll need your help with the upload work but the designs and workflows for that are not ready yet [20:54:30] tfinc, note that it already uses parser cache just like the desktop version. if "use parser cahe to store DOM transformation results" is what was intended, this neeeds tight interaction with platform, as while it will make mobile data persist in cache for longer, it will impact overall cache hit rate negatively [20:54:44] parser cache is huge but still finite [20:57:04] awjr is not around to discuss this stuff [20:58:24] he'll be back on tuesday [20:59:22] preilly, can we discuss this stuff? [21:03:01] preilly isn't at his desk. i'm betting he's at lunch [21:47:56] tfinc: you bet correctly [21:51:29] MaxSem: are you still around? [21:53:21] preilly, yes [21:54:31] can we co-ordinate our efforts regarding http://www.mediawiki.org/wiki/Mobile_support_in_MediaWiki_core ? [21:55:23] MaxSem: yes [21:55:28] MaxSem: I'm in a meeting [21:56:45] okay, let's be short. what parts of MF do you intend to work on for the next couple of days so that we don't create merge conflicts for each other? [21:57:13] preilly, you can email me or something if I will be gone by the time you can reply [22:13:51] New review: Reedy; "(no comment)" [mediawiki/extensions/MobileFrontend] (master); V: 1 C: 2; - https://gerrit.wikimedia.org/r/4392 [22:13:54] Change merged: Reedy; [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/4392 [22:14:30] preilly: MaxSem are there any changes you want to make to http://www.mediawiki.org/wiki/Mobile_support_in_MediaWiki_core before i mail it out to wikitech ? [22:14:47] tfinc: I think it's okay as is [22:15:05] preilly: what should we include about your recent skin and output buffer work ? [22:15:10] concur [22:15:52] i'm going to add a line for it in the timeline [22:15:59] added [22:43:27] tfinc: not sure what to say about the skin [22:43:37] tfinc: sorry, I missed that question [22:43:38] preilly: i already put in a line about. just refresh [22:44:39] tfinc: ah [22:45:06] tfinc: that did the trick [23:00:43] brion: preilly : take a look at http://etherpad.wikimedia.org/MobileFrontendCore and let me know if you want anything else in the email [23:02:28] * tfinc ponders what to mention about john du harts work [23:02:38] whee [23:03:38] sounds good so far [23:03:55] man i wish our etherpad worked on https :P [23:03:56] k [23:04:23] brion: why can't it ? [23:04:57] no idea, it just borks up and says you have to reconnect every few secs [23:05:14] tfinc, probably should clarify that it's moving 'mobileaction's not actions in general [23:05:27] though that's another thing to consider :) [23:05:33] done [23:07:01] preilly: this is going to wikitech .. do we really need to mention that were on free node ? [23:07:59] tfinc: I guess not [23:08:32] tfinc: FTFY [23:09:01] thanks [23:09:12] MaxSem: any other changes that you want to add ? [23:10:58] mmm [23:11:04] probably not [23:11:18] k [23:14:39] sent [23:14:54] tfinc: cool [23:22:35] Ryan_Lane: want to look at these packages on the vumi vm? [23:22:52] Ryan_Lane: I guess you are working on the cisco hardware [23:27:23] YuviPanda: i'm walking through all the US reviews now and breaking them up into categories [23:27:32] ok [23:36:33] ok .. US triage done … time to check out the UK [23:38:59] YuviPanda: if only more of the reviews could belike this "The app works perfectly now, especially as the last update destroyed it! As someone who uses Wikipedia mobile a lot, seriously guys this is the best update so far. The layout has changed but it's more efficient and faster. Don't hesitate because of the last update, you will be very happy with the latest one :)" [23:39:14] clearly someone who had 3.1 .. waited … and found everything working on 3.1.1 [23:39:19] tfinc: triaged into where? [23:39:56] i have them in an evernote page. will put them up after I'm done moving through english speaking countries [23:40:53] cool [23:44:22] I always just blindly update all applications [23:45:36] tfinc: we need to find out how to access action=clicktracking data [23:45:57] tfinc can get access to it, he has root ;) [23:45:59] am about done with making Language Links use the API, then can move on to the clicktracking. [23:46:08] YuviPanda: ask diedrik where it goes [23:46:15] tfinc: Reedy says it goes into a database. [23:46:18] and yes .. i likely have access to it [23:46:21] cool [23:46:24] YuviPanda: lots of things got into databases [23:46:33] * Reedy puts YuviPanda into a database [23:47:24] Look I'm in a database [23:47:45] no, *I* am in a database [23:47:48] Reedy put me there [23:48:26] reedy is big brother [23:48:35] always watching. [23:48:45] always putting people into databases [23:49:27] Why am *I* in a database? [23:50:35] : I think we should organize and make specific bugs that need fixing, and track them [23:50:39] YuviPanda: you are in the office, not in a database. [23:51:03] we need to find out how to access action=clicktracking data [23:51:08] also, whois just threw this up [23:51:13] preilly is connected on moorcock.freenode.net (TX, USA) [23:51:15] wait [23:51:18] how did that happen? [23:51:49] will the real YuviPanda please stand up ? [23:52:18] Michael John Moorcock (born 18 December 1939, in London) is an English writer, primarily of science fiction and fantasy, who has also published a number of literary novels. [23:52:37] BRAAAAAIIIINS [23:52:49] * ZombiePanda eats Reedy's brains [23:53:20] know what works aginst ZombiePandas? [23:53:24] bourbon. [23:53:53] Do you need a lighter too? [23:54:59] ZombiePanda: here is my first triage pass : http://etherpad.wikimedia.org/Wikipedia-iOS-3-1-1-issues [23:55:13] now its time to see which ones i can reproduce [23:57:32] tfinc: according to roan clicktracking goes into /var/log/aft on emery. [23:57:34] not a database [23:57:38] and i guess you have access to it [23:57:42] so can set it up [23:57:48] binasher: http://i.imgur.com/kx1vr.jpg [23:58:05] ZombiePanda: is a feed that the udp2log system receives ? [23:58:14] yes [23:58:45] tfinc: this was mentioned on the staff channel, I just pinged you there. [23:59:05] ZombiePanda: then we'll need to engage diedriks team to add the filter. new filters have a tendency of bringing the system to its knees [23:59:21] ZombiePanda: if you give me the pattern of the data i can mail him [23:59:28] or at least a description of it