17:29 <popey> #startmeeting Clock meeting
17:29 <meetingology> Meeting started Thu Jan 15 17:29:26 2015 UTC.  The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
17:29 <meetingology> 
17:29 <meetingology> Available commands: action commands idea info link nick
17:29 <popey> Long time no see!
17:29 <nik90_> yeah I have been moving houses and holidays on top of that
17:30 <popey> Golly!
17:30 <nik90_> how is everything going?
17:30 <popey> Great!
17:30 <popey> :)
17:30 <popey> Wanted to catch up with you on a few fronts.
17:30 <nik90_> I feel like I have missed quite a bit in the ubuntu touch land that I need to catch up on
17:30 <nik90_> go ahead
17:31 <popey> Ok, so first we need to review bugs and see if there's anything which urgently needs resolving.
17:31 <popey> The alarms bug I believe charles is on top of.
17:31 <nik90_> yeah I pinged him about that
17:31 <popey> But wanted to know if there's anything else that we should attempt to land soon.
17:31 <popey> feb 6th is when people will start getting phones in their hands
17:31 <popey> and wider a week or so after that
17:32 <nik90_> https://bugs.launchpad.net/ubuntu-clock-app/+bug/1362341
17:32 <nik90_> the above bug requires 2 fixes - one in indicator-dt and the other in clock app
17:32 <nik90_> the i-dt fix has landed
17:32 <popey> ok.
17:33 <nik90_> however the clock app fix is a bit tricky since it introduces a very minor visual flicker noticeable by the user
17:33 <popey> That's a clock issue or a toolkit one?
17:33 <nik90_> I discussed with zsombor and thinks we cant do much about it
17:33 <nik90_> toolkit one
17:34 <nik90_> related to the sdk alarms backend..its been fixed in vivid...but the patch size (~10k code change) is too big to backport at this stage
17:34 <popey> agreed
17:34 <nik90_> I rather introduce the visual flicker which is triggered only when the user switched to the clock app from another app i.e when clock app gains focus
17:35 <popey> We'll switch to vivid at some point
17:36 <nik90_> yeah
17:36 <nik90_> in vivid alarms is broken even more
17:36 <popey> was zsombor's reply "we can't fix this" or "we can't fix this right now"?
17:36 <nik90_> in rtm there is not much we can do to fix this
17:36 <nik90_> since it has been fixed in vivid, we just wait for the transition to vivid
17:37 <popey> right.
17:37 <nik90_> tbh, the flicker happens when you add a new alarm as well
17:37 <nik90_> its barely noticeable
17:38 <nik90_> I mean with the current clock app in store
17:39 <popey> at what point?
17:39 <popey> is it easy to reproduce?
17:39 <nik90_> yeah it is easy to reproduce. Ensure you have 2-3 alarms saved already and enabled. Then create a new alarm and save it.
17:40 <nik90_> at that point you will notice all the alarm switches refreshing (flickering) once
17:40 <popey> oh that
17:40 <popey> yes, i see that all over the place
17:40 <popey> not just clock
17:40 <popey> thats a really annoying UI glitch IMO
17:41 <nik90_> well it happens in the clock app since the entire alarm model is refreshed when adding a new alarm
17:41 <nik90_> zsombor fixed it to only affect the new alarm in vivid
17:41 <popey> right
17:42 <popey> So IMO I agree, I would land that fix
17:42 <nik90_> the thing is that in vivid, the alarms is broken where one cannot even edit alarms..and thereby I am not comfortable with requesting the new alarms backend to be backported to rtm just yet.
17:43 <popey> Agreed
17:43 <nik90_> ok. I will create a MP with the fix and get it approved.
17:43 <popey> Thanks.
17:43 <nik90_> and then ping you before merging to trunk
17:43 <popey> Ping me if I don't see it and I'll organise a store upload
17:43 <popey> yes.
17:43 <popey> The slight gotcha..
17:43 <nik90_> oh also, since 3.2.165 up until now, there have only 4 commits which do code changes to clock.
17:43 <popey> we have to manually test apps with QA if they're in the default image
17:44 <nik90_> I have listed them in http://pad.ubuntu.com/kY99vztlmS
17:44 <nik90_> yeah I knew about that protocol
17:44 <popey> perfect
17:44 <popey> ok.
17:44 <popey> So I am writing a set of clock test cases which we will give to davmor2 (probably) to test clock before we land in store.
17:44 <nik90_> all of 4 commits are minor and approved by ppl like  zsombor, leo, dpm etc
17:44 <nik90_> ack.
17:45 <nik90_> do also send me a copy, and I can add them to the clock app manual test suite if they aren't there already
17:45 <popey> do you already have manual tests ?
17:45 <nik90_> yeah..I have been running them before every store upload (last 2-3 ones atleast)
17:46 <popey> I will put them http://pad.ubuntu.com/ClockAppManualTesting
17:46 <popey> when I write them
17:46 <nik90_> http://bazaar.launchpad.net/~ubuntu-clock-dev/ubuntu-clock-app/utopic-3.0/view/head:/tests/manual/2014.com.ubuntu.clock:clock-tests/jobs/alarms.pxu
17:46 <nik90_> http://bazaar.launchpad.net/~ubuntu-clock-dev/ubuntu-clock-app/utopic-3.0/view/head:/tests/manual/2014.com.ubuntu.clock:clock-tests/jobs/setting.pxu
17:46 <nik90_> ok
17:47 <popey> Do you have a rough ETA ?
17:47 <nik90_> for the MP?
17:47 <popey> yes
17:47 <popey> so I can prioritise and get davmor2 lined up
17:47 <nik90_> tomorrow for sure
17:47 <nik90_> its a 5 lines patch
17:48 <popey> oh great.
17:48 <popey> I'll look out for it.
17:48 <nik90_> ok
17:49 <popey> Any other bugs we should discuss?
17:49 <nik90_> https://bugs.launchpad.net/ubuntu-ux/+bug/1354370
17:50 <nik90_> this required the designers to come with a more bolder default alarm sound
17:50 <popey> hah
17:50 <nik90_> once they do, I need to set it as default in the clock app
17:50 <popey> ok.
17:50 <popey> https://www.youtube.com/watch?v=k2VhB7vaZI0
17:50 <popey> that will do
17:50 <nik90_> yeah mzanetti's bugs are always practical ones
17:50 <davmor2> I don't want lining up :P
17:50 <nik90_> lol
17:51 <nik90_> popey: btw would the patch for https://bugs.launchpad.net/ubuntu-geonames/+bug/1359206 be merged by IS?
17:52 <popey> ooh, good call
17:52 <popey> I need to chase that up.
17:52 <popey> thanks
17:52 <nik90_> we could then remove the dependence on an external service
17:52 <nik90_> I am basically listing the bugs from https://launchpad.net/ubuntu-clock-app/+milestone/ota-1
17:53 <nik90_> I need to move many of them to later milestones
17:53 <popey> ok.
17:53 <nik90_> since they are frozen due to design queries
17:53 <popey> Have you had any conversations with design about stop watch and timer?
17:53 <nik90_> no
17:53 <popey> ok
17:55 <popey> Any other bugs you won't be bumping but feel we need to address sooner?
17:55 <nik90_> https://bugs.launchpad.net/ubuntu-clock-app/+bug/1354466
17:56 <nik90_> I dont have the expertise to handle this one ^^
17:56 <nik90_> its a more complex one, not sure if we can make time for this one
17:57 <popey> it references https://bugs.launchpad.net/ubuntu-clock-app/+bug/1354522 ?
17:57 <popey> which is fixed?
17:57 <nik90_> yes the other one is fixed
17:57 <popey> ok
17:57 <nik90_> the issue is that the clock app stores a default city list in xml file
17:58 <nik90_> xml files are not ready by the translation framework
17:58 <nik90_> and is the hard part
17:58 <popey> ah
17:58 <popey> so you'd need multiple xml files perhaps, one per lang?
17:59 <nik90_> yeah
17:59 <nik90_> and a code change in clock app to use the right file
18:00 <popey> hmm
18:02 <popey> ~277 entries in there
18:02 <popey> for launch I don't think we need to translate all of them to every language
18:02 <popey> (also, this must already be done, surely)?
18:02 <nik90_> I was told by Albert that city and country names are already translated in other projects
18:02 <nik90_> so it would be just recommended by the launchpad webui
18:03 <nik90_> which we can just choose
18:06 <popey> ok.
18:06 <popey> is that something you'd have time to look at?
18:07 <nik90_> I don't know how to fix this bug since I am not familiar with the translation stuff..I did try finding out how to fix it, but couldn't understand the solution.
18:08 <popey> ah okay.
18:08 <popey> I'll poke dpm in the morning and see what sagely advice he has
18:08 <nik90_> :D
18:09 * popey adds a to-do
18:09 <popey> Ok, anything else? :)
18:10 <nik90_> nothing for now :)
18:12 <popey> ok.
18:12 <popey> Lets wrap...
18:12 <popey> #endmeeting