== Meeting information ==
 * #ubuntu-touch-meeting: Weather Reboot, 22 Jan at 17:00 — 18:03 UTC
 * Full logs at [[http://ubottu.com/meetingology/logs/ubuntu-touch-meeting/2015/ubuntu-touch-meeting.2015-01-22-17.00.log.html]]



== Meeting summary ==

''LINK:'' https://docs.google.com/a/canonical.com/presentation/d/1qJ4wzwHsHGNb7GDVjrarMUj4lyro-dLR2_4Xu1b5vQU/edit 
''LINK:'' http://pad.ubuntu.com/WeatherRebootTasks 
''LINK:'' http://bazaar.launchpad.net/~ubuntu-weather-dev/ubuntu-weather-app/trunk/view/head:/tests/autopilot/ubuntu_weather_app/files/1.json 
''LINK:'' https://code.launchpad.net/~flscogna/ubuntu-weather-app/reorganization-and-native-launcher/+merge/241351 



== Vote results ==




== Done items ==

 * (none)



== People present (lines said) ==

 * popey (73)
 * nik90 (65)
 * ahayzen (63)
 * m-b-o (43)
 * meetingology (3)
 * rpadovani (3)



== Full Log ==


 17:00 <popey> #startmeeting Weather Reboot

 17:00 <meetingology> Meeting started Thu Jan 22 17:00:47 2015 UTC.  The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

 17:00 <meetingology> 

 17:00 <meetingology> Available commands: action commands idea info link nick

 17:00 <m-b-o> hey ho o/

 17:00 <popey> hey m-b-o !

 17:01 <m-b-o> hey popey

 17:01 * ahayzen wonders if nik90 is about

 17:01 <nik90> hey

 17:01 <nik90> I am here

 17:02 <popey> Right then! Where to start!?

 17:02 <ahayzen> the design doc maybe?

 17:02 <popey> yup

 17:03 <ahayzen> which was the one that had rtm+1 rtm+2 etc on it? ...

 17:03 <popey> https://docs.google.com/a/canonical.com/presentation/d/1qJ4wzwHsHGNb7GDVjrarMUj4lyro-dLR2_4Xu1b5vQU/edit

 17:03 <popey> that one?

 17:03 <ahayzen> yeah

 17:04 <popey> Ok.

 17:04 <popey> Shall we compile tasks and then put them into a blueprint?

 17:04 <ahayzen> yup

 17:04 <popey> http://pad.ubuntu.com/WeatherRebootTasks

 17:04 <m-b-o> yes

 17:05 <ahayzen> how are we going to start?... take a branch like we did with music?

 17:05 <ahayzen> and slowly replace each of the components/pages with the new design?

 17:05 <nik90> also new reboot branch?

 17:05 <m-b-o> perhaps it would make sense to restart from scratch

 17:06 <ahayzen> ok and then pull any components we need from the old one

 17:06 <ahayzen> may be a bit cleaner todo :)

 17:06 <ahayzen> so we can probably start  by detailing the pages

 17:06 <m-b-o> yes, the ground structure is quite different between the old and reboot one

 17:07 <nik90> m-b-o: You are the one more familiar with the code base, so its up to you if you  want to start from scratch (like what clock did) or just tweak stuff

 17:07 <ahayzen> and then the components inside them ...and turn that into work items

 17:07 <popey> +1 to start from scratch

 17:08 <ahayzen> agreed

 17:08 <nik90> +1

 17:08 <ahayzen> m-b-o, how do the current app talk to things like the weather channel are they in separate .js's or something? or in the QML?

 17:08 <m-b-o> I would start from scratch. The old one is based on tabs and has some things in it, which were added later on....

 17:08 <ahayzen> *how does the

 17:09 <m-b-o> ahayzen: yes, in seperate .js and reusable one-to-one I think

 17:09 <ahayzen> cool :)

 17:09 <m-b-o> there's localstorage for the locations and a js for the data access

 17:09 <nik90> btw which weather provider are we going with? Weather channel or open weather map?

 17:10 <ahayzen> the settings will have an option to change between....according to design

 17:10 <nik90> Since we are starting from scratch, I like to use u1db for storing locations if that is okay

 17:10 <nik90> ahayzen: ah yes, I see weather channel (default) and openweather map both available

 17:10 <popey> you have more experience of that nik90.

 17:11 <ahayzen> u1db \o/

 17:11 <popey> that sounds like a decision.

 17:11 <ahayzen> as long as we don't do multiple levels as that causes the sorting to foobar

 17:11 <nik90> it would be super simple to implement using u1db since storing locations is not exactly complicated

 17:11 <m-b-o> me too u1db :)

 17:11 <nik90> sweet

 17:13 <nik90> Can we put all the necessary design documents in a common google drive folder..I remember seeing visual mockups as well in a separate document.

 17:13 <nik90> easier to share one link than several

 17:13 <ahayzen> +1

 17:14 <ahayzen> there are like 4/5 docs lol

 17:14 <popey> yeah, link them all in the pad, then we can organise them

 17:14 <m-b-o> about using u1db: would it be ok to not migrate the localstorage data to u1db, since it's a reboot??

 17:15 <m-b-o> so to just scratch any locations

 17:16 <nik90> that's what I did with clock :), but let's see what popey thinks about that

 17:16 <popey> I don't understand the question?

 17:17 <nik90> the current weather app data is stored in localstorage..so when reboot replaces the old weather app, do we provide a transition from localstorage to the new u1db format?

 17:17 <m-b-o> should we move the data from the localstorage to the u1db when starting the reboot app for the first time on the users phones?

 17:17 <nik90> or do we just delete user data and start from scratch?

 17:17 <popey> ooh, good call.

 17:17 <popey> Ok, lets look at the practicalities.

 17:17 <ahayzen> it wouldn't be *that* hard to transition ?

 17:17 <popey> on 6th feb there will be ~30 public people who get a phone.

 17:17 * popey waves to rpadovani

 17:18 <ahayzen> assuming we have the same namespace ;)

 17:18 <popey> if we break their experience, they'll blog it.

 17:18 <rpadovani> \o/

 17:18 <popey> within a month or so, the devices are publicly available

 17:18 <m-b-o> http://bazaar.launchpad.net/~ubuntu-weather-dev/ubuntu-weather-app/trunk/view/head:/tests/autopilot/ubuntu_weather_app/files/1.json

 17:18 <popey> if we break _their_ experience we get way more issues :)

 17:18 <popey> So personally I'd like a migration path.

 17:18 <m-b-o> location data as stored ^

 17:18 <ahayzen> cool :)

 17:19 <rpadovani> popey, we have the same problem for calculator, the new one doesn't keep the history fo the old (but it's a very little problem IMO)

 17:19 <rpadovani> sorry for the OT

 17:19 <popey> no, its on topic :)

 17:19 <ahayzen> ....music migrates playlists

 17:19 <popey> show off ㋛

 17:19 <nik90> lol

 17:19 <ahayzen> hehe

 17:19 <popey> My perference is that we do, that's all.

 17:19 <nik90> well looking at the old data set, it seems like a lot of it

 17:20 <nik90> but ok, we can have a work item to track the transition code

 17:21 <nik90> actually to be honest, when I look at the old data set, we only need to preserve the "locations"...everything else we can fetch again

 17:21 <ahayzen> yup just like the lat/long/city then lookup?

 17:21 <m-b-o> nik90 indeed

 17:22 <nik90> yes

 17:23 <nik90> ahayzen: I take it all the design docs are linked in the pad?

 17:23 <popey> yes

 17:23 <popey> thats everything we have

 17:23 <ahayzen> ....will we need to be c++/qml or qml/js only ?

 17:23 * ahayzen i assumes c++/qml ?

 17:24 <m-b-o> ahayzen because of the timezone lookups it needs cpp...

 17:24 <nik90> tbh I am not sure, m-b-o I see that you have a c++ timezone plugin

 17:24 <ahayzen> as someone will need to create the new project

 17:24 <m-b-o> nik90 big unsolved problem

 17:24 <nik90> ah ok, so I suppose then we need c++/qml + cmake project type

 17:24 <ahayzen> is that because of the same timezone issue as clock?

 17:24 <nik90> m-b-o: can you briefly describe the issue you have there?

 17:24 <m-b-o> https://code.launchpad.net/~flscogna/ubuntu-weather-app/reorganization-and-native-launcher/+merge/241351

 17:25 <m-b-o> some bits missing to have it properly integrated

 17:25 <nik90> ahayzen: well we don't have that timezone issue in clock anymore .... now that we have the c++ plugin

 17:25 <m-b-o> which prevents the migration to ubuntu geonames

 17:25 <m-b-o> for location search

 17:25 <ahayzen> nik90, yeah thats i meant...is the plugin because of the same reason as clock having to use the plugin

 17:26 <nik90> m-b-o: I think that's fine..when ubuntu geonames provides all the necessary data, then switching to it should be a simple url and may be data gathering changes

 17:27 <nik90> Since I would need to do it for the clock as well, I think that can be done together

 17:27 <popey> ok, we can co-ordinate that with IS

 17:27 <m-b-o> nik90: okay. how do you do the timezone offset calcualtion in clock?

 17:28 <nik90> m-b-o: well ubuntu-geonames (or geonames) provides the timezone ID which the timezone plugin uses to automatically find the timezone offset while following the rules like dst, etc etc

 17:28 * nik90 still remembers the video popey linked w.r.t timezone chaotic rules :P

 17:29 <popey> hehe

 17:29 <nik90> Qt Timezone introduced in 5.2 will automatically provide the offsets

 17:29 <nik90> although why do you need the timezone info for weather?

 17:30 <m-b-o> you want to show the local time of the locations

 17:30 <nik90> I dont see it in the new design docs though

 17:30 <m-b-o> all the weather data points are using utc timestamps

 17:31 <ahayzen> hmm but would the hourly forecast need the offset?

 17:31 <m-b-o> there are hourly forecasts. and when you have shanghai as location, it's now friday for example

 17:32 <nik90> ah okay, so we do need to convert from utc -> location timezone

 17:32 <nik90> then I suppose we need the c++ timezone plugin

 17:32 <m-b-o> ahayzen yes, you only get a timezoneid and you have utc-timestamps for the data points

 17:32 <ahayzen> cool

 17:33 <m-b-o> it's neccessary

 17:33 <ahayzen> so we can have another work item to create the new c++/qml/cmake project in the new branch

 17:33 <ahayzen> popey, we'll need jenkins running on this new branch right?

 17:34 <popey> yup!

 17:34 <popey> need a work item for that, ci can set that up

 17:34 <ahayzen> cool we can have another work item to poke Francis when the branch is ready

 17:36 <popey> Once we have a working branch who wants responsibility for uploading to the store?

 17:36 <ahayzen> ...did you just volunteer yourself?

 17:36 * ahayzen hides

 17:36 <popey> heh :)

 17:36 <popey> ok.

 17:37 <nik90> ahayzen: nicely done :)

 17:37 <ahayzen> ;)

 17:37 <m-b-o> popey: why is wunderground api linked in the design doc?

 17:37 <popey> where?

 17:37 <m-b-o> under "severe alerts"

 17:38 <popey> Just a suggestion from design.

 17:38 <m-b-o> okay

 17:39 <popey> We haven't finally worked out the details of alarts

 17:39 <popey> *alerts

 17:39 <ahayzen> alerts are not in the focus of the initial reboot right?

 17:39 <ahayzen> as that was rtm+2 not +1

 17:39 <nik90> yeah, I am curious how it can be done..we will probably need help using the push service for alerts

 17:40 <popey> correct

 17:40 <popey> indeed

 17:41 <popey> lots of implications for that

 17:41 <popey> sending user location to a 3rd party service to send you weather alerts :S

 17:41 <nik90> :)

 17:41 <nik90> what's the timeline for the public release of reboot? (replacement of old weather app)

 17:41 <m-b-o> popey: there's a chance that twc data has alerts in it

 17:41 <ahayzen> 'asap' according to popey ;)

 17:42 <popey> yeah :)

 17:42 <popey> ahayzen says he works best under pressure

 17:42 <popey> so I said "next week" :D

 17:42 <ahayzen> yey \o/

 17:42 <nik90> lol

 17:43 <popey> I haven't been given a deadline to be fair.

 17:44 <ahayzen> popey, we have the date of the designers *possible* leaving date...

 17:44 <nik90> leaving date/

 17:44 <nik90> ?

 17:44 <popey> yeah, she's a contractor

 17:44 <popey> we don't know if her contract is being extended yet

 17:44 <ahayzen> so we should ensure any questions we have are raised before then

 17:45 <popey> yup, obviously some of the other designers can pitch in, but she's been focussed on it for the last month or so

 17:45 <nik90> perhaps we could use that as a deadline .. since usually we have tons of questions come up just when we start implemnting stuff

 17:45 <ahayzen> nik90, we have 2 weeks ...IIRC

 17:45 <nik90> ok that's too short :P

 17:47 <popey> we don't know for sure she's leaving yet

 17:47 <popey> and we can always grab some time from gventuri

 17:48 <ahayzen> yup

 17:48 <nik90> true

 17:49 <popey> ok, we have ~10 mins before nik90 has to make himself look beautiful for his date...

 17:49 <popey> shall we put some names to tasks?

 17:49 <ahayzen> :)

 17:49 <nik90> rofl

 17:50 <nik90> so in the work items, the translations and testing frameworks can come in later. It wont be helpful at the beginning anyway

 17:50 <ahayzen> yeah we need the new branch setup and the project setup first

 17:50 <ahayzen> so then we can start making things

 17:50 <popey> +1

 17:50 <nik90> btw m-b-o, ahayzen: For the 2nd task which is the project setup, I suggest we create a common branch so that we all can contribute to it at the same time

 17:51 <m-b-o> I would than add the data backend as soon it owuld be possible

 17:51 <m-b-o> nik90 yes

 17:51 <ahayzen> nik90, just create a /reboot ?

 17:51 <nik90> also I need to be added to the weatherapp dev team

 17:51 <nik90> yeah a new separate branch ... reboot should be fine

 17:52 <nik90> ahayzen: u want to take that task of creating a bare basic launchpad branch?

 17:52 <popey> added you

 17:52 <ahayzen> 'bare basic'

 17:52 <ahayzen> ?

 17:52 <nik90> ahayzen: as in just a readme file for instance..

 17:53 <ahayzen> nik90, heh ok :)

 17:53 <nik90> we can then push other stuff like the app folders, cmakelist etc to that branch

 17:53 <ahayzen> nik90, remember we have vthompson as well ;)

 17:53 <nik90> yes

 17:53 <nik90> ofc

 17:54 <ahayzen> wouldn't want him not to have a work item and feel like he is missing out ;)

 17:54 <nik90> the thing is we don't have work items for the actualy implementation yet.. just the project setup is being listed atm

 17:54 * popey adds an item for a blueprint

 17:54 <nik90> I haven't gone through the design docs yet

 17:55 <nik90> once I do, I should get a better idea of the stuff that we can split up and work on

 17:55 <popey> will you maybe get a chance over the weekend?

 17:55 <popey> we can re-visit the tasks early next week.

 17:56 <nik90> yes

 17:56 <ahayzen> which brings us onto....when we are next meeting?

 17:56 <nik90> oh btw, I am leaving to India next tuesday, so I will make sure to look through the design docs and work items this weekend

 17:57 <m-b-o> will be already on my way to fosdem on next thursday

 17:58 <nik90> does the original weather app meeting time work for everyone?

 17:58 <ahayzen> for now....but i start university again soon

 17:58 <popey> personally I'd prever this time.

 17:58 <m-b-o> me too!

 17:58 <popey> (I mean the time we are at now, 17:00 UTC)

 17:59 <popey> m-b-o: are you walking to fosdem? :)

 17:59 <m-b-o> popey indeed! and they want snow ... ;)

 17:59 <popey> hah

 17:59 <nik90> I am fine with this time too but not sure about vthompson

 17:59 <nik90> as

 18:00 <m-b-o> popey visiting friends on the way

 18:00 * popey is on the eurostar at lunchtime friday. will see you in a bar no doubt

 18:00 <m-b-o> popey ha, thalys ftw!

 18:00 <nik90> Okay I got to run guys

 18:00 <popey> thanks nik90 !

 18:00 <ahayzen> thanks nik90 o/

 18:00 <m-b-o> nik90 thanks!

 18:00 <nik90> I will check meeting logs for the time you guys decide

 18:00 <popey> nik90: m-b-o ahayzen I'll send a mail to figure out the best time for next week, okay?

 18:00 <nik90> see you guys, bye

 18:00 <ahayzen> yup

 18:00 <m-b-o> okay

 18:01 <popey> great!

 18:01 <popey> Ok, anything else before we wrap?

 18:01 <popey> well, there's a lot, obviously :)

 18:02 <m-b-o> popey cool to see you next week at fosdem! :)

 18:02 <ahayzen> probably best ... how is best for us to all communicate? irc/mail/hangouts?

 18:02 <m-b-o> ahayzen I can try to be available on irc, but mail is always a good choice for me

 18:02 <popey> ok.

 18:02 <ahayzen> cool

 18:03 <popey> ok, lets wrap then and I'll ping a mail out.

 18:03 <popey> thanks chaps!

 18:03 <m-b-o> thanks! :)

 18:03 <ahayzen> cool thanks m-b-o popey :)

 18:03 <popey> \o/

 18:03 <popey> #endmeeting



Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)