19:35 <mhall119> #startmeeting Clock App
19:35 <meetingology> Meeting started Fri Jun  7 19:35:59 2013 UTC.  The chair is mhall119. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
19:35 <meetingology> 
19:35 <meetingology> 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:36 <mhall119> Bugs: https://bugs.launchpad.net/ubuntu-clock-app
19:36 <mhall119> Blueprint: https://blueprints.launchpad.net/ubuntu-phone-commons/+spec/initial-clock-development
19:36 <mhall119> Burndown: http://status.ubuntu.com/coreapps-13.10/ubuntu-clock-dev-coreapps-13.10-month-2.html
19:36 <nik90> I started implementing the new visual designs (at least what is possible at the moment)
19:37 <mhall119> our burndown isn't looking so great
19:37 <mhall119> nik90: http://pad.ubuntu.com/X9yf5Jss8C has the work items
19:37 <nik90> some screenshots: http://ubuntuone.com/0Z707UZZqth2OCCM4SaXIq
19:37 <nik90> http://ubuntuone.com/5GAo2OLyk3PR0hu1AChJwh
19:37 <nik90> mhall119: true
19:38 <mhall119> looking good nik90
19:38 <nik90> I am planning to go ahead and start the implementation of the world clocks
19:38 <mhall119> nik90: I'd like to focus on Autopilot tests for what we already have before we add more
19:38 <nik90> I think alessandro is busy with his day to day stuff
19:38 <nik90> okay
19:38 <mhall119> with Saucy images coming soon, we're going to need proper testing to get updates into the images
19:39 <nik90> oh
19:39 <nik90> so only after the tests pass will the update get into the image?
19:39 <mhall119> balloons and I are creating individual work items for each test we need in the Core Appa
19:39 <mhall119> nik90: that's the plan, it's the way they're doing it for the rest of Ubuntu, so we need to start doing it too
19:40 <nik90> I have listed here all the test we will need at the moment
19:40 <nik90> http://paste.ubuntu.com/5742807/
19:40 <balloons> nik90, indeed.. the goal is to get a nice working set of calc tests, then I'll turn on the gated commits so things land only if they pass :-)
19:40 <nik90> thanks to balloons for the heads up :)
19:41 <nik90> balloons: ok
19:42 <mhall119> nik90: nice list, let me add them to the work items
19:42 <balloons> we did a test this morning with calc and it failed.. but I'm guessing you guys will be the first app to go through the process :-)
19:42 <balloons> nik90, I take it you saw http://www.theorangenotebook.com/2013/06/autopilot-tests-for-ubuntu-touch-core.html
19:43 <nik90> balloons: yes I saw it
19:43 <balloons> and the recipe and contribution guide? We're trying to get some folks in to help out.. I saw a test get added this morning to calc
19:43 <balloons> try and come out to the hackfest if you can: https://wiki.ubuntu.com/QATeam/Hackfest/20130613
19:43 <mhall119> balloons: happy with that list of work items?
19:43 <nik90> balloons: I did write a couple of tests some time back. Unfortunately I need to update them to autopilot 1.3
19:43 <nik90> I wrote a total of 3-4 tests
19:44 <balloons> nik90, fortunately updating them is REALLY easy
19:44 <balloons> 1.3 changed very little on the syntax side
19:44 <balloons> but alot changed on the backend
19:44 <nik90> I will split that MP into couple of small ones so that it is easy to review and get it merged
19:44 <nik90> oh ok
19:44 <balloons> mhall119, list looks great
19:44 <mhall119> nik90: I'm deleting the old work items for autopilot tests, so just assign yourself ot the ones you're going to work on
19:45 <nik90> it is being in my mind for quite some time
19:45 <nik90> mhall119: sure go ahead
19:45 <nik90> balloons: who do I ask for reviews?
19:45 <mhall119> I'm also scheduling them for month-3
19:45 <mhall119> so we have time to implement them all
19:45 <nik90> mhall119: ok
19:46 <balloons> nik90, reviews for autopilot? It's up to the project itself. I can review if you need help
19:46 <nik90> mhall119, balloons: When the respective bug reports are created, can you also give them milestone coreapps-month-3 on launchpad?
19:46 <mhall119> ok, getting off the autopilot
19:46 <balloons> some members of the autopilot team also volunteered to help
19:47 <nik90> balloons: that's great!
19:47 <mhall119> nik90: so we have an Alarm API meeting scheduled, zsombi and larsu are going to be the ones implementing it on the platform and SDK side
19:47 <mhall119> they want to talk to you guys (clock app devs) to make sure what they're planning on building will do what you need
19:47 <nik90> ok
19:48 <mhall119> instead of a generic background-execution API, I think it's going to be more of an alarm-specific API that the clock app would just use to register alarms with the system
19:49 <nik90> so the system will ensure that the alarms ring at the appropriate time rather than the clock app?
19:49 <mhall119> but as long as it fulfills the specific needs of the Clock app, that's all that we're shooting for this first time through
19:49 <mhall119> nik90: I believe so, but you'll get better information from zsombi and larsu
19:49 <nik90> alrite
19:49 <mhall119> just wanted to give you a head's up so it didn't take you by surprise if that's their plan
19:50 <mhall119> any questions or concerns about that meeting?
19:51 <nik90> that should be ok. Currently I am open to the fact that things constantly change since it is still early development
19:51 <mhall119> :)
19:51 <mhall119> great
19:51 <mhall119> so how is the visual design implementation going?
19:51 <nik90> well, I am waiting on quite of bit of stuff from the sdk.
19:51 <nik90> They are being worked on by florian and loicm
19:52 <nik90> only after they land in the sdk can I actually start the visual designs
19:52 <mhall119> nik90: do we have a list of stuff that we need from the SDK?
19:52 <nik90> yes. Me and David talked to florian about this
19:52 <nik90> Florian added things to a blueprint of the upcoming stuff from the sdk
19:52 <nik90> I cannot remember the link at the moment
19:53 <mhall119> ok, it'll be good to make a list and keep it updated, can you add work items to our Blueprint for each blocker you encounter?
19:53 <nik90> definitely. For month-2?
19:53 <mhall119> yeah, we can move any that take longer to implement to month-3
19:54 <nik90> ok
19:54 <mhall119> other than those things, how's the development going?
19:54 <nik90> will you be updating today's autopilot task to the blueprint?
19:54 <mhall119> thanks for getting those timing bugs fixed, btw
19:54 <nik90> development has slowed
19:54 <mhall119> which autopilot task?
19:54 <nik90> at least compared to before
19:54 <nik90> the ones we listed today
19:55 <mhall119> well, you've run out of features you can implement :)
19:55 <mhall119> yeah, I just updated the BP with them
19:55 <nik90> okay
19:55 <nik90> true, but we still need a lot of work to be done for the world clocks and alarm
19:56 <mhall119> well alarm should hopefully unblock in the next month, now that we have resources assigned to it on the platform side
19:56 <nik90> yes
19:56 <mhall119> is the world clocks part of the design spec?
19:56 <nik90> yes
19:56 <mhall119> ok
19:57 <mhall119> I'll move it up to month-3 too then, so that maybe we can get it in for the Beta
19:57 <nik90> but it is unfortunately not that easy to implement.
19:57 <nik90> That's why I talked to alessandro. me and him will be implementing it bit by bit to tackle it
19:57 <mhall119> how so?
19:58 <nik90> well, getting a list of cities with their timezone is difficult
19:58 <nik90> we thought of using tzdata (which is used in the desktop) but we cannot read files with javascript or qml
19:58 <nik90> so we need a c++ plugin
19:58 <mhall119> the weather app has a way of searching for cities, then they store just the cities the user has added, can you use that?
19:58 <nik90> and neither me or alessandro have that skill
19:59 <nik90> the weather team use the cities from openweather.org
19:59 <nik90> but they do not provide timezone info for them
19:59 <mhall119> oh :P
19:59 <mhall119> do you know what the desktop uses?
19:59 <nik90> It uses tzdata
19:59 <mhall119> ok, so you just need a way to read it
19:59 <nik90> yes
20:00 <mhall119> Kaleo was working on a component to allow reading files for the docviewer, you might check with him
20:00 <nik90> even the current time data indicator uses it
20:00 <nik90> oh ok
20:00 <nik90> I will ask him about it then
20:00 <mhall119> cool
20:00 <mhall119> anything else before we wrap up the meeting?
20:00 <nik90> nope.
20:00 <mhall119> #endmeeting