[00:00] oh [00:00] uh, [00:00] meant to ask that in -motu, pleae move to there === Andre_Gondim-afk is now known as Andre_Gondim === Andre_Gondim is now known as Andre_Gondim-afk === MaWaLe1 is now known as MaWaLe === thekorn_ is now known as thekorn === mdz_ is now known as mdz === thekorn_ is now known as thekorn === thekorn_ is now known as hekorn === hekorn is now known as thekorn === ScottK2 is now known as ScottK [16:01] hello [16:01] hi [16:01] Hallo [16:01] hi [16:02] hi [16:02] for a sec I was sure I had the time wrong. :) [16:02] #startmeeting [16:02] Meeting started at 11:02. The chair is robbiew. [16:02] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [16:02] hi [16:02] * robbiew was in too many irc concurrent conversations [16:03] so not much of an agenda this week [16:03] few topics [16:04] [TOPIC] BetaFreeze [16:04] New Topic: BetaFreeze [16:04] it's tomorrow, correct? [16:04] yes [16:05] okay...figure everyone knows this...so moving on [16:05] check for unreleased stuff lying around your hard disk, if you're anything like me [16:05] heh [16:05] (I'll send out a quick reminder to u-d-a this morning about the impending freeze) [16:05] hm, I have a bugfix to python-fstab that might be nice, if anyone wants to sponsor an upload tonight [16:06] poor liw...no upload rights :( [16:07] Is the beta freeze starting at 0UTC? [16:07] I'm not poor, I am rich in opportunities to talk people into helping me, it is quite fascinating :) [16:07] TheMuso: probably not, in practice [16:07] ok [16:08] [TOPIC] Sponsorship Queue [16:08] New Topic: Sponsorship Queue [16:09] jono is now sending platform managers monthly stats [16:09] "These stats are not intended as a name and shame, but to instead provide some insight on which members of your team are not meeting the expected requirements of the queue." [16:09] that sounds like naming and shaming ;) [16:10] "these don't incriminate, they just tell you who's guilty" [16:10] heh [16:10] FWIW, I'm not keeping score month to month [16:11] * Keybuk hasn't done any sponsoring [16:11] the stats probably aren't very accurate anyway, since "work on the sponsorship queue" != "uploading", particularly during freezes [16:11] but I'd be lying if I said I wouldn't notice significant droughts :P [16:11] slangasek: yep [16:11] which is not to say that I've been keeping up appropriately [16:11] * mvo coughs [16:12] well...understandably these numbers will fluctuate depending on where we are at in the release cycle [16:13] I'll just use it mostly to show how much our team kicks a$$ [16:13] heh [16:13] we have james_w, we can not loose :) [16:14] [TOPIC] Allhands [16:14] New Topic: Allhands [16:14] Just a reminder to start booking travel [16:15] Portland is booked [16:15] our charter jet will be arriving at noon on Tuesday [16:15] heh [16:15] slangasek: need a pilot? :p [16:15] :-) [16:16] the Austin Cartel travels separately to protect the organization from a single point of failure [16:16] folks should update https://wiki.canonical.com/AdminTeam/Travel/Barcelona2009 [16:16] once travel is booked [16:16] "Austin Cartel", isn't that the name of some DJ on MTV? [16:16] heh...I wouldn't know...don't watch MTV :P [16:17] that's really all I got [16:17] [TOPIC] AOB/Good News? [16:17] New Topic: AOB/Good News? [16:17] DebConf paper submissions? :) [16:17] Actually, federal travel regulations specificly state that Texans shouldn't co-mingle. [16:17] ah [16:18] * robbiew follows up now...sent an email [16:18] thx [16:18] debconf wants papers? [16:19] liw: heh [16:19] well, talks [16:19] good news: oem-priority bug list down to 1, which is not ours [16:19] have been beating on it a bit [16:19] liw: a pre-req for doing a talk is to register...but we are to wait for registration [16:19] cjwatson: whoot! [16:20] bad news: still suffering DNS issues, requesting that IS move my forward to my other domain now. [16:20] evand: heh...yeah, you're bouncing mail all over the "internets" [16:20] sorry [16:21] slangasek: randa is checking with marketing...hopefully we get an answer soon :/ [16:21] mmk [16:21] robbiew, what's the issue with talk registration? [16:22] liw: the issue is that we are supposed to wait to register [16:22] liw: I think we get some sort of discount as a sponsor [16:22] liw: but if you want to submit your talk proposal...you need to register :/ [16:22] well, I've already failed at the "wait" part, I assume randa will be able to clean it up after the fact anyway ;) [16:22] ah, ok [16:22] my question is whether I have a green light to submit my talk [16:22] slangasek: heh...I wouldn't worry too much about it [16:23] robbiew: travel for debconf: I'm planning on bringing the family, so I'm not sure how booking is going to work yet [16:23] slangasek: yeah...waiting on that [16:23] cjwatson: ok [16:23] mvo: so is the conflict checker no longer live? [16:23] robbiew: I'm also not sure yet whether I want to ask to go on Canonical's time but pay my own travel+accommodation, or just ask to go entirely on my own time :) [16:24] cjwatson: heh [16:24] slangasek: unfortunately not, there are some migration issues with the new storm version :/ [16:24] I suspect the former is probably more sensible, but I'm planning to go to some of debcamp as well [16:24] mvo: okie [16:24] cjwatson: I agree [16:25] but anyway, that's what I'm stuck on before doing anything cromulent about debconf [16:25] sure [16:26] anything else? [16:26] once... [16:26] slangasek: I can try to give it some love, but the issue was a bit tricky [16:26] cjwatson: I'm not sure that's a valid use of the word "cromulent" [16:26] twice... [16:26] * mvo looks up "cromulent" [16:26] #endmeeting [16:26] Meeting finished at 11:26. [16:27] thanks [16:27] Keybuk: it's a perfectly cromulent use [16:27] mvo: "valid" roughly ;) [16:27] thanks [16:27] thus my punny response to colin [16:27] thanks [16:27] thanks [16:27] thanks [16:27] robbiew, to submit papers for Debconf we have time until 15th April. I will try Marketing to give me an answer this week [16:27] mvo: some love would be good, I was asking for purposes of mentioning it in the beta freeze pre-announce, which I won't then [16:27] So, exactly what was this meeting about? It isn't on the fridge schedule. [16:28] GrueMaster: things tend to fall off the fridge [16:28] it's a remarkably good metaphor [16:28] this was the weekly meeting of the Ubuntu Foundations Team at Canonical [16:28] a BBC Production [16:28] the Producer was... [16:28] It would be nice if startmeeting had a subject line. [16:28] (it is on the new fridge calendar, of course) [16:28] http://fridge.ubuntu.com/calendar [16:29] ok [16:29] Still getting used to PDT time change (happened while I was in Oxford). [16:30] randa: thnx [16:56] Hello :) [16:58] hey everyone [16:58] * ara waves [16:58] hello again [16:59] Hi [16:59] * ogasawara waves [16:59] Hi [16:59] Howdy [16:59] hola! [17:00] salut cr3 [17:01] pedro_: hey hey! by the way, I must apologize for not having found time to participate in that samba hug day. just too darn busy :( [17:01] sbeattie, ping [17:01] hey [17:01] ok, let's start [17:01] cr3: no worries :-) [17:01] #startmeeting [17:01] Meeting started at 12:01. The chair is heno. [17:01] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [17:02] agenda as usual: https://wiki.ubuntu.com/QATeam/Meetings [17:02] [TOPIC] UbuntuBugDay highlights -- pedro [17:02] New Topic: UbuntuBugDay highlights -- pedro [17:02] Last Thursday we celebrated the Samba hug day, https://wiki.ubuntu.com/UbuntuBugDay/20090312 [17:02] lot of bugs were triaged as you can see per the graphs https://wiki.ubuntu.com/UbuntuBugDay/20090312?action=AttachFile&do=get&target=samba-1day-triaging.png [17:03] The server team helped us a lot solving questions we had (thanks ttx and mathiaz!) [17:04] and they made a pretty good marketing as well [17:04] blogging about it and remember it on the server meetings [17:05] as we talked about earlier pedro, we should make a point of bringing future bug days to other team meetings [17:05] so that they can plan their participation [17:06] yes that'd help a lot to improve the participation from their side [17:06] what's the next theme? [17:06] Ill add that to the organizing page [17:06] great [17:06] heno: cups [17:07] ok so our bug days heroes: paulduf, jgoguen and bigal50, thanks a lot guys for helping out and keep up the great work! [17:07] tomorrow is the cups hug day https://wiki.ubuntu.com/UbuntuBugDay/20090319 and jgoguen already started to work [17:07] so be fast or he is going to squash them all [17:08] Also keep an eye out for new apport bug reports as they'll include the new printing hook which has lots of information. [17:08] pedro_: is Till in the loop? [17:09] indeed [17:09] [TOPIC] New bug control members! -- bdmurray [17:09] New Topic: New bug control members! -- bdmurray [17:10] heno: haven't pinged him yet, isn't clear who is responsible for the package just looking to the changelog, but i'll do it and ping pitti as well he's doing some work there too [17:10] heno: will start adding the hug days to the meetings for the next one then (xorg) [17:10] pedro_: excellent, thanks [17:10] We have one new bug control member this week - Andres Mujica. Andres is particularly interested in kernel bug reports. [17:11] We also have one application, Joel Goguen, currently under review. [17:11] congrats Andres! [17:12] [TOPIC] Next Testing day topic & highlights from last UTD [17:12] New Topic: Next Testing day topic & highlights from last UTD [17:12] ara? ^ [17:12] In the last Testing day we were testing notify-osd [17:13] there was a good communication in the u-testing channel during european times [17:13] low points: MacSlow didn't show up in the end, but eeejay was a great help [17:14] also, people start testing, but there is no way to track their testing a la Litmus [17:14] so, if they don't find any bugs, they cannot show any where that they were there [17:14] ideas? [17:14] ara: attendees page [17:15] ara: what's Litmus? [17:15] I'm planning a meeting next week with Shaun and Nigel to look more at result tracking [17:15] cr3: paper used to test acidity ;) [17:15] cr3: https://litmus.mozilla.org/ [17:15] davmor2: that's with a lower case [17:16] heno: great [17:16] next week topic is beta smoke testing, davmor2? [17:16] in the old days we used wiki pages for this :) [17:16] Yes beta smoke [17:16] heno: could you suggest using Launchpad for this? they already get test results from checkbox, perhaps they could have an interface for either displaying or at very least querying test results [17:17] davmor2, fader: can we have a call tomorrow about Beta ISO testing? [17:17] yes [17:17] heno: Absolutely [17:17] fader: we can tack it on to our existing call [17:17] Sounds good :) [17:18] cool [17:18] 13.00 UTC [17:18] davmor2: I'll send you connection details [17:18] heno: for the call? [17:18] ta [17:18] davmor2: yes, does that work? [17:18] yes that's fine [17:19] cr3: LP is an option but probably not flexible enough [17:20] heno: the advantage of LP is that it could potentially create bugs based on failed test results [17:20] back to ara's question: what should be the testing day week after next? [17:20] could this not be integrated into tracker as it is a regular occurance now [17:20] should we do a server day? [17:20] alternatively audio [17:20] if you see the Calendar, we are running out of topics: https://wiki.ubuntu.com/Testing/UbuntuTestingDay/Calendar [17:21] davmor2: it would require openid integration and all that, possible but not trivial [17:21] heno: server is a good idea [17:21] ara: can you coordinate something with the server team? [17:21] heno: sure, will do [17:22] perhaps we'll all be testing in the cloud for one day :) [17:22] [TOPIC] Bug gravity - bdmurray [17:22] New Topic: Bug gravity - bdmurray [17:22] heno: checkbox-satellite integration with ec2 is something I would like to discuss during uds [17:23] hey there [17:23] satellites go in the clouds anyways, so how appropriate [17:23] heh [17:23] cr3: poet! [17:23] hey stgraber [17:23] Last week I mentioned the bug gravity report and showed some demos of it. I've added the script that generates the report to the ubuntu-qa-tools bzr branch if anyone wants to use it. [17:24] bdmurray: remind us of the link? [17:24] http://people.ubuntu.com/~brian/tmp/gravity/ [17:24] LINK received: http://people.ubuntu.com/~brian/tmp/gravity/ [17:24] (esp those of us who were not here), thanks [17:24] Those are some sample reports, not updated, from last week [17:25] pedro_: did you have a chance to look at any of the desktop ones? [17:25] is the weighting formula simple, would it appear in a legend? [17:26] bdmurray: i did some work with it during the last week, find it pretty useful [17:27] heno: it adds gravity for tags, bug privacy, then duplicates, subscribers and users affected [17:27] heno: I could add in a legend of sorts [17:28] bdmurray: great, good to be transparent about these things :) [17:29] bdmurray: it might be interesting to explore adding the webpage hits stuff to that as a low-level weighting, too. [17:29] is the plan to eventually add gravity to assignment lists? [17:29] (I forget if we covered this) [17:30] We hadn't really covered a use case for it. I think it is helpful when you have a large amount of bugs needing triaging. [17:30] or fixing [17:30] To find out which ones should maybe be triaged first [17:31] bdmurray: what would you like from the group - using the list and give feedback? [17:31] Shouldn't the importance be the gravity when looking at bugs to fix? [17:32] heno: yes, last week I was looking for feedback to see if it would be useful for us to run the report on qa.ubuntu.com for some packages. [17:32] true. gravity can perhaps be a guide in setting importance [17:33] linked from the status pages perhaps? [17:36] Yes, I think we should try a few on qa.u.c [17:36] That seems reasonable and then maybe remove the more than 2 duplicates and other reports [17:36] makes sense [17:36] ok, next [17:37] [TOPIC] Patch testing workflow - bdmurray [17:37] New Topic: Patch testing workflow - bdmurray [17:37] see https://wiki.ubuntu.com/Bugs/PatchTesting [17:37] That looks very useful! [17:38] Based on some community interest I documented how I test patches that are attached to bug reports at https://wiki.ubuntu.com/Bugs/PatchTesting. I wanted it to be approachable so it glosses over a couple of things like building virtual machines and setting up a package build environment. [17:38] I've walked through it a couple of times myself so could use feedback on the process. [17:39] This would be a good developer week session [17:39] bdmurray: great doc! [17:39] or bug/testing day theme even [17:39] bdmurray: if it's okay I'll have a look through it tomorrow and see if I can follow it. I figure if I can anyone can :) [17:40] davmor2: thanks! [17:40] at the very least worth a blog post :) [17:40] [TOPIC] Mozilla landing page - ara [17:40] New Topic: Mozilla landing page - ara [17:41] OK. I am just concern about our landing page [17:41] http://quality.mozilla.org/ [17:41] LINK received: http://quality.mozilla.org/ [17:41] the one at qa.ubuntu.com ? [17:41] if a person is thinking in participate in either mozilla qa or ubuntu qa, their page beat our http://qa.ubuntu.com/ [17:42] pedro_: yes. if you google for "ubuntu qa", that's the first result [17:43] I like the way Mozilla QA landing page starts with a general question "how do you want to get involved?" [17:43] it is very likely that, if you're already part of the qa team, you skip the landing page and go to wherever you need in that moment (reports, testcases, ...) [17:44] but if you're new, and want to get involved, the first thing that you try is qa.ubuntu.com, isn't it? [17:44] ara: https://wiki.ubuntu.com/QATeam/Specs/QAPortal [17:45] stgraber: is it easy to edit that page from the drupal backend (given content)? [17:46] I came in originally from ubuntu.com following the "Get Involved" link. [17:47] heno: is there any plan to push the development of the landing page? [17:49] I suspect we have over-engineered it and should step back and just write a decent landing page by hand [17:49] lot's of good ideas on that spec but we should just get a better page up [17:50] schwuk: you like writing things :) Can you do one based on the mozilla page? [17:51] I'll speak with stgraber tomorrow about posting it [17:51] heno: sure [17:52] (if you write a book you get picked on to write stuff :) ) [17:52] thanks ara for bringing that up [17:52] [TOPIC] Checkbox 0.7 - schwuk [17:52] New Topic: Checkbox 0.7 - schwuk [17:52] heno: it could also be a topic of a summer internship [17:53] ara: the more extended portal, yes [17:53] heno: I guess I deserve that... [17:53] So, Checkbox 0.7 has been released, and uploaded to Jaunty! [17:54] Please prod, poke, test, and use it. [17:54] \o/ [17:54] schwuk, cr3: congrats! [17:54] schwuk: nice! so I can run the supend/resume test using checkbox now right? [17:54] yes, please try the suspend script esp! [17:55] see https://wiki.ubuntu.com/KernelTeam/SuspendResume [17:55] ogasawara: Yes! [17:55] ara: thank you [17:55] ara: thanks, but it doesn't have the new shiny logo yet :) [17:56] cr3: yes, the most important feature, just left out, ouch! [17:56] any other topics? [17:56] I got a question [17:57] all these feature using scripts will they eventually end up in lp itself? [17:57] davmor2: what do you mean by "feature using scripts"? [17:58] davmor2: you mean the greasemonkey scripts? [17:58] Like bdmurray's gravity stuff [17:58] sbeattie: yes [17:58] davmor2: unlikely [17:59] though they may adopt some metrics and lists [18:00] some of the greasemonkey scripts are scheduled to end up in LP [18:00] cool :) [18:01] ok, let's wrap up! [18:01] #endmeeting [18:01] Meeting finished at 13:01. [18:01] thanks all! [18:01] thanks heno [18:01] thanks [18:01] ta [18:01] thanks! [18:01] thanks [18:02] thanks! === fader is now known as fader|lunch === thekorn_ is now known as thekorn === beuno_ is now known as beuno === j_ack_ is now known as j_ack === fader|lunch is now known as fader === plars_ is now known as plars === claydoh_ is now known as claydoh === Tonio__ is now known as Tonio_ === bazhang_ is now known as bazhang === asac_ is now known as asac === pgraner` is now known as pgraner