[03:41] jono: can you send the vUDS message to community-announce@lists.ubuntu.com too? [03:41] (UDS scheduling was a specific mention when creating the list :)) [03:46] looks like the announcement for UDS never made it there either, so at least getting this one there would be good [03:49] pleia2, sure [03:56] jono: thanks :) and added your address to accepts for that list [03:57] thanks pleia2 [05:05] good morning [05:12] hey, Tm_T [06:03] Silly makerbot wouldnt let me print a Ubuntu Coin [06:03] :( [07:01] good morning [13:11] cjohnston: ping [13:12] mhall119: around? [13:13] jcastro: yup [13:13] is there a cache in front of summit.u.c? [13:14] I am getting 1308 but some people are getting the May one [13:15] mhall119: also I have a new person who needs to shcedule, do you remember what team they should apply to? [13:16] jcastro: anybody managing the schedule should be a track lead [13:16] no idea about the cache, are you sure they don't have the url to the old summit? [13:16] yeah [13:18] mhall119: yeah he's a track lead, I just don't know what team he should apply to [13:18] he doesn't need to be on a team, track leads can schedule [13:19] is he listed as a track lead on http://summit.ubuntu.com/uds-1308/tracks ? [13:19] ah, nobody is, there's your problem [13:19] let me fix that [13:24] mhall119: we have some changes in track leads [13:24] ok, who's server/cloud track leads this time? [13:25] scott moder, dan westervelt, and antonio rosales [13:25] that's Scott Moser btw, typo [13:25] I assumed [13:26] what's dan's launchpad nick? [13:28] mhall119: danwest [13:29] thanks [13:29] so no Daviey ? [13:55] jcastro: mhall119 got you sorted out? [13:55] I think so? [13:56] mhall119: you can keep Daviey on if you want but we might as well get the transition done [13:57] cjohnston: were you looking for me earlier? [13:57] what's up nigelb! [13:59] busy times. otherwise nothing much. what about you? How's working for Canonical? (or is it Linaro?) [14:00] I understand busy times. Workin for Canonical.. Things are awesome [14:01] cjohnston: I'm doing the equivalent of purging render.py on our codebase.... [14:01] I've spent more time this week reading code than writing. [14:01] it sounds like you should be ready to take the task of render.py next week then [14:03] cjohnston: slots are all fixed now too, we can start importing anytime [14:05] mhall119: importing should already be happening [15:01] dpm, all set? [15:01] jono, yep, coming! [15:06] jcastro, is discourse working for you right now? [15:07] no it's down [15:07] ok [15:07] marco gets pings when it goes down [15:08] but he's in japan [15:09] ok [15:17] man this is embarrassing [15:18] dholbach: ask me what I am listening to right now [15:18] jcastro, what are you listening to right now? [15:19] ACE OF BASE [15:19] I tell you no lies [15:21] I thought that was impossible without serious substance abuse [15:21] dholbach: anything's possible [15:23] ok, I stand corrected then ;-) [15:23] :p [15:23] you just need to see my media library to see it is 'possible' === dholbach_ is now known as dholbach [15:28] dholbach: with Spotify anything is possible [15:28] I find lots of great stuff on mixcloud [15:29] good morning! [15:30] hi SergioMeneses [15:31] hi elfy how's everything? [15:32] pretty good thanks - you? [15:35] elfy, reading emails, writing wikis... today I have the day off :) [15:36] nice [15:37] so why aren't you outside doing outside stuff like reading at a bar watching the world go by :p [15:43] elfy, jajaja [15:43] elfy, because I have a lot of things to do here... maybe later [15:44] :p [16:37] have a great rest of your day - see you! [18:36] hey, dudes. [18:37] jono, mhall119, dpm, I'm happy to fill in more detail on my thoughts if you want me to, of course [18:37] not that dpm is here. Ah well :) [18:37] thanks aquarius :-) [18:37] dpm is crying [18:37] :-) [18:37] gah, he used to quite like me, I think, and now I've ruined it ;) [18:38] aquarius: I can give you login credentials and you can fix it yourself ;) [18:38] then I'll re-assign all the bugs to you [18:38] mhall119, the problem isn't really the IA -- I mean, that sorta kinda needs some fixing, but you knew that already. It's the uncertainty, which I tried to stress as being the main issue as I see it [18:38] and all the work items from this next vUDS [18:39] well, the IA changes and a general cleanup and link fixing will help a lot of the uncertainty [18:39] I think dev.u.c is actually not too bad at the stuff that it does; there's just a bunch of stuff that it doesn't do yet and I think it needs to :) [18:40] but part of the problem is, at our first Beta, we're all still a litle uncertain as well [18:40] oh, of course -- I'm definitely, absolutely, not pointing fingers and saying "why aren't you doing better"! [18:40] I've been there; I know what it's like :) [18:40] :) [18:42] (was just trying to find the SDK widget documentation pages in order to show an example, but I can't find them by looking in the menus, which is the IA thing :)) [18:43] (can't find a link to http://developer.ubuntu.com/api/ubuntu-12.10/qml/mobile/overview-ubuntu-sdk.html without googling) [18:44] IA? [18:45] Information architecture -- essentially, the sitemap and crosslinks [18:45] how to find your way around a site [18:45] ah [18:48] mhall119, the uncertainty complaint, at least as it relates to the SDK, basically boils down to all the occurrences of "This documentation is under development and is subject to change" which do not suggest *how* it might change. If it's going to change a little bit, that's not a problem; I do not mind if, say, OrientationHelper.automaticOrientation is currently a boolean and might change to be an enum. [18:48] (That will break my apps, but it's not a hard problem.) I do mind if OrientationHelper might completely go away and get replaced by something totally different; if that's the case, I'm not going to use it until it's stabilised. [18:49] I do not mind avoiding using a component! That's not a problem at all. But because all I get told is "this is subject to change" with no indication of whether the change will be minor or complete obsolescence, I basically have to assume that it might be a major change and therefore I am afraid to use any component which says that. [18:49] I'm OK with that too -- if that's what I should be doing, no worries. Saying "any component which is mentioned as under development *should not be used* unless you are prepared to work closely with the SDK team" would be fine! [18:52] anyway, I'm not trying to have a go :-) [19:01] aquarius: understood, I'll talk to the SDK guys to see if we can get that clarified [20:03] jono: don't you ... dun dun dun dun dun ... forget about me [20:03] http://www.youtube.com/watch?v=CdqoNKCCt7A [20:04] jcastro, eating lunch, can we chat soon? [20:05] fo sho [20:05] I hope you are enjoying that video while you eat === marcoceppi__ is now known as marcoceppi