13:02 #startmeeting Calendar meeting 13:02 Meeting started Thu Aug 20 13:02:18 2015 UTC. The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 13:02 13:02 Available commands: action commands idea info link nick 13:02 How are you kunal ? 13:02 mihir: you around? 13:02 hey popey 13:02 I am good, how are you guys ? 13:02 Hey kunal :) 13:02 yo guys 13:02 great, hey mihir ! 13:03 Ok here thanks 13:03 JMulholland: did you have any design updates for calendar? 13:03 hey faenil :) 13:04 o/ 13:04 we have a couple of design related bugs... 13:04 https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1466488 13:04 https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1464459 13:04 popey: Nothing to report, still waiting to see how we get on with the convergent version 13:04 https://docs.google.com/document/d/1UZEKYB1JS0CO0gEiPu701rhZSHimJYq6EgeLNhxG_1I/edit# 13:04 * JMulholland looks at the bugs 13:05 Right 13:05 First bug: I agree, minute by minute fidelity is of little or no use 13:06 second bug: I asked visual design for a suitable pallete of colours for us to use (based on the redesign work theyre doing). Will follow up and give them a nudge again 13:06 This is really a UITK bug 13:06 thanks 13:06 I already assigned the second bug to a visual designer, but I’ll follow up none the less 13:08 JMulholland: when you say "see how we get on with the convergent version", do you mean you're waiting on +1 from someone as it's work in progress? 13:09 popey more that I’m waiting on the work in progress and on stand-by for any gaps we might have, things that arent working in practice, etc 13:09 okay. 13:10 Thought for a moment you were expecting implementation from us! :D 13:10 popey: when do we expect this apps to be used on desktop ? 13:10 Good question! :) 13:10 We have a sprint next week, which should help cement things a bit 13:11 I wouldn’t pressume that popey, I’d ask you! haha 13:11 popey: okay great :) 13:14 JMulholland, 13:14 https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1432629 13:14 I will catch up with Bill next week also, to see what is happening with EDS / Buteo 13:14 can you clarify how we can reach to that respond event dialog ? 13:14 kunal yes? 13:14 kunal right 13:15 popey, that would be nice 13:15 kunal I would expect that an unresponded event would appear in the calendar (check the spec i linked at the start for how they might look) 13:16 kunal tapping one of those would show our usual event view, but with the buttons shown in the image I added to that bug report 13:16 make sense? 13:17 so when we tap unresponded event, we see that dialog, and once we respond it goes to event details ? 13:18 It’s not actually a dialogue but instead its the event view with some buttons 13:18 that way the user can see all the usual info relating to the event before they decide how they want to respond 13:19 ohh, so we have those buttons below event title ? 13:19 That’s right 13:20 but then where are the other details, or you just did not displayed for this pic ? 13:20 and the usual back-nav in the header area, so our users can see all the relevant info and arent forced to make a decision when they tap an unresponded event 13:21 no displayed, but I can do another sketch that has a more-filled-out event if that would help? 13:21 *not displayed 13:21 yes, that would be nice, I think I am confused 13:22 OK, I’ll do that and update the bug 13:24 Ok, any other bugs to look at? 13:24 JMulholland, one more bug 13:24 https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1407997 13:24 shoot 13:25 I realised we already have one checkbox in calendar list dialog 13:25 putting another one will not look nice 13:25 what do you think ? 13:26 I see what you mean, we cant have the enabled/disabled calendars check-box as well as one for disabling reminders… 13:26 yes, exactly 13:27 There may be an argument for the calendar list screeen to have a ‘>’ next to each entry, and in there we’d place an enabled/disabled switch and a reminders on/off switch 13:28 hm 13:28 so tap calendars, tap a calendar account in the list, then show the options in their own screen 13:28 ok, that can be done 13:28 hangon, popey’s not convinced :) 13:28 colours / enable/disable and reminders? 13:28 no, not unconvinced 13:28 even better 13:29 just pondering how many steps we take to do things 13:29 It would be a good place to allow people to configure calendar colours 13:29 which would be nice to have too 13:29 yeah, and would give more room for the calendar name 13:29 because you wouldn't have the colour thing on the front screen 13:30 good point 13:30 ok, I’ll sketch out some screens and attach them to the bug ASAP 13:30 thanks 13:30 ok, great 13:30 np 13:30 popey, for the same bug 13:31 we can add UI and flag, but actual enabling and disabling needs to be done by indicator or notification 13:31 It does? 13:31 can the indicator/notification not read that state? 13:33 I believe, as of now it just checks reminder property in envets 13:33 if event has reminder it just fire it 13:33 but if we add flag in calendar, before firing event based on reminder value 13:34 it needs to read new flag from calendar/eds collection 13:34 and act accordingly 13:34 hmm 13:34 This needs to be taken into account with the new notification stuff. 13:35 yes, I think so too 13:35 Ok, will speak to charles about this. 13:36 great 13:37 Ok, anything else? 13:38 I guess, I am done 13:38 Nothing on my end, I’ll follow up on those bugs asap 13:38 Hmm nothing from my side as well.. 13:39 what I feel is two things , we should refactor the code , i tried but getting some Cmake errors 13:39 i meant little more structured , like what other apps are following. 13:39 Refactor would make sense during the change to implement desktop convergence design 13:39 especially if we a new series in launchpad 13:40 we can continue to maintain the existing calendar while we update the design 13:40 popey: okay , updating will be the same as using the existing code and use in diff UI , am I correct/ 13:40 ?* 13:41 sure, but there may be underlying changes along the way 13:41 not just a ui change 13:41 you may notice things that could be optimised for example 13:43 but we can break that down once the design is done. 13:43 okay 13:43 so let's decide once you come back from the sprint , what to do with this. 13:43 okay! 13:43 anything else? 13:43 nothing from my side !! 13:44 Ok, lets wrap then, thanks everyone! 13:44 #endmeeting