[07:00] good morning [07:03] good morning [07:14] Morning o/ [08:39] * dholbach relocates, brb [08:48] aloha [09:31] dpm: would you mind if we pushed out meeting back 30 mins? [09:31] no worries if not. [09:41] popey, sure [09:41] thanks [09:41] done [09:42] ta [12:02] dpm: got any other example pages which have a 'call to action' button I can copy? [12:12] popey, the main d.u.c page [12:12] ta [12:13] or ubuntu.com has got one atm too [12:13] http://www.ubuntu.com/server [12:16] sorted, ta [12:16] dpm: https://developer.ubuntu.com/en/community/coreapps/music [12:56] * popey is afk for a couple of hours [13:55] balloons, davidcalle, dpm, mhall119, popey: LoCo Council (José) confirmed for tomorrow's Community Q&A. [13:56] \o/ [14:00] \o/ [14:33] * popey returns [14:42] popey: WB [14:44] popey: you know there is some musical event in farnborough this weekend ? [14:44] nope [14:47] popey: http://picnictomusicinthepark.co.uk/ [14:48] oh that, yeah. [15:26] mhall119, I have a quick question - we'd like to maintain a list of branches we'd like to import into the dev site and mark one of them default. what would your preference be? 1) in the code, 2) in the db (use admin interface or mgmt command), 3) separate branch which contains just the "config" [15:29] dholbach: 2 would probably be the most ideal, but will require more coding work on your part [15:29] 1 is likely easiest, and less complicated than 3 [15:29] mhall119, how would you do changes to the data in the db? [15:30] dholbach: create a new Model to hold this data, and make a ModelAdmin for it [15:31] mhall119, sure - we'll do that then [16:02] all right my friends - have a great rest of your day and see you tomorrow! [16:17] dholbach.. no! [16:17] I had a question for you :-)( [16:37] ok, calling it a day, see you all tomorrow! [18:36] mhall119, http://unity.ubuntu.com/autopilot/index.html has been resurrected. Can you kill it off again? [18:37] basically anything with autopilot on that subdomain should be killed [19:30] balloons: not sure what brought it back, do you know if it was setup on a cron or something? [19:39] mhall119, no.. I have an old rt where IS got rid of it [19:39] but since you did whatever, I see it's all back [19:46] balloons: all I did was update the WP theme [19:49] lol.. I know, it's coincidental I noticed I'm guessing [19:54] mhall119, I followed up with IS :p [20:06] balloons: what did they say? [20:07] mhall119, it's via RT. They will sort it I'm sure [21:33] hey mhall119 [21:33] or balloons [21:33] is it possible to snappy on a typical x86 box like say a NUC? [21:34] jcastro, you can always use kvm to install [21:34] yeah [21:34] but you would want just snappy right? [21:34] so let me tell you what I think is cool, and then you tell me how to do it. :D [21:35] so like, if I had a little home server with just snappy, the docker framework, and then some containers, say 5-6 [21:35] like basically an appliance [21:35] and all I want it to do is run the containers on boot or whatever [21:36] ahh right.. I'm totally down with that [21:37] oh I know it's a good idea, heh [21:37] I was just wondering if it's possible to install snappy like on a NUC [21:39] obviously I guess it's possible.. I'm wondering the best way to do it [21:39] I know ogra would have an opinion hah [21:39] I wonder if dustin has tried this [21:39] I am sure if I got an rpi2 this would be doable, but I don't have one [21:39] they key would be to get as close to baremetal as possible [21:40] that's the bit I'm not sure of. [21:40] jcastro, I would try flashing an amd64 image onto a nuc and see what happens [21:41] you should have ssh access to the box, and it should *just work* [21:41] yeah [21:41] especially if you go the nuc route.. keep it all intel, upstream stuff, but not too new [21:42] I can't imagine it would be missing support for anything