14:32 <popey> #startmeeting Clock meeting
14:32 <meetingology> 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 <meetingology> 
14:32 <meetingology> Available commands: action commands idea info link nick
14:32 <popey> Hows it going guys?
14:32 <gang66_> Great :-)
14:32 <nik90> Hi popey, gang66_ ..be there in a moment
14:33 <gang66_> I would like to ask if we could manage to push stopwatch with OTA-6
14:33 <popey> Unfortunately James can't be with us today, he's had to take some time off for a personal appointment.
14:34 <gang66_> With StopWatch we will need also translate new strings
14:35 <popey> The OTA-6 image is scheduled to be built on Tuesday
14:35 <popey> Not sure we can be included _in_ that image given we need QA to review.
14:35 <nik90> Hi :)
14:35 <popey> However the image won't go out to users until later, which we could sync with.
14:36 <nik90> 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 <gang66_> ok
14:37 <nik90> 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 <nik90> I got to know about it only today morning
14:38 <gang66_> I tested new alarm sound branch and it is not playing other sound when the "alarm sound" is missing
14:39 <nik90> You tested on the phone or desktop?
14:39 <gang66_> https://code.launchpad.net/~nik90/ubuntu-clock-app/update-default-alarm-sound/+merge/267953
14:39 <gang66_> Phone
14:39 <gang66_> BQ E4.5
14:39 <nik90> hmm strange, I would expect indicator-datetime to fallback on a known alarm sound
14:39 <nik90> alrite then we push that to after OTA-6 then
14:40 <gang66_> Please verify it on your phone
14:40 <gang66_> Maybe it is a bug in indicator datetime
14:40 <gang66_> ?
14:40 <nik90> ok, I will check it out
14:41 <gang66_> We have solution for integration stopper;
14:41 <gang66_> https://code.launchpad.net/~gang65/ubuntu-clock-app/ubuntu-clock-city-name-fix/+merge/266153
14:42 <nik90> Yes :D
14:43 <gang66_> 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 <popey> Not sure I understand the question.
14:44 <popey> You want to know data about what clients are most requesting?
14:44 <nik90> yes
14:44 <popey> Hm.
14:44 <popey> I don't know if we gather that information.
14:45 <popey> I'd anticipate much resistance asking for it, too.
14:45 <nik90> 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 <nik90> ok
14:45 <nik90> true
14:45 <popey> I expect it would be skewed by our own autopilot tests too :)
14:46 <gang66_> 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 <nik90> haha...well our autopilot tests only search from the static list since jenkins doesnt have internet access
14:46 <gang66_> Here is the query from Clock app
14:46 <popey> What's the goal?
14:47 <popey> Show a pre-defined list of cities where we know people already are?
14:47 <popey> That seems unhelpful given we don't sell in every country.
14:47 <popey> (well, we didn't but do now)
14:47 <nik90> 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 <popey> true
14:47 <nik90> and the static list we include is fully translated
14:48 <gang66_> yes
14:48 <gang66_> thanks nik90
14:48 <popey> I'm just not convinced we'll get statistically useful data.
14:48 <nik90> it is just to improve the experience further..but I do understand that it may breach user privacy
14:49 <popey> The other point is people don't do full searches
14:49 <popey> What if someone searches for "lon", is that London? Or some other city?
14:49 <nik90> indeed
14:49 <nik90> I didnt think of that
14:50 <popey> We can't know which result they pick, because that never gets sent back to the server (rightly)
14:50 <popey> Sorry to push back on this, but I'm just not convinced we'll get useful data from it
14:51 <popey> This is presuming we even log this stuff - which it's entirely possible we don't.
14:51 <nik90> 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 <popey> My gut reaction is to look at what other vendors do
14:52 <popey> And, look at public data for population density.
14:52 <nik90> which is how I compiled the initial list by looking at google's clock app
14:52 <popey> google + wikipedia + list of most populated cities
14:52 <nik90> hmm true that's a good idea ^^
14:52 <gang66_> ok
14:52 <gang66_> nice idea
14:52 <popey> 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 <nik90> +
14:53 <popey> s/)/"
14:53 <gang66_> I would like to have list of cites without users
14:53 <gang66_> so it will be only city names
14:53 <popey> https://en.wikipedia.org/wiki/List_of_cities_proper_by_population is a really nice list!
14:53 <gang66_> Don't get me wrong
14:54 <popey> unsurprisingly lots of chinese cities
14:54 * nik90 surprised to bengaluru when it is clearly Bangalore :P
14:55 <popey> So that would be my take, collect data from existing apps (ios, android, 3rd party) and public data.
14:55 <popey> That sound fair?
14:56 <nik90> yes
14:56 <gang66_> yes
14:56 <gang66_> We could create bug ticket for that
14:56 <nik90> 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 <popey> yeah, good idea
14:59 <gang66_> Do we need UX approval for that?
14:59 <popey> for keeping screen on, no
14:59 <popey> imo
14:59 <popey> It's just a super sensible thing to do :)
14:59 <nik90> indeed..it something you would notice only when testing the app
15:00 <nik90> 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 <nik90> it really depends on when we get the design approval and icon assets.
15:00 <popey> ok. Anything else?
15:00 <popey> feel free to poke design :)
15:00 <popey> via email preferably
15:00 <nik90> nope. We landed a couple of alarm page UI changes (minor)
15:01 <nik90> that's about it
15:01 <nik90> gang66_: I will retest your MP tonight and do a full code review in the weekend when I get time.
15:02 <nik90> popey: quick question, can I have the script you use to generate fat packages of clock?
15:03 <nik90> (hopefully it is as easy as pointing it at the source folder)
15:03 <gang66_> me too
15:03 <nik90> :)
15:03 <popey> sure nik90
15:03 <popey> got it from DanChapman :)
15:03 <popey> http://paste.ubuntu.com/12071631/
15:04 <nik90> sweet. thnx
15:04 <DanChapman> :)
15:05 <popey> Ok, anything else for clock?
15:05 <nik90> Nothing from me. gang66_ ?
15:07 <gang66_> no
15:07 <gang66_> thanks
15:07 <popey> \o/
15:07 <popey> thanks guys
15:08 <popey> #endmeeting