11:10:22 <popey> #startmeeting
11:10:22 <meetingology> Meeting started Thu Mar  7 11:10:22 2013 UTC.  The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
11:10:22 <meetingology> 
11:10:22 <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
11:10:46 <popey> So welcome to this meeting of Ubuntu Touch Facebook app developers..
11:11:10 <popey> I sent an agenda out with the invite, and we'll go through those items, and will need to follow up on the mailing list after..
11:11:39 <kedz> yeap got it..
11:11:39 <popey> #topic introductions
11:12:10 <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..
11:12:43 * popey pokes dpm
11:12:49 <dpm> hi
11:13:20 <kedz> I'm David Kedves, i currently works for a smaller company in Hungary, previously i was a subcontractor for Nokia for ~4 years, so i have some experience with qt4/qml
11:13:33 <popey> oh excellent
11:13:52 <dpm> I'm David Planella, and I've been setting up the teams with you all, so we all know each other :) I work at the Community team as Ubuntu App Development Liaison
11:13:55 <kedz> but i mainly a c++ guy... so i don't have so much ideas about how to start the stuff in pure qml
11:14:26 <popey> ok, I'm sure we can find someone to help with that.
11:14:41 <popey> ok, lets move on..
11:14:55 <popey> #topic Update blueprints
11:15:15 <popey> So one of the key ways we measure how well we're doing is the work items in blueprints.
11:15:20 <popey> https://blueprints.launchpad.net/ubuntu-facebook-app/+spec/initial-facebook-development
11:15:24 <popey> boy do we have a lot of work items
11:15:49 <popey> obviously at the start they're all "TODO", which is fine of course.
11:16:11 <popey> however the key thing for us is to have someone assigned to all of them, because in our experience if nobody is assigned to a work item, it won't get done.
11:16:56 <popey> we can tweak the assignments later on, but initially we need to get tasks assigned to _someone_ :D
11:16:58 <kedz> should the team distribute all these TODOs just right now? ... or how?
11:17:39 <popey> yes
11:17:57 <dpm> kedz, is there any particular area you'd like to start working on?
11:18:27 <kedz> i already prefixed with my name the messaging tasks
11:18:41 <kedz> but i may depend on the 'login'...
11:19:10 <kedz> but of course i can start working on those tasks without 'login' (eg.: by obtaining the access key from the facebook graph explorer)
11:19:40 <kedz> eg.: i've made already some shell scripts to fetch the facebook messages
11:19:58 <dpm> I think the main thing is to get the ball rolling, as some of the other apps are already in prototyping stages, but I do see a lot of work items,
11:20:12 <kedz> dpm, popey : btw, what this 'UI Layout' thingy means? is it about the design or about the qml codes?
11:20:43 <dpm> and I'm wondering whether we want to shorten the list to focus on getting a functional prototype with the minimum functionality
11:21:07 <popey> yeah, that makes sense
11:21:15 <popey> I think the list is somewhat unweildy right now
11:21:28 <dpm> kedz, good question. To be honest, I don't know, that's why I always suggest using full sentences for actions, so that it is clear what's meant by them
11:21:47 <kedz> yeah...
11:21:54 <dpm> so what about reviewing the list of work items together and come up with something that everyone understands and is doable?
11:22:07 <dpm> we can then expand upon that
11:22:25 <dpm> so first, to answer your question on login,
11:22:43 <dpm> as part of a UDS session yesterday, we discussed about the Friends service
11:23:16 <dpm> which essentially handles login for several "protocols" (e.g. Twitter, Facebook, etc)
11:23:52 <kedz> that sounds good... i scared about implementing the oauth thingy in javascript :-S
11:23:53 <dpm> I think this is something the Facebook team could make use of, which would not only simplify development, but you'd also be reusing components the rest of the phone stack uses
11:24:00 <dpm> oh dear, no :)
11:24:02 <popey> +1
11:24:25 <dpm> kedz, what about starting with a prototype that:
11:24:34 <dpm> a) hooks into Friends to do the login
11:24:41 <dpm> b) show a news feed
11:25:22 <dpm> do you think you might be able to do that? This would be the foundation upon what other members of the team and yourself could build on
11:25:48 <kedz> hm... i need more info about thins 'friends'... where is it available? (doc / packages) ?
11:26:11 <popey> robru: may be able to help here..?
11:26:12 <kedz> dpm, so the plan is to implement the first two screens from this https://ubuntu.mybalsamiq.com/projects/ubuntuphonecoreapps/Facebook%20app am i right?
11:26:15 <dpm> sure, yes, that was just the overall idea
11:26:26 <dpm> yeah
11:26:30 <popey> yup
11:27:00 <popey> it's the primary use of fb really, scrolling through the news feed, so would be a great place to start
11:27:13 <kedz> if i can get the login working "somehow"  i thing this is doable
11:27:23 <dpm> popey, 3:27 a.m in Canada, perhaps later on ;)
11:27:34 <popey> heh
11:27:59 <popey> ok, we'll take an action to trim down the work items list
11:28:27 <popey> #action Trim work item list to managable size
11:28:27 * meetingology Trim work item list to managable size
11:28:45 <popey> drat, supposed to put my nick in that aren't i?
11:29:03 <dpm> haven't used it for a while, not sure
11:29:15 <popey> #action popey ping mailing list to review shortened work item list
11:29:15 * meetingology popey ping mailing list to review shortened work item list
11:29:35 <dpm> https://wiki.ubuntu.com/meetingology
11:30:09 <popey> nvm
11:30:16 <popey> ok, so next item..
11:30:19 <dpm> #action dpm Ask robru and kenvandine to send an e-mail to the mailing list with detailed instructions on how to use the Friends service from a QML app
11:30:19 * meetingology dpm Ask robru and kenvandine to send an e-mail to the mailing list with detailed instructions on how to use the Friends service from a QML app
11:30:55 <popey> #action kedz create first cut of UI to display the news feed only
11:30:55 * meetingology kedz create first cut of UI to display the news feed only
11:31:08 <dpm> #action kedz Follow up the Friends instructions in the mailing list and implement the login UI
11:31:08 * meetingology kedz Follow up the Friends instructions in the mailing list and implement the login UI
11:31:17 <dpm> kedz, does that all make sense? ^
11:31:31 <kedz> yes, should i #accept these ?
11:31:48 <dpm> kedz, no need to, as long as you're happy with them
11:31:48 * kedz just reading that meetingology...
11:31:59 <kedz> ok
11:32:30 <popey> ok.. lets move on
11:32:38 <popey> #topic Set milestones
11:33:16 <popey> so with this I'd like to set a milestone date by which we should have a first working cut of the application
11:33:25 <popey> it doesnt need to have implemented all features, just the basics
11:34:02 <popey> so for facebook I'd imagine something like logging in, viewing feeds, posting, liking, commenting and possibly photos
11:34:07 <kedz> good question... this depends on the 'friends' thingy
11:34:42 <popey> yes, there may be external dependancies and we may need to pull in people from the Friends team to help get us up to speed
11:35:20 <popey> We have mid-May in mind for the first cut.
11:35:36 <popey> with ~July to aim for a more finished/polished app
11:35:39 <popey> how does that sound?
11:36:02 <popey> maybe call May "alpha"
11:36:28 <kedz> this depends also on the others... i hope i can meet with them at once..
11:36:58 * kedz alone can't do it in time :-S
11:37:08 <popey> well, yes :D
11:37:22 <popey> not expecting you to do it all
11:37:35 <kedz> but i saw already one guy in IRC logs... (at the first meeting where i wasn't there)
11:37:48 <kedz> he took the login tasks on the blueprint page...
11:37:59 <dpm> kedz, you're right, and as popey says, it's not expected that one person impleents everything!. I think for those who cannot attend the meetings we should perhaps make more use of the mailing list
11:38:29 <dpm> popey, it might make sense to send the meeting minutes to the list too (you might already have thought of this)
11:38:59 <popey> yeah, good idea
11:39:36 <popey> #action popey mail the list to get consensus on milestone dates for all apps
11:39:36 * meetingology popey mail the list to get consensus on milestone dates for all apps
11:40:29 <popey> #topic Populate PPA
11:40:39 <popey> so the final topic I had was really just an informational thing
11:41:01 <popey> once code is checked in, packages _should_ build and be available for install from https://launchpad.net/~ubuntu-touch-coreapps-drivers/+archive/daily  <- that ppa
11:41:22 <popey> the goal of this is to make it easy for people to test the apps, as they won't be in the daily build image for phone/tablet
11:41:32 <kedz> how it is possible to push sources there?
11:41:35 <popey> and they certainly won't be in any image builds made by 3rd parties like xda
11:41:39 <popey> kedz: it's automagic
11:41:49 <popey> we pull from the branch via jenkins, build and push to the ppa
11:41:56 <popey> you don't have to do anything
11:42:08 <kedz> ah ok, is it started already?
11:42:28 <popey> yes, but nobody has checked in any code since it was implemented
11:42:34 <dpm> kedz, are you familiar with the development tools and the process? I mean not the PPA building process, but e.g. getting the source code, creating branches, pushing, doing merge proposals, etc?
11:42:34 <popey> so no packages have appeared there yet
11:42:47 <popey> as soon as someone does, the packages will start appearing
11:42:47 <kedz> ah, ok ;-) that is why i can't see any distros .. etc
11:42:53 <popey> yeah ☺
11:43:01 <kedz> btw, will the packages be built for desktop ubuntus too?
11:43:04 <popey> we will also create a metapackage which will contain all the apps
11:43:19 <popey> so testers can just 1) add ppa, 2) install metapackage, and they'll get all the apps
11:43:37 <dpm> kedz, yeah, afaik, the PPA builds for arm and x86
11:43:55 <dpm> but if we use QML only, that should not even be a concern :)
11:44:11 <popey> my team will keep an eye on it, and we'll seek out the right people to fix it if the process breaks
11:44:26 <kedz> yeah... but i'm interested about the other packages.. maybe i can stole 'ideas' about theming or anything from the other stufsf
11:44:31 <kedz> *stuffs
11:44:37 <popey> well, you can bzr branch any of them
11:44:50 <popey> i have branched them all in a folder and keep it updated now and then
11:45:13 <kedz> yeah.. indeed
11:45:22 <popey> ok, that was it I think..
11:45:29 <popey> anything else we need to discuss dpm kedz ?
11:45:31 <dpm> so kedz, just to make sure you're good to get started, are you familiar with the development process and tools? ^^
11:45:39 <popey> #topic any other business
11:46:14 <kedz> dpm, i don't have too much experience with bzr but i think i can learn it
11:46:40 <dpm> kedz, the guide and the diagram at the bottom should help -> https://wiki.ubuntu.com/Touch/CoreApps/DevelopmentGuide
11:46:45 <kedz> debianization, qt, qml and all these dev stuffs are known for me
11:47:02 <dpm> bzr should be quite transparent in the process
11:47:19 <dpm> so you just use it to commit your code, push it online to a feature branch
11:47:30 <kedz> ok
11:47:36 <dpm> and when you're done, you send a merge proposal so that other members of the team review it
11:48:05 <dpm> if the review is ok, then the status will be changed to approved, and your branch will land automatically to trunk
11:48:27 <dpm> if it's not, you'll be asked to fix the code, and then you can resubmit the merge proposal
11:48:37 <kedz> ok
11:48:54 <dpm> basically, all you need to get started now is to run:
11:49:22 <dpm> bzr branch lp:ubuntu-facebook-app
11:49:30 <dpm> *hack* *hack* *hack*
11:49:33 <kedz> yeap i get it already
11:49:53 <kedz> s/get/cloned/
11:50:02 <dpm> cool
11:50:04 <dpm> and then
11:50:09 <kedz> i don't know which word fits here for BZR...
11:50:21 <popey> branch
11:50:22 <dpm> in bzr lingo the word is branch
11:50:24 <dpm> :)
11:50:33 <kedz> ok :-)
11:50:43 <popey> but do get in touch if you get stuck
11:50:47 <dpm> so then it's good practice to push your code online every now and then:
11:50:55 <popey> dpm and I are around on irc during European daytime (and often beyond)
11:51:00 <dpm> bzr push lp:~<yourlpid>/ubuntu-facebook-app/<yourfeaturename>
11:51:24 <dpm> yeah, just ping us any time, one of us will reply. You can also ping mhall119
11:51:31 * kedz also tries to be online @ european daytime
11:51:36 <dpm> nice
11:52:19 <popey> ok, I think we're done?
11:52:38 <dpm> that was all from my side, kedz, anything else you wanted to discuss/ask?
11:53:13 <kedz> nothing for now...
11:53:20 <popey> great
11:53:22 <popey> #endmeeting