From brian at ubuntu.com Mon Feb 5 22:24:56 2007 From: brian at ubuntu.com (Brian Murray) Date: Mon, 5 Feb 2007 14:24:56 -0800 Subject: Bug filing video? In-Reply-To: <20070131064740.GA18318@popey.com> References: <45BF369C.1010004@ubuntu.com> <20070131064740.GA18318@popey.com> Message-ID: <20070205222456.GD29703@murraytwins.com> On Wed, Jan 31, 2007 at 06:47:40AM +0000, Alan Pope wrote: > On Tue, Jan 30, 2007 at 01:14:20PM +0100, Henrik Nilsen Omma wrote: > > Hi, > > > > I came across an interesting thought in the ISO testing forum -- > > step-by-step instructions on filing a good bug, perhaps even a video. > > (CCing Alan Pope, our video Guru) > > > > Guru!? Yikes. :) > > Hang on, I'll get my loin cloth. > > > Quote: ... However I am still kinda afraid submitting a new bug. It's > > not that I will say something stupid or submit a duplicate bug (almost > > inevitable, since searching if a bug exists already or is a duplicate > > seems to be more an art than a science if you are new to linux), but > > mainly that I am not sure that the bug is worth posting and that it can > > be confirmed by others. Perhaps a "worked example" of a real bug being > > reported could help. E.g. a real story written by an experienced tester > > who finds a bug and reports it in the proper way, following the howto > > step by step, would be invaluable (a video of the process would be awesome). > > > > An excellent idea. We have a page [0] where you can specify what Screencasts you would like to see made. Once added someone (possibly > you) can add a specification from which a video can be made. > > > [0] https://wiki.ubuntu.com/ScreencastTeam/Requests > I didn't see a request for a bug filing video at that page yet, so I went ahead and created one. I also added some of what I thought would be appropriate material to cover [1]. If any one has any additional thoughts please add them to the spec. Brian [1] https://wiki.ubuntu.com/ScreencastTeam/Requests/LaunchpadBugSubmission -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From daniel.holbach at ubuntu.com Tue Feb 6 18:52:18 2007 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Tue, 06 Feb 2007 19:52:18 +0100 Subject: Bughelper Report 1 Message-ID: <1170787938.8734.31.camel@localhost> Hello everybody, here a quick summary of what happened since we split the bugsquad and bughelper lists (roughly a week). Decisions: * Documentation and bughelper-data commits don't need a review Enhancements: * [Bug 79151] support global clues -- we now support global clues, which means that totem can inherit clues from xine. Use the '-v' option * bughelper reads a config file in ~/.bughelper/config * Alex Muntada contributed manpages for bugxml and bughelper. The package will contain them. * You can 'try' clues before you write them in a clue file. Use '-t ' to do this, use '-T' instead of '-t' to only try the new clue. * [Bug 79157] RFE: support local clue files -- bughelper now respects a second directory, which you can configure in ~/.bughelper/config - you can put additional clue files there. * [Bug 81370] bughelper should show status and importance -- thanks for implementing this Fernado Ribeiro . * [Bug 79142] RFE: Read and write text files with bug numbers -- Andrew Ash contributed a patch that accepts --format=wiki or --format=html to display found bugs in a different format. * Some changes for Martin Pitt, so apport can download attachments from everywhere soon. * Lots of packaging changes, so we can get it into the archive soon. * XML is now quoted every time. * sanitizing changes to the parsed HTML. * [Bug 79148] RFE: Make bughelper case-insensitive by default -- thanks Fernando Ribeiro * clue files are now 'versioned' to indicate breakage (if we should every introduce some). * [Bug 82883] unclear bug.info for bugs with several source packages -- thanks Markus Korn for fixing this. * Respect in clue files and don't list obvious dupes. * --filter out certain bugs. * split into bughelper-data and bughelper. Ways to get involved: * Fix, discuss, report bugs: https://launchpad.net/bughelper/+bugs * Help fix 0.1 items: https://launchpad.net/bughelper/+milestone/0.1 * Write clue files: https://wiki.ubuntu.com/BugHelper/Documentation/WritingClueFiles Statistics: * 66 commits * 23 bugs fixed * 24 clues Join the Bughelper crew today. Have a nice day, Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From andrew.conkling at gmail.com Tue Feb 6 20:30:00 2007 From: andrew.conkling at gmail.com (Andrew Conkling) Date: Tue, 6 Feb 2007 15:30:00 -0500 Subject: Bug filing video? In-Reply-To: <20070205222456.GD29703@murraytwins.com> References: <45BF369C.1010004@ubuntu.com> <20070131064740.GA18318@popey.com> <20070205222456.GD29703@murraytwins.com> Message-ID: <616971f10702061230m14660a49we2774983f2843605@mail.gmail.com> On 2/5/07, Brian Murray wrote: > On Wed, Jan 31, 2007 at 06:47:40AM +0000, Alan Pope wrote: > > [0] https://wiki.ubuntu.com/ScreencastTeam/Requests > > I didn't see a request for a bug filing video at that page yet, so I > went ahead and created one. I also added some of what I thought would > be appropriate material to cover [1]. If any one has any additional > thoughts please add them to the spec. > > [1] https://wiki.ubuntu.com/ScreencastTeam/Requests/LaunchpadBugSubmission I added a few that I thought would be good. I'm a user (of course) and only a beginning triager, so I thought this would be useful: * Reporting a bug upstream * Marking a package as applying to an additional/different package If that's beyond the scope of the screencast, feel free to revert my changes. Cheers, Andrew From brian at ubuntu.com Tue Feb 6 20:42:37 2007 From: brian at ubuntu.com (Brian Murray) Date: Tue, 6 Feb 2007 12:42:37 -0800 Subject: Bug filing video? In-Reply-To: <616971f10702061230m14660a49we2774983f2843605@mail.gmail.com> References: <45BF369C.1010004@ubuntu.com> <20070131064740.GA18318@popey.com> <20070205222456.GD29703@murraytwins.com> <616971f10702061230m14660a49we2774983f2843605@mail.gmail.com> Message-ID: <20070206204237.GC18244@murraytwins.com> On Tue, Feb 06, 2007 at 03:30:00PM -0500, Andrew Conkling wrote: > On 2/5/07, Brian Murray wrote: > >On Wed, Jan 31, 2007 at 06:47:40AM +0000, Alan Pope wrote: > >> [0] https://wiki.ubuntu.com/ScreencastTeam/Requests > > > >I didn't see a request for a bug filing video at that page yet, so I > >went ahead and created one. I also added some of what I thought would > >be appropriate material to cover [1]. If any one has any additional > >thoughts please add them to the spec. > > > >[1] https://wiki.ubuntu.com/ScreencastTeam/Requests/LaunchpadBugSubmission > > I added a few that I thought would be good. I'm a user (of course) and > only a beginning triager, so I thought this would be useful: > * Reporting a bug upstream > * Marking a package as applying to an additional/different package > My intent with the screencast was to have it more for people who are submitting bugs for the first time. This ideally would get us a better quality of bug submitted in the first place. I do think the two ideas you have mentioned might be worthwhile as a screencast but think it should be a separate one. Brian -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From daniel.holbach at ubuntu.com Wed Feb 7 18:45:30 2007 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Wed, 07 Feb 2007 19:45:30 +0100 Subject: Bugs that need forwarding upstream Message-ID: <1170873930.5702.3.camel@localhost> Hello everybody, first of all: thanks to everybody who marked bugs as 'need forwarding upstream'. We now have 282 bugs that need checking and forwarding upstream: http://tinyurl.com/39ya5c The Desktop team alone has 47 bugs marked like that: http://tinyurl.com/32dfzl Let's try to make this a priority for the next days and especially the next HUG DAY (on Feb 14th!). Have a nice day, Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From jjesse at iserv.net Wed Feb 7 19:16:19 2007 From: jjesse at iserv.net (Jonathan Jesse) Date: Wed, 7 Feb 2007 14:16:19 -0500 (EST) Subject: Bugs that need forwarding upstream In-Reply-To: <1170873930.5702.3.camel@localhost> References: <1170873930.5702.3.camel@localhost> Message-ID: <30865.198.105.65.197.1170875779.squirrel@webmail.iserv.net> > Hello everybody, > > first of all: thanks to everybody who marked bugs as 'need forwarding > upstream'. We now have 282 bugs that need checking and forwarding > upstream: http://tinyurl.com/39ya5c > > The Desktop team alone has 47 bugs marked like that: > http://tinyurl.com/32dfzl > > Let's try to make this a priority for the next days and especially the > next HUG DAY (on Feb 14th!). > > Have a nice day, > Daniel > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > A little confused here so maybe some further explanation of the process needs to be explained to me. If indeed the bug is upstream shouldn't it have been filed against an upstream bug tracker which would automagically mark it upstream? Or am I a little confused for some reason? -- Jonathan Jesse From pochu27 at gmail.com Wed Feb 7 19:28:34 2007 From: pochu27 at gmail.com (Emilio Pozuelo Monfort) Date: Wed, 07 Feb 2007 20:28:34 +0100 Subject: Bugs that need forwarding upstream In-Reply-To: <30865.198.105.65.197.1170875779.squirrel@webmail.iserv.net> References: <1170873930.5702.3.camel@localhost> <30865.198.105.65.197.1170875779.squirrel@webmail.iserv.net> Message-ID: <45CA2862.3090709@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jonathan Jesse escribió: > A little confused here so maybe some further explanation of the process > needs to be explained to me. If indeed the bug is upstream shouldn't it > have been filed against an upstream bug tracker which would automagically > mark it upstream? Or am I a little confused for some reason? Hi Jonathan: The bug is in the upstream package, but it is also in the Ubuntu package, so we should report it upstream (not in the upstream package in malone, but in the upstream bug tracker). So we should report that bug upstream, and create a watch report in the Ubuntu bug. Please, correct me if I'm wrong :) Take care Emilio -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFyihhPHB1VjBTaKERAjxGAJ0ValteHwqhVCazDv6pErYRQsAsXgCbBhR2 x88riMsHxGg60r2YisqROQU= =e7rn -----END PGP SIGNATURE----- From daniel.holbach at ubuntu.com Wed Feb 7 19:41:24 2007 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Wed, 07 Feb 2007 20:41:24 +0100 Subject: Bugs that need forwarding upstream In-Reply-To: <30865.198.105.65.197.1170875779.squirrel@webmail.iserv.net> References: <1170873930.5702.3.camel@localhost> <30865.198.105.65.197.1170875779.squirrel@webmail.iserv.net> Message-ID: <1170877284.31224.4.camel@localhost> Hello Jonathan, On Mi, 2007-02-07 at 14:16 -0500, Jonathan Jesse wrote: > A little confused here so maybe some further explanation of the process > needs to be explained to me. If indeed the bug is upstream shouldn't it > have been filed against an upstream bug tracker which would automagically > mark it upstream? Or am I a little confused for some reason? there's no process yet for automatically filing bugs upstream. We need for all our bugs to * identify if indeed it is an upstream bug (this has been done in all of the list). * try to see if the bug has been filed upstream already (if so: add a bug watch for that bug). * file it upstream and add a bug watch Have a nice day, Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From daniel.holbach at ubuntu.com Thu Feb 8 18:28:18 2007 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Thu, 08 Feb 2007 19:28:18 +0100 Subject: bughelper in the archive Message-ID: <1170959298.23397.9.camel@localhost> Hello everybody, started off by Henrik Nilsen Omma and improved by lots of busy contributors, there's a new tool called bughelper in the archive since today. [1] [1] https://wiki.ubuntu.com/BugHelper bughelper is designed to help you with your daily bug work. You can * store information about certain sets of bugs in clue files, which other bug triagers can benefit from * easily search across ranges of bugs (and attachments) Find a short tutorial at [2], a quick guide how to contribute clue files at [3]. You'll almost certainly find somebody to help out with bughelper in #ubuntu-bugs on irc.freenode.net too. [2] https://wiki.ubuntu.com/BugHelper/Tutorial [3] https://wiki.ubuntu.com/BugHelper/Documentation/WritingClueFiles Bughelper development is still ongoing and the version in the archive is not 0.1 yet. If you want to help out with 0.1 goals, find them over here [4]. Find most of the discussions going on at [5]. [4] https://launchpad.net/bughelper/+milestone/0.1 [5] https://lists.ubuntu.com/mailman/listinfo/bughelper If you have ideas, how we could improve bughelper to make it suit your needs, let us know [6]. If you're on feisty, it's easy enough to install it: sudo apt-get install bughelper [6] https://launchpad.net/bughelper/+bugs Hope to see you all contributing to bughelper soon and hopefully bughelper will improve your bug workflow. Have a nice day, Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From towsonu2003 at gmail.com Mon Feb 12 00:32:06 2007 From: towsonu2003 at gmail.com (t u) Date: Sun, 11 Feb 2007 19:32:06 -0500 Subject: Bug descriptions and titles. In-Reply-To: <1171234681.16662.223.camel@localhost.localdomain> References: <1171234681.16662.223.camel@localhost.localdomain> Message-ID: <45CFB586.9070201@gmail.com> Robert Collins wrote: > Just a plea that we update bug descriptions and titles to be relevant - > it saves folk having to dig through the entire thread to get an idea of > whats wrong. For instance: > https://launchpad.net/ubuntu/+source/orbit2/+bug/67361 is a high > priority crasher, and something like 5-6 bugs I filed have been marked > as duplicates of that - but the description of the bug "Gaim crashes > after startup" didn't help with understanding why my bugs where being > closed as duplicates - theres no message when a bug is marked as > duplication, and I dont even use gaim. > > I've fixed the description in this case, but its by no means isolated. > > -Rob > > Just another bit of insight: In that same bug, people seem to keep attaching crash reports, even though no more is needed. I believe that they are doing so not to add more info really but because they are not sure whether their crash is the same as the one described in the bug, so they expect some kind of confirmation: "Yes, your crash report indicates that you're experiencing this bug" or "Your crash report is about something else, please report a new bug" Just so you keep in mind :) Thanks PS. Forwarding to bugsquad so they can keep Robert Collins' plea in mind as well :) From daniel.holbach at ubuntu.com Wed Feb 14 10:57:17 2007 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Wed, 14 Feb 2007 11:57:17 +0100 Subject: Universe bugs and how to get them under control Message-ID: <1171450637.8079.7.camel@bert> Hello everybody, we just had a MOTU meeting and were assembling our TODO list. For those who don't know yet: the MOTUs have lots of volunteers and lots of people joining in, some of them uncertain where to start in Ubuntu's Universe. I'd like us all to make an effort to tag Universe and Multiverse bugs (others maybe too) as: 'packaging' if you think that the bug lies only in the packaging. 'bitesize' if you think that it's suitable for a beginner. If you can think of tags that'd help with that, follow up to the list and let us know. References: * Universe/Multiverse bugs: http://tinyurl.com/2nu8rm * https://wiki.ubuntu.com/MOTU/Bugs Thanks a lot, have a nice day, Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From avoinemt at gmail.com Wed Feb 14 14:59:23 2007 From: avoinemt at gmail.com (Mathieu Avoine) Date: Wed, 14 Feb 2007 09:59:23 -0500 Subject: Bitesize bugs for new developpers? Resources? Message-ID: Hi everyone, Is anyone aware if there are people volunteering to support people who are already programmers but are unfamiliar with Linux and are willing to help? Like the bugs which are marked as "bitesize" could be used as "training" if someone (like a mentor) could help people (like me!) who want to help but don't know where to start. I tried a while ago to start working on projects but the resources are all scattered and I found that generally in the community it's very much a "chacun pour soi" kind of attitude which often deters the efforts of would-be programmers who could eventually bring something bigger to the community... To make a story short, I just stopped trying. I believe there must many people who follow the same path I did, and it's a waste. If there would be a clear, helpful entry point for new developpers, the community would grow bigger, faster. I guess some people may see the breaking point of actually being able to do something as the "acceptance test" but I don't think that helps the cause of open source very much. Thanks for you input Math On 2/14/07, Daniel Holbach wrote: > > Hello everybody, > > we just had a MOTU meeting and were assembling our TODO list. For those > who don't know yet: the MOTUs have lots of volunteers and lots of people > joining in, some of them uncertain where to start in Ubuntu's Universe. > > I'd like us all to make an effort to tag Universe and Multiverse bugs > (others maybe too) as: > > 'packaging' if you think that the bug lies only in the packaging. > 'bitesize' if you think that it's suitable for a beginner. > > If you can think of tags that'd help with that, follow up to the list > and let us know. > > References: > > * Universe/Multiverse bugs: http://tinyurl.com/2nu8rm > * https://wiki.ubuntu.com/MOTU/Bugs > > Thanks a lot, have a nice day, > Daniel > > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jjesse at iserv.net Wed Feb 14 15:39:59 2007 From: jjesse at iserv.net (Jonathan Jesse) Date: Wed, 14 Feb 2007 10:39:59 -0500 (EST) Subject: Bitesize bugs for new developpers? Resources? In-Reply-To: References: Message-ID: <32763.198.105.65.197.1171467599.squirrel@webmail.iserv.net> I think this would be a great idea, I think more "mentors" or "training" would be great. I'm not a developer and I don't even play one on television, but I found that if I just ask people for questions, often times the bug will become closed due to it either working after an update or no response from the initial requestor. I think more people need to see that they don't have to be a developer or even understand packaging to triage bugs. Maybe we need to lower the percieved level for initial bug triagers and then somehow graduate good triagers to a higher level? Isn't that the difference beteween ubuntu-bugs and ubuntu-qa? Maybe that needs to be discussed more widely? > Hi everyone, > > Is anyone aware if there are people volunteering to support people who are > already programmers but are unfamiliar with Linux and are willing to help? > Like the bugs which are marked as "bitesize" could be used as "training" > if > someone (like a mentor) could help people (like me!) who want to help but > don't know where to start. > > I tried a while ago to start working on projects but the resources are all > scattered and I found that generally in the community it's very much a > "chacun pour soi" kind of attitude which often deters the efforts of > would-be programmers who could eventually bring something bigger to the > community... To make a story short, I just stopped trying. I believe there > must many people who follow the same path I did, and it's a waste. If > there > would be a clear, helpful entry point for new developpers, the community > would grow bigger, faster. I guess some people may see the breaking point > of > actually being able to do something as the "acceptance test" but I don't > think that helps the cause of open source very much. > > Thanks for you input > > Math > > On 2/14/07, Daniel Holbach wrote: >> >> Hello everybody, >> >> we just had a MOTU meeting and were assembling our TODO list. For those >> who don't know yet: the MOTUs have lots of volunteers and lots of people >> joining in, some of them uncertain where to start in Ubuntu's Universe. >> >> I'd like us all to make an effort to tag Universe and Multiverse bugs >> (others maybe too) as: >> >> 'packaging' if you think that the bug lies only in the packaging. >> 'bitesize' if you think that it's suitable for a beginner. >> >> If you can think of tags that'd help with that, follow up to the list >> and let us know. >> >> References: >> >> * Universe/Multiverse bugs: http://tinyurl.com/2nu8rm >> * https://wiki.ubuntu.com/MOTU/Bugs >> >> Thanks a lot, have a nice day, >> Daniel >> >> >> -- >> Ubuntu-bugsquad mailing list >> Ubuntu-bugsquad at lists.ubuntu.com >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad >> >> >> > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > -- Jonathan Jesse From carthik at gmail.com Mon Feb 19 22:26:33 2007 From: carthik at gmail.com (Carthik Sharma) Date: Mon, 19 Feb 2007 17:26:33 -0500 Subject: Bug Stats Page Updated to Show Longer Time-Span Message-ID: <80f75db0702191426l73e26ff2h716998816b5ba89d@mail.gmail.com> Hi List, Sorry for being missing from the bugsquashing action. The #1 bug to fix for me right now is my problem with getting out of school. ;) I updated the bugstats graphs at http://people.ubuntu-in.org/~carthik/bugstats/ to reflect bug stats over (upto) a 6-month period. I know, this is "tool" mostly just for kicks, but heck, I did it anyway, since a couple of folks seemed to want this improvement. Regards, Carthik. -- Ph.D. Candidate University of Central Florida Homepage: http://carthik.net From daniel.holbach at ubuntu.com Tue Feb 20 11:12:58 2007 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Tue, 20 Feb 2007 12:12:58 +0100 Subject: Bug Tags Message-ID: <1171969978.30651.1.camel@bert> Hello everybody, we had quite some discussion over tags and their standardisation already, so I just wrote a small wiki document mentioning some we use regularly: https://wiki.ubuntu.com/BugSquad/Tags Please make use of them and point new contributors to them. Have a nice day, Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From daniel.holbach at ubuntu.com Tue Feb 20 16:47:38 2007 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Tue, 20 Feb 2007 17:47:38 +0100 Subject: [Fwd: Re: Bug Tags] Message-ID: <1171990058.29857.3.camel@bert> Hello Math, Yes, 'ubuntulove' can have a bigger scope than 'bitesize'. 'bitesize' is a really easy (maybe low prio) task, where you'll help a new contributor to understand processes and tools better. Have a nice day, Daniel -------------- next part -------------- An embedded message was scrubbed... From: "Mathieu Avoine" Subject: Re: Bug Tags Date: Tue, 20 Feb 2007 11:37:51 -0500 Size: 4408 URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From carthik at gmail.com Tue Feb 20 19:26:39 2007 From: carthik at gmail.com (Carthik Sharma) Date: Tue, 20 Feb 2007 14:26:39 -0500 Subject: Bug Tags In-Reply-To: <1171969978.30651.1.camel@bert> References: <1171969978.30651.1.camel@bert> Message-ID: <80f75db0702201126v10d0b731ie78128faac9cee4f@mail.gmail.com> On 2/20/07, Daniel Holbach wrote: > Hello everybody, > > we had quite some discussion over tags and their standardisation > already, so I just wrote a small wiki document mentioning some we use > regularly: https://wiki.ubuntu.com/BugSquad/Tags Some time ago, on this mailing list, someone proposed the use of a tag to highlight bugs that need forwarding. Can we use the tag "forward" or "upstream" for these? This will hopefully make life easier for member-developers while helping define a task for triagers. "forward" or "upstream" was what came to my mind, this can be improved :) Thank you, Carthik. -- Ph.D. Candidate University of Central Florida Homepage: http://carthik.net From daniel.holbach at ubuntu.com Tue Feb 20 19:50:23 2007 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Tue, 20 Feb 2007 20:50:23 +0100 Subject: Bug Tags In-Reply-To: <80f75db0702201126v10d0b731ie78128faac9cee4f@mail.gmail.com> References: <1171969978.30651.1.camel@bert> <80f75db0702201126v10d0b731ie78128faac9cee4f@mail.gmail.com> Message-ID: <1172001023.5887.5.camel@bert> Hello Carthik, On Di, 2007-02-20 at 14:26 -0500, Carthik Sharma wrote: > Some time ago, on this mailing list, someone proposed the use of a tag > to highlight bugs that need forwarding. Can we use the tag "forward" > or "upstream" for these? This will hopefully make life easier for > member-developers while helping define a task for triagers. > > "forward" or "upstream" was what came to my mind, this can be improved :) if you open an upstream task, but not assign a bug watch, it is marked as "needs forwarding". You can search for those bugs in the "Advanced Search". Have a nice day, Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From seb128 at ubuntu.com Tue Feb 20 21:55:11 2007 From: seb128 at ubuntu.com (Sebastien Bacher) Date: Tue, 20 Feb 2007 22:55:11 +0100 Subject: Call to participation: bugs cleanup on desktop packages for feisty Message-ID: <1172008512.11624.37.camel@seb128-desktop> Hi, The Desktop Team will do a round of cleaning up on desktop packages for feisty. We will start tomorrow with control-center. We will look at the bugs open on the package, clean up the list and note the problems that would be nice to get fixed for feisty. If you have some interest in a package this can be a good occasion to start working on it, the desktop team has lot to do and contributors are welcome to join. We will work from IRC on #ubuntu-desktop (freenode) and #ubuntu-bugs, and a summary of the work done during the day, with a list of the bugs that would be nice to fix for feisty, will be posted to the ubuntu-desktop and ubuntu-bugs lists. You are also welcome to make comments with a reply to that mail. The next cleanup day (and the package picked) will be announced with the summary mail. We are likely to do that several times a week until feisty beta. That's a good opportunity for you to point out problems that you would like to get fixed, to give a hand to make that happen, and to get a really rocking feisty desktop! Cheers, Sebastien Bacher From carthik at gmail.com Tue Feb 20 23:04:13 2007 From: carthik at gmail.com (Carthik Sharma) Date: Tue, 20 Feb 2007 18:04:13 -0500 Subject: Bug Tags In-Reply-To: <1172001023.5887.5.camel@bert> References: <1171969978.30651.1.camel@bert> <80f75db0702201126v10d0b731ie78128faac9cee4f@mail.gmail.com> <1172001023.5887.5.camel@bert> Message-ID: <80f75db0702201504sc0c65e1ve17d7923bbe3e32b@mail.gmail.com> Hi Daniel, On 2/20/07, Daniel Holbach wrote: > Hello Carthik, > > On Di, 2007-02-20 at 14:26 -0500, Carthik Sharma wrote: > > Some time ago, on this mailing list, someone proposed the use of a tag > > to highlight bugs that need forwarding. Can we use the tag "forward" > > or "upstream" for these? This will hopefully make life easier for > > member-developers while helping define a task for triagers. > > > > "forward" or "upstream" was what came to my mind, this can be improved :) > > if you open an upstream task, but not assign a bug watch, it is marked > as "needs forwarding". You can search for those bugs in the "Advanced > Search". Useful info(though I am a little late in learning it). I added this detail at https://wiki.ubuntu.com/Bugs/HowToTriage Thank you for your patient guidance :) Carthik. -- Ph.D. Candidate University of Central Florida Homepage: http://carthik.net From seb128 at ubuntu.com Thu Feb 22 00:34:08 2007 From: seb128 at ubuntu.com (Sebastien Bacher) Date: Thu, 22 Feb 2007 01:34:08 +0100 Subject: summary: control-center package cleanup Message-ID: <1172104448.6029.42.camel@seb128-desktop> Hi, Today was the first desktop packages cleanup day. There was not too much talk on IRC about the package, the list of bugs has got some cleanup action though and most of them are triaged now, thank you to the people who participated today! For people interested by stats on the package: - only 6 bugs are unconfirmed on the package - 22 bugs are "Needs Info" at the moment - 4 bugs should be fixed with the next update - 10 bugs are to forward upstream - no bug is marked to fix for feisty - only 1 bug has Importance >= high and is not marked "Fix Commited" yet One annoying bug pointed is that programs started by a keyboard shortcut don't have their environment set correctly (which creates problems to use the keyring for example), that's due to the fact than gnome-settings-daemon is spawned over dbus, that's an upstream problem: https://launchpad.net/ubuntu/+source/control-center/+bug/62163 There is probably some little bugs that should be easy enough to fix for feisty, your contribution on those is welcome as well so feel free to send patches or ping the desktop team if you want to start working on one Tomorrow we will look at the rhythmbox package. A new version (0.9.8) has just been uploaded today to feisty and that's a good opportunity to verify if bugs have been fixed with the update and not closed yet and to list new or known problems that would be nice to fix for feisty Cheers, Sebastien Bacher From daniel.holbach at ubuntu.com Thu Feb 22 15:27:24 2007 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Thu, 22 Feb 2007 16:27:24 +0100 Subject: Bughelper Report 2 Message-ID: <1172158044.13523.24.camel@bert> Hello everybody, We've been quite busy at fixing bugs the last two weeks and managed to fix all the 0.1 milestone bugs. [1] So now is a good time to test bughelper, improve documentation, and so on - so we can release 0.1. There are also some other bugs open at the moment, so there's enough to get involved with. [1] https://beta.launchpad.net/bughelper/+milestone/0.1 [2] https://beta.launchpad.net/bughelper/+bugs Here a bunch of changes we did since the last report: * improved documentation - manpages, tutorials, etc. * bughelper uploaded to Ubuntu * apport uses bits of bughelper internally * lots of bugfixes to make bughelper more robust and more accurate * treat the use bin="not" in the clue files correctly * add '--upstream' option, that not only considers upstream bugs too * add '--heuristic' option, that will try all clues on bugs that have no source package assigned and bugs whose package has no clue file yet * bugnumbers - option to count quantity of bugs (--stats) * added --status and --importance arguments to bugnumbers Statistics: * 94 commits (+28), * 35 bugs fixed (+12), * 24 clues (+8), * 13 contributors (Henrik Nilsen Omma, Daniel Holbach, Dean Sas, Vassilis Pandis, Brian Murray, Fernando Ribeiro, Luca Falavigna, Colin Watson, Alex Muntada, Markus Korn, Torsten Spindler, Padmanabhan Palanivelu, Michael Vogt) - if I forgot YOU, let me know and I'll add you to the list. :-) Join the Bughelper crew today. Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From seb128 at ubuntu.com Fri Feb 23 01:04:34 2007 From: seb128 at ubuntu.com (Sebastien Bacher) Date: Fri, 23 Feb 2007 02:04:34 +0100 Subject: summary: rhythmbox package cleanup Message-ID: <1172192674.8170.26.camel@seb128-desktop> Hi, The package picked for cleanup today was rhythmbox. Like yesterday IRC was mostly quiet, people did work though and the package looks in a pretty good shape for feisty, the bugs list is under control and no bug has been pointed as "would be nice to fix for feisty" For those who like stats, the package ones at the moment: - only 4 "Unconfirmed" bugs on the package - 11 bugs are "Needs Info" at the moment - 4 bugs are to forward upstream - all the bugs are importance medium, low or wishlist - there is no bug marked to fix for feisty That looks pretty good, upstream is doing a rocking work with bugs we are forwarding and the busquad and desktop team do a nice job to clean the launchpad list of problems and to maintain the package! Tomorrow we will look at gedit and gnome-media. Note than you can work on other things than bug triage, playing with the applications to spot problems that would be nice to fix before feisty for example. Cheers, Sebastien Bacher From matthew.revell at canonical.com Tue Feb 27 12:53:19 2007 From: matthew.revell at canonical.com (Matthew Revell) Date: Tue, 27 Feb 2007 12:53:19 +0000 Subject: Launchpad unavailable 2007-02-28 05:30 - 08:30 UTC Message-ID: <1172580799.6425.38.camel@honey> Hello, We're going to start the process of enabling translations for Feisty, the next version of Ubuntu. This requires some database changes and so we need to take Launchpad offline, between 05:30 and 08:30 UTC on Wednesday 28 February. While Launchpad is offline, we're also going to take the opportunity to make some efficiency improvements, which should lead to fewer timeouts. We're sorry that Launchpad will be offline for a few hours but we're sure you'll be pleased with the performance improvements. If you have any questions or comments, please join us in #launchpad on irc.freenode.net Thanks. -- Matthew Revell - talk to me about Launchpad mrevell in #launchpad, irc.freenode.net From seb128 at ubuntu.com Wed Feb 28 23:47:59 2007 From: seb128 at ubuntu.com (Sebastien Bacher) Date: Thu, 01 Mar 2007 00:47:59 +0100 Subject: desktop cleanup day summary: gedit and gnome-media Message-ID: <1172706480.32124.21.camel@seb128-desktop> Hi, The summary for that desktop clean day (with a delay due to new GNOME which kept the desktop team busy). The gedit and gnome-media bug lists are mostly cleaned now, thank you to everybody who contributed to that. The stats for the packages: * gedit - only 1 "Unconfirmed" bug on the package (which might be fixed on feisty) - 2 bugs are "Needs Info" at the moment - no bug to forward upstream - all the bugs are importance medium, low or wishlist - there is no bug marked to fix for feisty gedit seems to work pretty nicely and there is no bug that has been pointed as to fix for feisty * gnome-media - only 1 "Unconfirmed" bug on the package (which might be fixed on feisty) - 6 bugs are "Needs Info" at the moment - 3 bugs to forward upstream - all the bugs are importance medium, low or wishlist - there is no bug marked to fix for feisty gnome-media looks pretty good as well, no bug has been pointed as to fix for feisty there neither Tomorrow we will work on gnome-utils. The package has not too many bugs at the moment we will triage them first, then look at things that would be nice to fix for feisty and do some valgrind (https://wiki.ubuntu.com/Valgrind) debugging. Cheers, Sebastien Bacher