[01:23:48] tfinc: let me look at my logs and I'll tell you, but mostly wiktionary people [01:26:15] so we moved and broke links to 198 bugs in order to accommodate 0 bugs for wiktionary [01:26:18] thats less then ideal [01:27:21] tfinc: you said your docs were messed up? Could you point to them so I know what you're talking about? [01:28:02] hexmode: i'm going to have to dig them all up now. http://meta.wikimedia.org/wiki/Mobile_Projects/Contribute at least [01:28:39] but having all this moved while were pushing out new beta and asking our users to file bugs [01:28:44] is cumbersome at best [01:28:52] betas* [01:29:24] tfinc: I understand. I will make sure I don't change this stuff w/o consulting *you* in the future [01:30:23] it would have been nice if *any* developers who were involved for those 198 bugs were contacted. the wiktionary devs don't touch those bugs at all. [01:31:36] that said, I would really like to get bz products/components to be a *little* more sane and that was where I was coming from. The wikitionary devs just seemed to be affirming what I thought was (at least) a better way to go. [01:34:46] agreed. and thats why talking with the relevant team and seeing what their needs are first would have worked better then moving all of their work. the wiktionary folks on the other hand don't have a single filed bug. [01:35:02] but no matter. i'll just create a new structure that matches our development [01:35:08] so thats its sane again [01:35:32] but please don't move public bug lists without talking to the relevant team. we do outreach and have documentation that points to it [01:35:46] having the surprise of that breaking is less then fun [01:36:01] * tfinc is done ranting [01:37:16] I've updated the links on meta so they point to the open bugs again [01:38:11] thanks [01:38:31] * hexmode makes amends where he can [01:38:35] :) [01:38:39] :) [01:45:37] hexmode: https://bugzilla.wikimedia.org/enter_bug.cgi?product=Wikipedia%20App .. how can i create only a subset of OS's here that just correspond to mobile ? [01:47:57] tfinc: I the custom field I created is "mobile platform" ... let me see if I can make it available there. [01:49:15] tfinc: for now, it should be available everywhere [01:51:22] hexmode: here is the initial trimmed list that id need http://etherpad.wikimedia.org/MobileOperatingSystems [01:52:45] hexmode: seeing both OS and Mobile Platform is pretty confusing. can we just have it under OS ? [01:52:54] or .. just remove os then [01:53:10] hardware makes little sense to us too [01:53:20] as their are going to be way too many phones out there [01:53:43] tfinc: yes, but it required editing the templates, could you file a bug for these changes against our bz? [01:53:54] requires [01:53:55] sure, whats the right product/component ? [01:54:22] Wikimedia/Bugzilla [01:57:30] ok filed https://bugzilla.wikimedia.org/show_bug.cgi?id=34668 [02:42:18] hexmode: still around ? [02:42:30] yep [02:43:00] lets move all "Mobile Apps" -> "Wikimedia bugs" to "Wikipedia App" -> Generic [02:43:08] people are already starting to use my new product :D [02:43:16] hehe [02:49:09] hexmode: i also created a Wiktionary product … that way we can delete "Mobile apps" [02:49:16] and lessen the confusion [02:49:48] I thought we could just rename the mobile apps product to witionary app [02:49:59] hexmode: that works too [02:52:17] hexmode: do you have a good example of us using milestones ? [02:52:46] You could use them how we are on MW and MW extensions [02:53:01] 1.20WMF and 1.20 tarball [02:53:10] for example [02:53:30] beta and final version milestones [02:53:44] also "mysterious future" is always a good milestone [02:53:47] hexmode: whats the sort key for? [02:55:09] order things appear in the drop-down [02:55:24] at least, afaict [03:01:50] hexmode: why was this moved to mobile apps https://bugzilla.wikimedia.org/show_activity.cgi?id=30389 ? [03:01:55] it has nothing to do with mobile apps [03:02:45] and what happened to "Wikimedia Mobile" -> "Generic" [03:02:56] please don't tell me you moved everything from generic into mobile apps [03:04:06] * hexmode hopes that he didn't and checks [03:04:46] well, that should be easy to fix at this point, right [03:05:39] ugh .. you did. all of our apps and mobile site bugs are now collapsed into one totally wrong section [03:05:55] * tfinc slams head into desk  [03:07:51] tfinc: I thought you wanted "mobile apps/wikipedia" moved to your new product [03:08:01] didn't you ask me to do that? [03:08:08] * hexmode checks the backlog [03:08:44] lets move all "Mobile Apps" -> "Wikimedia bugs" to "Wikipedia App" -> [03:08:44] Generic [21:43] [03:08:44] [03:09:18] Hrm... [03:09:29] hexmode: what does that have to do with mah@everybody.org 2012-02-17 19:42:10 UTC Component generic Wikimedia [03:09:30] Product Wikimedia Mobile Mobile Apps [03:09:34] oh, yeah [03:09:43] just checked history, got them flipped [03:09:50] I can script us out of this mess [03:09:50] there was no reason to make that move [03:09:53] please do [03:10:01] * hexmode sighs [03:10:25] just so I get it right: [03:10:53] things that moved from "Wikimedia mobile"/"Mobile Apps" go back [03:10:58] right? [03:11:59] anything that was moved from "Wikimedia Mobile" -> "Generic" to "Wikimedia" -> "Mobile Apps" should be moved back [03:12:15] nothing else should happen besides that [03:12:50] now keep in mind. you've collapsed the product component tree so unless you have access to the change history .. i don't see how your going to easily fix this [03:13:21] yeah, I can script that bit, I've done it before [03:13:27] when dealing with that spammer [03:18:21] bug#30389 should go back to "Product: Wikimedia Mobile" and "Component: generic" right? [03:18:44] tfinc: And others like it, right? [03:18:51] let me check [03:18:59] yes [03:19:04] but only those that were generic before [03:19:09] if they were app related then they should stay [03:20:17] tfinc: k, only those that were "Product: Wikimedia Mobile" and "Component: generic" on Feb 16 should be returned to that state [03:20:19] will do [03:21:34] tfinc: some time when you are less busy, i'd like to chat about map tiles, etc. [03:22:34] aude: sure. catch me in the office tomorrow. it 7:30pm and after hexmode tells me were cleaned up id like to head home and take a break [03:22:42] tfinc: sure :) [03:22:50] it's rather late here [03:23:23] tfinc: it is gonna take a bit, go home. I'll stage this all and give you a list for tomorrow [03:23:52] hexmode: i see. then i'll mail out to mobile-l@ with the current status [08:39:58] Heya. [08:40:10] Is anything happening on Wikipedia Zero? [14:20:09] yuvipanda, https://www.mediawiki.org/wiki/Extension:MobileFrontend#prop.3Dexcerpt [14:55:16] Regarding the issue with the RTL bug in the MapQuest OSM tiles: [14:55:40] MapQuest is running Mapnik 2.0.0, which appears to not have the fix yet. [14:56:49] They were planning on waiting till the next release 2.0.1 or 2.1.0 to upgrade. Which supposedly is planned for soonish, but no specific date is set yet. [16:20:10] boo, simply putting html in the messages isn't enough [16:40:23] yuvipanda: yo! [16:40:53] yuvipanda: what do you think about our bugzilla refactor ? [17:08:25] tfinc: the "devices" component is not clear until the explanation is seen, but after clicking it's ok [17:09:13] "Generic" says "everything else". Maybe it should say "everything that doesn't fit elsewhere". [17:09:26] aharoni: i'm talking about "Wikipedia App" [17:09:33] tfinc: heya! [17:09:37] oh! [17:09:47] yuvipanda: thoughts on my bugzilla wikipedia app refactor ? [17:09:47] it's a whole separate product now. [17:09:51] correct [17:10:01] with its own version, milestones, and components [17:10:09] like how bugzilla is supposed to be used [17:10:16] :) [17:10:25] tfinc: haven't looked through it yet, was hacking away on the iOS version [17:10:29] will look now [17:10:31] yuvipanda: k [17:10:41] i'm going to commute into the office .. seeya guys in a couple [17:10:48] tfinc: okay [17:11:35] yuvipanda: note that hexmode is still cleaning up a bunch of bugs that should have never been moved to apps [17:11:35] ... and bugs in en.m.wikipedia.org should be file under the Mobile Frontend extension, right? [17:11:37] i have his list of those [17:11:42] aharoni: --^ [17:12:03] okay [17:12:04] aharoni: for those that know about MF then yes [17:12:15] otherwise the generic component under mobile works [17:12:16] tfinc: you got my email? You could do the change but I will if you want. [17:12:23] not everyone will know about MF [17:12:25] nor should they [17:12:33] hexmode: yes. i'll review when i get into the office [17:12:37] ok .. no i really have to go [17:12:39] now* [17:45:29] greetings all [17:46:04] yuvipanda: thoughts on the bugzilla refactor? [17:46:54] tfinc: i don't think we should have betas as version [17:46:54] s [17:47:06] also [17:47:24] how will you handle the fact that versions for android and ios are going to be different? [17:47:44] yuvipanda: did you see the bug that was referenced in my mail to mobile-l ? [17:47:53] about changing the template and having os versions [17:48:25] yeah, but I was talking about the App versions [17:48:36] IIRC Android app v1.1 is going to be iOS v3.1 [17:50:29] ahh taht [17:50:32] that* [17:51:32] once we have the os tag then we can just tag it as 3.1 [17:51:52] then it'll be clear [17:51:59] we need that os tag to clean this up [17:52:15] MaxSem: yuvipanda : stand up in 10min [17:52:28] sure [17:52:30] preilly and jdrobson will not be joining us. their recruiting at phpuk [17:52:50] tfinc: also, thoughts on forwarding beta announcement to wikitech-l? [17:53:58] yuvipanda: i told you yesterday [17:53:59] just do it [17:55:23] tfinc: okay [17:55:31] * yuvipanda goes to make his first crosspost [17:56:50] yuvipanda: about betas as versions [17:57:01] what would you have our users file bugs as during a beta period ? [17:57:14] s/as/against [17:57:15] tfinc: as 1.1 [17:57:19] or [17:57:22] 'master' [17:57:29] or an equivalent word [17:57:31] they won't know what master is [17:57:38] think non devs [17:57:43] the'll likely just look at whats in the about box [17:57:46] or what we say in our mails [17:57:49] which is .. beta [17:57:56] well, then imagine 9 RCs [17:58:00] :P [17:58:06] 1.1 could work [17:58:13] i like that better then master [17:58:23] perhaps [17:58:26] we can make it [17:58:33] 1.1 (current dev version) [17:58:34] lets see what mw does [17:58:38] 1.0.3 (current market release) [17:58:59] they use betas and rc's [17:59:06] along with -svn [17:59:26] no sign of awjr [17:59:34] lets give him a couple of minutes to show up [18:00:44] if he's not in by 10:05 then we'll just start [18:04:16] ah [18:04:18] wikitech-l spammed [18:04:20] MaxSem: yuvipanda dialing you in now [18:09:01] eww, sound quality sucks [18:10:40] yuvipanda, consider using a customized short URL for announcements. [18:10:55] aharoni: good point [18:10:57] will do from next time [18:11:02] to avoid typing small and capital letters on the phone, if for nothing else :) [18:15:02] yuvipanda: so 1) share keys 2) testing iOS (test flight) 3) testing MaxSem API's [18:15:06] yuvipanda: did i forget anything? [18:15:27] 3 is more like figure out when to start testing MaxSem's APIs [18:16:11] so lets figure out #1 and #2 first as they block #3 [18:16:54] yes [18:17:21] so as far as i know we 1) need keys 2) need to figure out how to store keys [18:17:31] which services do we need them for [18:17:33] ? [18:18:18] tfinc: let me look [18:22:39] 1. facebook 2. instapaper 3. Twitter [18:22:42] that's pretty much it [18:23:00] yuvipanda: heads up that i'm about to start on a meeting marathon [18:23:01] ok [18:23:06] 4. Read It Later [18:23:07] 4 [18:23:08] not 3 [18:23:11] tfinc: okay [18:23:23] the email says: "Test the quick search box integration. Tap the 'G' to show" etc. [18:23:28] to tap the 'G' where? [18:23:31] hmm [18:23:33] home screen [18:23:33] in the home screen [18:23:49] yuvipanda: we should clarify that on the next mail :D [18:23:52] yes :D [18:23:54] excellent point aharoni [18:24:00] i don't have a g in the home screen. [18:24:01] and perhaps stop reusing your alpha template so blatantly :D [18:24:06] i suppose that it's google. [18:24:20] its a G on most stock phones [18:24:24] but if a carrier customizes it [18:24:28] it could be anything [18:25:09] tfinc: not really. he doesn't have the QSB widget on [18:25:20] yuvipanda: that would do it [18:25:20] aharoni: tap the search button from home screen [18:27:49] hmm .. i guess we should create a new Facebook account for our app [18:27:55] because it makes no sense for it to be under me [18:28:54] s/me/personal account [18:29:53] lame. someone already took the "wikipedia" namespace on facebook [18:30:25] tfinc: sigh [18:31:07] same issue on twitter [18:31:16] app name is taken [18:31:44] perhaps WikipediaMobile [18:31:53] for now [18:32:07] i'm sure i could ask legal to get "Wikipedia" back for us [18:33:01] yuvipanda: what do you think about registering this app under the @WikipediaMobile handle ? [18:33:07] that would make more sense then my user account [18:33:09] on fb, it would likely be a good idea. [18:33:15] Amgine: yeah [18:33:20] tfinc: makes sense [18:34:17] while you're at it, you may want to register @[Project]Mobile [18:34:26] be proactive. [18:34:50] s/@WikipediaMobile/@WikimediaMobile [18:35:42] WikimediaMobile, not MediawikiMobile? [18:36:01] Amgine: correct [18:36:13] MediaWiki mobile would make no sense [18:36:27] yuvipanda: take a look: http://meta.wikimedia.org/wiki/Mobile_Projects/features#V1.2_.28drafting.29 [18:36:47] as our apps have nothing to do with mediawiki minus accessing the api [18:37:55] philinje: Localize Nearby view - done in OSM - already done [18:38:25] thanks [18:38:34] 1.2 - make languages not suck :D [18:38:40] language selection* :D [18:38:59] if you want to remove stuff, just keep it underneath in a separate heading [18:39:08] yuvipanda: jdrobson has expressed interest in wanting to dive into the app [18:39:14] tfinc: wwheeeeeee [18:39:15] philinje: k [18:39:28] yuvipanda: who's been code reviewing your changes ? [18:39:30] yeah, all the potential language features are in the list currently, but that is probably way too much [18:39:36] i've been meaning to ask that [18:39:56] philinje: lets setup a sprint planning meeting next week to sort through this [18:40:04] ok [18:40:22] tfinc: good question. Brion used to do that, but no CRs for a while [18:40:24] late next week or the following week actually as yuvi is still in v1.1 release mode [18:40:32] yuvipanda: thats not good [18:40:40] all changes should be reviewed [18:41:04] tfinc: who all can I poke? [18:41:29] start with jrobson [18:41:41] hmm, okay! [18:41:51] we need him to dive deeply into this stuff [18:42:24] alright. [18:42:30] will poke him when I next see him [18:42:57] he has an interview monday morning so after that [18:43:10] okay [18:44:18] philinje: we need to get .m sibling project switch over as needing to get scheduled on the roadmap [18:44:50] * tfinc shudders .. is in meetings till 4pm PST [18:44:53] staring now [18:44:59] * tfinc dies a little [18:45:10] ok, is that just about asking ops, and another email to mobile-l? [18:46:25] and us managing the discussions and new feature requests [18:46:34] philinje: did you see my bugzilla re-org for our app ? [18:49:05] briefly [18:54:55] yuvipanda: i'm asking legal right now to see if we can get "Wikipedia" back from facebook/twitter/etc [18:55:05] tfinc: okay [18:55:23] yuvipanda: so i'll try and figure out the app names issue [18:55:28] what about storage of the keys [18:55:31] what have we come up for that? [18:55:48] tfinc: we'll have to do same thing we did for Google Maps key [18:56:05] have one person store them securely, and add them in manually every 'release' [18:56:38] and by that you mean we'll store them in a secure location so that one person isn't a single point of failure [18:56:49] yes [18:57:02] what can we script ? [18:57:09] because signing the app was pretty easy [18:57:11] tfinc: I can put all the keys in one file [18:57:19] one .h file [18:57:29] so it can be a simple copy [18:57:37] simple file copy, that is [18:57:53] can we just have a top level config file for this? [18:58:07] how would our builds work with it? [18:58:37] tfinc: this is for iOS only - our iOS builds are still going to be 'open XCode, do x, y, z' [18:59:01] yuvipanda: right [18:59:04] yuck [18:59:07] tfinc: a top level config file is what I meant when I said 'all keys in one .h file' [18:59:12] k [18:59:21] just that it'll be a compile time config rather than run time [18:59:48] right [19:00:29] ok … the legal interns are looking into what we can do about the term "Wikipedia" for facebook/twitter/etc apps [19:00:57] yuvipanda: have you had a chance to sync up with Astagi ? [19:01:25] yes, sorted out the about page issue. [19:01:40] id hate for him to feel left out of the project [19:02:46] tfinc: I sorted that out. But we do have the general problem of not having bugs for volunteers to work on [19:03:05] shravan has told me he's back on mobile work from monday (he's packaging debian now) and I better come up with somthing by then [19:03:22] yuvipanda: V1.2 ! [19:04:23] tfinc: yes, it's taking up shape well now. [19:04:56] philinje: you seem to have a few bugs in the '1.2 drafting' section that have been marked resolved fixed [19:06:11] pchang you seem to have a few bugs in the '1.2 drafting' section that have been marked resolved fixeda [19:07:38] tfinc: also, UX [19:07:49] did we decide we're going to adopt PlaneMad's language stuff? [19:08:11] I'd hate to have to throw away code (esp. volunteer's) because the UX changes drastically under their feet [19:09:50] philinje: ^^ [19:16:05] sorry, in a meeting [19:16:41] philinje: ok [19:29:29] yuvipanda: can you move those resolve ones into v1.1? [19:30:20] philinje: they're all marked as resolved, can you do that once you're done with putting things into 1.2? [19:30:59] how many are resolved, a lot? [19:31:22] i found 2 [19:33:31] yuvipanda: so i really like his changes [19:33:52] i think this is where we take a couple of hours to do a rough mockup [19:33:54] and see if we like it [19:33:58] a tech spike [19:34:15] wonders how awjr would categorize it in agile [19:34:34] awjr: so we have feature that we need to test out .. were not 100% sure we want to do it .. but we need a running test of it to really know [19:34:48] tfinc: timebox a spike [19:34:57] like, take an afternoon to do exploratory development on X [19:35:14] yeah, exactly . just enough to get a one off mockup going [19:35:17] and make sure there's a list of questions that need to be answered by the spike [19:35:20] so that we can twiddle with it [19:35:55] yep and to get a better handle on any risk/dependencies/etc [19:36:47] we usually came up with a long list of questions to get answered by a spike, in order of priority. spikes would typically last 1/2 − 1 day and whoever was doing the spike would try to answer as many questions as they could within the timebox. [19:37:44] awjr: so what would be a good would be to have this as part of the planning meeting for 1.2 [19:38:02] yuvipanda: i suggested to move it a week forward [19:38:09] tfinc: you mean the spike itself? [19:38:10] so that your heads doesn't explode from 1.1 [19:38:20] tfinc: okay [19:38:24] awjr: so do you plan the spike as part of a sprint or does it live separately ? [19:38:32] i'd say we do a LOT of these spikes right after 1.1 goes out [19:38:39] which reminds me we need to schedule that ;) [19:38:40] it typically happens during a sprint [19:38:57] right, thats what i thought [19:39:07] we would create a story card for a spike, but it would just be conceived of differently than a typical story or task [19:39:18] we wouldn't assign points to it, so a spike does not contribute to your velocity [19:39:20] so i'd like to do the V1.2 meeting as an actual sprint planning meeting [19:39:23] so that we can lock in work [19:39:33] and have yuvipanda and whoever else dedicated on it for the next x weeks [19:42:24] the other big question is if we do a sprint planning meeting for V1.2 with 1-2 people [19:42:37] or if we do a sprint planning meeting with everyone across all projects [19:42:44] 'all project' -> [19:42:45] ? [19:42:46] zero, apps, mobile web, api [19:42:51] etc [19:45:29] ah [19:45:29] okay [20:03:08] yuvipanda: is "De-spriteify PhoneGap icons" done? [20:03:50] not completely. leave that open but don't block 1.1. let me update that [20:16:10] actually in 1.2 currently [20:16:42] hmm, leave that in 1.2 then [20:16:51] ok, i pulled the fixed ones out and added them to v1.1, except one which was a wontfix [20:17:22] okay [21:42:34] god damn race conditions [21:51:18] aharoni: do you have an iOS device? [21:56:41] the tiny bugs [21:56:47] are the ones that fuck you up [21:56:47] sigh [21:57:21] yuvipanda: can you archive the V1.0 issues that we've already deal with from http://meta.wikimedia.org/wiki/Mobile_Projects/WikipediaMobileAndroidFeedback ? [21:57:25] it see old issues there [21:58:04] tfinc: i'd rather not context switch right now. [21:58:12] can you poke philinje to take care of that page? [21:58:15] yuvipanda: no rush [21:58:18] ok [21:58:22] lets just wait on it [21:59:35] yuvipanda: i'll clean up that page [21:59:41] philinje: thanks [22:10:52] yuvipanda: no iOS [22:11:12] aharoni: Mac? [22:11:21] i18n testing :) [22:11:37] macs are not very popular in this country. [22:12:01] my wife sometimes uses one at the University (and hates it) [22:12:16] ah, just checking [22:12:36] will figure something out! [22:34:11] gnite everyone [22:34:33] note: menus on Android broken by latest commit. [22:34:39] [WikipediaMobile] yuvipanda pushed 1 new commit to master: http://git.io/6sukOg [22:34:39] [WikipediaMobile/master] Working version of menu disable in iOS. Broken in Android - YuviPanda [22:35:04] Project WikipediaMobile - Nightly builds build #191: SUCCESS in 13 sec: https://integration.mediawiki.org/ci/job/WikipediaMobile%20-%20Nightly%20builds/191/ [22:35:05] yuvipanda: Working version of menu disable in iOS. Broken in Android [22:58:32] happy bot :-) [23:24:31] hashar: the bot is happy as long as we feed hijm [23:24:32] him*