19:34:31 #startmeeting Ubuntu Touch Clock App 19:34:31 Meeting started Fri May 10 19:34:31 2013 UTC. The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 19:34:31 19:34:31 Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired 19:34:46 blueprint: https://blueprints.launchpad.net/ubuntu-phone-commons/+spec/initial-clock-development 19:34:55 reviews: https://code.launchpad.net/~ubuntu-clock-dev/ubuntu-clock-app/trunk/+activereviews 19:35:06 bugs: https://bugs.launchpad.net/ubuntu-clock-app 19:35:26 Sorry I couldn't make the design meeting, how did that go? 19:35:55 it went well. there were some bugs that were pointed out, and we are tracking them at the moment 19:36:06 they're filed in launchpad? 19:36:13 most of them yes 19:36:29 the rest should be filed by the designer soon 19:37:17 There was an issue filed by david planella. Apparently the stopwatch runs very slowly on a mobile device 19:37:29 could you verify that on your device next week? 19:37:34 sure can 19:37:43 do you know which device he used? 19:37:54 no :( 19:37:59 ok, no worries 19:38:07 I have a nexus 4 and nexus 7, will test on both 19:38:16 we're targetting Galaxy Nexus though which is slower 19:38:32 so if dpm doesn't have one of those, I'll make sure we have someone who does, test it 19:38:43 Here is the bug report he filed, https://bugs.launchpad.net/ubuntu-clock-app/+bug/1176555 19:39:02 I will ask him to include the mobile device he tested it on in the bug report 19:39:52 Right now, me and renato are basically refactoring the code, organizing, cleaning it for better debugging. 19:40:06 hang on, I'll get both devices 19:40:11 ok 19:40:47 right 19:42:19 yeah, it's too slow on a nexus 7 19:43:16 left a comment 19:44:07 nice. I wil track that. Not sure If I can fix that for the alpha 1 milestone though. 19:44:47 ok. feel free to ping me anytime if you want bugs confirmed on devices 19:45:11 There are some new issues cropping up due to changes upstream in the sdk. So we are waiting on some bugs to be fixed upstream. 19:45:14 will do. 19:45:46 next week is the end of milestone 1 19:46:05 so there's some items which probably need bumping to month 2 19:46:16 e.g. the postponed ones 19:46:29 same for blocked items 19:47:18 should I create a new milestone in the bug tracker? I would like move bugs which I am certain we cannot fix before next week to that new milestone. 19:48:08 the milestone should already exist... 19:48:16 coreapps-13.10-month-2 19:48:23 you are referring to the milestone in the blueprint. 19:48:41 I am referring to the one in the bug tracker. The current one is alpha 1 milestone. 19:49:02 oh, that's unfortunate, we should have them aligned 19:49:39 so yes, I would create them. 19:50:03 ah ok. no worries. I will make sure they are aligned to the blueprint milesstones. 19:50:09 thanks 19:50:15 however you might need to inform other core app dev to do the same 19:51:15 yes, that's true 19:52:40 anything else we need to discuss? 19:52:48 For the world clock feature, we are planning to use geonames.org website. 19:52:57 ok. 19:53:02 is there an api limit? 19:53:03 This was used by the ubuntu 11.04 installer to display timezone info 19:53:09 so it is definitely reliable 19:53:15 right 19:53:29 not sure of the api limit. Will look into it this week. 19:53:54 so you may have seen the blog post from Rick Spencer - VP of Ubuntu Engineering? 19:54:03 http://theravingrick.blogspot.co.uk/2013/05/woof-woof.html 19:54:10 yeah I did.regarding the daily usability at the end of this month 19:54:12 we're planning on dogfooding the phone by the end of the month 19:54:13 yeah 19:54:32 scary :) 19:55:00 The clock app will benefit from the daily usage testing 19:55:13 absolutely 19:55:24 if I'm late for work, I'll blame you guys ㋛ 19:55:30 hehe :) 19:57:00 do you know how to contact the designers by email? 19:57:27 I forgot to ask them some trivial questions during the meeting. 19:57:44 everyone has first.last@canonical.com addresses 19:57:50 who did you want to speak to? 19:58:01 I think lina if I am right 19:58:10 the new designer who was introduced the last time you were there. 19:58:24 I think she's the one in charge of clock app now. 19:58:41 * popey checks 19:59:17 lina.pio@canonical.com 19:59:39 ah thanks 20:00:28 I think that's all the questions I had in mind. 20:00:33 great. 20:00:38 I don't have anything else. 20:00:58 keep up the great work! 20:01:04 thanks nik90 20:01:09 #endmeeting