13:09 <popey> #startmeeting calendar meeting 13:09 <meetingology> Meeting started Thu Apr 2 13:09:24 2015 UTC. The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 13:09 <meetingology> 13:09 <meetingology> Available commands: action commands idea info link nick 13:09 <popey> hey, figured it was faster on irc than hangout :) 13:09 <kunal> :) 13:09 <popey> https://wiki.merproject.org/wiki/Buteo is the thing we're looking at, maybe renatu knows more, but I don't think we've made any commitment on timescales? 13:10 <kunal> yes, in last meeting he told something like that 13:10 <popey> oh yes. 13:10 <popey> Shall we look at the milestone and bugs then? 13:10 <kunal> but are we still considering or its final ? 13:11 <popey> I don't know 13:11 <popey> I don't think any code has been wrotten 13:11 <popey> *written 13:11 <popey> hey faenil 13:11 <faenil> o/ 13:11 <mihir> heya :) 13:11 <popey> So we had a milestone for this week https://launchpad.net/ubuntu-calendar-app/+milestone/2015-04-02 13:12 <renatu> yes we are going to move to buteo soon, but we do not have a time-line yet 13:12 <popey> ok, thanks renatu 13:12 <popey> How are those two bugs going? 13:12 <popey> https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1437031 13:12 <popey> https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1426519 13:13 <kunal> this Date time indicator bug 13:13 <kunal> I started working on it 13:13 <kunal> but there are lot of gray area 13:13 <kunal> like, I know what will be key (X-URL) but dont know what I should put there 13:14 <kunal> mean what should be value 13:14 <kunal> similarly what should be value for X-ICON 13:14 <kunal> also not sure how I can handle invocation from indicator 13:14 <popey> is that something we should just decide on, or we need input from renatu / charles ? 13:15 <kunal> renatu, mention something to add in jason file, but I think we need to add some code in QML as well 13:15 <kunal> but i could not find any information 13:15 <mihir> kunal: also there is a bug , https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1439049 13:15 <kunal> we need input from renatu /charles 13:15 <mihir> where they open event from indicator it opens Calendar instead of opening Event directly 13:16 <charles> good morning 13:16 <kunal> hi, charles 13:16 <charles> looking at scrollback 13:16 <kunal> I need some input 13:17 <kunal> I wanted to know what should I put as value for X-ICON and X-URL 13:17 <kunal> also how can i handle invocation from indicator 13:17 <kunal> to launch particular view in calendar 13:21 * popey fills charles with coffee 13:21 <kunal> popey, https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1437031 13:21 <kunal> this one is ready 13:21 <charles> kunal, unfortunately this would be a question for renatu or tedg. I haven't created a click hook to register for a url type before 13:21 <charles> popey, thanks :-) 13:22 <kunal> charles, ok 13:22 * popey pokes ted 13:22 * tedg waves 13:22 <popey> hey 13:22 <popey> *magic* 13:23 <popey> tedg: http://paste.ubuntu.com/10723944/ 13:23 <popey> (the scrollback) 13:23 <charles> popey, all you have to do is look in a mirror and say "tedg" five times 13:23 <popey> :) 13:24 <tedg> Oh, okay. Let me find the link. Just a sec. 13:24 <tedg> https://developer.ubuntu.com/en/apps/platform/guides/url-dispatcher-guide/ 13:25 <tedg> kunal, ^ that's how you register for a custom URL 13:25 <tedg> kunal, Then what you pass in just has to match that 13:25 <charles> kunal, once calendar-app is registered for "calendar:///foo", the foo part is up to you, whatever the app needs to load the particular event; e.g. "calendar:///eventId=id" 13:25 <tedg> kunal, It can really be anything you want 13:25 * charles adds a bookmark 13:25 <kunal> ok, 13:26 <popey> thanks tedg 13:26 <kunal> tedg, how this URL is delivered to QML code ? 13:27 <kunal> as command line ? 13:28 <tedg> kunal, https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.UriHandler/ 13:28 <tedg> kunal, It'll be command line if it is not started, if it is running (or restored) it'll be via dbus. But best to use that component 13:29 <kunal> ok, great, thanks tedg , it make all thing clear now 13:29 <popey> Excellent. 13:30 <popey> kunal: so that needs a bit more work, right? 13:30 <kunal> charles, so in last meeting we decided, if event does not belong to Reminder or Clock , you will treat them as Calendar event 13:30 <kunal> so do you want me to add those two parameter explicitly ? 13:30 <kunal> yes, popey 13:30 <charles> kunal, right, so we also need to agree on a fallback url 13:31 <charles> that datetime will know enough to hardcode in the case of a missing x-url 13:31 <popey> kunal: ok, lets bump it to the next milestone (I just added) so we don't lose it. 13:31 <kunal> but, instead i worked on this two bugs 13:31 <kunal> https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1437031 13:31 <kunal> https://bugs.launchpad.net/ubuntu/+source/ubuntu-calendar-app/+bug/1435542 13:31 <charles> whatever you need there is fine, just let me know what you want it to be 13:32 <kunal> charles, let use calendar:///eventID=XXXX 13:32 <kunal> for x-icon 13:32 <kunal> what should I use 13:32 <kunal> you need path to icon, or what ? 13:32 <charles> kunal, makes sense 13:33 <popey> path can move though, can't it? 13:33 <charles> yeah, actually tedg had an interesting point on this 13:33 <popey> or is it relative to the app install location? 13:34 <charles> he was thinking, packages can lie to us or omit it, it would be better for qtorganizer5-eds to insert the click package name, and for datetime to find the icon from that via the manifest / .desktop 13:34 <charles> I'm not sure today what we're going to do there, I need to get together with renatu and tedg and see if that's possible or not 13:35 <charles> so let's table the -icon for this week... 13:35 <kunal> Are't there generic icons for this, which we can use ? 13:35 <charles> for calendar, yes 13:35 <popey> ok 13:35 <tedg> I think that calendar could be the default as well. 13:35 <charles> calendar has it easier than the other apps, since anything that doesn't have the x-props is a calendar event 13:35 <tedg> i.e. if you didn't set the value at all. 13:36 <kunal> like this 13:36 <kunal> https://code.launchpad.net/~pkunal-parmar/ubuntu-calendar-app/CalendarIcon/+merge/254178 13:36 <kunal> ok 13:39 <popey> kunal: all good? 13:39 <kunal> yes 13:39 <kunal> now I know ,how I can resolve that issue 13:40 <kunal> so for next milestone, I will keep working on this 13:40 <kunal> plus I have few MR failing due to AP issue 13:40 <kunal> I will try to resolve those 13:40 <popey> ok. 13:41 <kunal> but there are some MR which can be merged 13:41 <kunal> https://code.launchpad.net/ubuntu-calendar-app/+activereviews 13:41 <popey> I'll test/approve/merge them. 13:41 <popey> Need those AP tests fixing to enable a store upload to happen 13:41 <kunal> ok, thanks 13:42 <popey> We shouldn't upload apps that don't pass all their AP tests. 13:42 <kunal> so as of now 13:42 <kunal> AP is failing for 13:42 <kunal> lp:~pkunal-parmar/ubuntu-calendar-app/TapToCreateEvent ⇒ lp:ubuntu-calendar-app 13:42 <kunal> which we need to evaluate anyway 13:42 <kunal> I will try to resolve this AP first 13:42 <kunal> lp:~pkunal-parmar/ubuntu-calendar-app/WeekNumber ⇒ lp:ubuntu-calendar-app 13:43 <popey> Well, trunk fails for me on my nexus 7 running RTM 13:43 <kunal> ok 13:43 <popey> so if trunk fails I'm not surprised those merges fail too 13:43 <popey> We should get trunk in shape, then not regress 13:43 <kunal> ok, I am was not aware of that 13:43 <popey> (easier said than done, I realise) :) 13:43 <popey> kunal: let me re-run again, and I'll file a bug for failing tests 13:44 <popey> I only ran it this morning, not had a chance to file bug. 13:44 <kunal> right, i agree, I will try to see if trunk fails for me 13:44 <kunal> if that happens, then I will try to fix trunk 13:44 <kunal> else my branch wich failes 13:44 <popey> ok. thanks. 13:45 <kunal> in anycase 13:45 <kunal> lp:~pkunal-parmar/ubuntu-calendar-app/CalendarIcon ⇒ lp:ubuntu-calendar-app 13:45 <kunal> this is just icon change 13:45 <kunal> we can merge it 13:45 <popey> approved 13:45 <kunal> ok :) 13:46 <popey> that was easy ㋛ 13:47 <kunal> :) 13:47 <popey> Anything else? 13:47 <kunal> so rest of them, I will confirm 13:47 <kunal> once after running AP from trunk 13:47 <kunal> nothing else from me 13:48 <popey> ok. 13:48 <popey> \o/ 13:48 <popey> Thanks kunal (and everyone else) 13:48 <popey> have a great weekend 13:48 <kunal> wc :) 13:48 <popey> #endmeeting