[13:23] <SiDi> Hello
[13:24] <SiDi> I've got a question for the catalan folks about UDS :)
[13:25] <Hobbsee> they don't have a loco channel?
[13:25] <SiDi> Well, i think they're around
[13:25] <SiDi> That's the channel for the UDS, right ? :O
[13:28] <Hobbsee> er, no?  This is the channel for scheduled ubuntu meetings.
[13:28] <SiDi> Ok, i failed then
[13:28] <SiDi> Sorry :)
[16:00] <robbiew> #startmeeting
[16:00] <MootBot> Meeting started at 10:00. The chair is robbiew.
[16:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:00] <robbiew> hello :)
[16:00] <Extend> hello;)
[16:00] <TheMuso> Greetings folks.
[16:01] <liw> yo
[16:01] <james_w> hi
[16:01]  * slangasek waves
[16:02] <evand> hi
[16:03] <cjwatson> hi
[16:04]  * robbiew is more tired from a flight from Austin to San Francisco, than from Austin to London 
[16:04] <robbiew> :/
[16:04] <robbiew> Going to make this quick, so I can catch my free breakfast :P
[16:04] <james_w> heh
[16:05] <TheMuso> haha
[16:06] <robbiew> [TOPIC] Jaunty
[16:06] <MootBot> New Topic:  Jaunty
[16:06] <robbiew> Anyone have some nasty bugs that I should be aware of?
[16:07] <cjwatson> bug 356518 sort of worries me if only because there's absolutely no indication of what's going wrong
[16:07] <liw> does it count that I can't read e-mail right now?
[16:07] <cjwatson> but you're already aware of that
[16:07] <robbiew> yes...aware of that one
[16:07] <robbiew> :)
[16:08] <robbiew> ok...I'll take silence as goodness....and not folks are just too beat to talk
[16:08] <robbiew> :P
[16:09] <cjwatson> james_w: have you got anywhere with bug 271962, or does it need help?
[16:09] <james_w> yeah, I'm a bit stumped as to where to look, but I haven't spent much time on it
[16:10] <robbiew> james_w: http://qa.ubuntu.com/reports/team-assigned/ubuntu-foundations-assigned-bug-tasks.html
[16:10] <slangasek> 350016 has been milestoned by doko, it looks like the python.m4 in automake could use some love yet (rather than just relying on a horrible hack in python get_python_lib(), ugh)
[16:10] <robbiew> ok
[16:10] <james_w> robbiew: well, I meant where to look in the code, but thanks :-p
[16:10] <robbiew> james_w: heh
[16:10] <robbiew> I know...just joking
[16:11] <robbiew> I posted a couple of youtube videos on our boot performance
[16:11] <robbiew> compared to Windows 7
[16:11] <robbiew> http://www.youtube.com/watch?v=EmVeSbuVB14
[16:11] <MootBot> LINK received:  http://www.youtube.com/watch?v=EmVeSbuVB14
[16:12] <robbiew> http://www.youtube.com/watch?v=ocYhEZlakXQ
[16:12] <MootBot> LINK received:  http://www.youtube.com/watch?v=ocYhEZlakXQ
[16:12] <robbiew> we are neck and neck on my X301
[16:12] <robbiew> but KILL on the eeePC 900 :)
[16:13] <robbiew> about the same on Suspend/Resume on the X301
[16:13] <evand> very cool!
[16:13] <cjwatson> I did a bit of test rebuilding recently using the new LP-native test rebuild feature, but we had to stop it because it turned out to spam buildd admins
[16:13] <cjwatson> infinity is doing one using the old infrastructure now
[16:13] <cjwatson> I filed seven bugs just for packages starting with 'a' from my run, though
[16:14] <robbiew> cjwatson: whoa
[16:14] <cjwatson> mostly universe, though
[16:14] <cjwatson> in fact I think all universe, so no cause for immediate panic
[16:15] <liw> THE UNIVERSE IS BROKEN! WE ARE ALL GOING TO VANISH IN A BIG BANG!
[16:15] <robbiew> BIG BANG = Computer Janitor Gets Overzealous
[16:16] <robbiew> [TOPIC] Karmic
[16:16] <MootBot> New Topic:  Karmic
[16:17] <robbiew> jono on us managers to start getting blueprints ready...so just an fyi
[16:17] <robbiew>  /s/on/is on
[16:17] <cjwatson> blueprints for the top-down items, or also for ideas from the team?
[16:17] <robbiew> I will create the ones for the internal roadmap items, but if you have some...make sure to let me know
[16:18] <robbiew> top-down and ideas :)
[16:18] <robbiew> I think we plan on having the UDS schedule ready by April 27th
[16:19] <slangasek> robbiew: let you know, or push them to the wiki?
[16:19] <robbiew> wiki is cool, as I'm subscribed to it
[16:20] <robbiew> https://wiki.ubuntu.com/FoundationsTeam/UDS/May2009
[16:21] <robbiew> [TOPIC] OEM/Platform Exchange
[16:21] <MootBot> New Topic:  OEM/Platform Exchange
[16:21] <robbiew> So...the Platform team was asked to exchange 3 engineers with the OEM team for 6 months
[16:21] <robbiew> not permanent
[16:22] <robbiew> to help both teams understand better what the other does...and how we work
[16:22] <liw> 6 months is pretty permanent at this pace of development... :)
[16:22] <robbiew> heh
[16:22] <robbiew> doko has graciously accepted the challenge :)
[16:22] <liw> so for clarification, the people who go visit the OEM team would do what?
[16:22] <robbiew> OEM stuff
[16:22] <robbiew> heh
[16:23] <TheMuso> So what happens with the toolchain work doko usually does?
[16:23] <cjwatson> they'll be working as regular members of the OEM team, more or less
[16:23] <robbiew> TheMuso: opportunity for others to step up ;)
[16:23] <cjwatson> likewise, the people transferring to us will be working more or less as regular members of the platform team
[16:23] <robbiew> we still need to work out the details
[16:23] <TheMuso> Ok
[16:23] <robbiew> and I suspect doko will not be 100% gone
[16:23] <robbiew> we would miss him :)
[16:24] <cjwatson> the toolchain is mostly ready for karmic, but:
[16:24] <robbiew> mterry will be coming over to our team...
[16:24] <cjwatson>  * we'll need people to keep an eye on glibc and gcc bugs, and forward them as appropriate (particularly in the case of gcc bugs that may block builds)
[16:24] <cjwatson>  * somebody's going to need to keep OpenJDK ticking over
[16:24] <cjwatson>  * Python 3.1
[16:24] <cjwatson> (and related python issues)
[16:25] <liw> just Python 3.1 and not all Python versions?
[16:25] <cjwatson> Python 3.1 is the bit that will involve most effort, I should think ...
[16:26] <cjwatson> doko can speak for himself on other things that he does, of course, but there is definitely some temporary handover needed; as robbiew says, hopefully we can use this as an opportunity for some cross-training
[16:26]  * liw would love to learn Python ;-)
[16:27] <liw> (otoh, I'd even more love to write stuff in Python, but hey...)
[16:27]  * robbiew puts liw down for python
[16:27] <robbiew> :P
[16:28] <liw> hm, doko is also the Python maintainer in Debian
[16:28] <cjwatson> doko mentioned to me that he was likely to continue doing some things in his spare time where he's the Debian maintainer
[16:28] <robbiew> right
[16:28] <robbiew> there are still a lot of details to work out on both sides
[16:28] <cjwatson> I don't think we can fairly expect to rely on him for Ubuntu work; obviously he'd be welcome but it wouldn't be fair to expect it
[16:29] <robbiew> but wanted to let folks know now
[16:29] <robbiew> right
[16:29] <robbiew> We are also getting a "loaner" from the Launchpad team :)
[16:30] <robbiew> Muharem will be doing a short tour of the Foundations Tea
[16:30] <robbiew> Team
[16:30] <robbiew> (we don't have to send anyone back)
[16:30] <robbiew> cjwatson: how long?  I've forgotten :/
[16:30] <cjwatson> I think the current plan is three months
[16:30] <robbiew> right, thnx
[16:31] <cjwatson> he's one of the Soyuz developers, as many of you will know, and part of the idea is to help them get a better idea of how we work from day to day
[16:31] <cjwatson> we've done some brainstorming, but suggestions for smallish projects tractable by a good Python programmer would be welcome
[16:33] <TheMuso> I'd offer to take the OEL challenge, however there is a fair amount of shifting sands with accessibility in the next 6-12 months, particularly speech wise, which I'd prefer to remain on top of.
[16:33] <TheMuso> OEM even
[16:33] <robbiew> TheMuso: Thanks.  we have our 3 platform team members for this round
[16:34] <robbiew> but I'll keep that in mind for the next one...assuming there is one :P
[16:34] <robbiew> I'd like to setup team mentors for both Mike Terry and Muharem
[16:35] <liw> robbiew, what time zones are they in?
[16:35] <robbiew> I think mvo would be good for Muharem :)
[16:35] <robbiew> liw: Muharem is in Germany (I think) and Mike is in the Eastern US
[16:37] <robbiew> evand would be good for Mike Terry...but he moved to the UK :/
[16:37] <evand> heh
[16:39] <robbiew> though I am a mentor for hugh blemings (Kernel team)...and he's in australia
[16:39] <robbiew> so it can work
[16:39] <robbiew> but I suspect that we need closer timezones than US central and Australia for a technical mentoring relationship :)
[16:40] <robbiew> [TOPIC] AOB/Good News?
[16:40] <MootBot> New Topic:  AOB/Good News?
[16:40]  * evand can still do it if there is no better fit
[16:40] <TheMuso> Yes, meeting times./
[16:40] <robbiew> ah yes
[16:40] <cjwatson> IIRC we only have Steve still in the US
[16:40] <liw> Finland and US/Eastern have a couple of hours of overlapping time for 9-17 work hours, so if no-one else is better suited, I can expose my ignorance of everything and mentor mterry
[16:40] <evand> Debconf?  What are we supposed to do with respect to registration and travel?  Is Maria handling this?
[16:41] <robbiew> evand: yes, randa is handling...through the wiki page
[16:41] <liw> good news: I upgraded my laptop to jaunty and only had to file two bugs; the upgrade itself was pretty smooth (except that we _really_ need to figure out something like ucf into dpkg proper so all pacakges get it)
[16:41] <robbiew> are you listed on it?
[16:41] <evand> yes
[16:41] <robbiew> then your good
[16:41] <evand> ok
[16:41] <slangasek> robbiew: still waiting for a green light to answer the DebConf CfP
[16:42] <liw> robbiew: still waiting for a green light to answer the DebConf CfP
[16:42] <randa> robbiew, Debconf..sorted today... Im registering everyone
[16:42] <robbiew> randa: ^^?
[16:42] <robbiew> randa: is the call for papers issue resolved?
[16:42] <TheMuso> So... Meeting time for me is currently 1 AM, which works for me today due to heading away for the easter weekend, however this is a slightly annoying time for me. If the meeting were either 1 hour earlier, or 2 hours later, I could either stay up if earlier, and work early again if later
[16:42] <randa> robbiew, give me a minute. Busy now, YES everything done.
[16:43] <cjwatson> randa: are we required to submit papers
[16:43] <cjwatson> ?
[16:43] <liw> randa, yay
[16:43] <robbiew> she used CAPS...so I will leave her alone now :)
[16:43] <robbiew> cjwatson: no
[16:43] <randa> robbiew, lol. Just a minute guys
[16:43] <robbiew> randa: no worries...I need to get to the Linux Collaboration Summit in a few anyways
[16:43]  * liw is happy to move meeting time up to 9 hours earlier :-)
[16:43] <slangasek> "resolved" would be that I know it's ok to submit the talk
[16:43] <slangasek> which I still don't :)
[16:44] <robbiew> TheMuso: Ok
[16:45] <robbiew> TheMuso: let me check the Fridge Calendar to see what conflicts (if any) we have...then I'll let folks know which way we move it
[16:45] <slangasek> moving the meeting 9 hours earlier sounds nice to me :)
[16:45] <TheMuso> robbiew: ok thanks
[16:45] <robbiew> I suspect it will be earlier....not 9 hours earlier though
[16:45] <mvo> 9h would be ok for me too, but not much more :)
[16:45] <TheMuso> Earlier is fine, since I'll just stay up for it.
[16:46] <robbiew> ok...gotta run to the Linux Collaboration Summit kickoff (in 15min)
[16:46] <robbiew> #endmeeting
[16:46] <MootBot> Meeting finished at 10:46.
[16:46] <robbiew> thanks@
[16:46] <liw> thanks
[16:46] <slangasek> have fun kicking off :)
[16:46] <evand> thanks
[16:46] <robbiew> heh
[16:47] <james_w> thanks
[16:47] <TheMuso> thanks
[16:48] <mvo> thanks
[18:00] <heno> hey
[18:00] <davmor2> Hello
[18:00] <schwuk> Hi
[18:00]  * ogasawara waves
[18:00] <pedro_> holas!
[18:00] <jtholmes> hello
[18:00] <fader_> Howdy
[18:01] <sbeattie> hey
[18:01] <heno> bdmurray: meeting ping
[18:02] <davmor2> heno: is that different to a normal ping :D
[18:02] <bdmurray> hi
[18:02] <heno> ara is on holiday and I've pinged cr3
[18:02] <heno> ok, we can start!
[18:02] <heno> #startmeeting
[18:02] <MootBot> Meeting started at 12:02. The chair is heno.
[18:02] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[18:03] <heno> [TOPIC] UbuntuBugDay highlights -- pedro
[18:03] <MootBot> New Topic:  UbuntuBugDay highlights -- pedro
[18:03] <pedro_> We celebrated the xorg hug day last Thursday
[18:03] <pedro_> it was pretty good as you can see per https://wiki.ubuntu.com/UbuntuBugDay/20090402
[18:03] <pedro_> and we also got nice comments from the maintainer
[18:04] <pedro_> Big Thanks to paulduf, gsmx, carlos3.14 and cwillu.com for their great work during the event
[18:04] <pedro_> Tomorrow we're going to have a Hug Day based on Bugs with Patches
[18:05] <pedro_> the page and list of bugs is already up https://wiki.ubuntu.com/UbuntuBugDay/20090409
[18:05] <pedro_> and there's already people working on them ;-)
[18:05] <bdmurray> Yeah, I just saw somebody updated a patched bug with a debdiff
[18:05] <pedro_> and i need to inform that i'm not going to be around tomorrow (i'm taking a holiday)
[18:06] <pedro_> so if any of you guys can be around #ubuntu-bugs to help people there would be perfect
[18:06] <bdmurray> I'll be there!
[18:07] <pedro_> I'm sure the documentation that bdmurray set up will help a lot :-)
[18:07] <pedro_> thanks bdmurray
[18:07] <heno> great, thanks pedro_ and bdmurray
[18:07] <heno> [TOPIC] New bug control members! -- bdmurray
[18:07] <MootBot> New Topic:  New bug control members! -- bdmurray
[18:08] <bdmurray> No news this week.
[18:08] <heno> ok
[18:08] <heno> [TOPIC] Next Testing day topic & highlights from last UTD -- heno
[18:08] <MootBot> New Topic:  Next Testing day topic & highlights from last UTD -- heno
[18:08] <davmor2> Didn't really happen I was too busy an ara is on hols
[18:09] <heno> We sort of botched this one in Ara's absence :(
[18:09] <davmor2> next week will be smoke testing
[18:09] <heno> We didn't send out an announcement the week before
[18:09] <davmor2> heno: I thought there was one on the friday
[18:10] <heno> right, next week it starts getting serious with RC smoke testing
[18:10] <heno> davmor2: on the blog?
[18:10] <davmor2> heno: pass I might of been dreaming
[18:11] <heno> I don't see one
[18:11] <davmor2> heno: me then :)
[18:11] <heno> we should start smoke testing ISOs tomorrow/Friday really
[18:12] <heno> I know davmor2 has already started
[18:12] <jtholmes> what do you mean smoke testing
[18:12] <heno> sbeattie: are you running some upgrade testing?
[18:12] <davmor2> jtholmes: general testing
[18:13] <davmor2> heno: oh did they get unfrozen
[18:13] <sbeattie> yes, I've been doing some upgrade testing, will do more.
[18:13] <bdmurray> hasn't mvo automated upgrade testing with ec2?
[18:14] <davmor2> heno: mvo froze them on friday I didn't know they had been unfrozen
[18:14] <heno> jtholmes: we do a quick sanity test of as many ISO images as possible to make sure they are generally in good shape for full validation testing next week
[18:15] <jtholmes> heno gotcha
[18:15] <sbeattie> yes, upgrades have been unfrozen, the issue around python-central/python2.6-minimal has been fixed.
[18:15] <sbeattie> davmor2: ^^^
[18:15] <davmor2> sbeattie: cool ta
[18:16]  * sbeattie got hit by it on one machine, so was quite interested in its resolution.
[18:16]  * davmor2 plans upgrades on hw tomorrow then :)
[18:16] <heno> bdmurray: he does some scripted testing but I sleep better when we supplement that with some testing of more real-world over-loaded installs
[18:17] <bdmurray> heno: makes sense, I wonder if we could use his infrastructure / tools though
[18:17] <heno> finally on testing days: the one after next will also be ISO smoke testing
[18:18] <heno> the next two weeks will be continual ISO testing really
[18:18] <heno> fader_: how broad is our automated install coverage now?
[18:18] <davmor2> heno: and lot's of it :D
[18:18] <sbeattie> bdmurray: I'll talk with him about it.
[18:18] <heno> all alternates i386 and amd64 every day? :)
[18:19] <fader_> heno: We're getting the official builds: desktop, server, kubuntu, ubuntu studio, and alternate
[18:19] <fader_> Both i386 and amd64, yes
[18:19] <davmor2> fader_: did cjwatson say whether his fix for lvm worked?
[18:19] <heno> fader_: do we have a way of seeing if there are gaps in that coverage?
[18:19] <fader_> heno: It's still high on my list to get a better report that reflects the breadth of testing we're getting, so we don't have a good way of seeing gaps right now
[18:20] <heno> is the distribution random or pre-determined?
[18:20] <fader_> davmor2: He thinks it did... we should know soon.  I'll be watching it for the next couple of days to see if it happens again.
[18:20] <jtholmes> I have been testing 386 ios's ubuntu and kubuntu every day for the last week and plan to continue
[18:21] <fader_> heno: The distribution happens as CD images are posted, so as soon as a new image is posted it gets put into the queue to be tested
[18:21] <bdmurray> jtholmes: that's great!  How are you reporting any bugs you find?
[18:21] <fader_> So it's semi-deterministic? :)
[18:21] <jtholmes> thru lp
[18:21] <bdmurray> Do you also add then to iso.qa.ubuntu.com?
[18:21] <heno> jtholmes: great! please let us know in #ubuntu-testing if anything turn up broken
[18:21] <cr3> heno: what kind of gaps might you have in mind? like that some flavour is not being tested for an extended period of time?
[18:22] <davmor2> bdmurray: not for smoketests
[18:22] <jtholmes> bdmurray, no I did not know about that will look there though and note any
[18:22] <cr3> heno: one thing we could do is make the builds page on the certification website publicly accessible, it doesn't contain any private data
[18:22] <jtholmes> heno ok will do
[18:22] <heno> fader_: ok, so semi-random we would see failures if the right ISOs get picked
[18:23] <heno> cr3: interesting, let's look at that afterwards
[18:23] <davmor2> fader_: what happens when more than one image is released in a day?
[18:23] <fader_> heno: Right... at the moment we might potentially miss an error in one flavor if another flavor were consistently being tested after it every time
[18:23] <fader_> heno: In practice I think the probability of this is reasonably low, but it's still something I'm aware of
[18:23] <heno> ok
[18:23] <fader_> davmor2: They get queued up and tested one after another
[18:24] <davmor2> fader_: ah okay cool
[18:24] <fader_> davmor2: cr3 has created a very nice system for scheduling the tests and making sure the images are all getting picked up
[18:24] <heno> [TOPIC] UbuntuOpenWeek call for topics! -- jcastro
[18:24] <MootBot> New Topic:  UbuntuOpenWeek call for topics! -- jcastro
[18:25] <cr3> davmor2: I detect every image which appears on cdimage.u.c and releases.u.c which get enqueued for testing
[18:26] <heno> We can certainly do a desktop automation session
[18:26] <heno> we have done some general triage sessions in the past
[18:27] <heno> should we done some where we focus in more detail on a package?
[18:28] <sbeattie> a "writing apport hooks" topic?
[18:28] <bdmurray> sbeattie: that's more appropriate for Developer week I think
[18:28] <heno> How about we announce our intention to do that and ask the community to suggest which packages we should cover triage for?
[18:28] <sbeattie> bdmurray: ah, okay.
[18:28] <pedro_> btw the prep page is at : https://wiki.ubuntu.com/UbuntuOpenWeek/Prep
[18:29] <davmor2> heno: how about checkbox always a fav
[18:29] <heno> ok, jcastro doesn't seem to be here so we'll move on
[18:30] <heno> davmor2: also for dev week I think
[18:30] <heno> [TOPIC] QA team landing page - suggestions and additions -- schwuk
[18:30] <MootBot> New Topic:  QA team landing page - suggestions and additions -- schwuk
[18:30] <heno> http://people.ubuntu.com/~schwuk/homepage/
[18:30] <MootBot> LINK received:  http://people.ubuntu.com/~schwuk/homepage/
[18:30] <schwuk> Fairly self explanatory - this is the start of the new QA landing page
[18:30] <davmor2> nice
[18:31] <fader_> I like it... very nice
[18:31] <pedro_> cool
[18:31] <schwuk> There's some cleanup to be done, and more text added, but is there anything people would lkike to add?
[18:31] <heno> schwuk: where should we collect feedback about missing items etc?
[18:31] <heno> will you set up a wiki page?
[18:31] <pedro_> would be nice to add the upcoming events related to qa? like hug days, testing days, meetings ?
[18:32] <schwuk> heno: yes
[18:32] <sbeattie> pedro_: agreed
[18:32] <heno> pedro_: +1
[18:32] <davmor2> pedro_: +1
[18:32] <heno> we need an easy way for many people to edit that
[18:32] <bdmurray> something like a revision control system
[18:33] <heno> right, a file in restricted access bzr
[18:33] <pedro_> yeah git
[18:33]  * pedro_ runs
[18:33] <bdmurray> heh
[18:33]  * schwuk chases pedro_ with a stick
[18:33] <pedro_> hehe
[18:33]  * davmor2 lends schwuk his hammer it hurts more than a stick
[18:34] <schwuk> The homepage will be moved to a bzr branch soon, but the events could be pulled from anywhere e.g. a QA Team calendar
[18:34] <sbeattie> can we pull the QA only events out of fridge's calendar?
[18:34] <pedro_> we're adding those to the fridge
[18:34] <davmor2> schwuk: is there a qa-calendar?
[18:34] <schwuk> sbeattie: I'm sure we can
[18:35] <heno> schwuk: will you research a suitable solution to that?
[18:35] <schwuk> heno: yes
[18:35] <heno> when should we aim to roll this out properly?
[18:35] <sbeattie> that would be ideal, given how poorly we are at updating the wiki page header.
[18:35] <schwuk> I'm creating a page at https://wiki.ubuntu.com/QATeam/HomePage to track comments etc.
[18:36] <davmor2> heno: after jaunty
[18:36] <heno> it would be good to have it for open week
[18:36] <bdmurray> when is that again?
[18:37] <heno> 27th+
[18:38] <heno> schwuk: shall we milestone the roll-out for the 27th?
[18:38] <schwuk> heno: sure
[18:38] <heno> (it's almost ready now IMO)
[18:38] <heno> thanks
[18:39] <heno> [TOPIC] Bugsquad mentors project -- pedro|heno
[18:39] <MootBot> New Topic:  Bugsquad mentors project -- pedro|heno
[18:39] <heno> We were talking about doing more active mentoring of people starting out with triage
[18:40] <heno> similar to the MOTU program
[18:40] <heno> pedro_: do you have a link to the MOTU one?
[18:40] <pedro_> https://wiki.ubuntu.com/MOTU/Mentoring
[18:40] <heno> where a new triager would have a contact point
[18:41] <heno> this would also encourage specialisation
[18:41] <heno> developers and bug control folks should be encouraged to mentor
[18:42] <heno> any volunteer mentors in this meeting? (and is this a good idea?)
[18:42] <pedro_> right now we have only a list of people to contact if you need help with something https://wiki.ubuntu.com/BugSquad/Contacts
[18:42] <pedro_> but not a lot of people know about that list and i wonder how many of the people listed there was contacted
[18:44] <bdmurray> I get contacted a lot but I'm not sure its because of that list. ;-)
[18:44] <heno> bdmurray: it's also tricky to identify a speciality for you :)
[18:45] <jtholmes> bdmurray, contact by email or irc or???
[18:45] <heno> there is a student column on the page so we can try to balance out the mentoring load
[18:45] <davmor2> heno: no bdmurray=Bug Dude
[18:46] <cr3> davmor2: so do people misinterpret that as "Dude to bug about bugs"?
[18:46] <bdmurray> e-mail, irc, via launchpad
[18:46] <heno> sbeattie: is regression/sru triage a category in this context?
[18:46] <davmor2> cr3: either way the bugs get fixed :)
[18:47] <sbeattie> heno: sure.
[18:48] <heno> bdmurray: anything you'd care more to mentor than other things? apport-hook issues?
[18:49] <bdmurray> heno: crazy bug queries, consolidating duplicates, writing apport-hooks / package bug guidelines
[18:50] <bdmurray> heno: update-manager / compiz as packages
[18:50] <heno> iow, 'advanced bug management techniques'
[18:50] <heno> ok, cool
[18:50] <heno> that's a good start
[18:52] <heno> I'll update the wiki and email the dev list asking for other topic mentors
[18:52] <heno> Any other business?
[18:52] <jtholmes> yes
[18:53] <jtholmes> the test cases
[18:53] <jtholmes> starting with the accessories section
[18:53] <jtholmes> terminal calculator text editor
[18:53] <jtholmes> the same names should be used in ubuntu and kubuntu test cases
[18:54] <heno> ref: http://testcases.qa.ubuntu.com/Applications
[18:54] <jtholmes> but to do that they have to have a prefix etc. any ideas
[18:54] <davmor2> jtholmes: Right realised what you on about now just name them like this /kubuntu/calculator
[18:54] <jtholmes> or calculatorku  calculatorub  and then both can have  texeditor as page name
[18:54] <Riddell> jumping in.  do the test cases cover checking translations?
[18:55] <davmor2> Riddell: no but good point
[18:55] <jtholmes> davmor2, ok can do
[18:56] <heno> only gets a brief mention in ISO test cases AFAIR
[18:56] <Riddell> davmor2: that's pretty important, especially since we just changed important parts of our translation setup
[18:56] <davmor2> Riddell: I think I did for keyboard and lanuage selection
[18:56] <davmor2> language even
[18:57] <heno> we should probably just have a separate translations test case or plan
[18:57] <heno> fader_: can you work with davmor2 to design one?
[18:58] <davmor2> heno: I can add it to system tests and it can get pulled into various tests from there
[18:58] <fader_> heno: Sure
[18:58] <heno> right and we can then have a plan that pulls in that intro plus various other desktop tests
[18:58] <davmor2> fader_: I'll throw an outline together tomorrow morning for that
[18:58] <heno> thanks fader_ and davmor2
[18:59] <fader_> davmor2: Thanks! :D
[18:59] <heno> AOB?
[18:59] <bdmurray> Yeah, I just learned about a new feature of apport-collect I wanted to share
[18:59] <heno> ok
[19:00] <bdmurray> One can use 'apport-collect -p compiz 1345' to add the compiz package hook information to any bug.
[19:00] <bdmurray> well to bug 1345 ;-)
[19:00] <ogasawara> bdmurray: nice
[19:00] <bdmurray> oops
[19:01] <heno> oh, cool!
[19:01] <bdmurray> Additionally mdz just wrote a hook for alsa-base which will gather information similar to alsa-info.sh
[19:01] <cr3> bdmurray: why not just use alsa-info.sh?
[19:01] <davmor2> nice
[19:02] <bdmurray> So we could ask sound related kernel bugs to run 'apport-collect -p alsa-base 1345'
[19:02] <davmor2> is there a pulse one yet
[19:02] <mdz> cr3: alsa-info.sh uploads a text blob to a pastebin
[19:02] <bdmurray> davmor2: not yet, its on the list
[19:02] <mdz> cr3: the apport hook separates the different info into nice attachments and uploads to launchpad
[19:02] <heno> and it will collect on crashes
[19:02] <cr3> mdz: thanks!
[19:02] <mdz> davmor2: should be very easy to write a basic one now
[19:02] <bdmurray> it's advanatageous to have it LP for scripting with the API too
[19:03] <heno> time's up
[19:03] <bdmurray> it being the alsa info
[19:03] <heno> thanks all!
[19:03] <heno> #endmeeting
[19:03] <MootBot> Meeting finished at 13:03.
[19:03] <davmor2> ta
[19:04] <jcastro> heno: quick question for you
[19:04] <sbeattie> bdmurray: another thing mdz pointed out to me is that the debian scripts in /usr/share/bug/ are a good starting point for writing hooks.
[19:04] <jcastro> heno: (sorry I missed the first part, I was an hour off on my calendar)
[19:04] <cr3> sbeattie: awesome, thanks for sharing that
[19:04] <bdmurray> sbeattie: yeah, that was mentioned when I was talking about the package bug guidelines
[19:04] <jcastro> heno: jono has assigned me to look into helping out the community aspect of triage "perception"
[19:05] <jcastro> heno: he was hoping pedro and I can work together on doing a quick analysis of things and reporting back
[19:05] <jcastro> would that be ok?
[19:06] <bdmurray> jcastro: if you need any numbers let me know
[19:07] <heno> jcastro: sure