[15:00] <alan_g> balloons: ping! <-- alf
[15:01] <balloons> alan_g :-). So I'm looking at your document for tasks. My only concern is having the dependencies on previous tasks
[15:02] <balloons> ideally these will be standalone. So I'm trying to think about how we could incoporate the same thing without having a hard dependency
[15:02] <balloons> as it stands, we'd be limiting who could work on tasks 2 and 3
[15:04] <alan_g> Well, there needs to be some base code to work with. And even if we took the mir examples as the base there's only one version of that.
[15:07] <balloons> right. So we could also hold the tasks until each one is completed. So we could not publish task 2 until at least one person has done task 1
[15:08] <balloons> that might be the simplest thing to do
[15:10] <balloons> are there other needs within the team? Like simple features or bugs? Documentation needs?
[15:13] <alan_g> "simple features" isn't so easy for a system library. There needs to be work elsewhere to expose the features.
[15:13] <alan_g> There are bugs, but the simple ones just get fixed
[15:16] <balloons> alan_g, yes I know. Something this low level isn't a trivial thing
[15:17] <balloons> But I figured I would ask. Do you have good documentation in all places?
[15:17] <balloons> How about having them review the getting started guide; perhaps write a contributing guide?
[15:17] <balloons> And I do think your idea of using MIR to create some examples is probably the best for coding work
[16:28] <alf> ogra_: Hi! If we want to ship a config file just on the phone (e.g. a special config file for lightdm) what would be the right package to put it in?
[16:29] <ogra_> there is a specifc settings package ... /me forgot the name ... to much snappy in my head recently :P
[16:30] <ogra_> ubuntu-touch-settings ...
[16:30] <alf> ogra_: great, thanks!