20:15 <popey> #startmeeting Weather meeting
20:15 <meetingology> Meeting started Fri Aug 28 20:15:17 2015 UTC.  The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
20:15 <meetingology> 
20:15 <meetingology> Available commands: action commands idea info link nick
20:15 <popey> ola!
20:15 <vthompson> hey all!
20:15 <ahayzen> o/ yo, hows your week been guys? ;-)
20:15 <vthompson> Doesn't matter... is Friday!
20:15 <ahayzen> \o/
20:15 <popey> \o/
20:15 <popey> never gets old
20:15 <ahayzen> whats the weather?
20:16 <vthompson> Cool enough to have the windows open
20:16 <popey> So, where are we with weather?
20:17 <vthompson> finishing off tests. I think we have 2 or so more to go
20:17 <ahayzen> the weather got this bad this week ... https://drive.google.com/file/d/0B3XynHVKfrvMRnp5d3Z6VVhCbjA/view
20:17 <ahayzen> "Heavy Intensity Rain"
20:17 <popey> wow
20:17 <popey> never seen that
20:18 <ahayzen> it was intense ;-) ... and yeah finishing off tests
20:18 <vthompson> That's from OWM. We updated the field it gets that text from because it's translatable by the API
20:18 <vthompson> or at least I assume that's where it's from
20:18 <vthompson> It's a bit more descriptive
20:18 <ahayzen> i'm gonna finish off the test svij is writing with him next week
20:18 <ahayzen> yeah its from OWM
20:19 <ahayzen> once the tests are done we are really close now?
20:19 <vthompson> k, I'm going to try to look at that pull to refresh test and change it to key off on something else to detect a refresh. ATM it's too much of a test of the PullToRefresh component itself... which isn't as useful
20:20 <ahayzen> did we decide what we were going todo when you have no network connection or it drops ?
20:20 <vthompson> hm, did we say we were going to hope for something in the SDK?
20:20 <ahayzen> vthompson, ah yeah that test still fails for me :-) and probably best todo something else
20:20 <ahayzen> popey, didn't you ask a designer on monday about it?
20:20 <vthompson> Or maybe we wanted designs
20:20 <popey> I asked mpt
20:21 <popey> he said we have no specific guidelines
20:21 <popey> he said it would be reasonable to use cached data
20:21 <ahayzen> what if there is none ?
20:21 <popey> or fall back to another provider if we really think the first one is dead
20:21 <ahayzen> ok could be a bit weird
20:22 <ahayzen> vthompson, i also noticed that we should show the loading bouncing thing in the location list from the bottom edge
20:22 <vthompson> hm
20:22 <ahayzen> as when i went to add a new location, and the network is slow it doesn't appear in the list until it gets a response
20:22 <ahayzen> and it looked like it had simply not added the location
20:22 <vthompson> That would be good. It does take a few seconds sometime
20:22 <ahayzen> but it was just being really really slow
20:22 <popey> but yes, if there's really no data, and no network, we should provide a decent messgae
20:22 <popey> like the one the web browser does
20:22 <popey> explain the problem and suggest an option
20:22 <vthompson> I think we do have one?
20:24 <ahayzen> i haven't seen one in the current app
20:24 <ahayzen> the loading thing just bounces infinitely
20:24 <vthompson> We have an empty state that shows "Search for current location..."
20:24 <vthompson> Otherwise you get the stale data... which should be "fine"
20:24 <popey> but not "There was a problem getting weather data from the internet"?
20:25 <ahayzen> but say if the http request fails
20:25 <vthompson> No we don't have any http request failure related messages
20:25 <ahayzen> thats what i think we need
20:25 <ahayzen> especially if OWM really is this erratic with being up/down
20:26 <vthompson> So instead of showing the cached data just show another blank screen with a connection error message?
20:26 <ahayzen> maybe we could have a failure text and a button to take you to the settings or just suggest to use another provider
20:26 <vthompson> That's kinda what Android does as well
20:26 <popey> yeah
20:27 <vthompson> Ok, maybe I'll try to put something together for that this weekend
20:27 <popey> Excellent.
20:28 <popey> Take inspiration from browser perhpas
20:28 <popey> *perhaps
20:28 <vthompson> Will do
20:28 <ahayzen> that'd be cool, i think its the last thing to add which changes the UI strings
20:29 <vthompson> do we know if the listitem stuff is still blocked and what an ETA of those changes might be?
20:29 <ahayzen> so when do we want to give it to QA for a run through? like end of next week ?
20:29 <ahayzen> its blocked if we are awaiting for mako
20:29 <ahayzen> and i don't know of the timeline, i would hope OTA7
20:30 <popey> waiting for what on mako?
20:30 <vthompson> There's one more mp I made to fix an eliding bug that I'd like to get in: https://code.launchpad.net/~vthompson/ubuntu-weather-app/fix-1469460/+merge/269451
20:30 * ahayzen finds bug
20:30 <vthompson> From there all the other bugs fixed in the new ListItems mp will be resolved.
20:31 <ahayzen> popey, https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1486008
20:31 <ahayzen> ok, i'll try and look at that MP
20:31 <popey> oh yes
20:32 <vthompson> So once the network failure empty state lands we can probably hand off to QA
20:32 <ahayzen> yup :-)
20:32 <popey> awesome.
20:32 <ahayzen> how many AP tests do we have now? like 8 or something ?
20:33 <ahayzen> https://bugs.launchpad.net/ubuntu-weather-app/+bugs?field.tag=needs-autopilot-test probably shows it quite well
20:33 <vthompson> 13  tests in reboot
20:33 <vthompson> a few more proposed
20:34 <popey> nice!
20:34 <ahayzen> 13 \o/
20:34 <vthompson> I think there are 4 or 5 more with the ones currently in progress
20:35 <ahayzen> yeah probably around that
20:36 <vthompson> For weather, do we ever think we'll look into converged designs?
20:36 <vthompson> Or do we see it as more of a side staged app
20:36 <ahayzen> i assume we will eventually
20:36 <popey> Yes, totally
20:36 <ahayzen> like take that list that is below and put it to the side...and show the hourly info :-)
20:37 <vthompson> yea
20:38 <vthompson> ahayzen, do you mind writing a bug to show the pull to refresh in the LocationsPage?
20:38 <vthompson> Otherwise I can
20:38 <ahayzen> pulltorefresh? i mean the loading bouncing thing
20:38 <vthompson> er, sorry, that's what I meant
20:38 <ahayzen> yeah i can do that :-)
20:38 <vthompson> I don't think that *needs* to be fixed before we release, but it'd be nice
20:39 <ahayzen> "loading bouncing thing"™
20:39 <ahayzen> yeah
20:41 <vthompson> popey, ahayzen so someone needs to write manual tests for QA?
20:41 <ahayzen> yup
20:41 <vthompson> It might be nice to get those done next week
20:41 <popey> ya, thats my task
20:41 <popey> not done it, will do
20:41 <ahayzen> :-)
20:41 <vthompson> awesome
20:41 <vthompson> Was there any social media related things for weather? Or am I getting confused with music?
20:42 <ahayzen> erm possibly confused
20:42 <vthompson> K, that's probable
20:42 <ahayzen> account-polld for weather alerts was something that could be discussed at some point
20:42 <ahayzen> as in if possible/viable/privacy friendly
20:43 <popey> oh, i had a chat about that with James
20:43 <popey> but we'll save that for another time :)
20:43 <ahayzen> :-)
20:44 <vthompson> Cool, hopefully when we talk next week the app will be in the hands of QA
20:44 <popey> shall I commit the manual tests to trunk, like nik90 did for clock?
20:44 <vthompson> I like that idea. In a readme?
20:44 <ahayzen> yeah if you want to ?
20:44 <ahayzen> via an MP ofc ;-)
20:44 <popey> ya
20:44 <popey> in a text file
20:45 <ahayzen> what format do they use in clock again ?
20:45 <vthompson> Is that something QA has an easy time looking at?
20:45 <ahayzen> 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
20:45 <ahayzen> something like ^^
20:46 <popey> yes
20:46 <popey> they do it already for clock
20:46 <nik90> clock app uses Checkbox format to write its manual tests. I was told at some point we will have checkbox touch app where a tester can run the tests like a wizard pressing Fail/Success buttons and generate a graph at the end.
20:46 <ahayzen> oooo checkbox awesome :-)
20:46 <nik90> but not sure how far the checkbox touch app is ready ;)
20:46 * ahayzen has that app installed
20:47 <nik90> the app you have installed has tests preinstalled. However the infrastructure to add 3rd party app tests is still being worked on, I believe
20:47 <vthompson> cool
20:47 <ahayzen> ah cool, that'd be awesome when its done
20:47 <popey> neato
20:47 <vthompson> So popey if you know how to set all that up for weather that'd be cool
20:47 <ahayzen> we should probably move weather+music onto that
20:48 <vthompson> +1
20:48 <ahayzen> as i know for some of the bugs we've had in music we should really be adding manual tests
20:49 <popey> ya
20:49 <nik90> indeed. its best to add some either automated/manual test to go along with critical bug fixes. That's we do with clock-app nowadays
20:50 <ahayzen> yup we should really be doing that as well
20:50 <ahayzen> just some are so convoluted lol
20:50 <vthompson> pshhhh, we never have bugs ;)
20:50 <ahayzen> well we don't...ms2/mh does ;-)
20:51 <popey> hah
20:51 <ahayzen> lol
20:51 <vthompson> So once we get a release close to being out, we should talk about 2.1 features and maybe make a blueprint
20:51 <popey> +1
20:52 <vthompson> kinda premature to talk now--because we'll forget it all
20:52 <ahayzen> yup
20:52 <ahayzen> hmm when is the next UOS ?
20:52 <popey> uhhh
20:52 <vthompson> November-ish I assume?
20:52 <ahayzen> last one feels like *ages* ago
20:53 <vthompson> That it does.
20:53 <ahayzen> thought they were every 3months ;-)
20:53 <vthompson> I thought 6?
20:53 <ahayzen> http://summit.ubuntu.com/uos-1505/all/ May!
20:54 <vthompson> Yea, I thought the last few years have been May and Nov.
20:54 <vthompson> For the client track/phone type of stuff
20:54 <ahayzen> ah maybe 6mth... http://summit.ubuntu.com/uos-1411/
20:54 <ahayzen> http://summit.ubuntu.com/past/
20:55 <ahayzen> well november lands well for us anyway... so we can plan then assuming there is one
20:55 <ahayzen> or is that too late ?
20:55 <popey> I think we should look at new features as soon as we're handing off to QA :)
20:55 <vthompson> seems lateish. We'll want to kinda plan some stuff in the coming weeks
20:56 <popey> ya
20:56 <ahayzen> yeah
20:56 <ahayzen> okies we'll do that
20:56 <vthompson> Not that we can't use the next UOS for other planning
20:56 <ahayzen> :-)
20:56 <vthompson> maybe we'll need to plan v2.2 ;)
20:57 <ahayzen> heh
20:58 <vthompson> Anything else we need to discuss?
20:58 <ahayzen> not from me i don't think
20:59 <vthompson> oh, I don't know why I just thought of this. Was there any branding requirements from TWC?
20:59 <ahayzen> ooo
20:59 <ahayzen> the old app had that logo thing in the corner ?
20:59 <vthompson> Like did we need to mention them on the front of the app like we did for the old version?
20:59 <vthompson> I seemed to think we were told we had to do that
20:59 <ahayzen> same
20:59 <ahayzen> the scope shows the logo in the header
20:59 <ahayzen> so thats probably how they get around it
21:00 <popey> No, we have our design :)
21:00 <vthompson> popey, could you look into that for us?
21:00 <popey> we had this discussion in Washington
21:00 <vthompson> Ok, cool. I don't recall it, but that makes sense
21:00 <popey> ben keyser and david pitkin duked that out months back
21:00 <popey> it doesn't fit the platform
21:00 <popey> to have someone elses branding on our apps
21:01 <vthompson> awesome
21:01 <ahayzen> okies
21:01 * ahayzen wonders what we will do for streaming services in music...
21:01 <popey> their logo will no doubt be somewhere
21:01 <ahayzen> ;-)
21:02 <popey> Anything else?
21:02 <vthompson> nothing from me
21:02 <ahayzen> not from me :-)
21:03 <popey> \o/
21:03 <popey> Thanks guys! Great meetings!
21:03 <ahayzen> have a great weekend guys :-)
21:03 <vthompson> Wait we had more than 1?
21:03 <popey> you too!
21:03 <vthompson> ;)
21:04 <popey> dammit, broke the illusion
21:04 <ahayzen> :-P
21:04 <vthompson> Later guys have a good wkend!
21:04 <ahayzen> o/
21:04 <popey> #endmeeting