14:02 <popey> #startmeeting calendar app meeting
14:02 <meetingology> Meeting started Thu Mar 26 14:02:52 2015 UTC.  The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
14:02 <meetingology> 
14:02 <meetingology> Available commands: action commands idea info link nick
14:02 <popey> How are you?
14:02 <kunal> how are you ?
14:02 <popey> :D
14:03 <kunal> I am good :)
14:03 <popey> great thanks
14:03 <popey> we set a milestone for today https://launchpad.net/ubuntu-calendar-app/+milestone/2015-03-26
14:03 <popey> hows the progress?
14:04 <kunal> bugs from last milestone are all resolved,
14:04 <kunal> merge is pending due to review
14:05 <popey> excellent
14:06 <popey> have created a new milestone for next thursday https://launchpad.net/ubuntu-calendar-app/+milestone/2015-04-02
14:06 <kunal> ok
14:07 <kunal> then we can start checking bugs and see which needs to be resolved on high priority
14:07 <popey> Yup, lets do that in a moment, I asked charles to join us
14:07 <popey> he had something to mention about calendar...
14:07 <charles> howdy
14:07 <popey> yo
14:08 <kunal> hi
14:08 <charles> so there are a couple of changes coming up in indicator-datetime that calendar-app can take advantage of
14:08 <charles> several apps are adding events in that datetime processes now, clock, calendar, and reminders
14:08 <charles> so one thing we all want is to be able to click on a menuitem in the indicator and launch to the right app, to the right event
14:09 <charles> datetime's adding an x-prop X-CANONICAL-ACTIVATION-URL to handle this
14:09 <charles> and renatu has a patch for qtorganizer5-eds to convert QOrganizerItemExtendedDetail objects into x-props
14:10 <renatu> charles, do we have a silo for your changes already?
14:10 <charles> so if you create a QOrganizerItemExtendedDetail for your event and specify a key/value pair of that x-prop name, and then a url that's registered to your app, then clicking on the menuitem will pass that url through url_dispatch() and calendar-app can consume it
14:11 <charles> renatu, no. Both the datetime and qtorganizer patches have been reviewed & approved, we could queue them for a silo
14:11 <renatu> charles, yes would be nice
14:11 <charles> they wouldn't land until after the freeze, but at least we'd have a ppa that people could use
14:12 <kunal> so, who will add that x-prop, which are synced from google cal ?
14:12 <charles> second item is similar to the first, adding an X-CANONICAL-ICON x-prop so that events can specify their icon in the menubar; e.g. events created with the reminders app can show the reminder icon
14:13 <charles> third and last is what to do about imported calendar events
14:13 <charles> since they won't have that x-prop
14:13 <charles> I'm open to suggestions on how to handle that. In the worst case, we could just launch calendar app
14:14 <renatu> charles, we should use a fallback url something like: "cal://...."
14:14 <renatu> then any calendar app can handle that
14:14 <charles> slightly better would be if calendar app supports a way to launch to a specific date/time, then indicator-datetime could pass in an iso time so that at least calendar-app could jump to the right place
14:14 <popey> Hm
14:15 <popey> So jumping to the day view with the right time/date focussed?
14:15 <popey> But not jumping directly to the event display view?
14:15 <kunal> but we support launching  calendar for event id, I guess you must be having event id ?
14:16 <renatu> we can use cal://eventId=X
14:16 <charles> that would be good
14:16 <kunal> I am not sure about url,  but we support that through command line parameter
14:16 <charles> so if there's no url specified, indicator-datetime could have enough hardwired logic to craft "cal://eventId=X" or whatever url form we all agree on
14:16 <kunal> how we can associate cal:// with calendar ?
14:17 <renatu> kunal, you can specify that on url-handle json file
14:17 <kunal> ok,
14:18 <kunal> so, I guess,  alarm and reminder are created by app so they must have required x-prop
14:18 <kunal> you can treat everything else as calendar event ?
14:18 <charles> yes, they'll both be adding QOrganizerItemExtendedDetail to set the x-prop
14:19 <kunal> ok
14:19 <charles> kunal, in the case where there's no x-prop we'll assume it's a calendar event in order to handle imported events from Google/elsewhere
14:19 <kunal> I can also add required x prop, for event created from cal app
14:20 <charles> sounds good
14:20 <charles> does cal://eventId=X sound alright for the 'fallback' url?
14:21 <popey> is "cal" long enough?
14:21 <popey> should it not be "calendar://"
14:21 <popey> I know it's picky, but if we wanted to link to a calculator thing there could be confusion there
14:22 <charles> renatu, any reason why you suggested 'cal', would 'calendar' work as well as a scheme?
14:23 <kunal> so basically, when adding event calendar needs to add 2 x-prop, one for url and one for icon
14:23 <kunal> and then calendar needs to handle invocation through URL ?
14:23 <charles> right
14:23 <renatu> charles, yes calendar is fine, since this is the not the "calendar app" app-id
14:23 <charles> kunal, that's everything
14:23 <charles> ok, so let's use "calendar://eventId=X"
14:24 <kunal> ok, great
14:24 <popey> this will only land in vivid, right?
14:24 <popey> not rtm?
14:24 <charles> definitely not rtm
14:24 <popey> Ok, good.
14:24 <popey> So that gives us a little more time.
14:24 <charles> we're at FF, so at this point I'd be happy to get it into vivid...
14:24 <popey> we need a bug to track this.
14:25 <kunal> charles, how I can test/use your code ?
14:25 <charles> popey, add calendar-app to https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1426519
14:25 <kunal> you mentioned PPA
14:25 <popey> ok
14:25 <popey> oh, you have
14:25 <charles> popey, that's where renatu's patch and my patch are
14:25 <popey> great
14:25 <charles> kunal, I'll put those two patches in the spreadsheet and get us a silo you can use
14:26 <kunal> ok
14:26 <charles> sounds good
14:26 <charles> I need to run in a minute and I've highjacked like 20 minutes of your meeting here :)
14:26 <charles> any questions?
14:26 <popey> Not from me, it's a welcome hijacking :)
14:27 <popey> we like new feature requests
14:27 <kunal> no, not from me, its clear to me
14:27 <popey> thanks charles renatu
14:27 <charles> cool, thanks kunal, thanks popey
14:27 <kunal> right :)
14:27 <charles> thanks renatu :D
14:27 <popey> kunal: so shall we review bugs and milestone things for next week?
14:27 <renatu> thanks guys
14:27 <kunal> popey, sure
14:29 <popey> ok, lets see, do we have any high/criticals we're not on top of?
14:30 <popey> we have a bunch that are fix-committed
14:30 <kunal> there are some sync related defects
14:30 <kunal> https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1370603
14:30 <kunal> https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1311165
14:31 <popey> The fix renatu made has landed in vivid, but still needs QA for RTM
14:31 <popey> and we're aiming for an RTM image next week
14:31 <kunal> ok
14:31 <popey> I'll chase that and hopefully we can get that into rtm
14:32 <popey> I'll push a new version of calendar to the store later on, and change the "fix committed" ones to "fix released" when I do.
14:33 <popey> which will clean up a bit
14:33 <popey> we have a bunch that need triage
14:33 <popey> https://bugs.launchpad.net/ubuntu-calendar-app/+bugs?orderby=status&start=0
14:33 <kunal> https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1199774
14:33 <kunal> many people are interested in this bug
14:34 <popey> interesting, yeah.
14:35 <popey> Do you have any ideas how we might go about that?
14:35 * popey moves it to medium, given we have a lot of users who are interested in this.
14:35 <kunal> I know how to import from ical from web
14:36 <popey> caldav would need to be done in sync-monitor wouldn't it?
14:36 <kunal> yes, I think the same
14:37 <kunal> there was also lot of discussion on bug, which ask support for syncing multiple calendar from google calendar account
14:37 * popey adds a task for sync-monitor
14:37 <popey> hmm, yeah.
14:38 <popey> renatu: do you have any kind of roadmap for sync-monitor?
14:38 <kunal> https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1309042
14:38 <renatu> popey, the idea is replace it with buteo
14:38 <popey> users seem to be interested in caldav and multi-calendar sync.
14:38 <popey> oh
14:39 <popey> never heard of buteo
14:39 <renatu> but we do not have any dates yet
14:39 <popey> oh, that does caldav...
14:39 <popey> https://wiki.merproject.org/wiki/Buteo
14:39 <renatu> popey, the same used by sailfish
14:39 <popey> ok, thanks renatu
14:40 <popey> kunal: i think that's out of our control for now then.
14:40 <popey> kunal: I'll leave a comment on those bugs and in the discourse
14:40 <kunal> ok
14:41 <renatu> popey, kunal, bill asked me to take a look on calendar app and find places where we can optimize. I already started it and I find some slow points on qtorganizer implementation and some small points on the app qml code
14:41 <renatu> I will send you patches soon :D
14:41 <kunal> ok, great
14:41 <popey> awesome!
14:42 <popey> kunal: so anything we can look at for next week, or should we use the calendar:// stuff to the milestone ?
14:43 <kunal> I think lets  do calendar:// stuff for next week
14:43 <kunal> meanwhile I will triage some bugs
14:43 <kunal> so we can work on those next week
14:43 <popey> ok.
14:44 <kunal> anyway, if i find something, I will add those to milestone
14:44 <popey> charles: can you add lp:ubuntu-calendar-app to https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1426519 ?
14:44 <popey> not the distribution package, but the upstream project
14:44 <popey> I dont seem to be able to.
14:45 <popey> charles: never mind, figured lp out :)
14:45 <popey> kunal: ok, targetted bug 1426519 for next weeks milestone. thanks.
14:45 <popey> Anything else?
14:46 <kunal> yes, Please approve review and approve those pending MRs
14:46 <kunal> also
14:46 <kunal> please have a look
14:46 <kunal> #1378380 	Should add event by tapping on screen in Day view
14:47 <popey> I will do.
14:47 <kunal> if  that woks then I will process further
14:47 <popey> excellent.
14:47 <popey> will test that. thanks.
14:48 <kunal> great, thanks :)
14:48 <popey> Ok, have a great weekend kunal, thanks.
14:48 <popey> #endmeeting