14:00 <popey> #startmeeting Ubuntu Touch Calendar App meeting 14:00 <meetingology> Meeting started Thu Jul 4 14:00:51 2013 UTC. The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 14:00 <meetingology> 14:00 <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:01 <popey> blueprint: https://blueprints.launchpad.net/ubuntu-phone-commons/+spec/initial-calendar-development 14:01 <popey> bugs: https://bugs.launchpad.net/ubuntu-calendar-app/+bugs 14:01 <popey> reviews: https://code.launchpad.net/ubuntu-calendar-app/+activereviews 14:01 <popey> burndown: http://status.ubuntu.com/coreapps-13.10/ 14:01 <popey> (I should script that) 14:01 <popey> anyway, how are you pkunal-parmar ? 14:01 <pkunal-parmar> yes, I am good 14:02 <popey> Did you see jono's email earlier / last night? 14:02 <pkunal-parmar> regarding what ? I am not sure. 14:03 <popey> hmm. i can't tell if you were on the list of not because he used BCC 14:03 <popey> the subject was "Call To Action! Getting Our Core Apps Dogfood Ready" 14:03 <popey> I can forward it to you if you didn't get it 14:04 <pkunal-parmar> ok, no i did not received such much, please forward 14:04 * dpm forwards it now 14:04 <popey> sorry about that. It's quite long, you don't need to read it right away ☻ 14:05 <pkunal-parmar> ok :) 14:05 <popey> The short summary is, we'd like to get all the apps to be "dogfoodable" by the end of this month 14:05 <pkunal-parmar> ok 14:05 <popey> We have a wiki page which lists the absolute minimum features we'd like to see finished by then.. 14:05 <popey> https://wiki.ubuntu.com/Touch/CoreApps/Dogfooding 14:05 <dpm> pkunal-parmar, ok, I've forwarded you the message 14:06 <popey> we have reviewed the work items and massaged them a bit. dpm do you want to talk about that a bit? 14:06 <dpm> sure 14:07 <dpm> in light of this new initiative 14:07 <dpm> to get our apps in a dogfoodable state, we are reviewing the work items for our core apps 14:07 <dpm> so that we ensure we're focusing on the most important features 14:08 <dpm> on the calendar app, that essentially meant 14:08 <dpm> after having had the designs for the new views 14:08 <dpm> to make sure work items for each one of the views are in the blueprint 14:09 <dpm> we've also reprioritized (removed or postponet) some other work items 14:09 <dpm> that we thought were of a lower priority for the dogfooding goal 14:09 <dpm> pkunal-parmar, does that make sense so far? 14:10 <pkunal-parmar> yes, that seems fine 14:10 <dpm> cool 14:10 <dpm> another thing we'd like to ensure is that developers can spend their time developing the app, and we've decided to rather involve the QA community in testing and writing tests 14:10 <pkunal-parmar> so , https://wiki.ubuntu.com/Touch/CoreApps/Dogfooding, this is our blueprint now ? 14:11 <pkunal-parmar> ok, that's nice :) 14:11 <popey> no, that's just high level goals. the blueprint is still in place 14:11 <popey> dpm: do you want to paste in the changes? 14:11 <dpm> pkunal-parmar, that's the page we're looking at as a general overview. The blueprint is still the same 14:11 <pkunal-parmar> ok 14:11 <dpm> yeah, that was going to be my next step :) 14:12 <dpm> pkunal-parmar, let me update the work items in the blueprint so that you can see the actual changes 14:12 <pkunal-parmar> great 14:12 <oSoMoN> dpm, popey: so involving the QA community to write tests for existing code sounds like a good idea, what about newly written code? 14:13 <dpm> oSoMoN, I think at this point the important thing is to get an initial set of tests up and running 14:13 <dpm> in the future, 14:14 <dpm> once we've got those, we might want to look at test-driven development, and get those who implement the features to provide a test when they land them 14:15 <dpm> but at this point, we think the main goal for the developers might be getting the apps in a state that they can be used for your everyday 14:15 <dpm> i.e. putting those with the best skills to do what they're best at and like best :) 14:16 <oSoMoN> that makes complete sense 14:17 <dpm> cool 14:17 <pkunal-parmar> oSoMoN, can you review my merge request, when you have time 14:17 <dpm> I'm still fighting with pasting the blueprint items, give me a sec :) 14:18 <oSoMoN> pkunal-parmar: yeah, sorry I’ve been super busy with the browser and notes app (and on holidays), but I’m not forgetting about your app 14:18 <oSoMoN> I mean, your MR 14:18 <pkunal-parmar> ok, thanks :) 14:18 <oSoMoN> pkunal-parmar: hopefully I’ll get to it sometime today or tomorrow 14:19 <dpm> pkunal-parmar, ok, here's how the reviewed blueprint looks like now: https://blueprints.launchpad.net/ubuntu-phone-commons/+spec/initial-calendar-development 14:20 <Cimi> btw, I have refactored the way the calendar works 14:20 <dpm> pkunal-parmar, essentially, as we said, we deprioritized some items and moved the testing actions you had assigned to be those for implementing the new views 14:20 <dpm> hey Cimi 14:20 <Cimi> this is the branch https://code.launchpad.net/~cimi/ubuntu-settings-components/calendar-newmodel 14:20 <Cimi> now is infinite 14:20 <Cimi> or you have have limits 14:21 <dpm> Cimi, so do you think we can mark "[cimi] Switch month component to reusable SystemComponents.Calendar: TODO" as INPROGRESS ? Is this the right work item? 14:21 <Cimi> yes 14:21 <oSoMoN> Cimi: do you have someone to review your code? 14:21 <dpm> Cimi, cool. And what's the status on this one: "[cimi] Package SystemComponents: TODO" ? 14:22 <Cimi> oSoMoN, micheal zanetti was 14:22 <Cimi> dpm, TODO 14:22 <oSoMoN> Cimi: ok, good 14:22 <dpm> Cimi, ack, thanks! 14:22 <pkunal-parmar> Cimi, so now month view can browse month infinitely ? 14:22 <Cimi> dpm, I'll work on that when I am happy of the code 14:22 <Cimi> dpm, no point of packaging crap stuff :) 14:22 <Cimi> pkunal-parmar, indeed 14:23 <dpm> makes sense :) 14:23 <pkunal-parmar> ok 14:23 <Cimi> pkunal-parmar, unless you use minimumDate or maximumDate to set limits 14:23 <dpm> pkunal-parmar, do the updated blueprint items make sense to you? Are you happy to work on the items you've got assigned? 14:23 <Cimi> there's like a listmodel 14:23 <Cimi> that gets prepend or append elements 14:23 <Cimi> when you interact 14:24 <Cimi> 5 max items 14:24 <Cimi> the current month plus some buffer 14:24 <pkunal-parmar> ok, that make sense 14:24 <pkunal-parmar> that was for cimi 14:25 <pkunal-parmar> regarding blueprint, [pkunal-parmar] Implement spread/pinch to zoom in/out: TODO 14:25 <pkunal-parmar> I have doubt for this 14:25 <pkunal-parmar> I want be able to test it 14:25 <pkunal-parmar> I test on dektop only 14:25 <popey> Good point! 14:25 <dpm> hmm, yeah, you're right 14:26 <popey> We may need to find someone with a device to look at that. 14:26 <dpm> let's unassign it for now until we figure this out 14:26 <dpm> done 14:26 <popey> pkunal-parmar: Do you have a laptop which supports multitouch? 14:26 <popey> (on the touchpad) 14:27 <pkunal-parmar> my laptop's touchpad support's multitouch 14:27 <pkunal-parmar> but i am not sure if driver supports it 14:27 <pkunal-parmar> it was working on windows 14:27 <pkunal-parmar> but not on ubuntu 14:27 <popey> Might be worth having a play with that. We have multi-touch libraries in Ubuntu 14:27 <popey> which laptop is it? 14:28 <pkunal-parmar> samsung sens rc710 14:28 <popey> ok. 14:29 <popey> Anything else before we wrap up? 14:29 <dpm> yeah, one last bit 14:29 <dpm> about switching to using the Qt Organizer API 14:29 <pkunal-parmar> I was reading something about simulator on mailing list, does that support multitouch ? 14:29 <dpm> hm, not sure what it was, I've not heard about it 14:30 <pkunal-parmar> ok, regarding Organizer API, popey told me that its already fixed in ppa:canonical-qt5-edgers/qt5-beta2 14:30 <dpm> indeed 14:31 <dpm> There is a work item to switch to using Qt Organizer to store events. Up until now, event info could only be stored in memory, which meant that when the app was closed, events could not be saved. Now you can install qtdeclarative5-jsondb-plugin 14:31 <pkunal-parmar> but I am not able to use it 14:31 <pkunal-parmar> Cannot mix incompatible Qt library (version 0x50002) with this library (version 0x50100) 14:31 <pkunal-parmar> Aborted (core dumped) 14:31 <dpm> from that PPA 14:31 <dpm> ah, bummer :( 14:31 <dpm> let me see if Mirv can help us 14:31 <pkunal-parmar> yes, there is some conflict 14:31 <pkunal-parmar> so i had to revert it 14:31 <pkunal-parmar> so not able to test those change 14:32 <dpm> I've asked if he can join us here, he might be able to help us 14:32 <pkunal-parmar> if i can get source code, then I might try compiling individual lib and try to use it 14:32 <popey> the source is in that ppa 14:32 <popey> add the ppa then "apt-get source <package>" 14:32 <pkunal-parmar> its whole Qt or just Organizer ? 14:33 <popey> Well, source for every package should be there. 14:33 <pkunal-parmar> I mean fix is in just Organizer or some other Qt module as well 14:33 <dpm> pkunal-parmar, I think it's just a matter of version incompatibility 14:34 <dpm> let's see if Mirv can shed some light on this, it might save us time in investigating it 14:34 <dpm> anyway, shall we jump into the design call? 14:34 <popey> we could ask in #ubuntu-app-devel where mirv and the other sdk guys hang out 14:34 <popey> thanks guys 14:34 <popey> #endmeeting