16:00:34 #startmeeting 16:00:34 Meeting started Tue May 15 16:00:34 2012 UTC. The chair is zul. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 16:00:34 16:00:34 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 16:00:58 so hi, i hope everyone has recovered from uds with their livers mostly intact 16:01:07 meh 16:01:09 o/ 16:01:17 utlemming: i know you havent 16:01:40 hello 16:01:46 #stubtopic Review ACTION points from previous meeting 16:01:52 #subtopic Review ACTION points from previous meeting 16:02:14 o/ 16:02:17 so there isnt an topics from the previous meeting lets get right to it 16:02:19 o/ 16:02:39 #topic Quantal Development 16:02:57 so last week was uds, and people should be getting their blueprints ready 16:03:15 this includes their work items for the blueprints as well 16:03:29 +1 16:03:34 also note that we'll be trying the new template version 16:03:39 \o/ 16:03:43 if you have never written a blueprint before you can ask for help as well 16:04:03 do we have the bzr/whiteboard integration working yet - maybe smoser or Ursinha` might know? 16:04:09 sigh 16:04:10 o/ 16:04:22 o/ 16:04:29 jamespage, Ursinha` and i talked a lot, but did not come to any real conclusion. 16:05:01 OK - suggest folk try out the template without a versioned whiteboard for the time being - we can swap over later. 16:05:12 sounds good 16:05:20 where do we find the new template again? 16:05:27 jamespage: can you send an email to ubuntu-server with the new template stuff? 16:05:33 +1 16:05:39 zul: ack - please action me for that 16:06:09 #action jamespage to send out an email to ubuntu-server about the new template 16:06:09 * meetingology jamespage to send out an email to ubuntu-server about the new template 16:06:33 also it looks like we may need to update http://reports.qa.ubuntu.com/reports/ubuntu-server/release-bugs.html for Quantal 16:06:40 ^^ action me 16:06:43 or is that just the header text that needs updated from Precise? 16:06:51 nah, needs a change. 16:07:20 #action daviey update release bugs for quantal 16:07:20 * meetingology daviey update release bugs for quantal 16:07:35 so looking at http://reports.qa.ubuntu.com/reports/ubuntu-server/release-bugs.html 16:08:16 there is possibly a good one or two SRU bugs that are good candidates for SRU of course they need to be fixed in quantal first 16:08:36 zul: How functional is the SRU tracker? 16:08:41 the one that jumps out at me is #880339 16:08:49 bug 880339 16:08:50 Daviey: havent touched it in a long time 16:09:32 it should be ressurected though 16:09:40 +1 16:10:17 does someone want to take that action? 16:10:41 if i show them again where everything is and clear out the database and possibly update it for precise 16:11:16 zul: I can give that a try 16:11:17 zul: give it to me - kinda forms part of my holistic review of triage etc.. anyway 16:11:33 oooh...deathmatch 16:11:41 i though Ursinha` did something with it 16:11:44 jamespage: and now that you mention it, where should we be trackingnew bugs from now on? 16:11:49 zul ping jamespage and I offline 16:12:08 I would be interested in knowing how it works even if jamespage takes the full action 16:12:09 http://reports.qa.ubuntu.com/reports/ubuntu-server/triage-report.html 16:12:12 #action zul talk to arosales and jamespage offline about SRU tracker 16:12:12 * meetingology zul talk to arosales and jamespage offline about SRU tracker 16:12:26 for the time being at least 16:12:37 anything else to bring up? 16:12:40 jamespage: thanks 16:13:23 jamespage/arosales/Daviey: is there anything im missing 16:13:39 for Quantal I think that is it for now 16:13:44 cool beans 16:13:47 I don't think so - blueprints and then merges! 16:13:51 zul: how long do we have? :) 16:14:00 Daviey: none 16:14:05 #topic Ubuntu Server Team Events 16:14:11 hah hah! 16:14:33 no more travel please! :) 16:14:35 so summer is coming up, so that means stuff like oscon, velocity, linuxcon, etc, etc etc 16:14:36 gluecon coming up for m_3 16:14:44 23-24 may 16:14:56 i might go to linuxcon, but waiting to hear on that 16:15:11 (plumber's, really) 16:15:11 s3h: oh, neat! 16:15:13 * zul hopes to stay home this summer 16:15:32 oh yeah OLS as well 16:15:33 Daviey: actually we're going to have a sprint, just you and me, here in LA, for the next 3 weeks. 16:15:37 (waitingn to hear from Daviey that is :) 16:15:45 SpamapS: sounds awesome. 16:16:11 moving on 16:16:14 Velocity is coming up 16:16:15 wait 16:16:20 I think somebody is going to that 16:16:25 (sorry I got majorly lagged out there) 16:16:27 im guessing m_3 16:16:39 velocity is at the end of june 16:16:45 Jorge and Hazmat I think 16:16:47 27-28 June 16:16:47 no Velocity for me... I'll be out of pocket 16:17:02 Oh and LISA talk submission deadline is this week 16:17:18 so for all ubuntu server users, make sure you get your "Ubuntu server is awesome" talks submitted! :) 16:17:21 that is all 16:17:28 * smb hopes to go to Plumbers and maybe XenSummit as it is just before that 16:17:49 Isn't plumbers in San Diego? 16:17:50 mmm....more citrix marketing 16:17:52 it is 16:17:58 * m_3 just hopes Plumbers scheduling is working seamlessly atm :) 16:18:15 yes, san diego... late august I think 16:18:25 m_3: talk to the IS guys.. they wrote charms for the schedule boxes too 16:18:26 29-31 16:18:49 ok thats enough about events. :) 16:18:50 SpamapS: that's the one on the summit charm.. don't think we're doing anything beyond that 16:19:03 #topic Weekly Updates & Questions for the QA Team (hggdh) 16:19:25 hi hggdh 16:19:28 if you are around 16:19:40 lots of good qa sessions at uds as well 16:20:08 Yeah QA were the rockstars of uds-q :) 16:20:32 i guess he is not here 16:20:41 #topic Weekly Updates & Questions for the Kernel Team (smb) 16:20:43 hi smb 16:20:48 \o 16:21:01 Are there Questions ? 16:21:01 i didnt attend any kernel sessions at uds 16:21:15 As I don't think I have much to report 16:21:16 er...what kernel are we using for quantal? ;) 16:21:30 2.6.24 16:21:33 :-P 16:21:51 how retro 16:22:00 any questions for smb? 16:22:21 big news from kernel team was that -virtual may be going away. 16:22:30 yay! 16:22:42 Right, more of a packaging change 16:22:57 replacing it with a regular server kernel? 16:23:09 no, that does not exist anymore 16:23:19 generic or generic-pae 16:23:19 regular generic kernel 16:23:28 ah i see 16:23:40 And having a split between minimal and additional modules 16:23:50 cool 16:23:59 anything else for smb? 16:24:25 As an aside, currently we can get an indication of whether a reporter is using a "desktop" machine via the kernel in bug reports. With this going away, perhaps we should add information to see if X or ubuntu-desktop or something is installed? 16:25:08 rbasak: well they can still have a server with ubuntu-desktop installed 16:25:35 That's the thing - there's no real distinction in technical terms, but pragmatically the information is useful when triaging 16:26:06 right totally agree and thats been a problem for a long while 16:26:31 rbasak: we get the install media 16:26:35 Hm, I may be wrong but potentially the linux-server meta package is still there 16:26:40 rbasak: thats a good indication of what they intended at install time 16:27:13 Yeah, seems to be true 16:27:23 SpamapS: install media can be maas now as well though 16:27:35 anyways i dont think its going to be solved as well 16:27:37 rbasak, ^ 16:27:41 er...solved now 16:27:49 We don't always get the install media, eg bug 999614. 16:27:50 Launchpad bug 999614 in php5 (Ubuntu) "new SoapClient() with connection_timeout = NULL breaks multi-dimensional arrays" [Undecided,Incomplete] https://launchpad.net/bugs/999614 16:28:07 That may be a cloud image or something 16:28:36 so moving on 16:28:42 rbasak: good timing 16:28:52 #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak) 16:28:53 Calxeda demoed MAAS working on their hardware at UDS! 16:28:54 Work on ARM server and MAAS is ongoing. 16:28:54 Any questions for me? 16:29:01 i want one 16:29:15 That's not a question :-) 16:29:30 please can i have one? 16:29:38 No. 16:29:40 :-P 16:30:01 I don't think any ETA for general marketing availability has been announced yet. 16:30:08 *market 16:30:18 * zul sighs 16:30:50 #topic Open Discussion 16:30:57 anyone want to get something off their chest 16:31:04 how was uds for everyone? 16:31:19 weird going back and forth for just 2 days 16:32:07 SpamapS: did you collect some good feedback for remote participants? 16:32:14 or was that handled pretty well? 16:32:37 I think we should consider google hangouts 16:32:56 we tried one for one talk. didn't work well 16:32:58 I see no reason to put people in a one-way audio bubble 16:33:05 I was in a couple of meetings where that worked OK 16:33:09 s3h: what went wrong? 16:33:13 google hangout swould be a useful addition. especially if integrated with the room. 16:33:14 need more bandwith i think 16:33:15 choppy, delay 16:33:22 Ah 16:33:27 I've found G+ to be choppy and delayed as well. 16:33:29 Thats surprising 16:33:36 How about a SIP hardware phone on speakerphone? 16:33:47 that would be aweseome 16:33:51 how about just mumble :) 16:34:07 SIP hardware phone was avaliable on request 16:34:15 did anyone try it? 16:34:16 The catch about two-way audio is that it relies on everyone being able to control their mute button 16:34:18 well anyway, I find it very hard to "participate" from IRC+delayed audio 16:34:29 The DMB meeting used one - it worked OK 16:34:30 SpamapS: +1, same here 16:34:35 But it did "work" and I felt that I was able to chime in a bit. 16:34:41 the delay makes it unusable if you're goign to be really involved 16:34:53 rbasak: thats the catch IRL too ;) 16:34:54 fine for just following along half-heartedly 16:35:02 The good thing about G+ is that someone managing things can identify who is causing an audio issue and remote mute him. 16:35:12 good conf lines can do that too :) 16:35:22 The catch is that this needs someone to manage things. 16:35:31 asterisk 16:35:32 i seriously didn't know about the sip lines. we should try those for next time 16:35:48 or yeah, asterisk to Daviey's server 16:35:50 anyway, remote participation is probably worth improving, but all in all, it worked fine and etherpad especially made it easy to keep track of session notes in multiple rooms 16:35:58 +1 for etherpad 16:36:24 just remember to save your notes.... 16:36:32 oh yeah - by when? 16:36:42 * jamespage shrugs 16:36:44 "before that storm rolling in" 16:36:47 not sure but the sooner the better 16:36:56 i would, but this meeting wont' end :) 16:37:00 lol 16:37:03 i think there was an email about uds feedback that you can do :) 16:37:18 so anything else so i can end the meeting for s3h? 16:37:33 if not 16:37:40 same time next week 16:37:44 #endmeeting