19:00 #startmeeting Weather app meeting 19:00 Meeting started Thu Dec 19 19:00:45 2013 UTC. The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 19:00 19:00 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:00 Some links.. 19:00 Weather App links:- 19:00 Bugs: https://bugs.launchpad.net/ubuntu-weather-app/+bugs 19:00 Reviews: https://code.launchpad.net/ubuntu-weather-app/+activereviews 19:01 Blueprint: https://blueprints.launchpad.net/ubuntu-phone-commons/+spec/coreapps-1404-weather-dev 19:01 General Links:- 19:01 Milestones: https://launchpad.net/ubuntu-phone-coreapps/+milestones 19:01 Burndown: http://status.ubuntu.com/coreapps-14.04/ 19:01 Blockers: https://wiki.ubuntu.com/Touch/CoreApps/Blockers 19:01 19:01 :D 19:01 How are you guys? 19:01 very good! I missed this meetings 19:01 Fine 19:01 me too! 19:02 I had a mini-agenda.. 19:02 * Deciding on features for 14.04 19:02 * Finalise work items 19:02 * Setting milestones for work items 19:02 * Bugs, merges, work items! 19:02 * Blockers 19:02 So really the features for 14.04 we had one main one.. 19:02 * Implementing the weather channel changes 19:03 WIP 19:03 I know you had a couple of questions m-b-o 19:03 oh yes :) 19:03 I poked dpm about them earlier and he's awaiting answers 19:03 I have new ones, some for you! 19:03 :) 19:03 \o/ 19:03 Go right ahead 19:03 https://code.launchpad.net/~martin-borho/ubuntu-weather-app/weather-channel-client 19:04 already working with TWC, even a the twc bar is added 19:04 1) the place is really narrow for those two links 19:04 especially on maguro 19:05 ooh! 19:06 2) I assume, we're using wunderground.com, right? So I don't know how to resolve the api data to get the TWC location for the links. Perhaps there's some spec for that? 19:06 The links in the csv 19:06 ok, for 1) we need to get a couple of screenshots and fire them at design 19:07 3) Get's everything released, thats getting merged into trunk? 19:07 for 2) I don't think it's based on location but locale 19:08 i.e. not that I'm in London, but that my system is en_GB 19:08 if it was en_CA or fr_CA that would differ, right? 19:08 I've meant in the URL_Schemes you'Ve send in the csv 19:09 ah 19:09 that's their location ID isn't it? 19:10 e.g. UKXX0057 for Farnborough 19:11 in the uk, in Germany it's the ZIP code 19:11 Does TWC api not convert location to their internal ID? 19:11 oof 19:11 is the TWC api wunderground.com? 19:12 yes, I thought so. 19:13 Sorry, I don't understand the problem ☻ 19:13 if you throw a german zip code in the does it work? 19:14 in Germany, but in UK it's not the zip code, I guess 19:16 Hamburg in UK http://uk.weather.com/weather/today/GMXX0049:1:GM 19:16 No, some kind of "location code" 19:16 right, so that works.. 19:16 http://uk.weather.com/weather/today/UKXX0057:1:GM 19:17 so you need to keep the location code in the app and link to that from the links in the bar, right? 19:18 yes, keeping the data is not the problem, but to resolve this code. 19:19 will have a second look 19:19 where does the city search list come from at the moment? 19:19 when you "add city"? 19:19 I could swear, the codes were differnt at the weekend 19:20 ahh, geonames 19:20 geonmaes.org 19:21 http://api.wunderground.com/api/558588d65ec9c24c/conditions/q/53.57532,10.01534.json 19:21 so i search for Hamburg, geonames returns the right stuff.. 19:21 where did you get GMXX0049 from? 19:21 yes, and somewhere inside sits the TWC Location ID 19:22 that'S the point! 19:22 heh 19:23 so IHAMBURG22 is the station ID returned there. 19:24 resolves on uk.weather.com to aberdeen 19:24 or aberdeen is the default when nothing found... 19:24 do you have a contact at TWC? 19:25 we do, but we have to go through someone else here. Not direct contact 19:25 okay. 19:25 I would fire a mail at dpm, I'll speak to him in the morning and we'll push for an answer 19:25 ok, thanks! 19:25 np 19:25 * popey adds to to-do 19:26 sorry guys, I've listening only to try to understand everything 19:26 np ☻ 19:26 :) 19:26 me too! :D 19:26 :P 19:26 So the only other thing I had to think about for 14.04 was convergence 19:26 what would the app look like on a tablet 19:27 glad you've listened both ;) 19:27 always 19:27 haha 19:27 :) 19:27 maybe on table we could use 2 columns 19:27 isn't the app in the "sidestage" or how it's called? 19:27 It can be, yes 19:28 one for houly or 10days forecast 19:28 and other with the current weather 19:28 but lets say for example someone wanted to see a longer forecast in one screen 19:28 rather than flip up/down 19:28 yes 19:28 at the moment they would click the link and break out to the website 19:28 which is not a great experience IMO 19:28 yes, what's really not nice 19:28 I'd rather you could get the data inside the app 19:29 but we have no design for that right now 19:29 yes. some sort of overview look 19:29 exactly 19:30 like the top bar at http://www.bbc.co.uk/weather/ 19:30 and for a given day.. http://www.bbc.co.uk/weather/2643743 19:30 something which shows you upcoming hours 19:30 yes 19:30 nobody really wants to know the weather *now*, they want the weather "today", "later" or "at the weekend" 19:31 you can look out the window for the weather nowe 19:31 -e 19:31 you're right 19:31 I think we need design input ☻ 19:32 I'll take an action to try and get some design involvement 19:32 so we have here some freedom to tinker around? 19:32 for now, sure 19:32 maybe a separate branch for playing around with things 19:33 ok 19:33 okay 19:33 about animations, I've working on them 19:33 great. 19:33 cool 19:33 I put a link up above to the Blockers page 19:34 by now looks good, but maybe we'll need to detect the device resolution 19:34 we want to make sure we have visiblity of any blockers you guys have 19:34 like if you're waiting on something from sdk or toolkit, we need to make a record so we chase it down 19:34 and don't loose anything 19:34 does it not work on grid units? 19:35 it's not about element size, it's about resource resolution 19:35 for little screens, we can't use big images 19:35 or for tablets,... 19:36 ah right 19:36 I'll search a way to detect this info 19:36 kaleo might be a good person to ping 19:36 if he's online 19:36 or take 3 levels of sizes 19:36 (he is) 19:37 ok, I'll ping him 19:37 or should we talk now? 19:37 you can ping him in #ubuntu-tablet maybe? 19:37 er, #ubuntu-touch 19:37 duh 19:38 yes, 19:38 oh i missed 19:06:58 < m-b-o> 3) Get's everything released, thats getting merged into trunk? 19:38 yes, once we have tests on everything and it passes, we land in trunk 19:39 okay 19:39 Anything else? 19:39 howto install autopilot 1.4? all tests are failing here du to old autopilot version 19:39 oh 19:39 on the phone or desktop? 19:39 * popey pokes balloons 19:40 python-autopilot was kept back yesterday so I thought removeing and installing again would help, but broke it completely 19:40 desktop 19:41 oof 19:41 what does apt-cache policy python-autopilot return ? 19:42 you probably need this ppa https://launchpad.net/~autopilot/+archive/ppa 19:42 Die folgenden Pakete haben unerfüllte Abhängigkeiten: 19:42 python-autopilot : Empfiehlt: libautopilot-qt (>= 1.4) aber 1.3+13.10.20130814bzr70saucy0 soll installiert werden 19:42 Beschädigt: libautopilot-qt (< 1.4) aber 1.3+13.10.20130814bzr70saucy0 soll installiert werden 19:42 1.4+14.04.20131125bzr404saucy0 for saucy 19:43 soryy for the paste 19:43 np 19:43 that's with the ppa 19:43 uh 19:45 will try another time again 19:46 hmm, my connection is playing up 19:48 right, back 19:48 Ok. you're on saucy m-b-o ? if so I'll try it here and report a bug if it breaks 19:49 yes, saucy 19:49 ok, will test here 19:49 alright, thanks 19:49 Ok, lets wrap up if there's nothing else? 19:49 No meeting next week, happy holidays! 19:49 Back in two weeks, 2nd jan.. okay? 19:49 meryy xmas! 19:49 You too! 19:50 you too neokore ☻ 19:50 yes 19:50 you too! 19:50 #endmeeting