== Meeting information == * #ubuntu-touch-meeting: ubuntu touch clock app meeting, 27 Sep at 19:35 — 20:04 UTC * Full logs at [[http://ubottu.com/meetingology/logs/ubuntu-touch-meeting/2013/ubuntu-touch-meeting.2013-09-27-19.35.log.html]] == Meeting summary == ''LINK:'' http://forum.geonames.org/ ''LINK:'' https://bugs.launchpad.net/ubuntu-clock-app/+bug/1210196 == Vote results == == Action items == * (none) == People present (lines said) == * nik90 (57) * popey (35) * balloons (13) * meetingology (3) == Full Log == 19:35 #startmeeting ubuntu touch clock app meeting 19:35 Meeting started Fri Sep 27 19:35:35 2013 UTC. The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 19:35 19:35 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:35 blueprint: https://blueprints.launchpad.net/ubuntu-phone-commons/+spec/initial-clock-development 19:36 bugs: https://bugs.launchpad.net/ubuntu-clock-app/+bugs?orderby=-importance&start=0 19:36 reviews: https://code.launchpad.net/ubuntu-clock-app/+activereviews 19:36 burndown: http://status.ubuntu.com/coreapps-13.10/ 19:36 So how are we doing? 19:36 good :) 19:36 alarms landed today 19:37 and few others high priority fixes as well 19:37 I brought up the subject of qmlscene performance on sdk call earlier 19:37 I will be testing qtlocation with gps this weekend and if happy, also get that in by next week mon-tues 19:37 excellent 19:37 I wont be able to test at all this weekend. 19:38 I have dedicated both my phones to running for 48 hours untouched 19:38 to see if the memory leak issue happens 19:38 no worries, I will test on my phone 19:38 but that is an issue (memory issue) worth investigating 19:39 I have some small bug fixes in mind 19:39 btw me, dpm, charles kerr, zsombi, renato and thomas strekl are discussing the alarm notification 19:39 i tried the alarm functionality earlier 19:39 not extensively 19:40 excellent. 19:40 hopefully we come up with a solution soon enough 19:40 oh btw you cannot save an alarm on the phone due to an EDS bug which renato is looking into 19:40 it suddenly appeared and he is investigating 19:40 but everything regarding alarms is now upstream 19:40 from the clock app everything regarding alarms is done 19:41 a big relief for me 19:42 Good to hear. 19:43 but the deadline for freezes is 10th oct? 19:43 Yes. 19:43 I hope to hear from Lina next week 19:43 and the bug regarding the county affecting weather and clock 19:44 m-b-o did some research 19:44 he found out that adminName2 is relevant for some countries while for other adminName3 is useful 19:44 but there is no space to include both with it being cramped 19:44 not sure what to do there 19:45 gah 19:45 can you display either or, if the other is blank? 19:45 well the other one isnt blank, that is the problem 19:46 so hard to say which one is useful without manually checking :( 19:46 hm 19:46 I will create a forum post to discuss this with the online api developers 19:47 I have got answers before in the forum 19:47 which forum is that? 19:48 http://forum.geonames.org/ 19:48 oh, handy 19:49 yeah ... that website is awesome 19:49 Are there any bugs that you found annoying while using the clock app and should be addressed soon? 19:50 heh, not that I haven't already told you about ☻ 19:50 hehe 19:50 well I finally now have time to address some small papercuts if you will 19:51 are they tagged as papercuts? 19:51 no not in the clock app 19:51 ok 19:51 how are the autopilot test cases looking 19:52 * popey glances at balloons 19:52 we have tests for stopwatch and timer 19:52 still need to write tests for clock and alarm 19:52 I hear talks of alarms 19:52 if it's unblocked let's update the bugs 19:52 they have been constantly changing so havent had the chance to write tests 19:52 well baloons we cant write for alarms yet 19:52 lol 19:53 an upstream bug regarding EDS still needs fixing 19:53 :-) hence there are none 19:53 ok, so it's still blocked 19:53 the alarm in the desktop works but not in phone 19:53 if I am right, autopilot is for both devices 19:54 balloons: Although we can write tests for adding a world clock 19:54 adding/deleting world clocks 19:54 * nik90 checks if there are bug reports concerning that 19:54 https://bugs.launchpad.net/ubuntu-clock-app/+bug/1210196 19:55 just add a note to all the bugs if we can about what's blocked and what's not, just to update them 19:55 ah yes 19:55 balloons: sure 19:55 I'll ask someone to work on world clock 19:56 okay, I just moved to the release milestone 19:56 balloons: btw any autopilot test in https://bugs.launchpad.net/ubuntu-clock-app/+milestone/final-1.0 is doable 19:57 done.. John will be surprised, hehe, better email him 19:58 hah 19:58 ? 19:58 * balloons assigned the world clock test bugs to john 19:59 oh :) 19:59 Thanks balloons 19:59 wonderful 20:00 Anything else? 20:00 Not from me 20:01 me neither 20:01 balloons: still here? 20:01 yes.. just sending off the email :-) 20:02 nothing else from me.. just update the bugs and let me know once they are unblocked for more tests 20:02 in general clock has been stable and I haven't had to mind it :-) 20:02 definitely 20:02 thnx 20:03 Ok, lets wrap. 20:03 once I noticed a test passing without it actually doing its thing..I fixed it 20:03 yup 20:03 haha 20:03 ahh assertless tests, yes have to be careful with those 20:04 +1 20:04 Ok. thanks guys. 20:04 Have a great weekend. 20:04 you too popey and balloons 20:04 #endmeeting Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)