17:00:48 <popey> #startmeeting Ubuntu Touch Calendar App Meeting
17:00:48 <meetingology> Meeting started Thu Mar  7 17:00:48 2013 UTC.  The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
17:00:48 <meetingology> 
17:00:48 <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
17:00:57 <popey> who is here?
17:00:57 <popey> o/
17:01:04 <popey> #topic introductions
17:01:21 <popey> I'm Alan Pope, I'm an Engineering Manager at Canonical, and have been asked to act as a Developer Liaison for all the touch apps..
17:01:33 * popey tickles dpm and mhall119
17:02:10 <markg85> I guess it would be nice of me to introduce myself as nobody probably knows me in here.
17:03:29 <popey> go for ity
17:03:31 <popey> -y
17:03:35 <markg85> I'm Mark, i occasionally work on KDE software and am playing with the Akonadi technology. My goal in there is to make a completely new calendar application for KDE written in QML.
17:03:58 <dpm> hey all
17:04:13 <markg85> Last week i attended the KDEPIM sprint (my second one) and made a lot of progress in making Akonadi calendar data availablei n pure QML components.
17:04:49 <frankencode> hi all
17:05:04 <popey> oh excellent. hi frankencode, we're just doing introductions..
17:05:05 <frankencode> missed the design meeting (tz=CET?)
17:05:09 <markg85> I am by no means a Ubuntu user or developer (actually using Archlinux and KDE ^_-) but i would certainly like it if we could work together on the calendar part because that would benefit both parties. And that's why i'
17:05:24 <markg85> i'm in here (invited by popey)
17:05:42 <frankencode> hi, mark
17:05:48 <markg85> Hi frankencode
17:06:22 <mariob> hi all
17:06:31 <markg85> frankencode: i guess you missed my two lines before you entered.. Shall i send them to you again?
17:06:42 <frankencode> yes, thx
17:06:54 <markg85> frankencode: I'm Mark, i occasionally work on KDE software and am playing with the Akonadi technology. My goal in there is to make a completely new calendar application for KDE written in QML.
17:07:03 <markg85> frankencode: Last week i attended the KDEPIM sprint (my second one) and made a lot of progress in making Akonadi calendar data availablei n pure QML components.
17:07:15 * mhall119 is here
17:07:22 <popey> Great to see everyone!
17:07:32 * popey is excited, some great progress has been made in such a short time!
17:07:40 <popey> ok..
17:07:57 <frankencode> yes, is fun to code qtquick 2
17:07:57 <popey> #topic Update blueprints - assign work items
17:08:12 <popey> So, I mailed the list about this earlier on...
17:08:29 <popey> the blueprint for the calendar app has a bunch of work items listed.. https://blueprints.launchpad.net/ubuntu-calendar-app/+spec/initial-calendar-development
17:08:49 <popey> Having the work items is great, what's even better is having people assigned to them ☺
17:09:23 <mariob> I need to change my work item... I'm on the "create event" view now since there's actually not an week view
17:09:30 <mariob> at not least a journey for it
17:09:50 <frankencode> yes, most of the items are confusing
17:10:02 <dpm> I think we can use this meeting to clean them up
17:10:18 <markg85> Can i ask what backend is used for the calendar if any?
17:10:42 <mariob> markg85: non for now, well a sqlite actually
17:10:57 <mariob> markg85: from within javascript
17:11:06 <frankencode> i was thinking a bit about the backend
17:11:14 <mariob> same here
17:11:30 <popey> so are there tasks which we can pick off and allocate right away?
17:11:33 <frankencode> but still have no clue, especially synchronization can be nasty
17:11:34 <markg85> Then this might be of interest (i did that in the last KDEPIM sprint last year) http://kdeblog.mageprojects.com/2012/10/17/the-kde-pim-meeting-just-awesome/
17:11:51 <mariob> markg85: This is what is used for now: http://bazaar.launchpad.net/~pkunal-parmar/ubuntu-calendar-app/EventAPI_EventView/view/head:/EventsAPI.js
17:12:31 <dpm> markg85, perhaps we can discuss this at the end of the meeting? I'm just suggesting it so that we can focus on the agenda first
17:12:54 <dpm> I think it'd be good to finish off the list of work items first
17:13:06 <markg85> Fine with me
17:13:13 <dpm> excellent, thanks markg85
17:13:46 <dpm> so I'm just taking notes on the fly: http://pad.ubuntu.com/xxmjXq1Qvu
17:14:30 <frankencode> i'm not allowed to access
17:14:51 <mariob> Ok, should I modify the blueprint myself now?
17:15:00 <popey> https://launchpad.net/~ubuntu-etherpad join that team
17:15:08 <popey> and it will give you access to the pad dpm created frankencode
17:15:56 <dpm> mariob, yes please, feel free to, but let's discuss a set of actions everyone is happy with and then we can update the blueprint at the end of the meeting. Does that sound good?
17:15:56 <popey> ok, approved you both, you should have access to http://pad.ubuntu.com/xxmjXq1Qvu now
17:16:25 <mariob> dpm: yes
17:16:32 <dpm> cool
17:16:56 <frankencode> works
17:17:27 <mariob> should the "new event view" be removed and replaced with "create event view"
17:17:30 <dpm> frankencode, the design team were really happy with your new branch, nice work
17:18:03 <frankencode> yes missed the meeting
17:18:20 <robru> dpm, hey, I'm up... what do you guys want to know about friends?
17:19:01 <mhall119> yes, I've been playing with the branch too, and it's fantastic
17:19:08 <dpm> hi robru, thanks for coming back to us. I sent an e-mail to you guys, so you can take it from there
17:19:40 <robru> dpm, oh, ok. I'm still wading through my emails this morning. Will reply ASAP ;-)
17:19:51 <dpm> excellent, thanks robru!
17:20:11 <frankencode> my focus is still prototyping the ui logic
17:21:42 <dpm> frankencode, does the work item there reflect that, or do you want to break it out in other smaller ones/add new ones?
17:21:52 <frankencode> ?
17:22:11 <frankencode> no thx
17:22:22 <frankencode> next item on my list: collaborate on the data model for the backend
17:22:48 <dpm> I think Mario Z was doing the data model, right?
17:22:51 <markg85> Is this where i can drop in?
17:22:54 <frankencode> i prefer a relational data model and go with the sqlite
17:23:18 <dpm> markg85, please, go ahead
17:23:36 <markg85> Right oke.
17:23:55 <frankencode> markg85: i thought start out with a local store and later-on make it sync with u1db, what you think?
17:24:27 <markg85> frankencode: my idea is quite a bit different from that
17:24:40 <frankencode> then elaborate
17:24:42 <mhall119> popey: on the desktop Unity uses e-d-s for datetime indicator integration
17:24:50 <markg85> In KDE we work with Akonadi. Which is a C++ project (no Qt or KDE involved there)
17:24:51 <mhall119> do you know how it will work on phablet/unity next?
17:25:01 <popey> I don't.
17:25:12 <popey> i think there was a session at vUDS about it though..
17:25:22 <popey> didrocks will likely know
17:25:38 <markg85> Mond you, Akonadi has previously been ported to the Nokia N900 so it is perfectly suitable of being used on mobile devices and will take a lot of pain away
17:25:51 <markg85> As in no more synchronization issues, multiple backends at will
17:26:06 <markg85> integration with a dozen services
17:26:15 * mariob thinks multiple backend is important
17:26:32 <markg85> And backed by companies (Kolab, KDAB) and they are doing very well.
17:26:57 <markg85> In the recent KDEPIM sprint that i mentioned earlier i sat down to make that exact data (the calendar) easily available through QML
17:26:59 <mariob> markg85: Do you know what Jolla is using?
17:27:26 <markg85> I have made an API draft of that here: http://community.kde.org/Calendar_API_QML (i invite you to take a look at it)
17:27:35 <markg85> mariob: nope, don't know
17:27:51 <mariob> All: Should we assign an item to markg85 so create a simple demo of the API etc?
17:28:04 <markg85> Using the API that i propose there, all you have to do is create a graphical frontend
17:28:26 <markg85> mariob: i already have a demo app, just not on this computer
17:28:35 <markg85> but i can send it to you if you want
17:28:37 <popey> perhaps you could mail the list?
17:28:46 <popey> we could continue the discussion there then?
17:28:49 <markg85> though that is aimed at replacing the KDE calender popup from the clock
17:28:59 <mariob> popey: agree
17:29:50 <markg85> I would really like to note that designing your own API in this matter will do a lot more harm for the devs assigned to that task then just using Akonadi.
17:30:22 <markg85> So i guess the question becomes: Would it be a feasible option to use Akonadi?
17:30:25 <dpm> markg85, do you think you could follow up on the mailing list with a demo for the team to study? Here's the mailing list: https://launchpad.net/~ubuntu-touch-coreapps
17:31:08 <markg85> dpm: yes, i can. Though that will have to wait till tomorrow or saturday
17:31:19 <popey> that's fine.
17:31:29 <dpm> indeed, that's good markg85
17:31:33 <mhall119> I'm all for re-using and collaborating whenever feasible
17:31:44 <markg85> Sorry to say, but i have to leave now. Will you guys be here in !30 minutes?
17:31:56 <mhall119> markg85: here or in #ubuntu-touch
17:31:58 <markg85> ~30*
17:32:04 <popey> #ubuntu-touch is better
17:32:07 <markg85> oke
17:32:09 <popey> we'll have other meetings here, just ping us
17:32:14 <popey> #topic Set milestones
17:32:17 <markg85> cya in 30 minutes then :)
17:32:24 <popey> so I mentioned this on the mailing list..
17:32:47 <popey> we'd like to target mid-may for an alpha-quality version of the calendar app (all of the apps in fact)
17:33:51 <popey> i think we can do that.. with 10 weeks between now and then
17:33:51 <mariob> popey: Do we have a well define scope for that?
17:33:51 <frankencode> i have no time in may, so let it be end of april
17:34:05 <popey> no mariob, and that's something we are going to work on ASAP
17:34:08 <dpm> markg85, what's your Launchpad id, so that I can add an action to e-mail the demo for you on the blueprint where we're tracking the project?
17:34:27 <popey> frankencode: well, it's between now and may, so april is good ☺
17:34:42 <mhall119> frankencode: we should be far enough along, and have enough built up, by end of April for others to carry if you're not available
17:34:50 <popey> +1
17:35:08 <frankencode> +1
17:35:30 <popey> ok, cool.
17:35:38 <popey> final thing..
17:35:45 <popey> (from me)
17:35:48 <popey> #topic Populate PPA
17:36:02 <popey> as of today we now have a PPA  -> https://launchpad.net/~ubuntu-touch-coreapps-drivers/+archive/daily
17:36:15 <frankencode> will there be support for raring?
17:36:16 <popey> it contains debs (x86, amd64 and armhf) with builds of all the apps
17:36:29 <popey> frankencode: yes, we can add that
17:36:46 <popey> however I expect those packages will work both on quantal and raring
17:36:48 <mhall119> we'd need separate branches
17:36:52 <popey> if nt we can fix that.
17:37:08 <frankencode> no need for starters, have to boot another machine then...
17:37:19 <mariob> frankencode: virtualbox :)
17:37:37 <popey> qmlscene doesn't work in virtualbox.. when I've tested it
17:37:37 <frankencode> mariob: spot on
17:37:47 <popey> needs GLES, which vbox doesn't implement
17:38:00 <popey> we're looking at how to implement a simulator / emulator though
17:38:06 <mariob> popey: oh, actually I've got vmware and it works fine
17:38:15 <popey> that's good news.
17:38:25 <frankencode> my realbox is even better;)
17:38:52 <frankencode> the package server takes trunk branch and creates nightly packages?
17:38:55 <popey> I'll send a mail to the list with some more details about the PPA shortly
17:38:57 <mhall119> so is the code currently in lp:~frankencode/ubuntu-calendar-app/MonthView going to be landing in trunk soon?
17:39:00 <popey> yes
17:39:04 <mhall119> \o/
17:39:09 <popey> but more frequently than nightly
17:39:33 <mhall119> wait, that 'yes' wasn't for me wa sit
17:39:36 <popey> nope
17:39:41 * dpm grins
17:39:48 <mhall119> /o\
17:40:04 <popey> however we can sort that out after mhall119
17:40:14 <popey> that was all I had...
17:40:22 <popey> #topic any other business
17:40:29 <dpm> frankencode, so to your question: yes, the PPA is updated daily from trunk
17:40:30 <popey> anything else? - questions/ concerns
17:40:38 <dpm> I've got something
17:40:55 <dpm> so to wrap up on the blueprint assignments,
17:41:29 <dpm> Does the list of new work items/assignments look sensible to everyone to replace the old one? -> http://pad.ubuntu.com/xxmjXq1Qvu
17:41:47 <dpm> Any other actions that you think we need to add or modify?
17:42:10 <mariob> dpm: I don't think we have a week view yet so you can "unsign" me from that item
17:43:00 <frankencode> the weekview is tightly integrated in the month view now
17:43:19 <dpm> mariob, is this better? -> http://pad.ubuntu.com/xxmjXq1Qvu
17:43:35 <mariob> frankencode: true, will step on each others toes :)
17:43:46 <mariob> yep
17:44:06 <mariob> frankencode: It's actually an agenda view, a week view shows all day for a week
17:44:48 <dpm> frankencode, happy with the work items in the pad? ^
17:45:06 <frankencode> yes
17:45:27 <popey> ok.. thanks so much for coming guys...
17:45:40 <mariob> bye
17:45:42 <popey> #endmeeting