20:17:09 <popey> #startmeeting Ubuntu Touch File Manager app meeting
20:17:09 <meetingology> Meeting started Thu Apr 25 20:17:09 2013 UTC.  The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
20:17:09 <meetingology> 
20:17:09 <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
20:17:20 <mhall119> hi CarlosMazieri and ajalkane
20:17:27 <popey> links..
20:17:28 <CarlosMazieri> hi
20:17:35 <popey> blueprint: https://blueprints.launchpad.net/ubuntu-phone-commons/+spec/initial-filemanager-development
20:17:48 <popey> reviews: https://code.launchpad.net/~ubuntu-filemanager-dev/ubuntu-filemanager-app/trunk/+activereviews
20:17:59 <popey> bugs: https://bugs.launchpad.net/ubuntu-filemanager-app
20:18:30 <popey> Ok, how are we doing?
20:19:21 <ajalkane> Waiting for resolving bug in latest SDK https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1172858
20:19:22 <mhall119> work items: http://pad.ubuntu.com/n7k8U0ABcL
20:20:21 <mhall119> I see a lot of "DONE" items
20:21:06 <CarlosMazieri> I think we are close to have a good FM.
20:21:40 <mhall119> CarlosMazieri: how does it currently try to open files?
20:22:09 <CarlosMazieri> the plugin does not open files, ajalkane is doing it in the UI.
20:22:12 <ajalkane> mhall119: Using QML's Qt.openExternalUrl (don't remember exact function name)
20:22:49 <mhall119> ok, that probably calls something on the platform level
20:22:51 <ajalkane> So the files are opened by whatever is registered in the mimetypes for the file
20:22:53 <mhall119> I'm assuming
20:22:57 <ajalkane> Yes
20:23:14 <mhall119> ok, cool, so if I get the ubuntu-docviewer-app registered, it should call that
20:23:22 <mhall119> thanks, I have a work item to do that, just wanted to make sure
20:23:26 <ajalkane> That's my assumption
20:23:34 <mhall119> ajalkane: I'll file a bug if it's wrong :)
20:23:55 <ajalkane> To Qt-project I assume :P
20:24:16 <mhall119> wherever is approprirate
20:24:26 <ajalkane> Of course we can do Ubuntu specific workarounds if necessary, but probably it won't be needed
20:24:39 <mhall119> alright, so starting with month-0
20:24:48 <mhall119> is the nemo plugin being auto-built from upstream now?
20:25:08 <mhall119> popey: ??
20:25:35 <popey> not yet, should get it sorted next week when I'm in the US and have people to beat nearby
20:25:58 <popey> now the release is out the way
20:26:04 <mhall119> Oakland is a baseball town, I'm sure you can find a bat for sale
20:26:27 <ajalkane> I'm again stressing that what used to be nemo-plugins has been cut into pieces
20:26:38 <ajalkane> What was this: https://github.com/nemomobile/nemo-qml-plugins
20:26:43 <mhall119> ajalkane: is that a good thing or a bad thing for us?
20:26:59 <ajalkane> is now this for FileManager's needs: https://github.com/nemomobile/nemo-qml-plugin-folderlistmodel
20:27:04 <ajalkane> It's goood for us I think
20:27:17 <ajalkane> Because the plugins are easier to manage for separate projects
20:27:51 <mhall119> ok, good
20:28:12 <mhall119> alright, on to month-1
20:28:21 <mhall119> we have multi-selection on the TODO list
20:28:28 <mhall119> with nobody assigned
20:28:41 <mhall119> is that blocked, or available to be worked on?
20:29:18 <ajalkane> It's available to be worked on, but I'm not sure if it's doable on our 2-man working team
20:30:07 <ajalkane> I'm not sure which one is more important, the bookmarks (which is not put in blueprints) or multiselection
20:30:33 <mhall119> popey: thoughts on that?
20:31:03 <popey> I'm inclined to think multiselection is a more common use case than bookmarks.
20:31:20 <popey> but then trying to think how many times I've used either or wanted either on a mobile device
20:31:52 <ajalkane> Indeed. They're both not too critical items.
20:32:27 <ajalkane> So perhaps I'll drop the bookmarks from the UI and work on multiselection if fixing and improving basic operations does not get in the way
20:32:46 <mhall119> file management on a phone itself isn't a common use case, so it's hard to tell what features would be expected
20:32:49 <ajalkane> As far as I can say right now, the QML plugin backend that Carlos has done should have the support for multiselection
20:33:31 <mhall119> so once the nemo plugin is building automatically, do you think we are ready to recommend this for the developer preview images?
20:33:54 <CarlosMazieri> ajalkane:  do you mean the plugin should carry selections ?
20:34:12 <ajalkane> mhall119: If Carlos' changes are applied as patches, sure. Right now only my changes have been submitted upstream.
20:34:57 <popey> I'd like to see this on the preview image too..
20:35:15 <mhall119> what work hasn't been submitted upstream yet?
20:35:39 <ajalkane> CarlosMazieri: I haven't looked at it much. But the plugin API supports copying multiple items to clipboard, so rest can be done on UI even though it might get slow if there's lots of files - but I don't think it's problem
20:36:09 <ajalkane> mhall119: recursive delete/copy, clipboard copy-cut-pasting, long file operation progress signals
20:36:27 <mhall119> is there anything preventing those from being submitted upstream?
20:37:31 <CarlosMazieri> I have no idea !
20:38:22 <ajalkane> In my estimation it requires some clean-up but it'll probably can be worked by doing merge request and working with upstream to get what they want fixed.
20:38:50 <mhall119> let's prioritize that then, so we get everything upstream and can build packages from upstream
20:38:56 <ajalkane> Ie. small stuff, but might take a bit time
20:39:17 <mhall119> I think that's more important right now than multi-select and bookmarks
20:39:31 <popey> +1
20:39:41 <mhall119> the features you guys already have in the file manager are more than enough for it to go into the developer preview image
20:40:08 <ajalkane> Yeah it'd be superb to have everything upstream
20:41:32 <ajalkane> When is the dev preview image been released, ie. the timeline you're shooting for with this?
20:41:48 <popey> every day
20:42:05 <popey> we build daily, and can request packages get included in that at any time
20:42:06 <ajalkane> Ah okay
20:42:39 <popey> but we have to meet some quality criteria, so we'll likely need a code review first
20:42:45 <popey> but i don't expect that to be a problem.
20:43:08 <mhall119> having a clean upstream package will help that too
20:43:10 <ajalkane> The quickest way would be to have something like Timo's earlier deb-build repo which had our patches on top of that. Because my experience with the nemo guys is that they're really busy and the merge requests can take several weeks.
20:44:01 <mhall119> that would be ok, as long as it's been submitted
20:44:18 <mhall119> so we know we won't be carrying to patches indefinitely
20:44:25 <ajalkane> Yeah I agree
20:44:27 <popey> yeah, so long as we can show we're doing the Right Thing ™ I'm sure it's fine
20:45:33 <popey> I'll bring it up at the sprint next week
20:45:33 <mhall119> alright, anything else?
20:45:35 <ajalkane> But I'll leave that to Carlos as it's his changes and he can better explain the design decisions and do changes.
20:46:21 <ajalkane> I can of course offer some help as I've done several merge requests
20:46:22 <CarlosMazieri> ajalkane: That is OK
20:46:45 <popey> Great.
20:48:40 <ajalkane> I can't think of nothing else. My time runs out during the end of next month, but hopefully the icons etc. remaining issues are solevd then so I can contribute a bit on those then
20:49:11 <ajalkane> And I can of course do a bit even after that, but not nearly as much as I've been able for past few months
20:49:18 <mhall119> ajalkane: you've done amazing work already, it's really appreciated
20:49:24 <popey> +1
20:49:27 <mhall119> same for you CarlosMazieri
20:49:34 <mhall119> you've both been rocking it
20:50:11 <ajalkane> Appreciated... and it's nice to see you Ubuntu guys supporting these projects so well
20:50:32 <CarlosMazieri> I would say the same, thank you.
20:50:40 <popey> I couldn't be more happy that we've found reliable people to collaborate with!
20:51:09 <popey> lets wrap up
20:51:21 <mhall119> popey: +1 on the awesome developers
20:51:46 <CarlosMazieri> Thanks, see you guys next week.
20:51:58 <ajalkane> Until next week
20:52:20 <popey> oh, I started the meeting didn't I?
20:52:22 <popey> #endmeeting