18:37 <mhall119> #startmeeting Weather App
18:37 <meetingology> Meeting started Thu May 23 18:37:31 2013 UTC.  The chair is mhall119. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
18:37 <meetingology> 
18:37 <meetingology> 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
18:37 <mhall119> Launchpad: https://launchpad.net/ubuntu-weather-app
18:37 <mhall119> Blueprint: https://blueprints.launchpad.net/ubuntu-phone-commons/+spec/initial-weather-development
18:38 <mhall119> Burndown: http://status.ubuntu.com/coreapps-13.10/ubuntu-weather-dev.html
18:38 <mhall119> so with the exception of the blocked visual stuff, the burndown is looking god
18:38 <mhall119> good
18:39 <mhall119> unfortunately no visual designs yet, but we're asking after it every day
18:39 <neokore> it's a great surprise for me
18:39 <neokore> I didn't know about it before
18:39 <mhall119> didn't know about what
18:39 <mhall119> ?
18:40 <neokore> About burndown page
18:40 <neokore> It's new for me
18:40 <mhall119> ah, yeah, we set those up a little while ago, helps keep track of progress
18:40 <mhall119> so your Blueprints looks good, everything scheduled for the month-2 milestone
18:40 <m-b-o> in the design meeting yesterday it was said that the settings for metrics will be in-app
18:40 <m-b-o> so it would not be blocked anymore
18:41 <mhall119> ok
18:41 <m-b-o> https://bugs.launchpad.net/ubuntu-weather-app/+bug/1182188
18:41 <mhall119> how about the u1db for storage?
18:42 <mhall119> settings we're going to get a QML object that will map to dconf on the backend
18:42 <m-b-o> have started with it and found some bugs and/or things that aren't possiblke now
18:42 <mhall119> did you file the bugs?  I know christian is still actively working on it
18:42 <m-b-o> https://bugs.launchpad.net/u1db-qt/+bug/1181359
18:43 <m-b-o> nasty one
18:43 <mhall119> we did have a build issue that I'm working to get resolved
18:43 <m-b-o> when the build works another issue should be fixed with indexing
18:43 <m-b-o> I hope it would be possible to delete docs then
18:43 <mhall119> wow, only 6 digit integers?  That is nasty
18:43 <m-b-o> will be fixed in qt 5.1
18:44 <mhall119> so can I unblock that work item?
18:44 <m-b-o> yes
18:44 <mhall119> cool
18:44 <m-b-o> I have a question about u1db
18:45 <mhall119> balloons: want to give you autopilot pitch and link?
18:45 <mhall119> m-b-o: shoot
18:45 <m-b-o> is it possible to have a database, with syncing disabled?
18:45 <m-b-o> because the locations will be synced, but the grabbed data from the api not
18:45 <mhall119> well syncing hasn't been implemented yet in the QML version
18:45 <m-b-o> and mixing u1db and localstorage is not so nice
18:46 <balloons> sure thing.. Martin is trying to get an autopilot jenkins up for the core apps. You can help by writing autopilot tests for your application. If you have existing tests already, please make sure they work, and are converted to autopilot 1.3
18:46 <mhall119> but syncing is always done manually by the code
18:46 <balloons> you can find out more info about writing autopilot testcase on https://wiki.ubuntu.com/Touch/Testing/Autopilot
18:47 <balloons> in addition, the developers hang out on #ubuntu-autopilot and are happy to answer questions.. I'm there also and on #ubuntu-touch. ping me if you need help
18:47 <mhall119> m-b-o: why is mixing u1db and local storage bad?
18:47 <mhall119> other than it's just more complexity
18:47 <neokore> thanks balloons
18:47 <m-b-o> complexity, yes
18:48 <m-b-o> I've the code already running
18:48 <m-b-o> with u1db and localstorage
18:48 <m-b-o> so storing all in u1db would be a nice-to-have
18:50 <mhall119> ok, is there any reason why syncing that data would be bad?
18:50 <mhall119> other than it being kind of pointless
18:50 <m-b-o> speed perhaps, data traffic under some cirumstances
18:51 <m-b-o> no blocker
18:51 <mhall119> ok
18:52 <mhall119> so it's a trade off really, complexity vs. resources
18:52 <m-b-o> yes
18:52 <mhall119> I think we can leave that up to you guys, as the developers, to decide
18:52 <neokore> ok
18:53 <m-b-o> I would wait till u1db-qt is stable enough and decide after some time
18:53 <mhall119> ok, one last thing before we end, I've been asked to define miletones for Alpha, Beta and Final releases of all the core apps
18:53 <m-b-o> shoudl be easy to change
18:53 <mhall119> m-b-o: that's fine, it should be stable in the next month
18:54 <mhall119> so, In my option Weather has already passed an Alpha level of functionality
18:54 <mhall119> I'd like to propose month-3 for Beta, which is mid-July
18:54 <m-b-o> okay for me
18:54 <neokore> perfect
18:54 <mhall119> that will give time enough to get U1DB integration done, and hopefully have the visual designs done and mostly implemented
18:55 <m-b-o> function wise only the settings are missing
18:55 <mhall119> and then final in month-4, mid August, to give time enough for it to be included in the phablet's final release
18:55 <mhall119> we also want to get Autopilot tests written (per balloons' link above)
18:56 <mhall119> when they switch to Saucy for the phablet images, we're going to need to go through the same QA process as other parts of the distro, which means we need tests and changes won't auto-land in the images unless all of the tests pass
18:56 <neokore> ok
18:57 <mhall119> balloons and fginther are working to enable running those tests in jenkins, so we just need to write them
18:57 <m-b-o> ok
18:58 <mhall119> any other questions, concerns, things I can do for you guys?
18:58 <neokore> for me it's all ok
18:59 <m-b-o> openweathermap api had some problems
18:59 <mhall119> m-b-o: what kind?
18:59 <m-b-o> it broke the code two times the last month
18:59 <m-b-o> changing properties and so on
19:00 <m-b-o> spec is not so stable
19:00 <mhall119> are we using an API?
19:00 <neokore> yes
19:00 <m-b-o> http://openweathermap.org/api
19:01 <mhall119> and that's changing?
19:01 <mhall119> even if you specify the API version in the URL?
19:01 <m-b-o> yes
19:01 <m-b-o> overall thge api is good and got better with v2.5
19:01 <mhall119> well that's not cool, have you contacted them about it?
19:02 <m-b-o> I've wrote some bug reports
19:02 <m-b-o> but I've also started to write an integration of yr.no api
19:02 <m-b-o> if ows stays this way
19:02 <mhall119> ok, good to have a fallback option
19:02 <mhall119> anything else?
19:03 <neokore> great, m-b-o!
19:03 <m-b-o> david suggested in the hangout meeting, that probably the F/C° distinction is part of the locale settings in the system
19:04 <m-b-o> he will look into it and he will tell us, if it's the case
19:04 <mhall119> ok, it might still be desired to have an option to diverge
19:04 <m-b-o> okay
19:04 <mhall119> my locale is US, but I'm starting to use Celcius more for temperature
19:05 <mhall119> alright, thanks for the great work you guys
19:05 <mhall119> #endmeeting