19:44 <popey> #startmeeting ubuntu touch clock app meeting
19:44 <meetingology> Meeting started Fri Aug  2 19:44:05 2013 UTC.  The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
19:44 <meetingology> 
19:44 <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:44 <popey> blueprint: https://blueprints.launchpad.net/ubuntu-phone-commons/+spec/initial-clock-development
19:44 <popey> bugs: https://bugs.launchpad.net/ubuntu-clock-app/+bugs?orderby=-id&start=0
19:44 <popey> reviews: https://code.launchpad.net/ubuntu-clock-app/+activereviews
19:44 <popey> burndown: http://status.ubuntu.com/coreapps-13.10/
19:44 <popey> hows it going nik90 ?
19:45 <nik90> Today thanks to mhall119's email we got new visual designs for Alarm
19:45 <mhall119> \o/
19:45 <nik90> I am maintaining a branch https://code.launchpad.net/~nik90/ubuntu-clock-app/official-designs where you can find all the designs
19:45 <nik90> you can see alarms and timer designs in the folder "Latest Designs"
19:45 <popey> oh excellent, nice one mhall119
19:46 <nik90> I think there was a small miscommunication since Lina thought we received them last week itself
19:46 * balloons leaves this here: http://reports.qa.ubuntu.com/smokeng/saucy/image/3317/ubuntu-clock-app-autopilot/
19:46 <nik90> balloons: so the timer autopilot tests are failing on the device?
19:47 <nik90> balloons: check out the error message at http://reports.qa.ubuntu.com/smokeng/saucy/image/3317/ubuntu-clock-autopilot/236748/
19:47 <nik90> it says the ubuntu-clock-app is not installed on device
19:50 <popey> hmm
19:50 <popey> ubuntu-clock-autopilot : Depends: ubuntu-clock-app (= 0.3bzr88saucy0) but 0.5bzr157saucy0 is to be installed
19:50 <popey> is that archive skew?
19:51 <popey> -autopilot package and app package not in sync
19:51 <nik90> also if you look at http://reports.qa.ubuntu.com/smokeng/saucy/image/3317/ you will notice there are two clock autopilot packages
19:51 <nik90> with different names
19:51 <balloons> yea, archive skew most likely.. I just wanted to point it out, as these are running on the devices themselves, which is cool
19:51 <nik90> balloons: yes it is pretty cool. I like the new qa dashboard
19:52 <balloons> be informed I've been told monday these will all break again as ppa's are being turned off
19:52 <balloons> nik90, the dashboard is much saner.. jenkins isn't really intended for nice viewing :-)
19:52 <nik90> balloons: wait what? No more PPa's?
19:52 <nik90> So then everybody who wants to test have to be runnign 13.10?
19:53 <popey> no
19:53 <balloons> just in the phone builds..moving to click pacakges
19:53 <popey> ppa's will be deactivated in the mobile build images
19:53 <popey> not for developers
19:53 <nik90> ah ok
19:53 <nik90> wow things are progressing fast.
19:53 <balloons> right.. and I take it mhall119 is going to update us for click packages right? you agree popey mhall119 is going to do all the work right?
19:54 <nik90> hehe poor mhall119
19:54 * popey jumps on a plane to spain
19:54 <mhall119> :P
19:54 <mhall119> click packages should already be made for the core apps
19:55 <nik90> mhall119: cool
19:55 <mhall119> I need to check with those guys though and make sure they submit the click manifests to our branches
19:56 <balloons> mhall119, that's excellent news actually, ty
19:56 <nik90> mhall119: So these new click packages are all done behindn the scenes and then uploaded to mobile image? Or would we see a change in launchpad?
19:56 <nik90> from the dev's point of view
19:58 <popey> aiui you should be able to build click packages in qtcreator
19:58 <popey> not sure that's landed yet though
19:58 <popey> but yes, there's a backend which does that
19:58 <mhall119> nik90: there should be a simple manifest file that is used to build the click package
19:58 <mhall119> instead of a whole ./debian/ directory
19:59 <nik90> mhall119: ah ok. I just asked to know if I had to do something on my side to trigger the click packages build. It looks similar to the way the packages are built by jenkins
19:59 <mhall119> the built .click packages will be uploaded to the software center (not deployed yet) where they will be discoverable from the software center scope (not working with the new software center yet) on the devices
20:00 <mhall119> nik90: I'm not sure how we'll get daily builds available using click....will have to ask
20:00 <nik90> mhall119: ok
20:01 <mhall119> in theory we could make jenkins build the click package and upload it to the software center website
20:01 <nik90> balloons: before I forget to say, I will need to convert existing autopilot tests to use elopio's autopilot emulators which landed in the sdk.
20:01 <mhall119> in theory...we'll see how that matches reality
20:01 <nik90> mhall119: that would be nice
20:02 <nik90> popey, mhall119: can you open clock-outline.png file. I have a question regarding that.
20:02 <nik90> in the official-designs branch
20:02 <balloons> nik90, yea, I would convert whenever you need to add additional tests
20:02 <balloons> if you get stuck, there's a couple examples; dropping letters and file manager
20:02 <mhall119> nik90: what's the designs branch lp: url
20:02 <mhall119> ?
20:02 <balloons> and of course elopio and I
20:03 <nik90> mhall119: https://code.launchpad.net/~nik90/ubuntu-clock-app/official-designs
20:05 <mhall119> nik90: ok, got "clock outline.png" open
20:05 <nik90> mhall119: there they show the transition from alarms to timer tab in which by default it shows the timer in digital format and also lists the timer presets
20:06 <nik90> I am wondering how will the user just create a timer for 10 seconds without having to first create a new timer preset
20:06 <nik90> I notice a similar pattern when transitioning from clock to alarms tab
20:07 <mhall119> nik90: hmmm, I'm not sure if the wireframe is meant to say that the initial view should be the list and digital time, or if the tab-switching and list-browsing were two separate thigns that they just happened to put together for convenience
20:07 <mhall119> I would think that the analog timer and alarm dials should be the initial view when switching to those tabs
20:08 <nik90> mhall119: I hope so too.
20:08 <nik90> I will need to wait until monday to get that confirmed with designers
20:08 <mhall119> nik90: email them today, but yeah it'll probably be Monday before we get an answer
20:09 <mhall119> for now, leave it as it is with the analog dial visible by default
20:09 <nik90> mhall119: will do so.
20:10 <nik90> mhall119: I really need these design meetings to happen. Will email all questions I can think off in an email today.
20:11 <popey> yeah, we've had an unfortunate run of people not being around
20:11 <nik90> I have other updates blueprints now. Replaced blocked with todos now
20:12 <nik90> I would say that covers many of the things I had in mind.
20:12 <nik90> mhall119: do you have a common place with blockers common to all core apps?
20:12 <nik90> like a list or blueprint?
20:13 <popey> https://wiki.ubuntu.com/Touch/SdkFeatureStatus
20:13 <popey> thats the only page really
20:14 <popey> other than that, it may be spread over the linked blueprints
20:14 <nik90> popey: ok. Thats good enough for me.
20:15 <nik90> Anything else to discuss?
20:16 <popey> i dont think so, i had nothing else
20:17 <nik90> mhall119, balloons: anything else to add. Otherwise we can wrap up
20:17 <nik90> to enjoy the weekend :)
20:17 <popey> \o/
20:17 <popey> thanks nik90
20:17 <balloons> I'm good I beliece.. thanks nik90
20:17 <popey> #endmeeting