19:40:22 #startmeeting Clock App 19:40:22 Meeting started Fri May 17 19:40:22 2013 UTC. The chair is mhall119. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 19:40:22 19:40:22 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:40:34 #topic month-2 milestone 19:40:50 so it looks like you guys have already moved work items to month-2, thanks for doing that 19:41:20 the World Clocks stuff, do you have anything from the design team about how it would look and work? 19:41:48 yes the app design clock journeys have mockups on how it should look 19:41:57 ok, great 19:42:10 it was being worked on by alessandro 19:42:20 so, something that was discussed during UDS was to define Alpha, Beta and Final milestones for each of the Core Apps 19:42:35 ok. 19:42:44 Is this in addition to the monthly milestones? 19:42:48 well, before we move on to that, is there anything else about month-2 we should talk about? 19:42:56 any blockers or concerns? 19:43:13 * nik90 looking at the blueprint work items 19:43:39 well we are still waiting on the alarms backend for scheduling 19:44:06 right, there was a session on that at UDS, did you get to attend it? 19:44:32 no, but I had a look at the videos. 19:44:45 ok, I didn't make it either 19:44:51 I hope you were referring to the app lifecycle session 19:44:53 but it should be enough to do what the Clock needs 19:44:57 yeah, http://summit.ubuntu.com/uds-1305/meeting/21763/client-1305-background-task-service/ 19:45:05 #link http://summit.ubuntu.com/uds-1305/meeting/21763/client-1305-background-task-service/ 19:45:44 I will have a look at it today or tomorrow and see how it goes. 19:45:54 Gather User Location info like Latitude and Longitude: BLOCKED 19:45:59 what is that one blocked on? 19:46:36 I am yet to finish going through qt mobility. So I am not sure how to implement geo-ip. 19:46:45 ok 19:46:55 I was hoping to wait for the weather-app team to implement it 19:47:06 since I heard someone in their team was working on it. 19:47:14 my limited understanding is that there's an abstraction-layer API in Qt Mobility with multiple backends, and that on the desktop it should still work, just using GeoIP instead of GPS 19:48:27 ok. I will try to implement that 19:48:34 I guess it is not a blocker but a todo then 19:48:44 ok 19:49:14 the alarm backend is blocked until we get the code implementation in the sdk for the background tasks. 19:49:29 yup, I don't know when exactly that will land 19:49:33 callum told me that the visual designs should land next week hopefully 19:49:43 so that's another blocker. 19:50:05 we can start on the alpha, beta milestone discussion 19:50:21 cool 19:50:29 popey has a work item from UDS to follow up on the visual designs 19:50:38 to get that unblocked 19:50:48 #topic major milestones 19:51:03 so as I was saying, we want to set Alpha, Beta and Final milestones 19:51:24 Final should be on or before September, to give time for finalizing the Ubuntu Touch 1.0 release 19:51:51 now Clock is already functional enough that, in my opinion, you guys passed Alpha already 19:52:14 true 19:52:17 so that really only leaves Beta 19:52:34 what we'll do is just pick one of the monthly milestones and say that's our Beta target 19:53:27 I think month-3, which ends July 16th, would be a good target 19:53:31 I have created the first 3 monthly milestones in launchpad..still need to create the other 3 to match the blueprints. Will do that tomorrow. 19:53:37 July is also when the SDK itself will have a Beta release 19:54:29 if by a 1.0 release, we are not expecting the clock app to also support landscape mode, then I think the target is achievable 19:54:57 because with the landscape mode, it will require ui changes as well which might make it more difficult. 19:55:23 is there really that much work? 19:55:59 I think it's okay to be portrait-only though for 1.0 19:56:01 to be honest, it is a bit hard to say since it will depend on the ease of use of layouts. But it brings a uncertainity 19:56:17 is there even a work item for landscape support? 19:56:41 yeah..I put it in the 3rd month..though it will be moved if necessary 19:57:08 yeah, let's push that back 19:57:19 which month do you want to move it to? 19:57:27 if you just leave it under "Work items:", it'll show on the burn-down, but not for any specific milestone 19:57:44 ah nice 19:58:01 then we can assign it to a specific milestone if and when we have a LayoutManager implemented and something from the Design team 19:58:14 I agree 19:58:48 I moved it. 19:59:04 so if we call July our Beta milestone, and August our Final, I think that's enough time to implement the rest of the features 19:59:31 yeah the major feature that still needs landing is the world clocks. 19:59:42 and I think 2 months is more than enough time to get that done 19:59:47 perfect 19:59:59 alright, anything else you want to discuss today? 20:00:17 nothing much. Me and david are getting the translation support complete. 20:00:36 I was thinking of sending a mail to the core app mailing list highlighting the do and don'ts 20:00:39 I saw your post on that 20:00:50 that should help them as well 20:00:54 are you still doing regular blogging about the Clock progress? 20:01:08 yeah..I will be posting this week's one tomorrow 20:01:23 that will help a lot of people, even outside of core apps 20:01:34 let me know when it's posted and I'll promote it on Facebook and G+ 20:01:48 sure 20:02:26 alright, I'm going to wrap things up now 20:02:30 I think that's about it 20:02:32 ok 20:02:33 #endmeeting