14:32 <popey> #startmeeting Clock meeting
14:32 <meetingology> Meeting started Thu Aug  6 14:32:30 2015 UTC.  The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
14:32 <meetingology> 
14:32 <meetingology> Available commands: action commands idea info link nick
14:32 <popey> How we doing nik90 gang66 ? :)
14:32 <nik90> Hi popey, gang66 :)
14:33 <nik90> quite good
14:34 <gang66> Great :-)
14:34 <nik90> noticed that several clock apps are getting design feedback. so those low hanging fruits can be fixed quickly.
14:34 <nik90> clock app bugs*
14:34 <popey> Yeah, the design team are on a sprint this week, attending to many bugs.
14:35 <nik90> ah ok
14:36 <gang66> I'm very happy with progress of Clock development
14:36 <nik90> we are closing on the completion of the stopwatch implementation. Just need some design feedback and assets to complete and merge it.
14:36 <gang66> Do we have James online?
14:37 <popey> no, he's at the sprint
14:37 <popey> so not at his keyboard
14:37 <nik90> ok
14:39 <nik90> Then its best to prepare a click package and then send that over to him for feedback on how to improve it further if required.
14:39 <popey> That sounds like a plan!
14:39 <gang66> Popey: Could you please it by yourself first?
14:39 <nik90> gang66: popey did test it for 23 hrs :)
14:40 <popey> I build click packages every day from trunk, so yes :)
14:40 <popey> When do you plan to land it?
14:41 <nik90> well we can't land it without talking to design first since there were some things missing in the design given to us like the laps list.
14:41 <popey> ah okay.
14:42 <nik90> but we're doing other things meanwhile like unit tests, minor papercuts in the implementation itself.
14:42 <nik90> so it looks a tiny bit different from what design intended
14:43 <gang66> Unfortunately timewatch is not on trunk branch
14:44 <gang66> popey what is your feeling regarding stopwatch?
14:44 <popey> My feeling?
14:45 <popey> I like it :)
14:45 <gang66> I mean User experience
14:45 <popey> I haven't broken it yet :)
14:45 <popey> I find it interesting that we have a clock we can toggle between analog and digital, but a stopwatch which is fixed digital.
14:46 <nik90> I have to say that's a relief, considering you're always pushing it to the boundaries and reporting back with strange bugs.
14:46 <nik90> hmm true
14:47 <popey> it sometimes swipes when I tap
14:47 <nik90> but then stuff like the edit alarm page, timers etc follow the sdk pattern and use time pickers instead of any fancy analog designs like we had previously in the old clock app
14:47 <popey> seems we are a bit trigger happy with swiping
14:47 <popey> e.g. when I just tapped the clock to switch to digital, it swiped over to stopwatch
14:47 <nik90> ah I disabled that totally after hearing mzanetti's feedback.
14:47 <nik90> you should try the latest build
14:48 <nik90> fixed those kind of papercuts
14:48 <popey> [M#|Lok
14:48 <popey> er, ok
14:49 <popey> should lap times be cleared when you stop/start?
14:50 <nik90> nope
14:50 <popey> thats odd
14:50 <nik90> only when you press clear
14:50 <popey> "lap 72"
14:50 <nik90> well its kind of like pausing the stopwatch?
14:50 <popey> i suppose, yes.
14:50 <popey> Just thinking about timing 3 people one after the other
14:51 <popey> i would have to write down the lap times between each run
14:51 <popey> otherwise I lose them when I start recording person #2 and person #3 runs
14:52 <nik90> hmm
14:53 * nik90 checks other apps behavior
14:53 <gang66> Later we would like to implement storing results in some histore, hidden in bottom edge
14:53 <popey> that would be neat
14:53 <popey> run 1, laps 1-3, run 2, laps 1-3 etc
14:54 <nik90> yes that would come in handy
14:54 <popey> especially if it had dates
14:54 <popey> so you could time your runs and compare yesterday / last week end
14:54 <popey> *etc
14:55 <nik90> technically shouldn't be hard to implement. Just need designs for the listview.
14:55 <nik90> may be could take cues from the calculator app
14:57 <popey> Which branch should I build a click from, for James?
14:58 <nik90> https://code.launchpad.net/~ubuntu-clock-dev/ubuntu-clock-app/stopwatch-feature-staging/+merge/266718
14:58 <nik90> although could you give until tonight to make some more minor adjustments?
14:58 <nik90> or do you need it now?
14:59 <popey> no rush
14:59 <popey> just ping me whenever
14:59 <nik90> cool
14:59 <popey> Anything else to discuss clock-wise?
15:00 <nik90> gang66 is looking into the world clock translation issue. So its completion would determine the possible release of clock 3.5
15:00 <nik90> meanwhile I will try to squeeze in other bug fixes.
15:00 <nik90> oh one thing popey
15:00 <popey> ok.
15:01 <nik90> since the transition to vivid and Ubuntu.Components 1.2, autopilots are broken in trunk. So incoming features and fixes are not accompanied with AP tests.
15:01 <popey> OTA-6 is soon :)
15:01 <popey> ah.
15:01 * popey pokes balloons  :)
15:01 <nik90> that was primarily the reason why I had froze everything at the time.
15:01 <nik90> we might need QA to help us fix trunk, and then we can take care of the rest
15:02 <nik90> they essential fail at step 1 where it cannot detect MainView due to sdk changes made in 1.2
15:02 <nik90> that's about it from my side
15:03 <popey> Do we have a bug tracking it?
15:03 <nik90> no
15:03 <nik90> I will create one asap after the meeting
15:04 <popey> ok, thanks
15:05 <popey> Ok, lets wrap up then. Thanks chaps!
15:05 <popey> #endmeeting