=== vanhoof_ is now known as vanhoof === doko_ is now known as doko === oubiwann` is now known as oubiwann === kenvandine_ is now known as kenvandine [07:15] hmm [07:15] persia: are we meeting tonight? === leoquant is now known as Guest58687 === lag` is now known as lag === Ursinha-afk is now known as Ursinha === zul__ is now known as zul === fader_` is now known as fader_ [13:18] hey === Ursinha is now known as Ursinha-lunch === s1aden is now known as sladen === zul__ is now known as zul [15:58] thank you zul [15:58] * smoser is heading out for 30 minutes. [15:58] hi [15:59] still 2 minutes according to my clock [15:59] o/ [16:00] hi so lets get that started [16:00] #startmeeting [16:00] Meeting started at 10:00. The chair is zul. [16:00] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [16:00] [TOPIC] Review ACTION points from previous meeting [16:00] New Topic: Review ACTION points from previous meeting [16:00] since there is nothing in the last meeting we jump to [16:00] [TOPIC] Natty Development [16:00] New Topic: Natty Development [16:00] so alpha3 is going to be released on thursday [16:01] your blueprints wi should be marked as postposted if they arent complete and carried over [16:01] iso testing this week so please help out [16:01] anything else? [16:01] Sounds good to me. [16:01] action + url for iso testign for the record? [16:02] [ACTION] iso testing - everybody (http://iso.qa.ubuntu.com) [16:02] ACTION received: iso testing - everybody (http://iso.qa.ubuntu.com) [16:02] :) [16:02] is robbie around? [16:03] if not we will move on...going once... [16:03] okies then [16:03] [TOPIC] Ubuntu Server Team Events [16:03] New Topic: Ubuntu Server Team Events [16:03] anyone have anything to add? [16:04] UDS is soon and sponsorship is open now so if you want to be sponsored please sign up [16:04] cool ;) [16:05] that means you ttx [16:05] lol [16:05] its in budapest this year in may [16:05] nice and toasty [16:05] [TOPIC] Weekly Updates & Questions for the QA Team (hggdh) [16:05] New Topic: Weekly Updates & Questions for the QA Team (hggdh) [16:05] hi hggdh [16:06] yo [16:06] anything to report? [16:06] this is A3 week, we will probably need help [16:06] Hggdh. Expect a news eucalyptus today. [16:07] yay! [16:07] New [16:07] Daviey: so I will refrain from testing it until you ping me [16:07] Cool [16:07] that [16:07] that it? ;) [16:07] hggdh: so I guess when you start testing we can take a deeper look into the PowerNap issue then [16:07] 's it [16:08] RoAkSoAx: yes, certainly [16:08] ok next [16:08] Hggdh... Any comments on a3 testing? [16:08] just need help right hggdh? [16:09] new ISO seems better, but some bare-metal installs would help [16:09] (we had an issue that only appeared in bare-metal) [16:09] Groovy [16:09] thanks [16:09] [TOPIC] Weekly Updates & Questions for the Kernel Team (smb) [16:09] New Topic: Weekly Updates & Questions for the Kernel Team (smb) [16:09] hi smb [16:09] Hi there [16:10] anything to report? [16:10] So not much. A bit of ec2 testing fallout, some xfs regression that was reported and some nasty Lucid behavior in net namespace. [16:11] bug 720095 [16:11] Launchpad bug 720095 in linux (Ubuntu) "vsftpd causes a vmalloc space leak in Lucid" [Medium,Confirmed] https://launchpad.net/bugs/720095 [16:11] oh thats fun [16:11] bug 725089 [16:11] Launchpad bug 725089 in linux (Ubuntu) "SECCOMP causes kernel panic on EC2 AMD64 image" [High,Confirmed] https://launchpad.net/bugs/725089 [16:11] bug 692848 [16:11] Launchpad bug 692848 in linux (Ubuntu Karmic) "Regression between 2.6.32-27 and 2.6.32-26 xfsdump SGI_FS_BULKSTAT errno = 22" [Medium,In progress] https://launchpad.net/bugs/692848 [16:12] people shouldnt use ftp anyways ;) [16:12] any questions? [16:12] The seccomp panic "luckily" is no regression, just a race that sometimes happens [16:12] .. [16:12] smb: bug id for net ns lucid ? [16:12] hallyn, Thats the vsftp bug [16:13] ah [16:13] Basically the problem is that the cleanup for clones of the net namespace hang around for a whole [16:13] Upstream changed a lot between Lucid and Maverick to batch things [16:14] Seems a bit much for backporting, so I try to find some smaller solution [16:14] (not with much luck yet) [16:14] .. [16:14] thanks [16:14] impressive root-cause finding ;) [16:15] [TOPIC] Weekly Updates & Questions for the Documentation Team (sommer) [16:15] New Topic: Weekly Updates & Questions for the Documentation Team (sommer) [16:15] sommer around? [16:15] im thinking no [16:15] well come back to that one if needed [16:15] [TOPIC] Weekly Updates & Questions from the Ubuntu Community [16:15] New Topic: Weekly Updates & Questions from the Ubuntu Community [16:15] o/ [16:15] hi kim0 [16:15] the thing I wanna mention [16:15] is the .. drum roll [16:16] Ubuntu Cloud Days [16:16] https://wiki.ubuntu.com/UbuntuCloudDays/ [16:16] basically very similar to UDW [16:16] everyone who's attending that meeting is a very good candidate to register a session [16:16] please choose one and write it in https://wiki.ubuntu.com/UbuntuCloudDays/Timetable [16:16] its just the two days right? [16:16] don't make me pick one for you [16:17] zul: well yes, unless I get flooded with volunteers [16:17] basically, I've written a blog post announcing it [16:17] kim0: cool [16:17] but dont wanna publish it before you guys have added a few sessions [16:17] so please go go go [16:17] that's mostly it for me [16:17] cool any questions? [16:17] nope [16:18] Exciting [16:18] any other questions for kim0 [16:18] [TOPIC] Open Discussion [16:18] New Topic: Open Discussion [16:18] kirkland: around? how was scale [16:19] or not [16:19] so lxcguest [16:20] we have been adding lxc containers support to openstack and we would like add lxcguest support to the uec-images [16:20] i have discussed with smoser that it should be brought into main. does anyone see an issue with that? [16:21] this would make testing images on openstack much more easier [16:21] woot [16:21] the work is already on the way to get it done [16:22] How will mainly bed supporting generic.lxc? [16:22] Who [16:22] us [16:22] or i missed the question [16:22] I support lxc [16:23] Hallyn, cool [16:23] and the lxc support in openstack is done through libvirt so that is also hallyn :) [16:23] Heh [16:23] [16:23] any other open discussion type things? [16:24] Nah [16:24] [TOPIC] Announce next meeting date and time [16:24] New Topic: Announce next meeting date and time [16:24] Tuesday, March 8 2011 16:00 UTC [16:24] thanks for comming [16:24] #endmeeting [16:24] Meeting finished at 10:24. [16:24] Short and sweet [16:35] wow. short meeting === dholbach_ is now known as dholbach [16:59] o/ [16:59] \o [16:59] o/ [16:59] \o [16:59] \o [17:00] o/ [17:00] \o [17:00] o/ [17:00] \o [17:01] #startmeeting [17:01] Meeting started at 11:01. The chair is bjf. [17:01] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [17:01] [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting [17:01] [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Natty [17:01] LINK received: https://wiki.ubuntu.com/KernelTeam/Meeting [17:01] LINK received: https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Natty [17:01] # Meeting Etiquette [17:01] # [17:01] # NOTE: '..' indicates that you are finished with your input. [17:01] # 'o/' indicates you have something you'd like to add (wait until you are recognized) [17:01] # [17:01] [TOPIC] Release Metrics (JFo) [17:01] New Topic: Release Metrics (JFo) [17:01] Release Meeting Bugs (8 bugs, 9 Blueprints) [17:01] ==== Beta 1 Milestoned Bugs (71 across all packages (up 15)) ==== [17:01] * 5 linux kernel bugs (up 1) [17:01] * 0 linux-ti-omap bugs (no change) [17:01] * 0 linux-meta-ti-omap bug (no change) [17:01] ==== Release Targeted Bugs (271 across all packages (up 6)) ==== [17:01] * 20 linux kernel bugs (down 3) [17:02] * 0 linux-ti-omap bugs (no change) [17:02] * 0 linux-meta-ti-omap bug (no change) [17:02] ==== Milestoned Features ==== [17:02] * 7 blueprints (Including HWE Blueprints) [17:02] ==== Maverick Updates Bugs ==== [17:02] * 60 Linux Bugs (down 3) [17:02] ==== Lucid Updates Bugs ==== [17:02] * 94 Linux Bugs (no change) [17:02] ==== Bugs with Patches Attached:77 (down 21) ==== [17:02] * [[https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.has_patch=on | Bugs with Patches]] [17:02] * [[http://qa.ubuntu.com/reports/ogasawara/csv-stats/bugs-with-patches/linux/ | Breakdown by status]] [17:02] .. [17:02] [TOPIC] Blueprints: Natty Bug Handling (JFo) [17:02] [LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-bug-handling [17:02] New Topic: Blueprints: Natty Bug Handling (JFo) [17:02] LINK received: https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-bug-handling [17:02] * apport hook change item: POSTPONED [17:02] I will not likely get to this before UDS, but if I do, I will update the status then. [17:02] * develop process for handling, validation & closure, and document in the wiki:INPROGRESS [17:02] I still have a bit of work to do on this. I didn't have the time over the past week to complete it. [17:02] * drive existing bugs with patches list to zero and keep it there:INPROGRESS [17:02] My thanks to those of you who have been working on this. The list continues to drop significantly [17:02] every week. [17:02] Other items in the list didn't get looked at this past week. I have time scheduled this [17:02] coming week to address them and, hopefully, close them out. [17:02] .. [17:03] [TOPIC] Status: General Natty (apw) [17:03] New Topic: Status: General Natty (apw) [17:03] The natty kernel is now at v2.6.38-5.32 (v2.6.38-rc6 based). Overall we have most of our development out of the way, with just the ecryptfs long filename work ongoing. We are currently concentrating on bug squashing for Natty. One area of concern is an interaction between vesafb and drmfb during boot, in some cases we are triggering gpu hangs; upstream says "don't do that". We are currently in freeze for Alpha-3. We are waiting on -rc7 which shou [17:03] ld be imminent, planning to upload it as soon as freeze lifts. [17:03] .. [17:03] [TOPIC] Status: Ecryptfs (jj) [17:03] New Topic: Status: Ecryptfs (jj) [17:03] No real progress - postponed for natty. xattr version still waiting for review, some work on in header version [17:04] .. [17:04] [TOPIC] Status: Stable Kernel Team (sconklin / bjf) [17:04] New Topic: Status: Stable Kernel Team (sconklin / bjf) [17:04] || We are in the middle of preparing kernels for a new cycle and uploading [17:04] || them to our PPA. We had planned to complete this last week but were [17:04] || delayed by a possible regression in the last set of kernels undergoing [17:04] || testing. This turned out not to be a regression, and we are free to proceed. [17:04] || We plan to have all the remaining packages uploaded today. [17:04] || [17:04] .. [17:04] [TOPIC] Security & bugfix kernels - Maverick/Lucid/Karmic/Hardy/Dapper (sconklin / bjf) [17:04] New Topic: Security & bugfix kernels - Maverick/Lucid/Karmic/Hardy/Dapper (sconklin / bjf) [17:04] || Package || Upd/Sec || Proposed || TiP || Verified || [17:04] || || || || || || [17:04] || dapper linux-source-2.6.15 || 2.6.15-55.93 || || || || [17:04] || --- linux-meta || 2.6.15-56 || || || || [17:04] || || || || || || [17:04] || hardy linux || 2.6.24-28.86 || || || || [17:04] || --- linux-meta || 2.6.24-28.30 || || || || [17:04] || || || || || || [17:04] || karmic linux || 2.6.31-22.73 || || || || [17:04] || --- linux-meta || 2.6.31-22.35 || || || || [17:04] || --- linux-ec2 || 2.6.31-307.27 || || || || [17:04] || --- linux-meta-ec2 || 2.6.31.307.6 || || || || [17:04] || --- linux-ports-meta || 2.6.31.22.18 || || || || [17:04] || --- linux-backports-modules-2.6.31 || 2.6.31.22.24 || || || || [17:04] || --- linux-fsl-imx51 || 2.6.31-112.30 || || || || [17:04] || --- linux-meta-fsl-imx51 || 2.6.31.112-10 || || || || [17:05] || --- linux-mvl-dove || 2.6.31.214.32 || || || || [17:05] || --- linux-meta-mvl-dove || 2.6.31.214.13 || || || || [17:05] || || || || || || [17:05] || lucid linux-ec2 || 2.6.32-312.24 || 2.6.32-313.26 || 8 || 6 || [17:05] || --- linux-ports-meta || 2.6.32.28.21 || 2.6.32.29.22 || 0 || 0 || [17:05] || --- linux-mvl-dove || 2.6.32-211.27 || 2.6.32-214.30 || 6 || 6 || [17:05] || --- linux-meta-mvl-dove || 2.6.32.209.12 || 2.6.32.214.15 || 0 || 0 || [17:05] || --- linux-lts-backport-maverick || 2.6.35-23.41~lucid1 || 2.6.35-25.44~lucid1 || 0 || 0 || [17:05] || --- linux-backports-modules-2.6.32 || 2.6.32-28.27 || 2.6.32-29.28 || 0 || 0 || [17:05] || --- linux || 2.6.32-28.55 || 2.6.32-29.58 || 6 || 6 || [17:05] || --- linux-meta || 2.6.32.28.32 || 2.6.32.29.35 || 0 || 0 || [17:05] || --- linux-meta-ec2 || 2.6.32.312.13 || 2.6.32.313.14 || 0 || 0 || [17:05] || || || || || || [17:05] || maverick linux-mvl-dove || || 2.6.32-414.30 || 4 || 4 || [17:05] || --- linux-meta-mvl-dove || || 2.6.32.414.4 || 0 || 0 || [17:05] || || || || || || [17:05] .. [17:05] [TOPIC] Status: HW Cert. Team (ara) [17:05] New Topic: Status: HW Cert. Team (ara) [17:06] anyone from Cert. standing in for ara today ? [17:06] [TOPIC] Incoming Bugs: Regressions (JFo) [17:06] New Topic: Incoming Bugs: Regressions (JFo) [17:06] Incoming Bugs [17:06] 182 Natty Bugs (up 2) [17:06] 1183 Maverick Bugs (down 2) [17:06] 1025 Lucid Bugs (up 6) [17:06] Current regression stats (broken down by release): [17:06] ==== regression-update ==== [17:06] * 40 maverick bugs (up 1) [17:06] * 75 lucid bugs (down 2) [17:06] * 7 karmic bugs (no change) [17:06] * 0 hardy bugs (no change) [17:07] ==== regression-release ==== [17:07] * 73 natty bugs (up 3) [17:07] * 237 maverick bugs (no change) [17:07] * 218 lucid bugs (up 10) [17:07] * 38 karmic bugs (no change) [17:07] * 2 hardy bugs (no change) [17:07] ==== regression-proposed ==== [17:07] * 0 natty bugs (down 1) [17:07] * 0 maverick bugs (down 2) [17:07] * 0 lucid bugs (no change) [17:07] * 0 karmic bug (no change) [17:07] .. [17:08] [TOPIC] Incoming Bugs: Bug day report (JFo) [17:08] New Topic: Incoming Bugs: Bug day report (JFo) [17:08] Last week's bug day was a success. We had quite a number of bugs reviewed. [17:08] Many changed states. I had the opportunity to take a closer look at the [17:08] arsenal script we use to process these and there is some work continuing there [17:08] to make that script work better. The next bug day will be next Tuesday. [17:08] I had originally hoped to have one today, but I couldn't get everything ready [17:08] and announced in time, so I will announce for next week. [17:08] .. [17:08] [TOPIC] Triage Status (JFo) [17:08] New Topic: Triage Status (JFo) [17:08] We have had quite a bit of interest in the periphery on bug triage. I have been [17:08] fielding a few requests in #ubuntu-bugs about the proper level of information needed [17:08] in bugs as well as the occasional private request. As always, I am recomending that [17:08] interested parties inquire in our channel on #ubuntu-kernel so that others [17:08] can benefit from the knowledge sharing. [17:08] .. [17:09] [TOPIC] Open Discussion or Questions: Raise your hand to be recognized (o/) [17:09] New Topic: Open Discussion or Questions: Raise your hand to be recognized (o/) [17:10] thanks everyone [17:10] #endmeeting [17:10] Meeting finished at 11:10. [17:10] thanks bjf [17:10] thanks bjf [17:10] thanks bjf === dholbach_ is now known as dholbach [17:12] wow bjf - 10 minutes... new record for the kernel team? ;) [17:13] heh [17:13] \o/ :-) === drubin_ is now known as drubin [18:00] ajmitch: ping [18:01] can't find wendar or fagan ... [18:02] I'll be back in 5 minutes, hopefully I won't be alone anymore by then ;) [18:30] stgraber: sorry, I'd forgotten it was this morning [18:31] stgraber: I think wendar said she'd be travelling & probably unavailable this week? [18:32] I seem to remember something like this yes [18:33] given how late I've come in, & no fagan, I'm guessing we may have to skip it this week [18:33] * ajmitch has to head out in 10 minutes [18:34] I've been slack & not written up http://www.novarata.net/mootbot/ubuntu-meeting.log.20110215_1214.html [18:35] ok, I'm fine skeeping this one. I only have one package assigned to me and the packager will send a new version for review. [18:35] so really nothing mouch to discuss this week [18:35] I think there was one new appliction submitted after the last meeting? [18:37] it's possible, I don't remember seeing it though [18:37] https://bugs.launchpad.net/ubuntu-app-review-board/+bug/719694 [18:37] Ubuntu bug 719694 in Ubuntu Application Review Board "Application Review Request: Tibesti 1.2.7" [Undecided,New] [18:38] & I was taking https://bugs.launchpad.net/ubuntu-app-review-board/+bug/718413 [18:38] Ubuntu bug 718413 in Ubuntu Application Review Board "Application Review Request: schedio 2.0.0-0ubuntu1" [Undecided,New] [18:40] * ajmitch thinks we should probably take it to the mailing list then - minutes from 2 weeks ago should be sent there [18:40] +1 [18:41] ok then :) [18:41] * ajmitch shall run off to work now === zul_ is now known as zul === debfx_ is now known as debfx === Ursinha-afk is now known as Ursinha [20:01] Gooooooood afternoon! [20:01] *ahem*, evening, in EMEA zone at least :) === neversfelde_ is now known as neversfelde [20:03] Any EMEA board members present? stgraber is on the phone but he should be here momentarily [20:03] is Rafael Laguna present? [20:07] Seems like today's meeting is a no-go. Next EMEA RMB meeting is on April 5th at 20:00 UTC. [20:12] highvoltage: Thanks for handling this. [20:13] drubin: you're welcome === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha [20:15] -meeting already over? [20:16] Raydiation: yes, there was only one applicant and they aren't around === Ursinha is now known as Ursinha-afk [20:58] is there a CC meeting happening here today? [21:00] according to the fridge there is! [21:00] mdz: yes, I think in a couple of minutes [21:00] mdz, yes [21:00] thanks [21:01] * pleia2 waves [21:01] #startmeeting [21:01] Meeting started at 15:01. The chair is pleia2. [21:01] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [21:01] * jono waves at pleia2 [21:01] ok, I'm not sure we will have quorum today (a few members can't make it) and the last minute agenda items may be tricky to cover, but we can talk about them [21:02] [LINK] https://wiki.ubuntu.com/CommunityCouncilAgenda [21:02] LINK received: https://wiki.ubuntu.com/CommunityCouncilAgenda [21:02] thanks for coordinating the session pleia2 [21:03] first off mdz is here to talk about the diversity statement he's been working on [21:03] [TOPIC] Diversity statement: next steps [21:03] New Topic: Diversity statement: next steps [21:03] yes, so I'd like to know what the CC would like to happen next with this [21:03] evening all [21:03] welcome sabdfl [21:03] how are you all? [21:03] hello sabdfl [21:04] hey sabdfl [21:04] are we rolling, or should we start? [21:04] so far the time line on the diversity statement has been: mdz proposed in the fall, came out with a draft with the CC approved last month, and posted on his blog for community review: http://mdzlog.alcor.net/2011/02/07/a-diversity-statement-for-ubuntu/ [21:04] sabdfl: we're going, on agenda item one "Diversity statement: next steps" [21:05] okdokey [21:06] I consider it more or less "done" in terms of the document, and would like to see it move forward to become an official statement and put into practice in the community [21:06] i think we ack'd it previously, in essentially the same form [21:06] with the caveat that there should be discussion [21:06] yes [21:06] since this is a community-developed document, I think the blessing by the CC should be sufficient to make it official [21:06] was there much commentary after your blog? [21:07] I summarized it to c-c@ a while back [21:07] 40 comments on the blog entry [21:07] maybe an Ubuntu Values page should be created on ubuntu.com with this and the CoC just to make this easy to find for the community [21:08] there were a lot of suggested wording changes, some of which are reasonable but not urgently needed (wordsmithing) [21:08] re-reading the text, i wonder why we don't have the paragraph on taking responsibility in the code of conduct? [21:08] "Whenever any participant has made a mistake, we expect them to take responsibility for it. If someone has been harmed or offended, it is our responsibility to listen carefully and respectfully, and do our best to right the wrong." [21:08] I actually have a code of conduct diff which goes along with this [21:08] and adds that [21:08] sabdfl: +1 for that [21:08] oh, it was also shared on the ubuntu-women and ubuntu-for-all lists [21:08] I can send that diff to c-c@ if you like [21:09] it's small [21:09] voice test [21:09] that would be great. i wouldn't block on this, but if the plan is to integrate that bit into the CoC, let's take it out of this one [21:10] sounds great [21:10] let me send the diff and we can discuss it [21:10] thanks mdz :) [21:10] I think they're complementary, but let's see [21:10] so if someone is offended that Cannonical makes public private information of a member and does nothing to right the wrong, how should that be handled? [21:10] also, the nod to python and dreamwidth would probably be better in a footnote than the statement itself [21:10] consider it a footnote [21:10] given the CC-BY nature it shouldn't be forgotten, but certainly isn't central [21:10] ok, then +1 from me [21:11] +1 here [21:11] +1 [21:11] what should I do next? [21:11] 1. send the CoC diff [21:11] 2. ... [21:11] chuckf: i think that would be a different matter than harrassment [21:11] I like Technoviking's idea of an Ubuntu Values page where this will go [21:11] mdz, since you've carried this, it's entirely appropriate for you to blog that the CC approved the statement [21:12] sabdfl: but the member is offended, if not harrassed [21:12] if you want one of us to blog in support, that's easily arranged too [21:12]