/srv/irclogs.ubuntu.com/2006/04/01/#ubuntu-meeting.txt

=== Blippe [n=henryson@1-1-11-41a.f.sth.bostream.se] has joined #ubuntu-meeting
=== cassidy [n=cassidy@f1-pc174.ulb.ac.be] has joined #ubuntu-meeting
=== j_ack [n=nico@p508DBAB5.dip0.t-ipconnect.de] has joined #ubuntu-meeting
ToadZzZztool@schedule Europe/Paris01:53
UbugtuSchedule for Europe/Paris: 27 Mar 17:00: Bug Squad | 28 Mar 22:00: Technical Board | 29 Mar 14:00: Edubuntu | 30 Mar 04:00: Dapper Development Status | 30 Mar 14:00: Edubuntu Cookbook | 31 Mar 23:00: Documentation Team01:53
=== Xnos [n=marco@201.123.44.112] has joined #ubuntu-meeting
=== artnay [i=artnay@hideout.unk.fi] has joined #ubuntu-meeting
=== slomo_ [n=slomo@ubuntu/member/slomo] has joined #ubuntu-meeting
bmonty@schedule US/Central03:30
UbugtuSchedule for US/Central: 27 Mar 09:00: Bug Squad | 28 Mar 14:00: Technical Board | 29 Mar 06:00: Edubuntu | 29 Mar 20:00: Dapper Development Status | 30 Mar 06:00: Edubuntu Cookbook | 31 Mar 15:00: Documentation Team03:30
MarioMeyer@topic03:30
MarioMeyer@schedule Brazil/East03:31
UbugtuSchedule for Brazil/East: 27 Mar 12:00: Bug Squad | 28 Mar 17:00: Technical Board | 29 Mar 09:00: Edubuntu | 29 Mar 23:00: Dapper Development Status | 30 Mar 09:00: Edubuntu Cookbook | 31 Mar 18:00: Documentation Team03:31
=== robitaille [n=daniel@ubuntu/member/robitaille] has joined #ubuntu-meeting
=== robitaille [n=daniel@ubuntu/member/robitaille] has joined #ubuntu-meeting
=== Xnos [n=marco@201.123.44.112] has joined #ubuntu-meeting
=== cyphase [n=cyphase@adsl-75-2-137-184.dsl.pltn13.sbcglobal.net] has joined #ubuntu-meeting
=== highvoltage [n=Jono@196.36.161.235] has joined #ubuntu-meeting
=== ogra [n=ogra@ubuntu/member/ogra] has joined #ubuntu-meeting
=== poningru_ [n=poningru@n128-227-55-122.xlate.ufl.edu] has joined #ubuntu-meeting
=== Mithrandir [n=tfheen@c5100BC63.inet.catch.no] has joined #ubuntu-meeting
=== dholbach [n=daniel@ubuntu/member/dholbach] has joined #ubuntu-meeting
dholbachgood morning09:02
JaneWhello09:04
dholbachhey JaneW!09:05
JaneWodd, I am only connected to some of my ubuntu # (the rest are disconnected) ...?09:05
simirathat is strange09:12
simiraand I just read "Ubuntugeek" instead of "bergeek"09:12
highvoltagehi JaneW 09:15
JaneWhello highvoltage 09:15
=== robitaille [n=daniel@ubuntu/member/robitaille] has joined #ubuntu-meeting
robitaille@schedule US/Pacific09:33
UbugtuSchedule for US/Pacific: 27 Mar 07:00: Bug Squad | 28 Mar 12:00: Technical Board | 29 Mar 04:00: Edubuntu | 29 Mar 18:00: Dapper Development Status | 30 Mar 04:00: Edubuntu Cookbook | 31 Mar 13:00: Documentation Team09:33
=== ubijtsa [n=anders@karlsson.force9.co.uk] has joined #ubuntu-meeting
=== doko [n=doko@dslb-088-073-097-034.pools.arcor-ip.net] has joined #ubuntu-meeting
=== mvo [n=egon@p54A64E58.dip.t-dialin.net] has joined #ubuntu-meeting
=== jane_ [n=JaneW@dsl-146-178-247.telkomadsl.co.za] has joined #ubuntu-meeting
=== G0SUB [n=ghoseb@ubuntu/member/g0sub] has joined #ubuntu-meeting
=== Seveas [n=seveas@ubuntu/member/seveas] has joined #ubuntu-meeting
=== simira_ [n=simira@194.24.252.250] has joined #ubuntu-meeting
=== MarioMeyer_ [n=meyer@ubuntu/member/mariomeyer] has joined #ubuntu-meeting
=== slomo [n=slomo@ubuntu/member/slomo] has joined #ubuntu-meeting
=== stgraber [i=steph@xeon.stargate-server.com] has joined #ubuntu-meeting
=== lbm [n=lbm@x1-6-00-13-10-7a-d1-e4.k233.webspeed.dk] has joined #ubuntu-meeting
=== Blippe [n=henryson@1-1-11-41a.f.sth.bostream.se] has joined #ubuntu-meeting
=== wold [n=wold@ev-217-129-81-225.netvisao.pt] has joined #ubuntu-meeting
=== zorba64 [n=zorba64@dsl-210-211-115-140.qld.veridas.net] has joined #ubuntu-meeting
=== zorba64 [n=zorba64@dsl-210-211-115-140.qld.veridas.net] has left #ubuntu-meeting []
=== Hirion [n=hirion@draugr.de] has joined #ubuntu-meeting
=== mvo [n=egon@p54A64E58.dip.t-dialin.net] has joined #ubuntu-meeting
=== licio [n=licio@ubuntu/member/licio] has joined #ubuntu-meeting
=== ian_brasil [n=ppbio@200.238.140.83] has joined #ubuntu-meeting
=== _mvo_ [n=egon@p54A64E58.dip.t-dialin.net] has joined #ubuntu-meeting
=== irvin [n=irvin@ubuntu/member/irvin] has joined #ubuntu-meeting
=== olive [n=olive@o.o6.fr] has joined #ubuntu-meeting
=== jsgotangco [n=jsg@ubuntu/member/jsgotangco] has joined #ubuntu-meeting
=== MiserySalin [n=Miranda@p54808702.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== Lure [n=luka@external-7.hermes.si] has joined #ubuntu-meeting
=== palppp [n=palppp@a707.smalands.lu.se] has joined #ubuntu-meeting
=== tormod [n=tormod@138.131.146.155] has joined #ubuntu-meeting
=== mgalvin [n=mgalvin@ubuntu/member/mgalvin] has joined #ubuntu-meeting
=== irvin [n=irvin@ubuntu/member/irvin] has joined #ubuntu-meeting
=== hunger [n=tobias@p54A61DAD.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== j_ack [n=nico@p508D9EE4.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== doko [n=doko@dslb-088-073-097-034.pools.arcor-ip.net] has joined #ubuntu-meeting
=== G0SUB [n=ghoseb@ubuntu/member/g0sub] has joined #ubuntu-meeting
=== irvin [n=irvin@ubuntu/member/irvin] has joined #ubuntu-meeting
=== seb128 [n=seb128@ubuntu/member/seb128] has joined #ubuntu-meeting
=== ..[topic/#ubuntu-meeting:Ubugtu] : Current meeting: Bug Squad | Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 28 Mar 20:00 UTC: Technical Board | 29 Mar 12:00 UTC: Edubuntu | 30 Mar 02:00 UTC: Dapper Development Status | 30 Mar 12:00 UTC: Edubuntu Cookbook | 31 Mar 21:00 UTC: Documentation Team
=== lakin [n=lakin@dsl-hill-66-18-228-60-cgy.nucleus.com] has joined #ubuntu-meeting
=== seaLne [n=seaLne@194.153.168.77] has joined #ubuntu-meeting
=== philbull [n=philbull@84.13.79.192] has joined #ubuntu-meeting
=== Lure [n=admin@external-7.hermes.si] has joined #ubuntu-meeting
=== kagou [n=kagou@88-136-2-16.adslgp.cegetel.net] has joined #ubuntu-meeting
dholbacheverybody get their snacks/tea/coffee/stuff ready? :-)04:58
fabbioneyeah04:58
lakinclose enough04:58
fabbionei had my 2 chicken sandwich with salad and fresh tomatos...04:58
ograhrm04:58
=== ogra only has coffee
=== ogra goes to look for food
=== _mvo_ has tea
Toadstoolready to go :)04:58
=== Lure has to visit that place... ;-)
jsgotangcoyeah04:59
=== jsgotangco has red bull instead
dholbachOk everybody... here we go!05:00
dholbachThis the first BugSquad meeting - welcome everybody!05:00
MiserySalinhello ;-)05:00
G0SUBhi!05:00
dholbachWhat do you think about doing a very quick round of introducing and saying what we work on wrt bugs?05:00
=== ogra waves his flyflap
jsgotangcodo we have a ribbon cutting ceremony?05:00
kagouhi05:00
fabbionesure05:01
dholbachI'm Daniel Holbach, work mostly on Desktop bugs, some accessibility bugs, some Universe bugs, assorted bugs of packages I maintain and now some Icon bugs as well... and some stuff I probably forgot05:01
=== JBennett [n=chatzill@cpe-66-24-28-210.stny.res.rr.com] has joined #ubuntu-meeting
dholbachjust write into the channel - we don't need an order yet :-)05:01
=== ogra is OliverGrawert having nightmares about unreproducable screensaver bugs
fabbioneI am your X God.. and your bugs are pestering my inbox...05:02
fabbioneeh whops05:02
fabbionei meant05:02
ogra(and i care about all edubuntu related breakage as well)05:02
=== Lure is LukaRenko looking for Kubuntu laptop/wireless stuff bugs...
fabbioneI am Fabio Di Nitto.. one of the X maintainer05:02
fabbionei need help to triage bugs05:02
G0SUBI am Baishampayan Ghose, I usually take a look at random Unconfirmed & Unassigned bugs. Would like to make sure there are zero untriaged bugs especially in MOTU-Science05:03
jsgotangcoI am Jerome Gotangco currently looking at some app specific bugs like Yelp, G-A-I, some desktop love like AbiWord and bluetooth and Daniel thinks its a good idea i subscribe to ubuntu-bugs05:03
=== _mvo_ is Michael Vogt and maintains a bunch of desktop software + has a interesst in CJK bugfixes
ToadstoolI'm Jrmie Corbier, a french newcomer in Ubuntu bug squashing world and I try to do my best to find bugs I can handle or triage05:03
=== cmvo [n=cmvo@62.225.11.174] has joined #ubuntu-meeting
philbullHi, I'm Phil Bull and I'm a community bug triager05:03
lakinI am Lakin Wecker, from Calgary, Alberta and have found that bug-triage is the easiest way for me to give back to Ubuntu, and would love to have easier ways to help others get involved in the same way.05:04
seb128I am Sebastien Bacher and I try to keep Desktop bugs under control :)05:04
=== seaLne is Kenny Duffus and does kubuntu triaging and testing
=== Pygi [n=mario@83-131-246-24.adsl.net.t-com.hr] has joined #ubuntu-meeting
=== slomo is Sebastian Drge and I stressed malone in the last time by bug triaging in all different areas ;)
kagoui'm Patrice Vetsel, a french newcomer too. And i'm too shy so i 'll just do my best on triage 05:04
=== jjesse [n=jjesse@mail.ftpb.com] has joined #ubuntu-meeting
=== fabbione hands the microphone to dholbach
dholbach(for the ones who just joined the channel: we had a quick introduction round... if you want to introduce yourself, just do so...)05:06
=== zakame [n=zak@ubuntu/member/zakame] has joined #ubuntu-meeting
zakamehi all05:06
dholbachI'm quite happy we have a diverse team around and hope we get some good stuff covered today05:06
dholbachwe have our agenda on https://wiki.ubuntu.com/BugSquad/Meeting05:06
=== heno [n=henrik@henrik.gotadsl.co.uk] has joined #ubuntu-meeting
zakameheya dholbach05:06
dholbachmaybe it makes sense to start with the 2nd agenda point, as "getting the team on track" is more general than the next bug day05:07
dholbachrobitaille can't attend today, but he brought some nice interesting facts to illustrate the current situation05:07
dholbachi'll just paste them05:07
dholbach"we seem to be gaining ~100 open bug per week (9500 2 weeks ago, 9600 last week, 9727 tonight). We are fighting a losing battle it seems :)"05:08
dholbach"over 2/3 of these open bugs are "unconfirmed". I think we should be doing better job at this. A lot of these bugs could probably be easily "confirmed"; often it is obvious from the comments that multiple people are seeing these bugs. Confirming a bug is a good way to show an unexperienced bug reporter that his/her bug report is valued. It's a lot better to do this than having a bug report that goes totally unanswered for months if not e05:08
dholbachver. So maybe we should put little bit more effort in confirming new and old bugs."05:08
dholbach"In Debian's area of LP, there are nearly 3000 open bugs. The large majority of these bugs are actually closed from a long time ago; when bugzilla bugs were imported, the ubuntu task kept its bugzilla.u.c status, but if it was linked to debbugs it got an open debian task. These false-open-debian-upstreams bug show up in the list of subscribed bug reports of Ubuntu developpers. It would be nice to clean these up to remove the number of us05:08
dholbacheless bug reports floating around. But it's a very long, boring, and with not a lot of rewards task."05:08
dholbachI think that all of us who have to do with bugs longer than the last days know that robitaille's statements are only accurate.05:09
jsgotangcoive seen a lot of wishlist entries that can be easily addressed though05:09
dholbachCan we think of ideas to make the BugSquad's efforts make all our lifes easier?05:09
dholbachjsgotangco: wishlist entries like what? and addressed how?05:09
fabbionei think we should first divide working areas here05:09
slomoregarding the unconfirmed bugs... i saw many unconfirmed bugs in the past too where there already was some discussion and more people having that problem. it seems people have some kind of fear to set a bug on confirmed :)05:09
G0SUBI second the idea of making the bugsquad the default assignee of all ubuntu bugs without any package05:10
philbullG0SUB: +105:10
fabbioneG0SUB: i disagree.. it doesn't do any good05:10
jsgotangcoit'll also fill up mailboxes heh05:10
dholbachG0SUB: you know that it's *a lot* of traffic and mails you'll get05:10
fabbioneunassigned or tons of bugs assigned to the same teams makes no difference05:10
zakamedoes LP currently provide a grep-like tool for ploughing unconfirmed seemingly-duplicate bugs?05:11
G0SUBwell, how'd we get this done otherwise?05:11
Toadstoolwe should encourage people to search for already existing bugs and confirm them instead of filing another duplicate one05:11
ograwe should divide ubuntu-bugs@ into more sections ...05:11
lakinfabbione: but we can't currently produce a list of bugs which are filed without a package,   I'm not sure of any way to get to them .. so they end up just falling through the cracks for months on end.05:11
dholbachI liked the idea of having a list where new bugs go, which are not assigned to a package.05:11
fabbionelakin: unassigned does not mean without a package. a package entry is mandatory in the bug report05:11
dholbachwith new bugs, I mean only the first mail / first entry05:11
G0SUBdholbach: that's also a plausible idea ... wrt having a list05:12
lakinfabbione: no it's not.05:12
Lurefabbione: many report with ubuntu package05:12
lakinfabbione: and G0SUB was talking about those bugs _without_ a package.05:12
dholbachfabbione: no, there are a hug lot of bugs against 'Ubuntu'05:12
ogradholbach, but asssigned ones or the ones with packages should show up elsewhere 05:12
fabbioneoh craptastic05:12
fabbionebut i consider that as triaging 05:12
dholbachogra: what do you mean?05:12
ogra<dholbach> I liked the idea of having a list where new bugs go, which are not assigned to a package.05:12
fabbionethat's why i was saying we should identify the areas where we want to work05:13
fabbioneand later define the tools we need to accomplish that05:13
Toadstool+105:13
henoI would actually like a 'package' for the WinFOSS stuff if possible, because those get filed right on the distro ATM, but should go to me05:13
dholbachyes, that's a good idea, fabbione05:13
zakameok05:13
fabbioneok let's take turns in talking05:13
jsgotangcowe currently have 4,400+ on unassigned05:13
dholbachheno: you can create an upstream product05:13
fabbioneotherwise it will get too confusing05:13
fabbionedholbach: do you want to lead the discussion?05:13
henodholbach: thanks, will do05:13
dholbachOk... let's get back to the work areas.05:13
dholbachHow can we ensure to make progress there?05:14
fabbionelet's identify them first05:14
fabbioneimho we have 2 areas to work on05:14
fabbionemake that 305:14
G0SUBour main problem is the bunch of UNCO & Unassigned bugs ...05:14
fabbione- new incoming bugs05:14
seaLneunassigned bugs aren't helped by you not being able to assign a bug when you create it05:14
fabbione- bug triaging (UNCO & unassigned)05:14
dholbachlet fabbione speak out05:14
fabbione- old bug junk05:15
fabbionenow...05:15
fabbionethe problem is to get over the back log of bugs05:15
fabbionein the past i would have used a very simple but very effective way to get rid of crap05:15
fabbionelike:05:15
fabbione- decide when it's time to reset the counter05:16
fabbione- mass processing of bugs from whatever status to date X -> Fix Released05:16
fabbione- ask politely the submitters to reopen bugs that are still there05:16
fabbionethis process would "kill" old bugs backlog easily05:17
fabbionebut05:17
fabbionewe can't batch process in malone to do it05:17
=== lakin raises his hand
=== jsgotangco raises hand
fabbioneso we need to find a similar method to do it now05:17
fabbioneonce that's done05:17
fabbionethe team can and should focus on 2 areas only05:17
ograthe mail interface isnt scriptable ?05:17
dholbachlakin, jsgotangco?05:17
fabbionea few people could just look at new bugs05:17
fabbioneand make reassing them to the appropriate package05:18
jsgotangcodo we assume an old bug (say bug ID 3045) is fixed because we uploaded a new version?05:18
zakame+105:18
fabbioneanother few people can look at what's left to see if it is assigned to the proper bugs05:18
fabbionein this way we can clean up a lot of junk05:18
fabbioneand i truely mean a lot05:18
dholbachfabbione: what do you propose? teams for these bug areas regardless of desktop/kernel/x/kubuntu/universe/..05:18
lakinWith the fact that previous releases of Ubuntu are supported for X number of years, how can we close bugs with "fix released" when they still exist in an old release, and it's only been fixed in a new release?05:18
=== vuntz_ [n=vuntz@volin.imag.fr] has joined #ubuntu-meeting
jjesse+1 lakin05:19
seb128yeah, you open a "backport task" if you want a fix backported05:19
seb128you don't keep the "normal task"05:19
Lurelakin: +1, we need to separate bugs to releases - and it should be easy05:19
seb128that's on the right frame05:19
dholbachyes, we should make more use of that.05:19
fabbionedholbach: teams can form later on.. as soon as we get rid of the backlog05:19
ograLure, then we'll never close most of them05:19
fabbionedholbach: it is also natural for a person to look at bugs that are in his area of interest05:19
dholbachfabbione: I think your proposal makes perfect sense for NeedsInfo bugs, which are open and unanswered for say 3-4 weeks05:19
G0SUBfabbione: IMO, we can only close warty bugs like that05:19
fabbioneG0SUB: no, you can close easy hoary and breezy too.05:20
seb128bugs should be closed when fixed with current package, if a fix is worth backporting a backport task should be open05:20
ograseb128, ++05:20
dholbachfabbione: so you propose kind of a "release schedule" for the bug team?05:20
fabbionewhat we really really really care is that if the bug is still present or not in the development release05:20
slomoseb128: ++05:20
=== highvoltage [n=Jono@196.36.161.235] has joined #ubuntu-meeting
fabbionedholbach: sort of.. yes05:20
fabbionefor the stable releases, it is nice to know if the bugs are there05:20
fabbionebut we can rarely fix them05:21
fabbionesince almost none of them are of so high severity impact to require a -update05:21
dholbachseb128: what do you think about fabbione's proposal?05:21
seb128is that basically "let's close all the deprecated bugs now"?05:22
fabbioneogra: scripting the email interface is partially possible, assuming you have passphrase-less gpg key05:22
=== lakin raises his hand again.
G0SUBhow do we know which ones are deprecated?05:22
dholbachlakin: go ahead05:22
fabbioneG0SUB: see above: -set date X05:22
G0SUBokay05:22
fabbioneyou do it arbitrary.. like 3 months ago05:22
fabbioneor something we agree upon05:22
G0SUBfine, I like the idea05:22
seb128usual practice is to close "Needs Infos" bug after some weeks without a reply05:22
slomobut only bugs that had no activity since then, yes?05:23
lakinSure, no one single bug might be serious enough for an update, but for some packages, having 10 of these fixes should qualify as serious enough for an update IMHO.05:23
seb128but we can't close unconfirmed bugs like that05:23
MiserySalinby the way... does someone will write a summary of this decisions? For new members to read it for what to do in this situations05:23
=== Blippe [n=henryson@1-1-11-41a.f.sth.bostream.se] has joined #ubuntu-meeting
dholbachI like seb128's proposal too05:23
dholbachMiserySalin: I step up to do this05:23
MiserySalinah ok... thanks05:23
fabbioneseb128: the problems with your approach are:05:23
G0SUBMiserySalin: a summary will be written05:23
fabbione- the submitter might have provided info, the maintainer didn't check05:23
MiserySalinBecause I will forgot the half :-D05:23
fabbione- most of the bugs are in Uncorfimed state05:24
ogracant we ask the launchpadders for such a feature (closing needinfo bugs automatically after some time05:24
fabbionein this way you apply a "filter" that will help us almost >< this much05:24
ogra)05:24
seb128fabbione: my approach ensure I'm not frustating anybody by closing a bug that it took care to file and than nobody bothered commenting on05:24
Lurefabbione: your proposal is to clean back log only now (once), but then later appliy the rule only to needs info?05:24
vuntz_ogra: would be nice05:24
fabbioneseb128: that is why i underlined to politely ask to reopen if it is still true05:24
seb128fabbione: sure05:25
fabbioneLure: clean the backlog is a one operation only. It does not get repeated05:25
fabbionethe moment in which you clean the backlog, you MUST have the team in place to do the assigned task05:25
Toadstoolfabbione: once the bug is set to Needs Info, if someone adds a commentary the close timer could be reset too...05:25
fabbioneas i mentioned above05:25
Lurefabbione: then we need to ensure that we do not get in similar situation again... 05:25
dholbachI agree with seb128 here. His proposal requires more work, but it ensures that we don't tread on anyone's toes... if we take great care of setting bug statuses, the NeedInfo state should be effective enough for such closing of bugs05:25
seb128fabbione: maybe malone should automatically reopen on new comment so bugs don't stay to Needs Infos (I say that but I hated that when GNOME did it)05:25
dholbachlakin: you wanted to say something05:26
fabbioneseb128: i don't want malone to do anything, because it doesn't even have the basic tools to do what i am proposing05:26
lakinSure, no one single bug might be serious enough for an update for old releases, but for some packages, having 10 of these fixes should qualify as serious enough for an update IMHO.05:26
fabbioneseb128: like masschanging bugs05:26
seb128it has05:26
slomofabbione: you can masschange bugs05:27
fabbionelakin: 10 small fixes don't make one serious05:27
Lureseb128: how?05:27
seb128fabbione: do we have an xmlrpc interface yet?05:27
fabbioneslomo: no last time i checked.. like 2 days ago05:27
fabbioneseb128: no idea...05:27
dholbachOk... can we think of, what might be reasonable for the moment?05:27
slomofabbione: see https://wiki.launchpad.canonical.com/MaloneEmailInterfaceUserDoc#head-7e93c0730c2a71e7f7bccfbf0c3382b6adc962a505:27
seb128fabbione: anyway you can do a script and mail05:27
slomofabbione: but that isn't of much use for us here imho05:27
fabbioneslomo: yes i know the email interface, there are other practical issues :)05:27
lakinnot to mention that there might be local companies that provide support and/or fixes for non-development branches of ubuntu on a per fee basis that might want to track this stuff in launchpad.  I just can't accept that when something is fixed in the development release, that we should ignore it for older releases.05:28
fabbionei discussed this exact problems 2 days ago with SteveA05:28
dholbachlakin: some fixes are not suitable for backporting, like stuff that requires libary updates, or new upstream vresions05:28
seb128we can get launchpad guys making default "lists" matching what we need easily05:28
fabbionelakin: if you have a better proposal, please speak05:28
lakinThat is, until the release reaches the unsupported state.05:28
dholbachlakin: -updates fixes need to be *very precise and focussed*05:28
seb128let's not discuss what is backport material now05:29
ograand well tested05:29
fabbionelakin: otherwise we need to create a team big enough to handle all of it05:29
seb128it's rather maintainer decision anyway05:29
dholbachyes05:29
lakinI'm not suggesting that we start trying to fix it, just that we keep track of where the bug exists in older releases, but we can discuss this later.05:29
dholbachok... which lists and reports would help us much to assign them to the bug squad team?05:29
seb128lakin: open a backport task05:29
lakinseb128: k05:30
dholbach"needsinfo, 3-4 weeks no info" was already mentioned05:30
seb128there is an option to the right frame05:30
dholbachwhat else can we think of?05:30
philbullno replies?05:30
jsgotangcoyes05:30
philbullthese are usually quick to triage05:30
philbull*usually*05:30
lakinlist of bugs which have no package05:30
seb128"no package"? ie: assigned to "Ubuntu"?05:30
dholbachlakin: these are a lot, but I agree, it would make much sense05:31
seb128we already have that05:31
lakinerr, yes, filed against "ubuntu" 05:31
fabbione- let 's assign a person or two to that?05:31
lakinwe do? where?05:31
fabbioneso that we can start having them reassinged to at least the proper team?05:31
Toadstoollakin: with advanced search in malone maybe05:31
seb128lakin: hum, in fact no, but that's just a wishlist for malone05:32
lakinseb128: yeah, I've filed a bug against malone for it.05:32
dholbachif we could set up a mailfilter for a new mailing list that'd be great "bug against Ubuntu, first bug post"05:33
jsgotangcothat would be nice05:33
G0SUBI like the mailing list idea05:33
dholbachi'll ask around, how we could achieve that05:33
seb128lakin: number?05:33
=== tormod [n=tormod@138.131.146.155] has left #ubuntu-meeting ["Ex-Chat"]
dholbachok these two points would be easy for newcomers05:34
dholbachand they surely would clean up malone05:34
dholbachhow do we approach the 6895 unconfirmed bugs?05:34
lakinseb128, 3507505:34
zakameone bug at a time05:35
philbulldholbach: package at a time05:35
G0SUBphilbull: if there is no package?05:35
zakameout of that 6k or so bugs a quarter or a half of those may be dupes05:35
philbullhmmm05:35
dholbachI'm going to announce bug days every two weeks - friday will be the next one... if teams are to propose 'packages to triage' that'll be fine05:35
lakinOne problem with approaching the unconfirmed bugs are that there are quite a few older bugs which have an unconfirmed status, but which have been: assigned properly, commented on by developers, and are even in the midst of being fixed ... we need ubuntu developers to keep up with their bug lists like seb128 does.05:35
jsgotangcocould we like focus on specific packages for some hug days05:36
jsgotangcolike desktop-bugs in 2 weeks05:36
G0SUBjsgotangco: ++05:36
seb128there is an import bug which hurts for that05:36
philbullwhat are the packages with most bugs against them?05:36
seb128all the "UPSTREAM" bugs have been imported as "unconfirmed"05:36
dholbachphilbull: nautilus, evolution05:36
philbullbut do we have an exact list?05:36
G0SUBugh!05:36
dholbach(on the Desktop side)05:37
=== sladen is late. He's also Paul Sladen.
Lurephilbull: would be good to have top list by package05:37
lakinI started to go through them, but felt like I might be stepping on developers toes ... and I admit, all I was doing was confirming them.  What's the approach we should take with them?05:37
philbullb.g.o has this05:37
dholbachhttps://launchpad.net/people/desktop-bugs/+packagebugs05:37
philbullhttp://bugzilla.gnome.org/page.cgi?id=reports.html05:38
dholbachlakin: that's something every bug triager has to live with, you *might* step on somebody's toes, but mostly you learn by it :-)05:38
jsgotangcothe worse thing you'll get is that it gets rejected05:38
lakindholbach: I know, but when you're working through a list of bugs, and _every_ bug makes you feel like you're doing this, it makes it tough to motivate yourself to continue.05:39
seb128lakin: you don't go on anybody else toes if you don't edit the same bug at the same time which is not really likely05:39
=== lakin needs thicker skin, apparently
seb128lakin: best way to not steep on the toes of anybody, pick the bugs older than a week05:39
seb128you can assume you don't "jump" on the bug before the maintainer has a chance to comment so05:40
irvinand asking around #ubuntu-motu and #ubuntu-devel does help05:40
dholbachi like the "by package" approach, if we would send out the BugSquad News (hi vuntz!), we could link to the packages we'Re about to check and which ones we cleaned already05:40
seb128lakin: I've pinged bradb about #35075 he will try to get it fixed for next launchpad update05:40
dholbachand #ubuntu-bugs05:40
=== buga [n=burjang@csomalin.csoma.elte.hu] has joined #ubuntu-meeting
lakinseb128: ++05:41
lakin:)05:41
dholbachso now we have three things which will hopefully make life easier: 1) old-needs-info-cleaning, 2) new-ubuntu-bugs-triaging and 3) by-package-cleanup05:41
jsgotangcoi like the package group approach05:41
dholbachjsgotangco: what do you mean by package group?05:42
jsgotangcolike for a certain time frame do triage on desktop05:42
=== kagou [n=kagou@88-136-30-253.adslgp.cegetel.net] has joined #ubuntu-meeting
jsgotangcothe move to a new set after that05:42
G0SUByeah, that's a good idea IMO05:43
philbulli'm worried that those groups are too big05:43
G0SUBlike we declare that in the next HUG day we take a look at desktop-bugs05:43
slomophilbull: dito... we should use smaller groups of packages...05:43
slomonot something as big as desktop05:43
dholbachjsgotangco: I'm not quite sure that Kubuntu people will have much patience with that... e.g: assign bugs to panel/applets, nautilus/gnomevfs, etc - they most likely won't be able to test bugs proplery05:43
jsgotangcowell evolution alone has tons05:43
G0SUBhehe05:43
dholbachWhat I'm trying to say is that people have areas, where they're good at05:44
dholbachso "triage what you know/work with" might be a good mantra to get started05:44
seb128better if people work on what they are interested05:44
dholbachjsgotangco: does that make sense? or isn't this what you meant?05:44
jsgotangcowell it does make sense to me05:44
jsgotangcoi focus on certain apps05:44
jsgotangcoinstead of tackling the whole Unassigned bit05:45
jsgotangcoit can be overwhelming even for a team05:45
dholbachyeah05:45
jjessei do as well, ij ust try to focus on the little things that i can help with05:45
lakinI think if we get a nice set of reports of bugs that the ubuntu-bug squad is responsible for, and have a way to split these reports up by packages, or sets of packages, it will be easy to get a list that each person feels comfortable working through.05:46
jsgotangcoi just notice that there are active bugs out there with lots of comments but people are afraid to at least change the status to needs info or confirmed05:46
dholbachso if we would start wiki pages with what set we're currently working on, say kubuntu team does kdeedu and kdebase and desktop team does nautilus and gnomevfs for a week and we send a report to the maiing list it'd be great to show we're actually moving something05:46
jsgotangcoeven if there's like 5+ conversations going05:46
jjesseagreed jsgotangco05:46
Lurejsgotangco: +105:47
G0SUBdholbach: +105:47
dholbachI feel that we move step by step and people will accept the idea of bug statuses more and more05:47
dholbachdo you think that with the ideas we had, it's easy enough for newcomers to begin?05:48
zakamedholbach: +105:48
dholbachmaybe some of the new guys in here can speak up and tell us about their experiences05:48
Toadstooldholbach: +105:48
ogradholbach, apart from kdeedu being part of edubuntu +1 as well :)05:48
philbullthe documentation for triaging needs to be more explicit05:48
dholbachwho starts BugSquad/DocumentationTODO on the wiki?05:49
philbullI just did05:50
dholbachso if we had better documentation and tell them: "this week'S bugs are gnome-system-tools, gnome-utils and gthumb" will make it easy for them?05:50
philbulleasier...not easy05:50
dholbach(if they're interested in the Desktop end of bug triage)05:50
G0SUBIt might05:50
seb128should we have a list to discuss bugs on?05:51
philbullthere are things that need to be explained05:51
dholbachWhat else is missing?05:51
dholbachis the coverage on #ubuntu-bugs good enough?05:51
philbullwell, I had real problems deciding who to assign things to05:51
philbull#ubuntu-bugs is good, yeah :)05:51
dholbachoh yes... a "team list" might be useful, with explanations of what they do05:51
seb128the issue is that "they"(== launchpad team) don't want to do default assignee05:52
seb128the workflow is supposed people are subscribed to a bug05:52
ogrameh05:52
dholbachseb128: we just shouldn't name it ...-bugs@, so people start reporting bugs there ;)05:52
seb128and you take the assignment only when you start working on something05:52
dholbachand I think that's a good idea05:53
Toadstoola bigger disclaimer about duplicates on the "report a bug" page and a smarter search engine would also make things a little easier to my mind05:53
dholbachso it's more a matter of subscribing then assigning05:53
dholbachToadstool: the duplicates thing is filed as well05:53
dholbachToadstool: but I agree it's needed05:53
dholbachback to the "team's list"05:53
dholbachfor "Ubuntu" bugs, it makes sense05:54
ograand the search engine is constantly beiong worked on ...05:54
ograit will improve over time05:54
dholbach"this might be an X problem, who do I subscribe to get input?" is a valid question05:54
dholbachok, now we all know that fabbione is the X god, but still... some people might not know yet :)05:54
zakamedholbach: heh I just asked that question some time ago05:55
=== jsgotangco prays to X god to fix those x bugs
=== harisund [n=harisund@ip24-255-87-152.br.br.cox.net] has joined #ubuntu-meeting
fabbionejsgotangco: i am in really urgent need of help triaging bugs05:55
=== harisund [n=harisund@ip24-255-87-152.br.br.cox.net] has left #ubuntu-meeting []
fabbionei just can't get anywork done with 500 bugs of backlog05:55
=== jsgotangco starts looking at xorg
lakinafter some of the recent mailing lists discussions I made this page (https://wiki.ubuntu.com/HelpingBugReporters) which got a bit of traffic.  the comments by AndreasSchildibach and FrancoisDenisGonthier might be appropriate for this meeting?05:55
fabbionejsgotangco: wanna team up for that?05:56
fabbionejsgotangco: i am not asking you to fix.. just to triage05:56
jsgotangcosure05:56
G0SUBfabbione: I am willing05:56
jsgotangcoany particular package?05:56
zakamefabbione: me too05:56
fabbioneok.. if you guys are volunteering.. let's take it after the meeting05:56
G0SUBok05:56
fabbionei will give you hints on how to start05:56
jsgotangcocool05:57
dholbach(I hope everybody signed up for http://launchpad.net/people/bugsquad already)05:57
dholbachwhat about seb128's idea of a bugsquad mailing list?05:57
fabbionedholbach: we are already on 20000 ml05:58
fabbionewe should keep this process slim and fast05:58
jsgotangcolol05:58
fabbionei am not sure YAML will help here05:58
dholbachfabbione: new triagers might not be and some are not on IRC all day05:58
dholbachit's just a question at the moment05:58
ografabbione, dont argue with dholbach about mailing lists ... youre surely loose in the end :P05:58
zakamehaha05:58
Toadstool:)05:58
dholbachogra: pffft05:58
G0SUBYAML? Yet Another Mailing List ? (wasn't it YAML Ain't a Markup Language?)05:58
fabbionedholbach: if we are going to use the ml for discussion i am ok...05:59
ograthats how he always starts ... "<dholbach> it's just a question at the moment"05:59
seb128the issue is to have a place out of IRC where people can ask about whatever is an issue for them05:59
fabbionebut if it will become a duplicate of ubuntu-bugs, it's pointless05:59
ogra:)05:59
seb128like they are not sure of where to assign stuff, or how to start or what to do about a bug05:59
dholbachfabbione: i 100%ly agree05:59
jsgotangcoi'd go for organizational stuff05:59
dholbachi like the idea too05:59
fabbionedholbach: ok05:59
seb128not a list to sends all the bugs we get05:59
ografabbione, ubuntu-bugs is only an auto importer for malone, isnt it ?05:59
fabbioneok.. works for me05:59
kagouseb128: i agree05:59
dholbachcool06:00
ogras/for/from/06:00
dholbachso how do we make the next hug day a blast?06:00
fabbionedholbach: kill all bugs? :D06:00
dholbachapart from filing detailed descriptions of what to work on (on the wiki), improving our documentation?06:00
zakameuhh, finding people who will make the hug day a blast =)06:00
dholbacheverybody of us paints a picture of bugs and we blog it to link to the hug day announce? :-)06:00
kagoufabbione: how ? do you have a black hole ?06:00
fabbionedholbach: ime the major issue is the  "burocracy" behind working on bug.. we need to make the process slim06:00
fabbionekagou: you have one too.. /dev/null06:01
dholbachfabbione: bureaucracy like what?06:01
ogradholbach, using malone06:01
G0SUBheh06:01
fabbionedholbach: like people asking what they should work on, how to do it.. etc.. they should just do in a perfect world :)06:01
lakinIs one of the improved documentation items going to be lists of searches that produce bugs of a certain triage-status along with links to the standard responses to those types of bugs?  (Could help new members feel more comfortable about the first sets of bugs that they triage)?06:01
dholbachogra: if you can't depict the picture a bit clearer, we're unable to discuss it06:01
zakamehmm, speaking of getting slimmer, does the new reportbug work on LP?06:01
dholbachfabbione: right06:01
=== _mvo_ [n=egon@p54A6642A.dip.t-dialin.net] has joined #ubuntu-meeting
dholbachzakame: no06:02
dholbachlakin: that's a brilliant idea06:02
ogradholbach, the malone workflow is horrible compared to bugzilla ... i wont argue about that here, since it will improve ... but its a major slowdown ...06:02
dholbachlakin: we should take that maybe to #ubuntu-bugs later on06:02
lakinok06:02
seb128GNOME guys do a "theme list" for every bug day06:02
seb128like "previous cycle bugs" to triage06:03
ogradholbach, nothing to discuss, just a statement ...06:03
G0SUBogra: it's just a PITA (malone)06:03
seb128or "new unconfirmed"06:03
fabbioneseb128: ++06:03
seb128we could do some theme day06:03
Toadstoolthat's a great idea06:03
seb128"multimedia bugs" day06:03
ograG0SUB, it will improve 06:03
dholbachcool06:03
dholbachapart from that... I was serious about the PR machinery for the next hug day, how do we do it? :-)06:03
slomoseb128: that's a very very very good idea ;)06:03
G0SUBogra: I hope it does ...06:03
fabbionehmmmmm06:03
fabbioneseb128: the idea of theme is good, but we have one issue...06:03
lakinI prefer themes days to asking for certain packages to be done on a specific hug-day.  Everyone works on that theme within the sets of packages they feel comfortable with.06:03
fabbionelet say it's "X hugs day"06:04
fabbioneam I expected to be around 36 hours for coverage?06:04
dholbachwe made it UTC times the last time, so just 24h06:04
fabbionewell06:04
dholbachhttps://wiki.ubuntu.com/UbuntuBugDay/Attending06:05
fabbionei am still not capable of working 24 hours in a raw on X06:05
fabbionegiven i am almost the only one working on it06:05
dholbachwhat do you all think about giving fabio a hand on next hug day?06:05
fabbionedholbach: when is that?06:05
dholbachfriday06:06
fabbione*shrug*06:06
fabbioneok let's talk about time and life06:06
fabbionefirst lesson:06:06
G0SUBlet's make the next one `X HUG Day'06:06
fabbione- there is a life out there... and it's not made of little greeen men 06:06
ograpffft06:06
G0SUBheh06:06
ograthats what yopur *wife* tells you !06:06
fabbioneogra: yes!06:06
fabbioneok...06:07
fabbioneanyway06:07
ogradont belive her !!06:07
fabbionelet's try it on friday06:07
fabbionebut i won't be able to cover more than 10/12 hours06:07
lakinUntil we get a bug-reporter application (like discussed on ubuntu-devel) which can automatically gather various information from the machine before reporting the bug, could we ask the developers to edit a certain wiki pages with default information that is needed for certain packages.  So we can start the process of gathering extra information for the bug-reports?06:07
dholbachlakin: DebuggingProcedures06:07
dholbachbut it needs love for sure06:07
dholbachwe should put it on a big todo list too06:08
lakinok.06:08
dholbachand we should send out detailed minutes of the meeting so everybody knows what we work on/worked on06:08
Toadstoolyeah well I think that's one of the point we should work on, improve WiKi pages about debugging06:08
G0SUBgoody :)06:08
fabbionedholbach: time.. we are at 68 minutes06:08
fabbionedholbach: i suggest a break or to stop06:09
dholbachi want to finish with sladen's questions06:09
fabbioneok06:09
dholbachand take the rest to #ubuntu-bugs06:09
dholbachwhere I hope you all hang out from now on06:09
sladenlakin: we sort-of have the hwdb, but can't get any data back out of that06:09
dholbachsladen had some questions as well, to answer some of them: point 1) what is the problem exactly? point 2) this would mean a bug report on Malone, no? 3) yes, it's a leftover, which will hopefully/perhaps be reactivated06:09
ograsladen, sure you can ... you can download the speciofic dataset and read it in vi ...06:10
dholbachI will try to take care of the mailing list and all other stuff we covered, but I'll need you help for some of them, but let's take that to #ubuntu-bugs06:10
jsgotangcoogra: open up 20GB in vi? :D06:11
ograjsgotangco, one dataset is ~240k06:11
dholbachWe should have a meeting again, after we see how our efforts emerge, but maybe we can discuss this on our fresh mailing list, when we have it.06:11
sladendholbach: We should document somewhere that we don't fix non-security bugs in released versions (and can point users at that page)06:11
ograthe whole db is 5G currently ... (~220000 entries)06:11
sladendholbach: could do with a   Unconfirmed Needs Info   and an   Confirmed Needs Info06:12
dholbachsladen: we should add it to http://wiki.ubuntu.com/Bugs/Responses06:12
dholbachsladen: that should be discussed with the Launchheads, no?06:12
ograsladen, the concept will change a bit for the 3/5y supported reelases06:12
sladendholbach: and (3), Debzilla should die and isn't actually related to debbugs06:12
seb128sorry I was away a few min06:12
dholbachsladen: that's not something we as a bugsquad have to decided06:12
dholbachdecide06:12
=== sladen happy. done.
dholbachI want to thank you all for being here and trying to make the best out of the bug situation. I think this was a very productive meeting.06:13
G0SUB:)06:13
dholbachThank you all!06:13
G0SUBcheers!06:13
seb128fabbione: you don't need to be here the whole day, some other people should have enough clue to triage basic xorg stuff (mark duplicates, figure if that's a driver issue, etc)06:13
ogradholbach, thanks for leading us :)06:14
zakamethanks06:14
philbullthanks dholbach :)06:14
Toadstoolthanks dholbach ^^06:14
fabbioneok guys06:14
fabbionefor who would like to help with X triaging06:14
dholbachthanks06:14
fabbionei suggest we take a 5 minutes break06:14
kagouthanks dholbach06:15
seb128thank you dholbach06:15
=== MiserySalin [n=Miranda@p54808702.dip0.t-ipconnect.de] has joined #ubuntu-meeting
fabbioneand i will give some highlights on how to do it on #ubuntu-bugs06:15
fabbionedoes that work?06:15
dholbachfabbione: maybe we can add some stuff to http://wiki.ubuntu.com/DebuggingProcedures06:15
seb128fabbione: feel free to do a wiki page on the topic :)06:15
fabbionedholbach: there should be already a page for that06:15
zakamecoolness!06:16
lakinthanks dholbach06:16
fabbionehttps://wiki.ubuntu.com/DebuggingXAutoconfiguration06:16
fabbionesee06:16
jsgotangcook06:17
fabbioneok be back in 506:17
zakameoki06:17
=== heno [n=henrik@henrik.gotadsl.co.uk] has left #ubuntu-meeting ["Ex-Chat"]
=== philbull [n=philbull@84.13.79.192] has left #ubuntu-meeting []
=== irvin [n=irvin@ubuntu/member/irvin] has left #ubuntu-meeting ["Leaving"]
=== ..[topic/#ubuntu-meeting:Ubugtu] : Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 28 Mar 20:00 UTC: Technical Board | 29 Mar 12:00 UTC: Edubuntu | 30 Mar 02:00 UTC: Dapper Development Status | 30 Mar 12:00 UTC: Edubuntu Cookbook | 31 Mar 21:00 UTC: Documentation Team | 03 Apr 09:00 UTC: Community Council
=== jjesse [n=jjesse@mail.ftpb.com] has left #ubuntu-meeting ["Konversation]
=== highvoltage [n=Jono@mtngprs7.mtn.co.za] has joined #ubuntu-meeting
=== cmvo [n=cmvo@62.225.11.174] has left #ubuntu-meeting []
=== kagou [n=kagou@88-136-30-253.adslgp.cegetel.net] has left #ubuntu-meeting ["Ex-Chat"]
=== Lure [n=admin@clj46-234.dial-up.arnes.si] has joined #ubuntu-meeting
=== MarioMeyer [n=meyer@ubuntu/member/mariomeyer] has joined #ubuntu-meeting
=== hunger [n=tobias@p54A61A76.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== seaLne [n=seaLne@194.153.168.77] has left #ubuntu-meeting []
=== lucas [n=lucas@d80-170-130-57.cust.tele2.fr] has joined #ubuntu-meeting
=== lakin [n=lakin@dsl-hill-66-18-228-60-cgy.nucleus.com] has joined #ubuntu-meeting
=== highvoltage reads dholbach's mail about finding bugsquad and realises he missed the meeting
=== Lure_ [n=admin@clj46-234.dial-up.arnes.si] has joined #ubuntu-meeting
=== lucas [n=lucas@ubuntu/member/lucas] has joined #ubuntu-meeting
zakamehighvoltage: awww07:38
=== Lure [n=admin@clj46-234.dial-up.arnes.si] has left #ubuntu-meeting ["Konversation]
=== Simira [n=simira@194.24.252.250] has joined #ubuntu-meeting
=== hunger [n=tobias@p54A61A76.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== Nefass [n=Nefass@201-26-116-144.dsl.telesp.net.br] has joined #ubuntu-meeting
=== Nefass [n=Nefass@201-26-116-144.dsl.telesp.net.br] has left #ubuntu-meeting ["Fui]
=== MiserySalin [n=Miranda@p54808702.dip0.t-ipconnect.de] has left #ubuntu-meeting []
=== lucas [n=lucas@d213-103-220-47.cust.tele2.fr] has joined #ubuntu-meeting
=== Klaidas [n=klaidas@unaffiliated/klaidas] has joined #ubuntu-meeting
=== mvo [n=egon@p54A6642A.dip.t-dialin.net] has joined #ubuntu-meeting
=== highvoltage [n=Jono@ubuntu/member/highvoltage] has left #ubuntu-meeting []
=== lbm [n=lbm@x1-6-00-13-10-7a-d1-e4.k233.webspeed.dk] has joined #ubuntu-meeting
=== Blippe [n=henryson@1-1-11-41a.f.sth.bostream.se] has joined #ubuntu-meeting
=== cassidy [n=cassidy@f1-pc174.ulb.ac.be] has joined #ubuntu-meeting
=== Blippe [n=henryson@1-1-11-41a.f.sth.bostream.se] has joined #ubuntu-meeting
=== lamont [n=lamont@mib.fc.hp.com] has joined #ubuntu-meeting
=== lamont [n=lamont@mib.fc.hp.com] has joined #ubuntu-meeting
=== slomo_ [n=slomo@ubuntu/member/slomo] has joined #ubuntu-meeting
=== Hirion [n=hirion@draugr.de] has left #ubuntu-meeting []
=== pbrunier [n=pbrunier@gnu/webmaster/pbrunier] has joined #ubuntu-meeting
=== pbrunier [n=pbrunier@gnu/webmaster/pbrunier] has left #ubuntu-meeting ["Leaving"]
=== Simira [n=simira@tellus.err.no] has joined #ubuntu-meeting
=== lamont [n=lamont@mib.fc.hp.com] has joined #ubuntu-meeting
=== lamont [n=lamont@mib.fc.hp.com] has joined #ubuntu-meeting
=== _xhaker [n=xhaker@213.201.220.218] has joined #ubuntu-meeting
=== raphink|pala [n=raphink@bur91-2-82-231-159-240.fbx.proxad.net] has joined #ubuntu-meeting
=== raphink [n=raphink@ubuntu/member/raphink] has joined #ubuntu-meeting

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!