== Meeting information == * #ubuntu-touch-meeting: Clock meeting, 13 Aug at 14:32 — 15:08 UTC * Full logs at [[http://ubottu.com/meetingology/logs/ubuntu-touch-meeting/2015/ubuntu-touch-meeting.2015-08-13-14.32.log.html]] == Meeting summary == ''LINK:'' https://code.launchpad.net/~nik90/ubuntu-clock-app/update-default-alarm-sound/+merge/267953 ''LINK:'' https://code.launchpad.net/~gang65/ubuntu-clock-app/ubuntu-clock-city-name-fix/+merge/266153 ''LINK:'' https://en.wikipedia.org/wiki/List_of_cities_proper_by_population is a really nice list! ''LINK:'' http://paste.ubuntu.com/12071631/ == Vote results == == Done items == * (none) == People present (lines said) == * popey (46) * nik90 (38) * gang66_ (29) * meetingology (3) * DanChapman (1) == Full Log == 14:32 #startmeeting Clock meeting 14:32 Meeting started Thu Aug 13 14:32:15 2015 UTC. The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 14:32 14:32 Available commands: action commands idea info link nick 14:32 Hows it going guys? 14:32 Great :-) 14:32 Hi popey, gang66_ ..be there in a moment 14:33 I would like to ask if we could manage to push stopwatch with OTA-6 14:33 Unfortunately James can't be with us today, he's had to take some time off for a personal appointment. 14:34 With StopWatch we will need also translate new strings 14:35 The OTA-6 image is scheduled to be built on Tuesday 14:35 Not sure we can be included _in_ that image given we need QA to review. 14:35 Hi :) 14:35 However the image won't go out to users until later, which we could sync with. 14:36 that would too close for comfort to getting it in before tuesday. Also the QA team must be really busy due to the gcc5 stuff 14:37 ok 14:37 also with image #94, we got 2 additional alarm sounds and one of them will be made the default. So updating clock after OTA-6 when we're sure that the new sounds have landed in the phone is better imo. 14:37 I got to know about it only today morning 14:38 I tested new alarm sound branch and it is not playing other sound when the "alarm sound" is missing 14:39 You tested on the phone or desktop? 14:39 https://code.launchpad.net/~nik90/ubuntu-clock-app/update-default-alarm-sound/+merge/267953 14:39 Phone 14:39 BQ E4.5 14:39 hmm strange, I would expect indicator-datetime to fallback on a known alarm sound 14:39 alrite then we push that to after OTA-6 then 14:40 Please verify it on your phone 14:40 Maybe it is a bug in indicator datetime 14:40 ? 14:40 ok, I will check it out 14:41 We have solution for integration stopper; 14:41 https://code.launchpad.net/~gang65/ubuntu-clock-app/ubuntu-clock-city-name-fix/+merge/266153 14:42 Yes :D 14:43 Popey: I would like to ask, if we could receive queries from geonames? I would like to get list of most frequent citynames and buildin init to our Static list 14:44 Not sure I understand the question. 14:44 You want to know data about what clients are most requesting? 14:44 yes 14:44 Hm. 14:44 I don't know if we gather that information. 14:45 I'd anticipate much resistance asking for it, too. 14:45 surely there must be cities that are commonly searched through ubuntu geonames, and we could use that data to improve our static city list. 14:45 ok 14:45 true 14:45 I expect it would be skewed by our own autopilot tests too :) 14:46 var url = String("%1%2%3") .arg("http://geoname-lookup.ubuntu.com/?query=") .arg(searchField.text) .arg("&app=com.ubuntu.clock&version=3.4.x") 14:46 haha...well our autopilot tests only search from the static list since jenkins doesnt have internet access 14:46 Here is the query from Clock app 14:46 What's the goal? 14:47 Show a pre-defined list of cities where we know people already are? 14:47 That seems unhelpful given we don't sell in every country. 14:47 (well, we didn't but do now) 14:47 popey: right now we provide a list of 250 cities. If we knew the cities people searched outside the 250, we could add it to our own list, so they wouldnt have to go online. 14:47 true 14:47 and the static list we include is fully translated 14:48 yes 14:48 thanks nik90 14:48 I'm just not convinced we'll get statistically useful data. 14:48 it is just to improve the experience further..but I do understand that it may breach user privacy 14:49 The other point is people don't do full searches 14:49 What if someone searches for "lon", is that London? Or some other city? 14:49 indeed 14:49 I didnt think of that 14:50 We can't know which result they pick, because that never gets sent back to the server (rightly) 14:50 Sorry to push back on this, but I'm just not convinced we'll get useful data from it 14:51 This is presuming we even log this stuff - which it's entirely possible we don't. 14:51 no no I understand. I didnt think about the partial search and also the useful of the data that is collectable (rightly so) 14:51 My gut reaction is to look at what other vendors do 14:52 And, look at public data for population density. 14:52 which is how I compiled the initial list by looking at google's clock app 14:52 google + wikipedia + list of most populated cities 14:52 hmm true that's a good idea ^^ 14:52 ok 14:52 nice idea 14:52 Would almost certainly be more useful than "list of people who already have ubuntu and have looked up their city during the installation of one app) 14:53 + 14:53 s/)/" 14:53 I would like to have list of cites without users 14:53 so it will be only city names 14:53 https://en.wikipedia.org/wiki/List_of_cities_proper_by_population is a really nice list! 14:53 Don't get me wrong 14:54 unsurprisingly lots of chinese cities 14:54 * nik90 surprised to bengaluru when it is clearly Bangalore :P 14:55 So that would be my take, collect data from existing apps (ios, android, 3rd party) and public data. 14:55 That sound fair? 14:56 yes 14:56 yes 14:56 We could create bug ticket for that 14:56 I just got a idea from mzanetti's app to keep the screen on when the stopwatch is running. Its a nice little polish. 14:57 yeah, good idea 14:59 Do we need UX approval for that? 14:59 for keeping screen on, no 14:59 imo 14:59 It's just a super sensible thing to do :) 14:59 indeed..it something you would notice only when testing the app 15:00 alrite let's see next week how the progress goes since any new string we introduce (stopwatch) will need translations and those take another 2-3 days minimum. 15:00 it really depends on when we get the design approval and icon assets. 15:00 ok. Anything else? 15:00 feel free to poke design :) 15:00 via email preferably 15:00 nope. We landed a couple of alarm page UI changes (minor) 15:01 that's about it 15:01 gang66_: I will retest your MP tonight and do a full code review in the weekend when I get time. 15:02 popey: quick question, can I have the script you use to generate fat packages of clock? 15:03 (hopefully it is as easy as pointing it at the source folder) 15:03 me too 15:03 :) 15:03 sure nik90 15:03 got it from DanChapman :) 15:03 http://paste.ubuntu.com/12071631/ 15:04 sweet. thnx 15:04 :) 15:05 Ok, anything else for clock? 15:05 Nothing from me. gang66_ ? 15:07 no 15:07 thanks 15:07 \o/ 15:07 thanks guys 15:08 #endmeeting Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)