== Meeting information ==
 * #ubuntu-touch-meeting: Calendar App, 06 Jun at 14:05 — 14:29 UTC
 * Full logs at [[http://ubottu.com/meetingology/logs/ubuntu-touch-meeting/2013/ubuntu-touch-meeting.2013-06-06-14.05.log.html]]



== Meeting summary ==




== Vote results ==




== Action items ==

 * (none)



== People present (lines said) ==

 * mhall119 (38)
 * pkunal-parmar (33)
 * Cimi (28)
 * meetingology (3)



== Full Log ==


 14:05 <mhall119> #startmeeting Calendar App

 14:05 <meetingology> Meeting started Thu Jun  6 14:05:07 2013 UTC.  The chair is mhall119. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

 14:05 <meetingology> 

 14:05 <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

 14:05 <mhall119> Bugs: https://bugs.launchpad.net/ubuntu-calendar-app

 14:05 <mhall119> Blueprint: https://blueprints.launchpad.net/ubuntu-phone-commons/+spec/initial-calendar-development

 14:05 <mhall119> Burndown: http://status.ubuntu.com/coreapps-13.10/ubuntu-calendar-dev-coreapps-13.10-month-2.html

 14:06 <mhall119> so there's a number of bugs currently listed

 14:07 <pkunal-parmar> i think some of them need feedback from design team

 14:07 <mhall119> for the bugs?

 14:07 <Cimi> hi guys

 14:07 <mhall119> hi Cimi

 14:08 <pkunal-parmar> yes, like for week number, add new event and edit event

 14:08 <Cimi> I've put some code into a branch, it's a little bit more clean

 14:08 <Cimi> lp:~cimi/indicators-client/system-components

 14:08 <Cimi> there's a Calendar component inside

 14:08 <mhall119> pkunal-parmar: ok, can you just run through the list of bugs and triage them?  So mark them as confirmed if they're valid, make things like week number "wishlist" priority, etc

 14:08 <Cimi> I'm currently working on tests...

 14:09 <mhall119> Cimi: is that component re-usable?

 14:09 <Cimi> mhall119, I think it is

 14:09 <Cimi> but you guys have to look at it

 14:10 <Cimi> it's a fork of your code

 14:10 <Cimi> with some APIs we needed

 14:10 <Cimi> I changed some APIs so you need to adapt it

 14:10 <mhall119> Cimi: there's a discussing starting about providing Ubuntu.Components.Extras for new widgets, are these system components going to live there, or somewhere else?

 14:10 <Cimi> might go there indeed

 14:11 <mhall119> ok

 14:12 <pkunal-parmar> so how wer are supposed to use it, is it packaged and we can import it ?

 14:12 <Cimi> at the moment is work in progress

 14:12 <pkunal-parmar> ok

 14:12 <Cimi> but soon the idea is to start using it

 14:12 <mhall119> Cimi: what do you need to finish it and make it into a package?

 14:12 <Cimi> my take is that, the easier way

 14:12 <Cimi> you copy and paste my code

 14:13 <Cimi> start adapting the rest of the app

 14:13 <Cimi> if you need anything else, you tell me

 14:13 <Cimi> I'm always on connected

 14:13 <Cimi> so for the beginning we sync our code (copy&paste)

 14:13 <Cimi> then when we have a place to store it we remove from the calendar and use the import

 14:14 <pkunal-parmar> yes, we can start with that

 14:14 <mhall119> Cimi: I'll put that as a work item for month-3

 14:14 <Cimi> ok

 14:14 <Cimi> let the development of the calendar happen only on my branch

 14:15 <Cimi> so if you need anything, I/we need to add to that branch

 14:15 <Cimi> otherwise it's a pain keep the code in sync

 14:15 <pkunal-parmar> so you mean only month view right ?

 14:15 <Cimi> I don't know your requirements so I believe the best way is to use it and feedback

 14:15 <Cimi> yes

 14:15 <Cimi> only that

 14:16 <mhall119> Cimi: I'm adding a work item for you to get it packaged next month too

 14:16 <Cimi> mhall119, sure, good

 14:16 <mhall119> alright, now for the month-2 work items

 14:16 <mhall119> Switch to Qt Organizer event storage: TODO

 14:16 <mhall119> pkunal-parmar: any progress on that?

 14:17 <pkunal-parmar> yes

 14:17 <pkunal-parmar> I started working on that

 14:17 <pkunal-parmar> currenly I am able to use it with DiaryView

 14:17 <mhall119> excellent, do you know what it's currently using for backend storage?

 14:17 <pkunal-parmar> but facing some problem using it with TimeLineView

 14:17 <pkunal-parmar> seems like Qt bug

 14:18 <pkunal-parmar> I am using memory as storage

 14:18 <pkunal-parmar> but I am importing iCal files to work with

 14:18 <mhall119> does Qt Location save it somewhere on disk?

 14:18 <pkunal-parmar> its able to import iCal file as well

 14:19 <pkunal-parmar> I guess I can export it to some file

 14:19 <pkunal-parmar> did not tried it yet

 14:19 <pkunal-parmar> so my idea is to import on start up and export at exit

 14:19 <pkunal-parmar> and use memory as storage while its running

 14:19 <mhall119> hmmm, I thought Qt Organizer was suppose to handle storage for us

 14:20 <mhall119> so they could put an evolution-data-server backend in place

 14:20 <pkunal-parmar> I think EDS is going to implement some backend for it

 14:20 <pkunal-parmar> you they will need to implement backend plugin that I can use with Qt Organizer

 14:21 <mhall119> ok, and you think that will handle loading/storing automatically at that point?

 14:21 <pkunal-parmar> you -> yes

 14:21 <mhall119> ok

 14:21 <pkunal-parmar> yes right

 14:21 <mhall119> ok, cool, I'll try to get a timeline from them on when that might be available

 14:21 <pkunal-parmar> this import/ export is only time being until EDS plugin is available

 14:22 <mhall119> cool

 14:22 <mhall119> how about Create the "Create event" view: BLOCKED

 14:22 <mhall119> are we still blocked on that?

 14:23 <pkunal-parmar> yes,  I am waiting for design

 14:23 <mhall119> ok, we have a call with them in 10 minutes, I'll be there today

 14:23 <pkunal-parmar> ok

 14:24 <mhall119> alright, that's all for work items

 14:24 <pkunal-parmar> we have discussed this them earlier as well, I guess they might be working on it

 14:24 <mhall119> the calculator is getting it's visual designs this week, I'm hoping they'll have some for calendar sometime soon

 14:25 <pkunal-parmar> ok, that sounds good

 14:25 <mhall119> pkunal-parmar: you said you're going to make it read and save ical files?

 14:25 <pkunal-parmar> yes, Qt Organizer model supports it

 14:25 <mhall119> would it be possible to add a simple dialog for adding an ical URL?  That way I could give it my google calendar URL and import all my events

 14:26 <mhall119> then I wouldn't have to use google's awful web version

 14:26 <pkunal-parmar> online URL can be imported

 14:26 <pkunal-parmar> but file from storage is difficult as there is no file dialog

 14:27 <mhall119> yeah, Kaleo was going to be working on a component to let you do that via QML

 14:27 <pkunal-parmar> that's great, any idea when it will be available ?

 14:28 <mhall119> no, he was working on it for the docviewer, and it was a high priority for them

 14:28 <mhall119> but I'll check up on it

 14:28 <pkunal-parmar> ok

 14:28 <mhall119> alright, any other questions or concerns?

 14:29 <pkunal-parmar> no, I am done

 14:29 <mhall119> #endmeeting



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