=== chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === alan_g is now known as alan_g|lunch === marcusto_ is now known as marcustomlinson_ === marcustomlinson_ is now known as marcustomlinson === alan_g|lunch is now known as alan_g [15:00] balloons: ping! <-- alf [15:01] alan_g :-). So I'm looking at your document for tasks. My only concern is having the dependencies on previous tasks [15:02] 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] as it stands, we'd be limiting who could work on tasks 2 and 3 [15:04] 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] 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] that might be the simplest thing to do [15:10] are there other needs within the team? Like simple features or bugs? Documentation needs? [15:13] "simple features" isn't so easy for a system library. There needs to be work elsewhere to expose the features. [15:13] There are bugs, but the simple ones just get fixed [15:16] alan_g, yes I know. Something this low level isn't a trivial thing [15:17] But I figured I would ask. Do you have good documentation in all places? [15:17] How about having them review the getting started guide; perhaps write a contributing guide? [15:17] And I do think your idea of using MIR to create some examples is probably the best for coding work [16:28] 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] there is a specifc settings package ... /me forgot the name ... to much snappy in my head recently :P [16:30] ubuntu-touch-settings ... [16:30] ogra_: great, thanks! === dandrader is now known as dandrader|afk === alan_g is now known as alan_g|EOD === dandrader|afk is now known as dandrader