== Meeting information ==
 * #ubuntu-touch-meeting: Calendar App, 23 May at 14:07 — 14:37 UTC
 * Full logs at [[http://ubottu.com/meetingology/logs/ubuntu-touch-meeting/2013/ubuntu-touch-meeting.2013-05-23-14.07.log.html]]



== Meeting summary ==




== Vote results ==




== Action items ==

 * (none)



== People present (lines said) ==

 * mhall119 (44)
 * Cimi (36)
 * pkunal-parmar (20)
 * timp (10)
 * balloons (6)
 * meetingology (3)
 * dpm (1)



== Full Log ==


 14:07 <mhall119> #startmeeting Calendar App

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

 14:07 <meetingology> 

 14:07 <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:08 <mhall119> Blueprint: https://blueprints.launchpad.net/ubuntu-phone-commons/+spec/initial-calendar-development

 14:08 <mhall119> Launchpad: https://launchpad.net/ubuntu-calendar-app

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

 14:09 <mhall119> pkunal-parmar: do you know if the status of the work items on the Blueprint are up to date?

 14:09 <pkunal-parmar> [mariob] Create the "Create event" view: TODO

 14:10 <pkunal-parmar> this, I think David, sent mail to design team, and we are waiting for feedback

 14:10 <mhall119> asking for designs for that screen?

 14:11 <pkunal-parmar> yes,  we sent some prototype screens and was looking for feedback

 14:11 <mhall119> ok, I'll mark that one as BLOCKED

 14:11 <pkunal-parmar> ok

 14:12 <pkunal-parmar> That UI also needs Date and Time picker

 14:12 <pkunal-parmar> I heard SDK team is going to create those, is that correct ?

 14:13 <pkunal-parmar> [mariozorz] Implement backend data model

 14:13 <timp> that is correct, but it is not a priority for the SDK beta release

 14:13 <pkunal-parmar> ok

 14:13 <pkunal-parmar> that, I guess now we are planning to use, Organizer API from Qt with UDS as backend

 14:13 <timp> Cimi: or are you working on those? I am not sure if Date/Time picker is the same as what you are working on (calendar component?)

 14:14 <mhall119> pkunal-parmar: yes, the Organizer API will let us add an evolution-data-server backend without you having ot change code

 14:15 <Cimi> timp, no

 14:15 <pkunal-parmar> ok, then I guess we dont need "[mariozorz] Implement backend data model" this workitem, or need to change its scope

 14:15 <Cimi> so here I come

 14:15 <mhall119> pkunal-parmar: we also have: Switch to system-wide event storage: TODO

 14:15 <Cimi> for the indicators we need a calendar component

 14:15 <mhall119> which I suppose is the one to keep

 14:15 <Cimi> thus I wanted to grab the code from the calendar app

 14:16 <Cimi> fix it

 14:16 <Cimi> add tests

 14:16 <Cimi> and then make the calendar app simply import the component

 14:16 <Cimi> I was wondering if you guys wanted to work on that too

 14:17 <pkunal-parmar> you mean month View ? or what exactly ?

 14:17 <mhall119> Cimi: I think the Calendar's needs for a calendar widget are likely to be much more, and much more complex, than apps that just need a widget

 14:18 <Cimi> mhall119, like what?

 14:18 <Cimi> mhall119, models?

 14:19 <mhall119> I'm thinking the kind of information to display

 14:19 <mhall119> like indications about what events and how many are on each day

 14:19 <Cimi> indeed, that's what I meant with models

 14:19 <Cimi> models of multiple calendars

 14:20 <mhall119> things that you wouldn't necessarily need in a simple date-picker

 14:20 <Cimi> the calendar in indicators should not be a simple date time picker

 14:20 <mhall119> which raises the question of whether we want to have all of that in a simple date-picker anyway, so that we can re-use components

 14:20 <Cimi> I would show an indicator of pending events

 14:21 <timp> can I try to make something clear?

 14:21 <timp> date picker will be a simple... date picker

 14:21 <mhall119> ok, the calendar in the datetime indicator would be closer to the calendar app's, yes

 14:21 <timp> and a calendar component that cimi works on is something else, am I correct?

 14:21 <Cimi> yeah

 14:21 <Cimi> a calendar is a calendar

 14:22 <Cimi> a date time picker is usually three sliders to change date

 14:22 <timp> a date picker might look like a calendar. but maybe not. I haven't checked for designs yet.

 14:22 <Cimi> I believe the month view of the calendar app will be the same of very same of the calendar indicator

 14:22 <mhall119> ok, in that case I think we're all in agreement that re-using is best

 14:23 <Cimi> timp, a date time picker has to have at least a three slider mode

 14:23 <Cimi> timp, imagine today is 23 may 2013

 14:23 <mhall119> so then where should the code live?  In the Calendar app?  In the Indicator?  Some 3rd package?

 14:23 <Cimi> and you want to set 17 June 1926

 14:23 <Cimi> keep click on year back :)

 14:23 <Cimi> until you arrive 1926

 14:23 <Cimi> mhall119, it will move somewhere in the SDK

 14:24 <mhall119> Cimi: http://jqueryui.com/datepicker/ uses a calendar-month-view widget

 14:24 <Cimi> mhall119, #bad

 14:25 <Cimi> mhall119, again, on a phone do 17 june 1926

 14:25 <Cimi> swiping calendars :D

 14:25 <mhall119> but common and, I would say, even expected

 14:25 <timp> I'm not sure that is bad. I see some advantages, for example it may be handy to see the weekday when you pick a date

 14:25 <timp> I think in the end design will make the decision

 14:25 <mhall119> Cimi: I suppose it's up to the developer to know the expected use cases

 14:25 <timp> maybe they have already, but I am not aware of it

 14:26 <timp> perhaps a combination of the two ideas

 14:26 <Cimi> mhall119, indeed

 14:26 <Cimi> mhall119, that's why I believe we need both

 14:26 <Cimi> mhall119, or when we need to set a date of birth, it's a nightmare

 14:26 <mhall119> at any rate, Cimi will you work with the calendar app developers to make sure they can re-use the component once you've pulled it out?

 14:27 <Cimi> mhall119, that's why I was attending the meeting

 14:27 <Cimi> mhall119, I hoped to find someone

 14:27 <Cimi> that was working on the widget itself

 14:27 <Cimi> so we can work together

 14:27 <mhall119> pkunal-parmar: who's done the most work on that part of the app?

 14:28 <pkunal-parmar> I can help

 14:28 <mhall119> cool

 14:28 <Cimi> awesome

 14:28 <mhall119> so we're almost out of time, and the call with the design team is going to start in just a couple minutes

 14:28 <Cimi> pkunal-parmar, I'll start reviewing and putting the calendar component somewhere

 14:29 <pkunal-parmar> ok

 14:29 <pkunal-parmar> sure, let me know if you need anything from me

 14:29 <mhall119> pkunal-parmar: I'm updating the Blueprint, and moving the rest of the TODO work items to month-2 milestone

 14:29 <mhall119> pkunal-parmar: one last thing we need to discuss is setting milestone targets for Alpha, Beta and Final release

 14:29 <pkunal-parmar> ok

 14:30 <mhall119> I think we should make month-2 our Alpha goal, with it using the Organizer API

 14:30 <mhall119> that, I think, is our highest priority ATM

 14:31 <pkunal-parmar> I agree, anyway we made enough progress on UI side

 14:31 <mhall119> then we can shoot for a Beta in month-3

 14:31 <mhall119> which is mid-July

 14:32 <mhall119> and hopefully by then it'll have the e-d-s backend

 14:32 <pkunal-parmar> sorry, when will be Alpha ?

 14:32 <mhall119> mid-June

 14:32 <pkunal-parmar> ok

 14:32 <mhall119> about 3 weeks

 14:33 <mhall119> do you think mid-July is reasonable for a Beta?

 14:33 <pkunal-parmar> support for E-D-S will be part of calendar scope or some other team will be working on it ?

 14:33 <mhall119> or should we push it back to mid-August?

 14:33 <dpm> hey pkunal-parmar, joining the design call?

 14:33 <mhall119> pkunal-parmar: another team

 14:33 * balloons notes he didn't know you met in a special room :-)

 14:33 <mhall119> dpm: just wrapping up here

 14:33 <balloons> I wanted to talk about autopilot really quick with all the teams

 14:34 <mhall119> dpm: in the design call, please make sure we're going to get a design for the "Add an Event" dialog, including date & time picker, we're blocked on that

 14:34 <mhall119> balloons: you have -4 minutes, go!

 14:35 <balloons> lol.. ok, I'll be very brief. Martin is still working on setting up a jenkins to autorun the autopilot tests for the core apps. However, many apps don't have tests written. In addition, the tests written that we found didn't seem to work properly. Finally, the tests also need to be ported to autopilot 1.3 :-)

 14:36 <pkunal-parmar> do we have some documentation on how to write those ?

 14:36 <mhall119> docs link?

 14:36 <balloons> So, just a friendly reminder to do a few things: 1) Write your autopilot tests, and make sure they work (even if you have to keep them simple at first). 2) If you have old tests, convert them to 1.3: http://unity.ubuntu.com/autopilot/porting/porting.html

 14:36 <balloons> pkunal-parmar, mhall119 yes.. you can use the wiki page: https://wiki.ubuntu.com/Touch/Testing/Autopilot

 14:36 <mhall119> and you can always find balloons in #ubuntu-touch (right balloons?) if you need help during the week

 14:37 <balloons> If there's lacking info there or something is wrong, etc, please just ping me and I'm happy to help

 14:37 <mhall119> alright, wrapping itup

 14:37 <mhall119> #endmeeting



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