[00:07:39] okay, fix pushed [00:08:02] [Commons-iOS] montehurd opened pull request #37: Straight to uploads if previous credentials found (master...straightToUploads) http://git.io/Iy-mSg [00:08:17] fix confirmed [00:08:17] Sorry MaxSem which fox [00:08:21] Fix [00:08:28] Oh ipad :) [00:08:30] whee [00:08:31] device-specific CSS [00:08:46] K checking as well [00:09:08] still not seeing it, but maybe need to wait for RL cache to expire [00:09:50] you need fresh *HTML* ;) [00:10:26] there it is [00:10:39] im seeing it now [00:11:05] lol Maryana - is http://bug-attachment.wikimedia.org/attachment.cgi?id=11789 your phone? [00:11:16] looks bloodthirsty:) [00:11:31] lol [00:11:40] yeah, haha, it's from a comic that my friend did [00:11:48] i figured it would ward off iphone thieves :) [00:12:03] i totally forgot about it when i took that screenshot [00:12:14] sorry for subjecting the bugzilla community to horror comics [00:12:24] so can we confirm https://mingle.corp.wikimedia.org/projects/mobile/cards/478 ? [00:12:41] K I checked ipad, UA for opera and I see [00:12:53] ooh, didn't realize we deployed it today [00:12:54] It :) [00:12:56] * Maryana checks [00:13:31] lovely! [00:16:01] jcmish_, Maryana: everything looking ok in prod now/ [00:16:42] awjr: Yessir [00:17:09] Much better Maryana ? [00:17:36] yep :) [00:17:50] ok sweet thanks everyone - im gonna take off. hopefully see you all tomorrow [00:18:05] Feel better awjr [00:18:14] thanks jcmish_ :) [00:18:21] I'm gonna drop too folks [00:18:44] [Commons-iOS] brion pushed 3 new commits to master: http://git.io/lS8rcw [00:18:44] Commons-iOS/master c682df4 Monte Hurd: Added i18n for the login button text.... [00:18:44] Commons-iOS/master 6f85d23 Monte Hurd: Auto login if previous credentials found... [00:18:45] Commons-iOS/master f0218d7 Brion Vibber: Merge pull request #37 from montehurd/straightToUploads... [00:19:31] [Commons-iOS] brion pushed 1 new commit to master: http://git.io/kqxoTw [00:19:31] Commons-iOS/master 8486e9e Brion Vibber: bump to 0.18 [01:03:37] mhurd: expect bugs coming your way now that i have the latest iOS version running [01:03:51] will do :) [01:03:52] mhurd: biggest one will be how badly the interface blocks when you trigger a refresh [01:04:14] agreed [01:04:39] mhurd: why do we block on all operations within the UI but the account tab ? [01:05:36] when the add media button is pushed? [01:06:09] New review: Jdlrobson; "am breaking this into smaller commits to make review easier. Please review it's dependencies though!" [mediawiki/extensions/MobileFrontend] (master) C: -2; - https://gerrit.wikimedia.org/r/56351 [01:07:21] 1) from my uploads pull down from the top most images to trigger a feed refresh [01:07:35] 2) try to tap config, add image, anything but 'Account' [01:07:42] 3) wait... wait ... wait [01:07:48] New patchset: Jdlrobson; "Make the universe explode by making a desktop AND mobile skin called Minerva" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/56351 [01:07:48] New patchset: Jdlrobson; "Rewrite footer how skins do it" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/58426 [01:07:49] New patchset: Jdlrobson; "Rename scriptUrl to wgScript" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/58443 [01:22:03] mhurd: --^ [01:22:23] its weird - mine still seems to respond [05:01:39] New patchset: Jdlrobson; "RL: Add modules and module styles to page as modules found" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/56887 [05:50:11] New patchset: Jdlrobson; "Rename scriptUrl to wgScript" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/58443 [05:50:11] New patchset: Jdlrobson; "Make the universe explode by making a desktop AND mobile skin called Minerva" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/56351 [05:50:11] New patchset: Jdlrobson; "Rewrite footer how skins do it" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/58426 [05:50:12] New patchset: Jdlrobson; "Rewrite menu generation" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/58458 [05:50:12] New patchset: Jdlrobson; "Cleanup Skin language and variants" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/58459 [10:59:41] New patchset: Zfilipin; "Updated Ruby gems" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/58485 [13:42:43] [android-commons] yuvipanda pushed 1 new commit to master: http://git.io/BSBc9A [13:42:43] android-commons/master 1252755 YuviPanda: Remove results of {{subst:unc}} when adding categories... [13:43:25] Project Android-Commons (mobile) - Nightly builds build #142: SUCCESS in 46 sec: https://integration.wikimedia.org/ci/job/Android-Commons%20(mobile)%20-%20Nightly%20builds/142/ [13:43:25] yuvipanda: Remove results of {{subst:unc}} when adding categories [15:20:04] Email [15:20:32] hello Macfarl92 [15:22:03] Viber [15:23:59] Hello Yuvi panda [15:24:13] Hello Macfarl92 [15:24:16] how can we help you? [15:26:38] How can i contact you besides wikipedia [15:46:13] hey qgil [15:46:31] YuviPanda, "UX as close to official version as possible." [15:46:47] actually now that I read it I don't like "Topic / platform doesn't overlap with official projects." either. [15:46:49] sounds like cookie licking [15:47:13] qgil: yup, that neither. [15:47:33] qgil: 1. if you are building an app for android, what is the point of making it look exactly like the current app? [15:47:51] qgil: and if you are building for a platform that doesn't have a official version, then you would want to make it feel native to that platform, not copy from elsewhere [15:47:52] "UX as close to official version as possible. Adaptations to native look & feel specific to the OS platform are welcome." [15:48:19] "Stick to native conventions on the target platform as much as possible" [15:48:21] if the official one has a toolbar with 4 options you still want that [15:48:32] not at all, no? [15:48:38] UX = user experience, not just having same screenshots [15:48:52] YuviPanda, ok, the first point is feature parity [15:48:57] do you agree on feature party? [15:49:18] I just don't want to put artiicial restrictions on it [15:49:28] Open Source, Privacy Policy, Open Analytics, Community Support, Maintainer [15:49:31] should be good enough [15:49:34] why play Apple? [15:49:52] -1 to feature parity as well [15:50:12] The reasoning is [15:50:22] We don't hav resources to develop apps for all platforms [15:50:42] we don't even have resources to watch and support the development of multiple apps done by others [15:50:54] so the simplest pragmatic solutiuon is [15:51:22] If you want to have an official Wikipedia app in platform X it needs to be conceptually like a port of the official app [15:51:40] this way you don't mess with user expectations and the evaluation is simpler [15:51:43] so [15:51:45] first is [15:51:49] the 'official app' is a moving target [15:51:50] the API is public and anybody can buold apps using our data [15:51:59] currently it is 'stable' which is simply another word for 'dead'. [15:52:06] the apps team has decided to abandon PhoneGap and move to something else [15:52:16] would you expect people to scram and port all theirs once we port? [15:52:38] fundamentally, I don't think Official Apps should be treated any different from Volunteers' apps. [15:52:39] YuviPanda, I think this discussion would benefit from actual examples [15:52:47] qgil: what examples, exactly? [15:52:58] qgil: nobody has actually developed alternative apps that want to use the trademark [15:53:08] so anything we talk about is going to be hypothetical [15:53:10] one example: Nokia wants to contribute an official Wikipedia app for Windows Phone [15:53:17] and that is a real example [15:53:26] sure [15:53:37] so they would want to show off how apps are in their native environment (Windows Phone) [15:53:54] why should we ask them to feature match and UX match our android app? [15:53:57] yes, and this is what we have told them [15:53:58] our abandoned android app, even? [15:54:18] it's the easiest for everybody [15:54:32] qgil: there was a mailing list thread about it a few days ago, and me and brion responded to tfinc telling them to do it as long as they do *not* look at our official app for cues [15:54:41] qgil: I disagree qgil. Not policing at all is easiest for everybody [15:54:48] qgil: we should restrict based on license, ads, privacy. [15:54:52] not arbitrary features [15:54:53] take the Android app that is currently in Google Play, implement the corresponding features in Windows Phone and apply the Metro UI as Microsoft recommends [15:55:04] -1 again. [15:55:11] YuviPanda, well, you can ideed discuss this with Kul and Tomasz [15:55:26] btw, Nokia has no problems with this approach [15:55:26] I will do so when tfinc comes online today. [15:55:39] sure, but I don't want people looking at the Official app as a benchmark [15:55:47] it is *abandoned* by us. if we don't think it is good [15:55:51] we should *not* be pointing other people to it [15:56:03] qgil: and I strongly reccomended against them looking at the official app [15:56:08] qgil: and tfinc told me that is what he told them [15:56:10] I'll clarify. [15:56:10] from a user point of view that is the benchmark [15:56:26] if we think something better should exist, it should be first in the official Wikipedia app [15:56:43] qgil: there is nobody working on the official Wikipedia app [15:56:56] It is doenloaded every day from Google Play and App Store [15:57:08] "if we think something better should exist, it should be first in the official Wikipedia app " can not happen when nobody is working on it [15:57:11] no matter how many people download it [15:57:29] anyway, I'll talk to tfinc about it. I strongly reccomend removing those three points [15:57:39] YuviPanda, anyway, there was a problem and I helped solve it. If you can hep solving the problem better please by all means. :) [15:57:44] will do :) [15:57:48] Nokia was waiting for us, now the ball is in their court., [15:57:59] and they have a specific reference to work on. [15:58:25] qgil: that is scary. The email response from the app team (me *and* brion) was to completely disregard the native app [15:58:26] err [15:58:28] the official app [15:58:47] if you have a better reference that WMF Mobile Partners and Engineering teams are happy to approve as official one day, please pitch it to them. [15:59:12] I am against the idea of a reference at all [15:59:19] or an 'approval' that is engineering / features based [15:59:28] but I'll talk to tfinc and get it sorted :) [15:59:51] YuviPanda, an alternative is letting Nokia go wild, and then when they are done we might tell them. Mmm sorry but we don't have the resources to assess this app and decide whether it should be official. [16:00:37] "I talked to brion on IRC, and we concur. Our response should be something along 'Go for it guys, but do not use github.com/wikimedia/WikipediaMobile. We are not going to support that codebase or derivatives of it' " [16:00:46] YuviPanda, you are right that the current plan is not perfect, but is a plan nonetheless. You are welcome to impreove it. [16:01:15] YuviPanda, they are not using the PhoneGap codebase, they are doing 100% native WP & Metro [16:02:01] I really hope they don't implement saved pages [16:02:04] since we are goign to remove that [16:02:05] anyway [16:02:07] I'll talk to tfinc [16:02:08] about it [16:02:19] YuviPanda, is there a roadmap somewhere? [16:02:40] qgil: no, because there's nothing planned for the next 2 quarters. [16:02:58] nothing -> no features, no UX changes. [16:03:04] hence the major -2 for the 'UX requirement' [16:03:12] but if you know you will get rid of Saved pages of whatever feature it would be good to know [16:03:36] qgil: if you want I can make a list of 'essential features' that will be the minimum supported by the app team. [16:03:49] that would be useful [16:04:11] writing in the talk page now [16:04:15] and we could require "essential features" parity [16:04:41] qgil: +1 on that [16:06:27] edited: Parity of essential features with the official version. [16:06:27] UX integrated with the native OS, taking the official version as reference. [16:06:50] qgil: done [16:07:09] qgil: again, -1 on that :) [16:07:11] on the official version [16:07:15] on Android, for example [16:07:30] the official version uses completely outdated patterns at all parts of the UI. [16:07:42] taking it as a reference would be a bad idea and not something we want to encourage [16:07:49] I agree with the first part though [16:08:17] essential features: I need to take more than 2 minutes to come up with the list. [16:08:22] you need :) [16:08:43] qgil: the features that the official app has that are not there are: 1. Nearby 2. Saved Pages :) [16:09:34] 3. History [16:10:04] qgil: I'll get consensus for it from the rest of the app team before moving it to the main page from the talk page [16:10:22] removed , taking the official version as reference [16:10:53] wonderful :) [16:10:56] qgil: finally, "Topic / platform doesn't overlap with official projects. " [16:11:05] those essential features should be listed in the Wikipedia app pages, not in that list of Main criteria [16:11:17] qgil: really? why split it out that way? [16:11:24] qgil: those are essential features for 'approval' [16:11:31] i don't see how that makes sense in the app page [16:11:40] YuviPanda, because that is interesing information to anybody interested in the Wikipedia app, not only those porting it [16:11:48] we can link [16:12:03] also the official apps can be about Wiktionary etc, not only Wikipedia [16:12:19] hmm, right. makes sense. [16:12:37] I still don't like it, but I'll talk to tfinc about it [16:12:44] someone making a 'hebrew wikipedia' app, for example [16:12:49] need not implement 'language switching' [16:12:59] YuviPanda, every app page needs to have all the documentation ref that app. Ideally including a roadmap. [16:13:30] YuviPanda, if I'm working on a Wikiwhatever app it is normal that I take its documentation as a reference [16:14:15] at this point we're talking about personal preferences qgil :) [16:14:20] to start with, I think it is a bad idea to have a Wikipedia In My Language app [16:14:22] https://meta.wikimedia.org/wiki/Talk:Wikimedia_Apps/proposal#One_app_for_one_project [16:14:29] yeah, I -1'd that too [16:14:46] The fundamental thing is that I don't want to put blanket restrictions [16:15:08] it makes perfect sense to have a, say, "Hindi Wikipedia app" if your platform does not support Unicode rendering of hindi [16:15:14] and you have to build a image based rasterizer [16:15:15] YuviPanda, personal preferences? if the Wikipedia app has 5 essential features why do I need to know only by visiting https://meta.wikimedia.org/wiki/Wikimedia_Apps/proposal ? [16:15:16] for people to read it [16:15:29] qgil: no, i was talking about "YuviPanda, if I'm working on a Wikiwhatever app it is normal that I take its documentation as a reference " [16:15:53] and it would be a huge burden to expect those people to build a renderer for every language [16:15:58] beurocracy bad. [16:16:33] qgil: also, "Topic / platform doesn't overlap with official projects. " [16:16:39] if we require feature parity and then say you can't do what the official app does... [16:16:48] + is cookie licking [16:20:40] https://meta.wikimedia.org/w/index.php?title=Wikimedia_Apps%2Fproposal&diff=5382532&oldid=5382502 [16:21:42] YuviPanda, the principle is simple: if there is already an official WikiSpecies app for FirefoxOS we won't approve a second one. [16:22:15] in the same way that if there is already a Wiktionary project in Urdu we are not accepting a second one [16:22:50] that makes sense, but in that case "Topic / platform doesn't overlap with official projects. " should be reworded to represent that [16:23:19] YuviPanda, to me it reads the same... Can you find a a better sentence? [16:23:19] to me it sounds like "If there is a Wikispecies app for FireFox OS then we won't do anything related to Wikispecieis on ANdroid" [16:23:37] ok, leme see [16:23:45] *WikiSpecieis [16:23:47] gah [16:23:50] I can't spell [16:24:42] YuviPanda, "Your combination of Wikimedia project / mobile platform doesn't exist yet."? [16:25:00] well, that sounds the same too. [16:25:09] see my example about rendering, hindi and wikipedia before [16:25:23] I don't see what the problem is as long as we don't have two things with the same name [16:25:48] "There does not exist another official app for your platform with the same name"? [16:26:05] YuviPanda, so where is your patch? ;) I already had two attempts at writing a sentence that looks clear to me [16:26:17] my patch got reverted :P [16:26:18] if someone comes with an exception then they can explain it at mobile-l and we can agree on it [16:26:29] isn't that overhead? [16:26:31] YuviPanda, did your patch touch that sentence? [16:26:43] no because I didn't notice it. but I just said "There does not exist another official app for your platform with the same name"? [16:26:57] overhead would be to deal with the more probable attempts of building the third Wikivoyage app... [16:27:15] as long as they are all not called Wikivoyage [16:27:25] I think that is *good* [16:27:25] competition is nice! [16:27:31] If they are not called Wikivoyage then they are not official, and anybody can do whatever they want [16:27:39] 'Wikivoyage ' [16:27:59] I'm just applying the same principles Wikimedia pplies for "desktop" projects [16:28:10] an app is very different from a desktop project [16:28:16] since desktop projects run on our infrastructure [16:28:17] apps do not [16:28:39] official apps are published under the name of the Wikimedia Foundation anyway [16:29:06] YuviPanda, and I'd rather be dealing with this problem when someone wants to actually do one of such projects [16:29:22] me too [16:29:36] we have got 3 requests in 6 months for anything mobile app. I don't think this is overhead [16:30:19] we couldn't deal properly with previous requests because we didn't even have a list of main criteria. Now we have one. [16:30:22] so I think the problem is I wasn't involved in the discussion with tfinc. I'll talk to him and then get back to you. [16:30:32] yes, and it is not aligned with what we want to do, I think [16:30:39] patches welcoe :) [16:30:40] m [16:30:45] hopefully they won't be reverted :) [16:30:51] qgil: you should put a draft notice on it, I think. [16:30:59] I still ave to maintain a whole component [16:31:01] have [16:31:08] hmm? [16:31:58] hey mhurd :) [16:32:06] hey yuvi! [16:32:06] mhurd: do you know if brion re-submitted to apple? [16:32:16] mhurd: or are you guys doing bugfixes before re-submitting? [16:32:17] not sure - i think he was going to [16:32:36] hmm, okay [16:32:43] yes i believe quite a few commits were being appended [16:32:53] ah, nice [16:32:53] yay :) [16:34:02] mhurd: what IRC client are you on? [16:34:22] colloquy [16:34:36] mhurd: hmm, tab completion is nice :) you can hit y to complete to my name [16:34:41] it'll also notify me so that I'll look [16:34:51] YuviPanda: omg [16:34:58] YuviPanda: thanks :) [16:35:02] mhurd: also, try LimeChat. much better than Colloquy. I converted tfinc to LimeChat and he hasn't gone back :D [16:35:03] mhurd: :D [16:35:16] YuviPanda: will do! [16:35:21] mhurd: :D :D [16:37:47] hey brion [16:37:54] hello again :) [16:37:55] brion: are you submitting the iOS app to the app store as is? [16:37:58] brion: or making new commits? [16:38:21] tfinc had a complaint about the refresh speed, so i may try to fix that first :) [16:38:49] i hate that anything we submit to the store will be permanently 1-2 weeks behind development by the time it comes out [16:39:08] brion: i thought of a couple potential issues last night that the apple may be picky about... [16:39:29] shoot [16:40:04] brion: so, if we don't have it in the store by Monday, I'm going to push on with the watchlist notices for the Android app alone. [16:40:08] i've heard that they can bounce submissions if they have excessive output (ala NSLog) [16:40:18] brion: I'll be off in 2 weeks :( [16:40:23] ah yeah i've got a shitton of NSLog()s :) [16:40:33] YuviPanda: feel free to keep on trucking yes :D [16:40:38] also if submitted version number is < 1.0 [16:40:38] we'll catch up while you're away [16:40:39] brion: sweet :) [16:40:47] heh yeah [16:40:55] even though that's not yet exposed in the ui [16:41:01] brion: we should plan on what you gonna catch up while I'm away [16:41:04] wait does the app store show version number? [16:41:11] ya [16:41:22] yep. https://itunes.apple.com/us/app/wikipedia-mobile/id324715238 shows 3.3.1 [16:41:29] ok i'll have to bump it to 1.0 :) [16:42:48] mhurd: ok i'm adding some notes at http://etherpad.wikimedia.org/commons-ios-fixes [16:43:20] YuviPanda: so for watch list notices we'll need something server-side to push the notice, won't we? [16:43:26] brion: nah, not really [16:43:32] if you want i could replace all NSLog with WMLog, then create a "debug" scheme with a "don't log" setting which i'd check in WMLog. that way we could easily switch between a verbose output and release mode [16:43:38] brion: we just go through the community, and they edit a mediawiki namespace message [16:43:49] mhurd: that's exactly what i was thinking yeah [16:44:03] i've done it before, if you'd like i can take it on [16:44:29] YuviPanda: oh so like general broadcast notifications? [16:44:32] mhurd: go for it [16:44:34] brion: yeah, pretty much [16:44:41] but the patch would be pretty massive :) [16:44:49] spiff that's easy, do a periodic poll [16:44:49] but i can do it pretty quick [16:44:54] on android anyway :) [16:45:12] mhurd: yeah big patch easy fix :) [16:45:17] :) [16:46:39] brion: poll what? [16:46:51] brion: also seen https://meta.wikimedia.org/wiki/Wikimedia_Apps/proposal? [16:47:18] ah i'll have to look at that [16:48:30] brion: it first said that it should mimic the official app's UX, which I don't think is a good idea :) [16:48:35] brion: look at the talk page too [16:48:47] brion: we should really mark the official app as 'deprecated' someplace [16:48:59] brion: we don't want people looking at it for *any* kind of reference / guidance whatsoever [16:49:02] brion: thoughts? [16:49:06] reading [16:53:14] starting to comment on the discussion :) [16:53:19] brion: :) [17:00:32] brion: standup! [17:00:34] brion: standup! [17:00:54] woop it's that time [17:05:12] http://etherpad.wikimedia.org/commons-ios-fixes [17:15:09] http://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/2013-04-08/Wikizine [17:15:17] awjr, jdlrobson, maxsem ^ [17:15:30] thanks Maryana! [17:16:03] "deployment of sidebar, a new facility in its mobile website" [17:16:09] yeah, hehe [17:16:12] time to re-enable my bz account [17:16:17] mhurd: were you saying you needed a 3.5" iOS test device? [17:16:22] i'm going to comment & let them know that's not quite right, maxsem [17:16:23] Chukcha not reader, Chukcha writer [17:16:44] brion: i can just pass mhurd the iPhone4S [17:16:47] ok [17:16:47] brion: ya i tried a 3g from the drawer but Xcode didn't support [17:16:58] tfinc: perfect [17:17:12] mhurd: yeah in my personal drawer i've also got a 3gs which can run iOS 6 but the 4s will do fine [17:17:14] mhurd: oh i didn't expect that to make signpost :) [17:17:18] and will be prettier :) [17:17:19] i just wont be able to do screenshots then but will describe as best as i can [17:17:22] maxsem: :D [17:23:27] awjr_away: MaxSem can we get https://gerrit.wikimedia.org/r/#/c/56887/ merged? [17:23:37] looking [17:25:23] ori-l: can i steal you for some code review today? [17:25:53] brion: mhurd YuviPanda the iOS app requires title and desc. is that a real req ? [17:26:07] tfinc: think so. [17:26:17] tfinc: it won't upload an image unless they're both set [17:26:25] or… it shouldn't :D [17:26:30] brion: you should make desc optional [17:26:36] hmmm [17:26:37] brion: but present [17:26:41] i do notice my descs are often the same as my titles [17:26:42] i know it wont upload. i'm asking if its required for commons [17:26:47] and title mandatory [17:26:49] ah [17:26:53] good question [17:26:53] tfinc: tiltle mandotory [17:27:09] tfinc: description highly reccomended to avoid deletion [17:27:14] what are our users actually filling in? i bet the same thing in both ? [17:27:50] tfinc: i havent checked. [17:28:14] tfinc: oh actually not [17:28:25] a good number are filling in actual wikitext [17:28:27] brion: mhurde: [17:28:27] * https://bugzilla.wikimedia.org/show_bug.cgi?id=47083 [17:28:27] * https://bugzilla.wikimedia.org/show_bug.cgi?id=47084 [17:28:28] * https://bugzilla.wikimedia.org/show_bug.cgi?id=47085 [17:28:30] with appropriate templates [17:28:30] * https://bugzilla.wikimedia.org/show_bug.cgi?id=47086 [17:28:39] staggering [17:28:45] i was surprised [17:28:57] all those french uploads had {{fr|actualdesc}} [17:29:01] he did those by hand [17:29:09] I wonder if we could put some better text to motivate people there then [17:29:11] tfinc: was https://bugzilla.wikimedia.org/show_bug.cgi?id=47083 on the 4s or another device? [17:29:20] tfinc: indeed. [17:29:23] all of these were on the 4S [17:29:29] that mhurd has now [17:29:38] ok so it's the 3.5" screen that's at issue, good [17:29:57] s/below/beneath [17:30:08] yeah [17:30:30] so not retina but 3.5'' [17:30:46] yep. [17:30:49] assigning that one to monte :) [17:31:16] bug title updated [17:31:39] tx [17:32:35] Maryana: is https://docs.google.com/a/wikimedia.org/spreadsheet/ccc?key=0Aoizbfxc5g6KdEkza0xkQnJlM0o0TXlwQXhDOUFvYnc#gid=0 up to date [Roadmap] ? [17:33:51] Maryana: are we really going to get to Mobile notifications ? [17:33:55] in april [17:34:06] New review: MaxSem; "This looks pretty botched up: $wgMFVaryResources is ignored." [mediawiki/extensions/MobileFrontend] (master) C: -1; - https://gerrit.wikimedia.org/r/56887 [17:34:28]