[16:00] <zul> so lets get this started
[16:00] <zul> #startmeeting
[16:00] <meetingology> 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] <meetingology> 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] <zul> so hi, i hope everyone has recovered from uds with their livers mostly intact
[16:01] <utlemming> meh
[16:01] <Daviey> o/
[16:01] <zul> utlemming: i know you havent
[16:01] <arosales> hello
[16:01] <zul> #stubtopic Review ACTION points from previous meeting
[16:01] <zul> #subtopic Review ACTION points from previous meeting
[16:02] <jamespage> o/
[16:02] <zul> so there isnt an topics from the previous meeting lets get right to it
[16:02] <m_3> o/
[16:02] <zul> #topic  Quantal Development
[16:02] <zul> so last week was uds, and people should be getting their blueprints ready
[16:03] <zul> this includes their work items for the blueprints as well
[16:03] <jamespage> +1
[16:03] <arosales> also note that we'll be trying the new template version
[16:03] <jamespage> \o/
[16:03] <zul> if you have never written a blueprint before you can ask for help as well
[16:04] <jamespage> do we have the bzr/whiteboard integration working yet - maybe smoser or Ursinha` might know?
[16:04] <s3h> sigh
[16:04] <roaksoax> o/
[16:04] <SpamapS> o/
[16:04] <smoser> jamespage, Ursinha` and i talked a lot, but did not come to any real conclusion.
[16:05] <jamespage> OK - suggest folk try out the template without a versioned whiteboard for the time being - we can swap over later.
[16:05] <Daviey> sounds good
[16:05] <s3h> where do we find the new template again?
[16:05] <zul> jamespage: can you send an email to ubuntu-server with the new template stuff?
[16:05] <roaksoax> +1
[16:05] <jamespage> zul: ack - please action me for that
[16:06] <zul> #action jamespage to send out an email to ubuntu-server about the new template
[16:06] <meetingology> ACTION: jamespage to send out an email to ubuntu-server about the new template
[16:06] <arosales> also it looks like we may need to update http://reports.qa.ubuntu.com/reports/ubuntu-server/release-bugs.html for Quantal
[16:06] <Daviey> ^^ action me
[16:06] <arosales> or is that just the header text that needs updated from Precise?
[16:06] <Daviey> nah, needs a change.
[16:07] <zul> #action  daviey update release bugs for quantal
[16:07] <meetingology> ACTION: daviey update release bugs for quantal
[16:07] <zul> so looking at http://reports.qa.ubuntu.com/reports/ubuntu-server/release-bugs.html
[16:08] <zul> 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] <Daviey> zul: How functional is the SRU tracker?
[16:08] <zul> the one that jumps out at me is #880339
[16:08] <Daviey> bug 880339
[16:08] <zul> Daviey: havent touched it in a long time
[16:09] <zul> it should be ressurected though
[16:09] <jamespage> +1
[16:10] <zul> does someone want to take that action?
[16:10] <zul> if i show them again where everything is and clear out the database and possibly update it for precise
[16:11] <arosales> zul: I can give that a try
[16:11] <jamespage> zul: give it to me - kinda forms part of my holistic review of triage etc.. anyway
[16:11] <zul> oooh...deathmatch
[16:11] <zul> i though Ursinha` did something with it
[16:11] <roaksoax> jamespage: and now that you mention it, where should we be trackingnew bugs from now on?
[16:11] <arosales> zul ping jamespage and I offline
[16:12] <arosales> I would be interested in knowing how it works even if jamespage takes the full action
[16:12] <jamespage> http://reports.qa.ubuntu.com/reports/ubuntu-server/triage-report.html
[16:12] <zul> #action zul talk to arosales and jamespage offline about SRU tracker
[16:12] <meetingology> ACTION: zul talk to arosales and jamespage offline about SRU tracker
[16:12] <jamespage> for the time being at least
[16:12] <zul> anything else to bring up?
[16:12] <roaksoax> jamespage: thanks
[16:13] <zul> jamespage/arosales/Daviey: is there anything im missing
[16:13] <arosales> for Quantal I think that is it for now
[16:13] <zul> cool beans
[16:13] <jamespage> I don't think so - blueprints and then merges!
[16:13] <Daviey> zul: how long do we have? :)
[16:14] <zul> Daviey: none
[16:14] <zul> #topic Ubuntu Server Team Events
[16:14] <zul> hah hah!
[16:14] <Daviey> no more travel please! :)
[16:14] <zul> so summer is coming up, so that means stuff like oscon, velocity, linuxcon, etc, etc etc
[16:14] <arosales> gluecon coming up for m_3
[16:14] <arosales> 23-24 may
[16:14] <s3h> i might go to linuxcon, but waiting to hear on that
[16:15] <s3h> (plumber's, really)
[16:15] <Daviey> s3h: oh, neat!
[16:15]  * zul hopes to stay home this summer
[16:15] <zul> oh yeah OLS as well
[16:15] <SpamapS> Daviey: actually we're going to have a sprint, just you and me, here in LA, for the next 3 weeks.
[16:15] <s3h> (waitingn to hear from Daviey that is :)
[16:15] <Daviey> SpamapS: sounds awesome.
[16:16] <zul> moving on
[16:16] <SpamapS> Velocity is coming up
[16:16] <SpamapS> wait
[16:16] <SpamapS> I think somebody is going to that
[16:16] <SpamapS> (sorry I got majorly lagged out there)
[16:16] <zul> im guessing m_3
[16:16] <arosales> velocity is at the end of june
[16:16] <SpamapS> Jorge and Hazmat I think
[16:16] <arosales> 27-28 June
[16:16] <m_3> no Velocity for me... I'll be out of pocket
[16:17] <SpamapS> Oh and LISA talk submission deadline is this week
[16:17] <SpamapS> so for all ubuntu server users, make sure you get your "Ubuntu server is awesome" talks submitted! :)
[16:17] <SpamapS> that is all
[16:17]  * smb hopes to go to Plumbers and maybe XenSummit as it is just before that
[16:17] <SpamapS> Isn't plumbers in San Diego?
[16:17] <zul> mmm....more citrix marketing
[16:17] <zul> it is
[16:17]  * m_3 just hopes Plumbers scheduling is working seamlessly atm :)
[16:18] <m_3> yes, san diego... late august I think
[16:18] <SpamapS> m_3: talk to the IS guys.. they wrote charms for the schedule boxes too
[16:18] <smb> 29-31
[16:18] <SpamapS> ok thats enough about events. :)
[16:18] <m_3> SpamapS: that's the one on the summit charm.. don't think we're doing anything beyond that
[16:19] <zul> #topic Weekly Updates & Questions for the QA Team (hggdh)
[16:19] <zul> hi hggdh
[16:19] <zul> if you are around
[16:19] <zul> lots of good qa sessions at uds as well
[16:20] <SpamapS> Yeah QA were the rockstars of uds-q :)
[16:20] <zul> i guess he is not here
[16:20] <zul> #topic Weekly Updates & Questions for the Kernel Team (smb)
[16:20] <zul> hi smb
[16:20] <smb> \o
[16:21] <smb> Are there Questions ?
[16:21] <zul> i didnt attend any kernel sessions at uds
[16:21] <smb> As I don't think I have much to report
[16:21] <zul> er...what kernel are we using for quantal? ;)
[16:21] <smb> 2.6.24
[16:21] <smb> :-P
[16:21] <zul> how retro
[16:22] <zul> any questions for smb?
[16:22] <smoser> big news from kernel team was that -virtual may be going away.
[16:22] <zul> yay!
[16:22] <smb> Right, more of a packaging change
[16:22] <zul> replacing it with a regular server kernel?
[16:23] <smb> no, that does not exist anymore
[16:23] <smb> generic or generic-pae
[16:23] <zul> regular generic kernel
[16:23] <zul> ah i see
[16:23] <smb> And having a split between minimal and additional modules
[16:23] <zul> cool
[16:23] <zul> anything else for smb?
[16:24] <rbasak> 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] <zul> rbasak: well they can still have a server with ubuntu-desktop installed
[16:25] <rbasak> That's the thing - there's no real distinction in technical terms, but pragmatically the information is useful when triaging
[16:26] <zul> right totally agree and thats been a problem for a long while
[16:26] <SpamapS> rbasak: we get the install media
[16:26] <smb> Hm, I may be wrong but potentially the linux-server meta package is still there
[16:26] <SpamapS> rbasak: thats a good indication of what they intended at install time
[16:27] <smb> Yeah, seems to be true
[16:27] <zul> SpamapS: install media can be maas now as well though
[16:27] <zul> anyways i dont think its going to be solved as well
[16:27] <smb> rbasak, ^
[16:27] <zul> er...solved now
[16:27] <rbasak> We don't always get the install media, eg bug 999614.
[16:28] <rbasak> That may be a cloud image or something
[16:28] <zul> so moving on
[16:28] <zul> rbasak: good timing
[16:28] <zul> #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)
[16:28] <rbasak> Calxeda demoed MAAS working on their hardware at UDS!
[16:28] <rbasak> Work on ARM server and MAAS is ongoing.
[16:28] <rbasak> Any questions for me?
[16:29] <zul> i want one
[16:29] <rbasak> That's not a question :-)
[16:29] <zul> please can i have one?
[16:29] <rbasak> No.
[16:29] <rbasak> :-P
[16:30] <rbasak> I don't think any ETA for general marketing availability has been announced yet.
[16:30] <rbasak> *market
[16:30]  * zul sighs
[16:30] <zul> #topic Open Discussion
[16:30] <zul> anyone want to get something off their chest
[16:31] <zul> how was uds for everyone?
[16:31] <SpamapS> weird going back and forth for just 2 days
[16:32] <arosales> SpamapS: did you collect some good feedback for remote participants?
[16:32] <arosales> or was that handled pretty well?
[16:32] <SpamapS> I think we should consider google hangouts
[16:32] <s3h> we tried one for one talk.   didn't work well
[16:32] <SpamapS> I see no reason to put people in a one-way audio bubble
[16:33] <jamespage> I was in a couple of meetings where that worked OK
[16:33] <SpamapS> s3h: what went wrong?
[16:33] <smoser> google hangout swould be a useful addition. especially if integrated with the room.
[16:33] <zul> need more bandwith i think
[16:33] <s3h> choppy, delay
[16:33] <SpamapS> Ah
[16:33] <rbasak> I've found G+ to be choppy and delayed as well.
[16:33] <SpamapS> Thats surprising
[16:33] <rbasak> How about a SIP hardware phone on speakerphone?
[16:33] <s3h> that would be aweseome
[16:33] <s3h> how about just mumble :)
[16:34] <jamespage> SIP hardware phone was avaliable on request
[16:34] <s3h> did anyone try it?
[16:34] <rbasak> The catch about two-way audio is that it relies on everyone being able to control their mute button
[16:34] <SpamapS> well anyway, I find it very hard to "participate" from IRC+delayed audio
[16:34] <jamespage> The DMB meeting used one - it worked OK
[16:34] <s3h> SpamapS: +1, same here
[16:34] <SpamapS> But it did "work" and I felt that I was able to chime in a bit.
[16:34] <s3h> the delay makes it unusable if you're goign to be really involved
[16:34] <SpamapS> rbasak: thats the catch IRL too ;)
[16:34] <s3h> fine for just following along half-heartedly
[16:35] <rbasak> The good thing about G+ is that someone managing things can identify who is causing an audio issue and remote mute him.
[16:35] <s3h> good conf lines can do that too :)
[16:35] <rbasak> The catch is that this needs someone to manage things.
[16:35] <zul> asterisk
[16:35] <s3h> i seriously didn't know about the sip lines.  we should try those for next time
[16:35] <s3h> or yeah, asterisk to Daviey's server
[16:35] <SpamapS> 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] <s3h> +1 for etherpad
[16:36] <jamespage> just remember to save your notes....
[16:36] <s3h> oh yeah - by when?
[16:36]  * jamespage shrugs
[16:36] <s3h> "before that storm rolling in"
[16:36] <jamespage> not sure but the sooner the better
[16:36] <s3h> i would, but this meeting wont' end :)
[16:37] <jamespage> lol
[16:37] <zul> i think there was an email about uds feedback that you can do :)
[16:37] <zul> so anything else so i can end the meeting for s3h?
[16:37] <zul> if not
[16:37] <zul> same time next week
[16:37] <zul> #endmeeting
[16:37] <meetingology> Meeting ended Tue May 15 16:37:44 2012 UTC.
[16:37] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-05-15-16.00.moin.txt
[16:37] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-05-15-16.00.html
[16:37] <s3h> thanks :)
[16:37] <arosales> zul thanks for chairing
[16:38] <roaksoax> \o/
[16:38] <zul> arosales: no probs this is the longest possible time i have before i chair again ;)
[16:38] <roaksoax> lol
[17:00] <jsalisbury> #startmeeting
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> ## This is the Ubuntu Kernel Team weekly status meeting.
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[17:00] <meetingology> Meeting started Tue May 15 17:00:33 2012 UTC.  The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[17:00] <meetingology> 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
[17:00] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Precise
[17:00] <jsalisbury> # Meeting Etiquette
[17:00] <jsalisbury> #
[17:00] <jsalisbury> # NOTE: '..' indicates that you are finished with your input.
[17:00] <jsalisbury> #       'o/' indicates you have something to add (please wait until you are recognized)
[17:00] <jsalisbury> Roll Call for Ubuntu Kernel Weekly Status Meeting
[17:00] <ppisati> o/
[17:00] <ogasawara> o/
[17:00] <henrix> o/
[17:01] <bjf> o/
[17:01] <cking> o/
[17:01] <herton> o/
[17:01] <jsalisbury> [TOPIC] ARM Status (ppisati)
[17:01] <ppisati> work on a Q/omap4 kernel is ongoing, but apart from that, nothing to report this week
[17:01] <ppisati> ..
[17:01] <sconklin> o/ Late
[17:01] <jsalisbury> [TOPIC] Release Metrics and Incoming Bugs (jsalisbury)
[17:01] <jsalisbury> Release metrics and incoming bug data can be reviewed at the following link:
[17:01] <jsalisbury> [LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt
[17:01] <jsalisbury> ..
[17:02] <jsalisbury> [TOPIC] Status: Quantal Development Kernel (ogasawara)
[17:02] <ogasawara> a few things...
[17:02] <ogasawara> [LINK] http://status.ubuntu.com/ubuntu-quantal/canonical-kernel-distro-team
[17:02] <ogasawara> Work items are beginning to populate the blueprints.  I'll start calling
[17:02] <ogasawara> out specific work items in upcoming meetings.
[17:02] <ogasawara> We've rebased the Quantal kernel to upstream v3.4-rc7.  We uploaded but
[17:02] <ogasawara> ran into a build failure on i386.  Test builds are currently underway
[17:02] <ogasawara> and we will re-upload shortly.  We also have the quantal kernel building
[17:02] <ogasawara> in precise.  We are getting a PPA set up so that testing can commence.
[17:02] <ogasawara> Important upcoming dates:
[17:02] <ogasawara>  * Thurs Jun 7 - Alpha 1 (~3 weeks)
[17:02] <ogasawara> ..
[17:03] <jsalisbury> [TOPIC] Status: CVE's (apw)
[17:03] <apw> Currently we have 82 CVEs on our radar, with 5 new CVEs in the last
[17:03] <apw> three weeks.  See the CVE matrix for the current list:
[17:03] <apw>  
[17:03] <apw> [LINK] http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html
[17:03] <apw>  
[17:03] <apw> Overall the backlog has increased slightly slightly this week:
[17:03] <apw>  
[17:03] <apw> [LINK] http://people.canonical.com/~kernel/status/cve-metrics.txt
[17:03] <apw> [LINK] http://people.canonical.com/~kernel/cve/pkg/CVE-linux.txt
[17:03] <apw>  
[17:03] <apw> This week sees Quantal listed for the first time, and the addition
[17:03] <apw> of the armadaxp kernels for ease of tracking.
[17:03] <apw>  
[17:03] <apw> ..
[17:03] <jsalisbury> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Precise/Oneiric/Natty/Lucid/Hardy (bjf/herton/henrix)
[17:03] <bjf> Here is the status for the main kernels, until today (May  15):
[17:03] <bjf>  
[17:03] <bjf>  * Hardy    - 2.6.24-31.101 - Testing; Single CVE
[17:03] <bjf>  * Lucid    - 2.6.32-41.89  - Testing; 5 CVEs
[17:03] <bjf>  * Natty    - 2.6.38-15.59  - Nothing this cycle
[17:04] <bjf>  * Oneiric  - 3.0.0-20.34   - Testing; 4 stable upstream releases (approx. 300 commits)
[17:04] <bjf>  * Precise  - 3.2.0-24.38   - Testing; 2 stable upstream releases (approx. 140 commits)
[17:04] <bjf>  
[17:04] <bjf> Current opened tracking bugs details:
[17:04] <bjf>  * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html
[17:04] <bjf>  
[17:04] <bjf> For SRUs, SRU report is a good source of information:
[17:04] <bjf>  * http://people.canonical.com/~kernel/reports/sru-report.html
[17:04] <bjf>  
[17:04] <bjf> Future stable cadence cycles:
[17:04] <bjf>  * https://wiki.ubuntu.com/QuantalQuetzal/ReleaseInterlock
[17:04] <bjf>  
[17:04] <bjf> ..
[17:04] <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
[17:04] <jsalisbury> Thanks everyone
[17:05] <jsalisbury> #endmeeting
[17:05] <meetingology> Meeting ended Tue May 15 17:05:01 2012 UTC.
[17:05] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-05-15-17.00.moin.txt
[17:05] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-05-15-17.00.html
[17:07] <jussi> cripes, you guys are quick
[17:13] <apw> jussi, blink and you miss it
[17:13] <jussi> apw: true that