== Meeting information ==
 * #ubuntu-touch-meeting: calendar meeting, 11 Jun at 13:00 — 13:51 UTC
 * Full logs at [[http://ubottu.com/meetingology/logs/ubuntu-touch-meeting/2015/ubuntu-touch-meeting.2015-06-11-13.00.log.html]]



== Meeting summary ==

''LINK:'' https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1455377 
''LINK:'' https://code.launchpad.net/~pkunal-parmar/ubuntu-calendar-app/MonthHighlight/+merge/259323 
''LINK:'' https://bugs.launchpad.net/content-hub/+bug/1464244 
''LINK:'' http://ubottu.com/meetingology/logs/ubuntu-touch-meeting/2015/ubuntu-touch-meeting.2015-06-04-13.01.log.html 



== Vote results ==




== Done items ==

 * (none)



== People present (lines said) ==

 * kunal (76)
 * popey (54)
 * kenvandine (12)
 * renatu (12)
 * meetingology (3)
 * faenil (1)



== Full Log ==


 13:00 <popey> #startmeeting calendar meeting

 13:00 <meetingology> Meeting started Thu Jun 11 13:00:33 2015 UTC.  The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

 13:00 <meetingology> 

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

 13:00 <popey> hey guys

 13:00 <faenil> o/

 13:01 <renatu> kunal, I did not find any real problem on qtornizer-eds

 13:03 <kunal> Hi renatu

 13:05 <kunal> ok, that bug seems similar to

 13:05 <kunal> https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1455377

 13:05 <kunal> when I see events coming from EDS

 13:05 <kunal> qml: Thu Jun 11 00:00:00 2015 GMT+0900---Fri Jun 12 00:00:00 2015 GMT+0900

 13:05 <kunal> qml: Thu Jun 11 00:00:00 2015 GMT+0900---Fri Jun 12 00:00:00 2015 GMT+0900

 13:05 <kunal> qml: Fri Jun 12 00:00:00 2015 GMT+0900---Sat Jun 13 00:00:00 2015 GMT+0900

 13:05 <kunal> qml: Fri Jun 12 00:00:00 2015 GMT+0900---Sat Jun 13 00:00:00 2015 GMT+0900

 13:05 <kunal> qml: Sat Jun 13 00:00:00 2015 GMT+0900---Sun Jun 14 00:00:00 2015 GMT+0900

 13:05 <kunal> qml: Sat Jun 13 00:00:00 2015 GMT+0900---Sun Jun 14 00:00:00 2015 GMT+0900

 13:05 <kunal> event's end date seems wrong

 13:06 <kunal> it should start and end on same date

 13:06 <kunal> like

 13:06 <kunal> qml: Thu Jun 11 00:00:00 2015 GMT+0900---Thu Jun 11 00:00:00 2015 GMT+0900

 13:06 <popey> so do we need the patch renatu made for eds _and_ that calendar patch?

 13:06 <kunal> I think only EDS patch should work

 13:07 <renatu> kunal, eds saves all days evens with diff start and end date

 13:08 <renatu> kunal, you should handle that on the app

 13:08 <kunal> renatu, when I create All day event for single day

 13:08 <kunal> I get below start and end date

 13:08 <kunal> qml: Thu Jun 11 00:00:00 2015 GMT+0900---Thu Jun 11 00:00:00 2015 GMT+0900

 13:08 <kunal> date is same

 13:08 <kunal> when  I create recurrent all day event

 13:09 <kunal> I get

 13:09 <kunal> qml: Thu Jun 11 00:00:00 2015 GMT+0900---Fri Jun 12 00:00:00 2015 GMT+0900

 13:09 <kunal> end date is wrong

 13:09 <renatu> kunal, On eds its creates with diff enddate

 13:09 <kunal> why ?

 13:10 <renatu> kunal, this is how Eds works

 13:10 <renatu> kunal, and this make more sense then:  Thu Jun 11 00:00:00 2015 GMT+0900---Thu Jun 11 00:00:00 2015 GMT+0900

 13:10 <renatu> kunal, you can test it on your deskto

 13:11 <renatu> *desktop

 13:11 <renatu> try create a event with evolution

 13:11 <renatu> and check the result

 13:16 <kunal> so in any case, behavior should be consistent for one day or recurrent event

 13:20 <popey> So essentially we need to cope with what we get from EDS is what you're saying renatu ?

 13:20 <kunal> and this is what i get

 13:20 <kunal> qml: Thu Jun 11 00:00:00 2015 GMT+0900---Fri Jun 12 00:00:00 2015 GMT+0900

 13:20 <kunal> qml: Thu Jun 11 00:00:00 2015 GMT+0900---Fri Jun 12 00:00:00 2015 GMT+0900

 13:20 <kunal> qml: Fri Jun 12 00:00:00 2015 GMT+0900---Sat Jun 13 00:00:00 2015 GMT+0900

 13:20 <kunal> qml: Fri Jun 12 00:00:00 2015 GMT+0900---Sat Jun 13 00:00:00 2015 GMT+0900

 13:20 <popey> for a single event the start/end are same, for a repeating event the start/end differ?

 13:20 <kunal> If I create all day event which span multiple day

 13:20 <kunal> qml: Thu Jun 11 22:30:00 2015 GMT+0900 ---  Fri Jun 12 23:30:00 2015 GMT+0900

 13:21 <kunal> popey, that is case as of now

 13:21 <popey> right

 13:21 <kunal> and behavior is different is i create all day event which span lets say two days

 13:21 <kunal> qml: Thu Jun 11 22:30:00 2015 GMT+0900 ---  Fri Jun 12 23:30:00 2015 GMT+0900

 13:21 <kunal> like this

 13:21 <kunal> I still get

 13:21 <kunal> dates like

 13:21 <kunal> qml: Thu Jun 11 00:00:00 2015 GMT+0900---Fri Jun 12 00:00:00 2015 GMT+0900

 13:21 <kunal> qml: Thu Jun 11 00:00:00 2015 GMT+0900---Fri Jun 12 00:00:00 2015 GMT+0900

 13:21 <kunal> qml: Fri Jun 12 00:00:00 2015 GMT+0900---Sat Jun 13 00:00:00 2015 GMT+0900

 13:21 <kunal> qml: Fri Jun 12 00:00:00 2015 GMT+0900---Sat Jun 13 00:00:00 2015 GMT+0900

 13:21 <kunal> which is not consistent

 13:22 <popey> So when we create an event in qml, we should use the Thu Jun 11 00:00:00 2015 GMT+0900---Fri Jun 12 00:00:00 2015 GMT+0900 format?

 13:22 <popey> rather than adding the time in, as you have?

 13:22 <popey> I mean, when we create multi-day events, the time is irrelavent

 13:22 <popey> so when ticking "all day" we should zero the time

 13:22 <kunal> time is irrelavent

 13:22 <popey> ok.

 13:22 <kunal> that's what I understand

 13:23 <kunal> because we set all day flag to event

 13:25 <popey> renatu: what are we doing wrong if this is expected from eds?

 13:28 <popey> While he thinks on that

 13:29 <popey> I uploaded latest calendar trunk to the store

 13:29 <popey> and have asked QA to test. - even with the above bug

 13:29 <renatu> popey, sorry I am attending 2 meetings :d

 13:29 <popey> understood

 13:29 <kunal> ok,

 13:29 <popey> So I think we need to focus on the above bug as a priority because it will likely block QA approving the app into the store.

 13:29 <renatu> popey, I can discuss with kunal after I finish my hangout

 13:29 <kunal> popey, I modified this MR

 13:29 <popey> ok

 13:29 <kunal> https://code.launchpad.net/~pkunal-parmar/ubuntu-calendar-app/MonthHighlight/+merge/259323

 13:29 <kunal> can you check again

 13:30 * popey looks now

 13:30 <kunal> I tried to adjust month highlight so it dont overlap

 13:33 <popey> kunal: ok, found a couple more issues, will reply on the merge

 13:33 <kunal> ok

 13:33 <kunal> I raised this bug

 13:33 <kunal> https://bugs.launchpad.net/content-hub/+bug/1464244

 13:35 * popey looks

 13:35 <kunal> for ical content hub support

 13:35 <kunal> just for info

 13:35 <popey> ok

 13:35 <popey> we talked about this last week I think with kenvandine ?

 13:35 <kunal> yes

 13:35 <kunal> we did

 13:36 <popey> might have to go back and re-read the log to see what kenvandine said we should do :)

 13:36 <kunal> ok :)

 13:36 <kenvandine> popey, it was to add a content type for event

 13:36 <kenvandine> and calendar-app could provide an import handler for events

 13:37 <popey> http://ubottu.com/meetingology/logs/ubuntu-touch-meeting/2015/ubuntu-touch-meeting.2015-06-04-13.01.log.html

 13:37 <popey> kenvandine: where should the content type go?

 13:37 <kenvandine> i will say that isn't on the short term todo list...

 13:37 <popey> in content-hub itself?

 13:37 <kenvandine> to the calendar-app

 13:37 <popey> sure

 13:37 <popey> oh

 13:38 <kenvandine> the calendar-app would need to be able to read the downloaded file and handle it

 13:38 <kenvandine> content-hub would just let the browser send the file to calendar app

 13:38 <popey> ok.

 13:38 <kunal> kenvandine, that will be fine

 13:38 <kenvandine> i can add it to the wish list in our backlog

 13:38 <kunal> we can handle ical file and format, if we get access to it

 13:39 <popey> please do kenvandine

 13:39 <kenvandine> something like ContentType.Event

 13:39 <kenvandine> ?

 13:39 <popey> kenvandine: any idea how much work this is in content-hub side?

 13:39 <kenvandine> not much, if we just add ContentType.Event

 13:39 <kenvandine> then a tiny tweak in the browser

 13:39 <popey> this has been a long requested feature for calendar

 13:40 <popey> and makes it a lot more useful, especially for people who don't sync to the evil empire

 13:40 <kenvandine> popey, i'll get it on the list... you help convince bfiller that we should do it :)

 13:40 <popey> sure!

 13:41 <popey> expect email :)

 13:41 <kunal> thanks :)

 13:41 <popey> \o/

 13:41 <kunal> popey, "Swipe between months, I'd expect no day to be hi-lighted, but the 1st of the month always is."

 13:42 <popey> yeah

 13:42 <kunal> so by default there shold not be any highlight ?

 13:42 <popey> correct

 13:42 <popey> until I tap one

 13:42 <popey> As I understand it.

 13:42 <kunal> as of now I am selecting 1st by default

 13:42 <kunal> ok, I can make it so

 13:42 <popey> We can confirm with James, when he's back next week.

 13:42 <popey> but it looks odd to me

 13:43 <kunal> ok,

 13:43 <popey> Anything else?

 13:43 <kunal> but then I used similar logic for weekview highlight as well

 13:44 <kunal> yes

 13:44 <kunal> Sometimes I can trigger a situation where a day is hi-lighted with grey box _and_ has orange in-fill... *and* today is highlighted in orange too.

 13:44 <kunal> for this

 13:44 <kunal> so you mean you see three highlight ?

 13:44 <kunal> on same month or between two month ?

 13:46 <popey> i see two highlights

 13:46 <popey> one for today - orange

 13:46 <popey> one for another day in the month, also orange

 13:46 <popey> I can't reproduce it often

 13:46 <popey> so unless you can, it may be some wierd glitch here

 13:47 <kunal> ok,

 13:47 <kunal> I will try to reproduce

 13:48 <popey> thanks

 13:48 <kunal> ok, nothing else from me now

 13:51 <popey> Great, thanks kunal

 13:51 <popey> (and renatu) :)

 13:51 <popey> take care.

 13:51 <popey> #endmeeting



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