From daniel.holbach at ubuntu.com Fri Sep 1 08:41:38 2006 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Fri, 01 Sep 2006 10:41:38 +0200 Subject: Easy Tasks Message-ID: <1157100098.15498.8.camel@localhost> Hellas everybody, as some might have noticed, I added two new lists of bugs to https://wiki.ubuntu.com/DesktopTeam/Bugs * http://tinyurl.com/nm4n3 - is a list of bugs that can be checked for duplicates upstream and probably forwarded. This is an easy task, because bugs marked on this list are likely to contain needed information already. * http://tinyurl.com/rp3xk - is a list of bugs tagged as 'ubuntulove' - these are mostly hacking or packaging tasks that are isolated and where help would be appreciated. I hope the lists will turn out useful, but I have little doubt: after marking the first task 'ubuntulove' yesterday, 5 hours later a patch was attached to it. (Vassilis - you rock!) Have a nice day, Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Dies ist ein digital signierter Nachrichtenteil URL: From gnomefreak at gmail.com Fri Sep 8 20:00:40 2006 From: gnomefreak at gmail.com (John Vivirito) Date: Fri, 08 Sep 2006 16:00:40 -0400 Subject: announcment: ubuntu-desktop-effects team Message-ID: <4501CBE8.8040001@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Launchpad now has the team ubuntu-desktop-effects at : https://launchpad.net/people/ubuntu-desktop-effects the team is set up primarly for xgl, compiz, aiglx bugs. This is an open team everyone is encouraged to join and help make these graphical enhancments the best they can be. - -- GnomeFreak https://wiki.ubuntu.com/JohnVivirito https://launchpad.net/people/gnomefreak http://freewebs.com/ubuntufreak Linux User# 414246 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFAcvnqig4QTwcPCoRAqW3AJ4qbfu1+WUrQp+6i/CnPzIprxOrIACfdsDq dQoswlirhuhZ3n0czMYOzFw= =1rTQ -----END PGP SIGNATURE----- From daniel.holbach at ubuntu.com Mon Sep 11 06:27:25 2006 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Mon, 11 Sep 2006 08:27:25 +0200 Subject: Bug Triage Privileges In-Reply-To: <200609102230.21375.grasshopper@linuxkungfu.org> References: <200609102230.21375.grasshopper@linuxkungfu.org> Message-ID: <1157956045.4804.11.camel@lovegood> Hello Rocco, Am Sonntag, den 10.09.2006, 22:30 -0500 schrieb Rocco Stanzione: > When I say "triage" I refer to setting the importance of a bug, which I was > sure until recently was the same thing. To triage is much more than that. Triaging a bug is * making sure all information is available (version number, debug backtrace, test case to reproduce, ...) * make sure it's no duplicate * the right people subscribed to it * it's maybe forwarded upstream * ... > Still more wiki pages and docs > explain how to triage correctly, but none (that I could find) indicate how to > get those privileges. This should indeed be documented. > When I found out that it was restricted to -qa > (and -dev and -core-dev), I inquired about getting membership in -qa and was > told that it was a very elite group. I'm not sure who told you that, but it's not true. For this group we make sure that team members are known as Bug Triagers already and know what they do. Simon Law and I are Administrators of that team - although he set it up and I leave the task mostly to him and look after the 'bugsquad' team myself. It's useful to set a bug importance, sure - but my observation is that it takes a while until people stop seeing their bug as critical - which is not really useful. If we can improve the process, I'm all ears to how to do so. Have a nice day, Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Dies ist ein digital signierter Nachrichtenteil URL: From daniel.holbach at ubuntu.com Mon Sep 11 10:55:08 2006 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Mon, 11 Sep 2006 12:55:08 +0200 Subject: Telepathy team Message-ID: <1157972108.26243.7.camel@localhost> Hi everybody, you might have heard of a funky, new and shiny technology called telepathy [1]. Today I founded the team [2] to integrate telepathy's efforts into Ubuntu. We're going to * integrate Upstream's efforts into Ubuntu [3] * work on bugs [4] * test Telepathy * cheerlead and make everybody happy with it. [1] http://telepathy.freedesktop.org/ [2] https://launchpad.net/people/telepathy [3] http://wiki.ubuntu.com/Telepathy/TODO [4] https://launchpad.net/people/telepathy/+packagebugs We need a lot of hands on deck, especially trying to get the best bits and pieces in before UniverseFreeze (Sep. 28). Thanks a lot and see you in the team! Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Dies ist ein digital signierter Nachrichtenteil URL: From grasshopper at linuxkungfu.org Mon Sep 11 13:10:11 2006 From: grasshopper at linuxkungfu.org (Rocco Stanzione) Date: Mon, 11 Sep 2006 08:10:11 -0500 Subject: Bug Triage Privileges In-Reply-To: <1157956045.4804.11.camel@lovegood> References: <200609102230.21375.grasshopper@linuxkungfu.org> <1157956045.4804.11.camel@lovegood> Message-ID: <200609110810.12094.grasshopper@linuxkungfu.org> On Monday 11 September 2006 1:27 am, Daniel Holbach wrote: > > When I say "triage" I refer to setting the importance of a bug, which I > > was sure until recently was the same thing. > > To triage is much more than that. Triaging a bug is > * making sure all information is available (version number, debug > backtrace, test case to reproduce, ...) > * make sure it's no duplicate > * the right people subscribed to it > * it's maybe forwarded upstream > * ... I was likely thrown off by the default "untriaged" importance of bugs. Maybe we could change this to a dash or something to prevent clashing nomenclature, but I'll file this on lp. > > When I found out that it was restricted to -qa > > (and -dev and -core-dev), I inquired about getting membership in -qa and > > was told that it was a very elite group. > > I'm not sure who told you that, but it's not true. For this group we > make sure that team members are known as Bug Triagers already and know > what they do. Simon Law and I are Administrators of that team - > although he set it up and I leave the task mostly to him and look after > the 'bugsquad' team myself. > > It's useful to set a bug importance, sure - but my observation is that > it takes a while until people stop seeing their bug as critical - which > is not really useful. The criteria for ubuntu membership include something like a sustained, significant contribution. This leaves me still convinced that ubuntu members can be trusted with the importance of bugs. > If we can improve the process, I'm all ears to how to do so. I definitely have a suggestion. If the temptation is for people to mark their own bugs as critical, let's narrow the scope of the restriction to that - until whatever criteria are met, users may not set the importance of their *own* bugs. I've mentioned this before, and gotten the reply that sometimes, for some people, it's appropriate and useful for them to do that. But those people are already able to do that. For everyone else, who is already able to do (what I see as) much more destructive things to a bug than set incorrect importance, I think we could get maximum benefit with minimum abuse by allowing them to set the importance of other people's bugs. Thanks, Rocco Stanzione From pandisv at yahoo.co.uk Mon Sep 11 13:51:01 2006 From: pandisv at yahoo.co.uk (Vassilis Pandis) Date: Mon, 11 Sep 2006 14:51:01 +0100 (BST) Subject: Bug Triage Privileges In-Reply-To: <200609110810.12094.grasshopper@linuxkungfu.org> Message-ID: <20060911135101.64461.qmail@web25012.mail.ukl.yahoo.com> > > If we can improve the process, I'm all ears to how to do so. > > I definitely have a suggestion. If the temptation is for people to mark their > own bugs as critical, let's narrow the scope of the restriction to that - > until whatever criteria are met, users may not set the importance of their > *own* bugs. I've mentioned this before, and gotten the reply that sometimes, > for some people, it's appropriate and useful for them to do that. But those > people are already able to do that. For everyone else, who is already able > to do (what I see as) much more destructive things to a bug than set > incorrect importance, I think we could get maximum benefit with minimum abuse > by allowing them to set the importance of other people's bugs. > > Thanks, > > Rocco Stanzione What about allowing users to only reduce the importance of bug reports? (I'm sure this has been already brought up). Allowing users to increase the importance of bugs that they did not find is not an ideal solution: A user that's affected by a bug not filed by them will still be able to increase its importance. ___________________________________________________________ Copy addresses and emails from any email account to Yahoo! Mail - quick, easy and free. http://uk.docs.yahoo.com/trueswitch2.html From dennis at kaarsemaker.net Mon Sep 11 14:42:49 2006 From: dennis at kaarsemaker.net (Dennis Kaarsemaker) Date: Mon, 11 Sep 2006 16:42:49 +0200 Subject: Bug Triage Privileges In-Reply-To: <200609110810.12094.grasshopper@linuxkungfu.org> References: <200609102230.21375.grasshopper@linuxkungfu.org> <1157956045.4804.11.camel@lovegood> <200609110810.12094.grasshopper@linuxkungfu.org> Message-ID: <1157985769.5397.3.camel@mirage> On ma, 2006-09-11 at 08:10 -0500, Rocco Stanzione wrote: > The criteria for ubuntu membership include something like a sustained, > significant contribution. This leaves me still convinced that ubuntu > members can be trusted with the importance of bugs. I don't share that feeling. Bug work is only one of the many ways to contribut to Ubuntu. There are Ubuntu members who hardly ever visit Malone. -- Dennis K. Time is an illusion, lunchtime doubly so. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 191 bytes Desc: This is a digitally signed message part URL: From joelbryan.juliano at gmail.com Mon Sep 11 17:21:32 2006 From: joelbryan.juliano at gmail.com (Joel Bryan Juliano) Date: Tue, 12 Sep 2006 01:21:32 +0800 Subject: Telepathy team In-Reply-To: <1157972108.26243.7.camel@localhost> References: <1157972108.26243.7.camel@localhost> Message-ID: Unified Framework for all forms of real time conversations, including IRC, video and audio calls!, that is so awesome!, can I join to test the framework? On 9/11/06, Daniel Holbach wrote: > > Hi everybody, > > you might have heard of a funky, new and shiny technology called > telepathy [1]. Today I founded the team [2] to integrate telepathy's > efforts into Ubuntu. > > We're going to > * integrate Upstream's efforts into Ubuntu [3] > * work on bugs [4] > * test Telepathy > * cheerlead and make everybody happy with it. > > [1] http://telepathy.freedesktop.org/ > [2] https://launchpad.net/people/telepathy > [3] http://wiki.ubuntu.com/Telepathy/TODO > [4] https://launchpad.net/people/telepathy/+packagebugs > > > We need a lot of hands on deck, especially trying to get the best bits > and pieces in before UniverseFreeze (Sep. 28). > > Thanks a lot and see you in the team! > Daniel > > > > -- > ubuntu-desktop mailing list > ubuntu-desktop at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From carthik at gmail.com Tue Sep 12 00:20:10 2006 From: carthik at gmail.com (Carthik Sharma) Date: Mon, 11 Sep 2006 20:20:10 -0400 Subject: Spot for plots Message-ID: <80f75db0609111720l8e1b58eo90cdab4b3ba1df0f@mail.gmail.com> Hi team, I have been secretly working on plots of the bug activity (# of open bugs etc) at launchpad over a period of time. I need to put this up somewhere. Since it is so hard to find a server with gnuplot installed and since my desktop cannot afford to be always-on, I was wondering if there is a feasible solution to the problem. I'll need to use wget, python and gnuplot, in addition to a server to serve the pages. Its just a few pages, and the plots are not huge (like < 4K each). Could I get some space on people.ubuntu.com? How would I go about requesting/obtaining this? If this isn't possible, any other ideas are welcome. I am an Ubuntu member, if that matters at all. Regards, Carthik. -- Ph.D. Candidate University of Central Florida Homepage: http://carthik.net From sfllaw at ubuntu.com Tue Sep 12 04:54:20 2006 From: sfllaw at ubuntu.com (Simon Law) Date: Tue, 12 Sep 2006 00:54:20 -0400 Subject: UbuntuHugDay: 13 September 2006 Message-ID: <20060912045420.GO7336@law.yi.org> Hello freedom lovers, Once again, I'm pleased to announce the Ubuntu Hug Day. The BugSquad is always looking for new volunteers and we'd love it if you joined us. We'll be meeting in the #ubuntu-bugs IRC channel on irc.freenode.net. When, you ask? All of Wednesday, whereever you are. Just hop on and introduce yourself. https://wiki.ubuntu.com/UbuntuBugDay We'll be concentrating on forwarding bugs from our bug-tracker, Malone, to any upstream projects. This helps everyone by providing good, researched bug reports for upstream projects to look at. And then the new code lands in Ubuntu. https://wiki.ubuntu.com/Bugs/CommonTasks Hope to see you there! Cheers, -- Simon Law http://www.law.yi.org/~sfllaw/ From benakiva at gmail.com Tue Sep 12 13:00:35 2006 From: benakiva at gmail.com (Itzhak Ben-Akiva) Date: Tue, 12 Sep 2006 16:00:35 +0300 Subject: Telepathy team In-Reply-To: References: <1157972108.26243.7.camel@localhost> Message-ID: Hi Daniel, Cool! I'm interested to join the team. How can I contribute to the project? Coding?? cheers, Itzhak On 9/11/06, Joel Bryan Juliano wrote: > Unified Framework for all forms of real time conversations, including IRC, > video and audio calls!, that is so awesome!, can I join to test the > framework? > > > On 9/11/06, Daniel Holbach wrote: > > > Hi everybody, > > you might have heard of a funky, new and shiny technology called > telepathy [1]. Today I founded the team [2] to integrate telepathy's > efforts into Ubuntu. > > We're going to > * integrate Upstream's efforts into Ubuntu [3] > * work on bugs [4] > * test Telepathy > * cheerlead and make everybody happy with it. > > [1] http://telepathy.freedesktop.org/ > [2] https://launchpad.net/people/telepathy > [3] http://wiki.ubuntu.com/Telepathy/TODO > [4] https://launchpad.net/people/telepathy/+packagebugs > > > We need a lot of hands on deck, especially trying to get the best bits > and pieces in before UniverseFreeze (Sep. 28). > > Thanks a lot and see you in the team! > Daniel > > > > -- > ubuntu-desktop mailing list > ubuntu-desktop at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop > > > > > > > -- > ubuntu-devel mailing list > ubuntu-devel at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel > > > From daniel.holbach at ubuntu.com Tue Sep 12 14:42:18 2006 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Tue, 12 Sep 2006 16:42:18 +0200 Subject: Telepathy team In-Reply-To: References: <1157972108.26243.7.camel@localhost> Message-ID: <1158072138.21518.1.camel@localhost> Hello Itzhak, Am Dienstag, den 12.09.2006, 16:00 +0300 schrieb Itzhak Ben-Akiva: > Cool! I'm interested to join the team. How can I contribute to the > project? Coding?? the less you're afraid of the code, the better. At the moment we focus our energy on getting telepathy modules into Ubuntu, getting them tested, play with them and communicate with Upstream. http://wiki.ubuntu.com/Telepathy has some more pointers. Have a nice day, Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Dies ist ein digital signierter Nachrichtenteil URL: From benakiva at gmail.com Tue Sep 12 16:01:27 2006 From: benakiva at gmail.com (Itzhak Ben-Akiva) Date: Tue, 12 Sep 2006 19:01:27 +0300 Subject: Telepathy team In-Reply-To: <1158072138.21518.1.camel@localhost> References: <1157972108.26243.7.camel@localhost> <1158072138.21518.1.camel@localhost> Message-ID: Hi Daniel, So, we're speaking of testing and packaging, right? I'll get my hands on this this evening, i.e., first of all installing telepathy on my notebook and playing around. cheers, Itzhak On 9/12/06, Daniel Holbach wrote: > Hello Itzhak, > > Am Dienstag, den 12.09.2006, 16:00 +0300 schrieb Itzhak Ben-Akiva: > > Cool! I'm interested to join the team. How can I contribute to the > > project? Coding?? > > the less you're afraid of the code, the better. At the moment we focus > our energy on getting telepathy modules into Ubuntu, getting them > tested, play with them and communicate with Upstream. > > http://wiki.ubuntu.com/Telepathy has some more pointers. > > Have a nice day, > Daniel > > > > -- > ubuntu-devel mailing list > ubuntu-devel at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel > > > > From jonzep at gmail.com Tue Sep 12 18:49:21 2006 From: jonzep at gmail.com (Jonathan Zeppettini) Date: Tue, 12 Sep 2006 14:49:21 -0400 Subject: gnome-system-monitor issue... Message-ID: Could someone please confirm this for me. https://launchpad.net/distros/ubuntu/+source/gnome-system-monitor/+bug/60112 Thanks. -- JZ From daniel.holbach at ubuntu.com Thu Sep 14 16:53:06 2006 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Thu, 14 Sep 2006 18:53:06 +0200 Subject: Bug Tags Message-ID: <1158252786.7656.7.camel@localhost> Hello everybody, Sébastien and I chatted a bit about making clever use of tags for the Desktop Bugs. I started http://wiki.ubuntu.com/DesktopTeam/BugTags and hope you can all join into the discussion. Some aims we should agree on in the beginning: * have a small set of tags * make the world a better place with them * agree to use common tags and not our own For the Desktop Bugs Team nautilus and evolution (and their friends) are the biggest and best customers for tags and we probably should always have them in mind. Please join in the discussion - either on the wiki page or on the mailing list, the earlier we change our workflow on those bugs the better. Have a nice day and thanks for your input, Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Dies ist ein digital signierter Nachrichtenteil URL: From carthik at gmail.com Thu Sep 14 18:47:11 2006 From: carthik at gmail.com (Carthik Sharma) Date: Thu, 14 Sep 2006 14:47:11 -0400 Subject: Bug Tags In-Reply-To: <1158252786.7656.7.camel@localhost> References: <1158252786.7656.7.camel@localhost> Message-ID: <80f75db0609141147k3c9a6d22xaf9a6a30b7b0c772@mail.gmail.com> On 9/14/06, Daniel Holbach wrote: > Hello everybody, > > Sébastien and I chatted a bit about making clever use of tags for the > Desktop Bugs. I started http://wiki.ubuntu.com/DesktopTeam/BugTags and > hope you can all join into the discussion. > > Some aims we should agree on in the beginning: > * have a small set of tags > * make the world a better place with them > * agree to use common tags and not our own > > For the Desktop Bugs Team nautilus and evolution (and their friends) are > the biggest and best customers for tags and we probably should always > have them in mind. > > Please join in the discussion - either on the wiki page or on the > mailing list, the earlier we change our workflow on those bugs the > better. Maybe the best way forward would be to add to the wiki page any tags that one creates when triaging bugs. It is difficult to come up with a taxonomy/nomenclature by just thinking about the problem of coming up with unique tags, but when triaging, one can easily see patterns, and come up with tags to identify sub-sets of bugs. As an alternative, one could propose use of a new tag, and get it idiot-proofed on the mailing list before putting it to work. I hope I make sense. Regards, Carthik. > > Have a nice day and thanks for your input, > Daniel > > > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > > > -- Ph.D. Candidate University of Central Florida Homepage: http://carthik.net From seb128 at ubuntu.com Fri Sep 15 17:29:14 2006 From: seb128 at ubuntu.com (Sebastien Bacher) Date: Fri, 15 Sep 2006 19:29:14 +0200 Subject: gnome-system-monitor issue... In-Reply-To: References: Message-ID: <1158341354.29289.26.camel@seb128-desktop> Le mardi 12 septembre 2006 à 14:49 -0400, Jonathan Zeppettini a écrit : > Could someone please confirm this for me. > > https://launchpad.net/distros/ubuntu/+source/gnome-system-monitor/+bug/60112 I've confirmed the bug and forwarded upstream. We get hundreds or bugs a week so it can take some time to get a reply Cheers, Sebastien Bacher From daniel.holbach at ubuntu.com Mon Sep 18 06:12:12 2006 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Mon, 18 Sep 2006 08:12:12 +0200 Subject: Bug Tags In-Reply-To: <80f75db0609141147k3c9a6d22xaf9a6a30b7b0c772@mail.gmail.com> References: <1158252786.7656.7.camel@localhost> <80f75db0609141147k3c9a6d22xaf9a6a30b7b0c772@mail.gmail.com> Message-ID: <1158559932.15951.9.camel@localhost> Hello everybody, Am Donnerstag, den 14.09.2006, 14:47 -0400 schrieb Carthik Sharma: > Maybe the best way forward would be to add to the wiki page any tags > that one creates when triaging bugs. It is difficult to come up with a > taxonomy/nomenclature by just thinking about the problem of coming up > with unique tags, but when triaging, one can easily see patterns, and > come up with tags to identify sub-sets of bugs. > > As an alternative, one could propose use of a new tag, and get it > idiot-proofed on the mailing list before putting it to work. Basically I'm fine with both options - it'd just be nice to have sort of an overview for the team, so we don't start off with 12348945 different tags. :-) Another option is to use the Bug Title to indicate which 'part' of the package it is about. Sébastien already did this for gnome-system-tools, where "[user-admin] ..." is part of the Bug Title now. Have a nice day, Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Dies ist ein digital signierter Nachrichtenteil URL: From seb128 at ubuntu.com Mon Sep 18 08:13:32 2006 From: seb128 at ubuntu.com (Sebastien Bacher) Date: Mon, 18 Sep 2006 10:13:32 +0200 Subject: Bug Tags In-Reply-To: <1158559932.15951.9.camel@localhost> References: <1158252786.7656.7.camel@localhost> <80f75db0609141147k3c9a6d22xaf9a6a30b7b0c772@mail.gmail.com> <1158559932.15951.9.camel@localhost> Message-ID: <1158567212.4824.19.camel@seb128-desktop> Le lundi 18 septembre 2006 à 08:12 +0200, Daniel Holbach a écrit : > > As an alternative, one could propose use of a new tag, and get it > > idiot-proofed on the mailing list before putting it to work. I'm not sure than using the list for reviewing tag would work, there is lot of packages and tags which make sense and we are busy enough without starting discussing every tag. Should we try to limit the use of tags to a determined set? Launchpad is supposed to filter the most used tags for a package anyway. > Basically I'm fine with both options - it'd just be nice to have sort of > an overview for the team, so we don't start off with 12348945 different > tags. :-) Having "12348945 different tags" is not an issue if launchpad filter the top used ones from the "noise". Maybe we should have a common "product rule", somebody suggested something like "product-component" and discuss on the list non-product-specific tags, like "easyfix" or "backtrace_needed" or "to_forward"? Do we need to use a product namespace for tags or do they apply to the context of the package browsed anyway? > Another option is to use the Bug Title to indicate which 'part' of the > package it is about. Sébastien already did this for gnome-system-tools, > where "[user-admin] ..." is part of the Bug Title now. For g-s-t I updated the titles and set tags too Cheers, Sebastien Bacher From daniel.holbach at ubuntu.com Mon Sep 18 13:55:36 2006 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Mon, 18 Sep 2006 15:55:36 +0200 Subject: New pilot-link, gnome-pilot (and conduits) have landed - call for testing Message-ID: <1158587736.14935.6.camel@lovegood> Hello everybody, the Open Source world received a bag full of goodness in the last weeks and good news for PDA owners: a new set of pilot-link (0.12.1), gnome-pilot and gnome-pilot-conduits (both 2.0.14) have landed in Edgy, which should make a lot of models work better now. We'd appreciate it, if you could test an up to date Edgy and either make a note on https://wiki.ubuntu.com/PDATesters/Hardware (be sure to note down the version of the package as well) or file a bug in Launchpad, if things don't work for you. PS: Please don't post your experiences on the mailing list. Thanks a lot for testing, have a nice day, Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Dies ist ein digital signierter Nachrichtenteil URL: From dean at deansas.org Mon Sep 18 12:27:33 2006 From: dean at deansas.org (Dean Sas) Date: Mon, 18 Sep 2006 13:27:33 +0100 Subject: Bug Tags In-Reply-To: <1158567212.4824.19.camel@seb128-desktop> References: <1158252786.7656.7.camel@localhost> <80f75db0609141147k3c9a6d22xaf9a6a30b7b0c772@mail.gmail.com> <1158559932.15951.9.camel@localhost> <1158567212.4824.19.camel@seb128-desktop> Message-ID: <450E90B5.5060709@deansas.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sebastien Bacher wrote: > Le lundi 18 septembre 2006 à 08:12 +0200, Daniel Holbach a écrit : > >>> As an alternative, one could propose use of a new tag, and get it >>> idiot-proofed on the mailing list before putting it to work. > > I'm not sure than using the list for reviewing tag would work, there is > lot of packages and tags which make sense and we are busy enough without > starting discussing every tag. Should we try to limit the use of tags to > a determined set? Launchpad is supposed to filter the most used tags for > a package anyway. I think that a "be bold" policy would be good, if you think a particular tag is useful then just go ahead and start using it, but drop a mail to the relevant lists with the tagname and it's usage so other people can use your idea, there's no need to have a big discussion on each tag. A tag will only get to be most used if there's more than one person using it. A wiki page listing the tags already in use will ensure we don't have people using two differently named tags for the same thing. >> Basically I'm fine with both options - it'd just be nice to have sort of >> an overview for the team, so we don't start off with 12348945 different >> tags. :-) > > Having "12348945 different tags" is not an issue if launchpad filter the > top used ones from the "noise". > > Maybe we should have a common "product rule", somebody suggested > something like "product-component" and discuss on the list > non-product-specific tags, like "easyfix" or "backtrace_needed" or > "to_forward"? Do we need to use a product namespace for tags or do they > apply to the context of the package browsed anyway? We already have the 'ubuntulove' tag, which I imagine would overlap with "easyfix". Also we already have http://tinyurl.com/nm4n3 for bugs which need forwarding, I think the opposite may be useful though - bugs which are ubuntu specific such as those introduced by packaging ("packagebug"?). Dean -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFFDpC0eedO8dcp9nYRAp8PAJ41yW2Y9RcJ8cJmPHr+l61oWfhSYwCffF05 lBzwEOebr5dJMTOIM3vKmQ8= =QHQi -----END PGP SIGNATURE----- From sfllaw at ubuntu.com Mon Sep 25 19:16:38 2006 From: sfllaw at ubuntu.com (Simon Law) Date: Mon, 25 Sep 2006 15:16:38 -0400 Subject: UbuntuBugDay - 27 September 2006 Message-ID: <20060925191638.GZ26946@law.yi.org> Hello Ubuntu Lovers! This Wednesday, we'll be holding another Ubuntu Bug Day. That's right, it's when we all get together to try to help squash bugs. This week, we'll once again be forwarding bugs upstream to their original authors. We'll be meeting on the #ubuntu-bugs IRC channel on irc.freenode.net. Drop by and lend a hand! For more information, please go to https://wiki.ubuntu.com/UbuntuBugDay Cheers, -- Simon Law http://www.law.yi.org/~sfllaw/ From daniel.holbach at ubuntu.com Tue Sep 26 15:01:31 2006 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Tue, 26 Sep 2006 17:01:31 +0200 Subject: Bug Tasks! Message-ID: <1159282891.5479.11.camel@localhost> Hello everybody, I added some more easy bug tasks to: https://wiki.ubuntu.com/DesktopTeam/Bugs * Forwarding bugs upstream - bugs with upstream tasks that have no bugwatch added - that's easy enough to do, it just requires checking, if the bug is filed upstream already. * Ubuntu LOVE tasks - easy hacking tasks * Bugs that haven't been touched in a while - "Recently changed", but sort order reversed * Old NeedsInfo bugs - some might be closed with a nice reply from http://wiki.ubuntu.com/Bugs/Responses I'm sure you can think of other clever tasks, feel free to add them. I'd be happy to see other teams use those as well. Another thing: you as experienced bug squad members, could you please try to push newbies in the right direction (maybe at some of those bugs) tomorrow at the HUG DAY? Thanks a lot, Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Dies ist ein digital signierter Nachrichtenteil URL: From towsonu2003 at gmail.com Wed Sep 27 04:49:10 2006 From: towsonu2003 at gmail.com (t u) Date: Wed, 27 Sep 2006 00:49:10 -0400 Subject: need help triaging a bug Message-ID: <451A02C6.9070303@gmail.com> I'd like to confirm or reject this bug I encountered. fairly old. needs someone who have both openoffice 1.1.3 and the latest openoffice to see if you can reproduce it. very minor bug -> very little effort needed. involves converting file to pdf in both versions... have a look please: https://launchpad.net/distros/ubuntu/+source/openoffice.org/+bug/23573 thanks :) PS. no, I'm not the bug reporter haha -- Please scan all atachments for viruses. Or (though you might like Rodin) you might as well avoid "The Gates of Hell" and use Linux. From carthik at gmail.com Wed Sep 27 05:10:07 2006 From: carthik at gmail.com (Carthik Sharma) Date: Wed, 27 Sep 2006 01:10:07 -0400 Subject: need help triaging a bug In-Reply-To: <451A02C6.9070303@gmail.com> References: <451A02C6.9070303@gmail.com> Message-ID: <80f75db0609262210y322703b4w7586197bfa893571@mail.gmail.com> Hi towsonu, On 9/27/06, t u wrote: > > I'd like to confirm or reject this bug I encountered. fairly old. needs > someone who have both openoffice 1.1.3 and the latest openoffice to see > if you can reproduce it. very minor bug -> very little effort needed. > involves converting file to pdf in both versions... Since installing the old OO.org and all it's dependencies would basically be easiest done by installing Hoary (or using the help of a neighbourhood apt-ninja), I'd just download the example .sxw files that the original reported has linked to and try it out with the Dapper/Edgy version of OO.org . I did, and I find that in example 1, the file size (pdf) is 20.2kB and in example 2, the pdf file is 359.8kB. We can compare these to the values reporterd by the original reporter for the sizes of the files generated with the older version. I beg to differ that exporting to pdf using both versions of OO.org on one computer is not a trivial task ;) have a look please: > https://launchpad.net/distros/ubuntu/+source/openoffice.org/+bug/23573 I can attach and send the files to you seperately if you want, but reproducing them must be simple :) Carthik. thanks :) > > PS. no, I'm not the bug reporter haha > -- > Please scan all atachments for viruses. > Or (though you might like Rodin) you might as well avoid "The Gates of > Hell" and use Linux. > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > -- Ph.D. Candidate University of Central Florida Homepage: http://carthik.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From towsonu2003 at gmail.com Thu Sep 28 03:25:44 2006 From: towsonu2003 at gmail.com (t u) Date: Wed, 27 Sep 2006 23:25:44 -0400 Subject: Proposal: assign people to specific jobs Message-ID: <451B40B8.7040509@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, although I have been doing this for a very little time, I noticed that even some very basic bugs aren't triaged at all. for example, no one assigns X crashes to xorg, or kernel crashes ("computer hanged") to the kernel. do you think it would be a good idea to assign some (6-7) people just to assigning bugs to packages, and some others (5-6) just to try to fix the status of bugs? [others could be "free players".] assigning bugs to packages is important especially because otherwise the package maintainer cannot know about the bug. thanks :) - -- Please scan all atachments for viruses. Or (though you might like Rodin) you might as well avoid "The Gates of Hell" and use Linux. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFFG0C4LM1JzWwJYEYRArCqAJ4h8U9djJsW70eQA79tmvw7mSKVtwCeNyvo wv6oMecvKmZ32xeP8spsHU8= =CiU+ -----END PGP SIGNATURE----- From towsonu2003 at gmail.com Thu Sep 28 09:32:49 2006 From: towsonu2003 at gmail.com (t u) Date: Thu, 28 Sep 2006 05:32:49 -0400 Subject: updating pages Message-ID: <451B96C1.3050406@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, can anyone with more knowledge then I have update the following pages: https://wiki.ubuntu.com/HelpingWithBugs https://wiki.ubuntu.com/Bugs/HowToTriage (referred from above page) https://wiki.ubuntu.com/Bugs/Responses https://wiki.ubuntu.com/SourcePackage https://wiki.ubuntu.com/AdoptingPackages https://wiki.ubuntu.com/BugSquashing (referred from DrinkingFromTheFirehose page we have at HelpingWithBugs) These pages seem to contain some vague / outdated / invalid information. especially the outdated+vague info on BugResponses caused me some trouble: https://launchpad.net/distros/ubuntu/+bug/62468 thanks a lot :) - -- Please scan all attachments for viruses. Or (though you might like Rodin) you might as well avoid "The Gates of Hell" and use Linux. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFFG5bBLM1JzWwJYEYRAsHAAKCg8TX0WmS3OHy5ipQ9/HA2Ht8qZQCeJc5y jgdi0pKgOZF/NlmeXga2QeU= =uYoR -----END PGP SIGNATURE----- From caroline.ford.work at googlemail.com Thu Sep 28 10:01:39 2006 From: caroline.ford.work at googlemail.com (Caroline Ford) Date: Thu, 28 Sep 2006 11:01:39 +0100 Subject: updating pages In-Reply-To: <451B96C1.3050406@gmail.com> References: <451B96C1.3050406@gmail.com> Message-ID: <1159437699.5935.15.camel@localhost> I think the Responses page needs much more work to be usable. I note that no-one seems to be using those stock responses - and this is a good thing as I know I hate it when I get a stock response to technical support emails ;) That page implies that problems with translations are not bugs when they are. The answer given - "fix it yourself!" is not helpful to bug reporters or to translators who would like to know when there are problems.. Don't we also want to know about bugs in Dapper? It is not obsoleted by Edgy. Caroline From pandisv at yahoo.co.uk Thu Sep 28 10:41:13 2006 From: pandisv at yahoo.co.uk (Vassilis Pandis) Date: Thu, 28 Sep 2006 11:41:13 +0100 (BST) Subject: updating pages In-Reply-To: <1159437699.5935.15.camel@localhost> Message-ID: <20060928104113.26131.qmail@web25007.mail.ukl.yahoo.com> --- Caroline Ford wrote: > I think the Responses page needs much more work to be usable. I note > that no-one seems to be using those stock responses - and this is a good > thing as I know I hate it when I get a stock response to technical > support emails ;) I agree that some work should be done. I particularly do not like the "If the bug is not described well" response. A casual user reporting a bug does not want to read an essay on how to report bugs correctly. And even if they do, they will still not include the relevant information since the link is too general. > Don't we also want to know about bugs in Dapper? It is not obsoleted by > Edgy. > >From what I understand, it's usual for bugs specific to dapper (fixed in edgy) to be rejected. On one hand this is fairly reasonable considering the strict policy of -updates but on the other hand, I don't see why _IF_ an update is to be made, a typo in a man page can't be fixed. Of course, this does not apply to non-blockers with non-trivial changes. Vassilis ___________________________________________________________ Copy addresses and emails from any email account to Yahoo! Mail - quick, easy and free. http://uk.docs.yahoo.com/trueswitch2.html From daniel.holbach at ubuntu.com Thu Sep 28 12:28:09 2006 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Thu, 28 Sep 2006 14:28:09 +0200 Subject: Proposal: assign people to specific jobs In-Reply-To: <451B40B8.7040509@gmail.com> References: <451B40B8.7040509@gmail.com> Message-ID: <1159446489.16721.5.camel@localhost> Hello, Am Mittwoch, den 27.09.2006, 23:25 -0400 schrieb t u: > do you think it would be a good idea to assign some (6-7) people just to > assigning bugs to packages, and some others (5-6) just to try to fix the > status of bugs? [others could be "free players".] > assigning bugs to packages is important especially because otherwise the > package maintainer cannot know about the bug. I think it's not quite easy to 'assign' people to something. Most people in the BugSquad are volunteers. I agree, though, that it'd be nice to have groups in the BugSquad that focus on specific tasks or specific areas of bugs. For the Desktop Team or Maintainer Teams (like Accessibility) we do this already and it's quite natural to look at bugs that you have expertise with - it's easier to have an overview over less bugs. New users joining the BugSquad will also have an easier life, if they can join one group and get specific instructions and not generic answers and 17000 open bugs to look at. What can we do better to achieve this? One option would be to try to form specific Triaging Teams with explanatory wiki pages - what do you all think about that and which team would you like to lead / join? Have a nice day, Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Dies ist ein digital signierter Nachrichtenteil URL: From dh at mailempfang.de Thu Sep 28 12:29:46 2006 From: dh at mailempfang.de (Daniel Holbach) Date: Thu, 28 Sep 2006 14:29:46 +0200 Subject: updating pages In-Reply-To: <451B96C1.3050406@gmail.com> References: <451B96C1.3050406@gmail.com> Message-ID: <1159446586.16721.8.camel@localhost> Hello, Am Donnerstag, den 28.09.2006, 05:32 -0400 schrieb t u: > can anyone with more knowledge then I have update the following pages: would you and others please try to express difficulties with pointers to the specific Bugs/ page to https://wiki.ubuntu.com/BugSquad/DocumentationTODO ? It'd be nice and an easy job for some of us to fix issues in some spare minutes and avoid confusion. 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: Dies ist ein digital signierter Nachrichtenteil URL: From ubuntu at kagou.fr Thu Sep 28 13:22:01 2006 From: ubuntu at kagou.fr (ubuntu) Date: Thu, 28 Sep 2006 15:22:01 +0200 Subject: Proposal: assign people to specific jobs In-Reply-To: <1159446489.16721.5.camel@localhost> References: <451B40B8.7040509@gmail.com> <1159446489.16721.5.camel@localhost> Message-ID: <451BCC79.4070202@kagou.fr> Daniel Holbach a écrit : ... > I think it's not quite easy to 'assign' people to something. Most people > in the BugSquad are volunteers. Indeed. I think that volunteers are happy to find/assign/follow bugs for specific packages or group of packages they have interest for. Regards -- Patrice Vetsel Aka/Alias Kagou https://launchpad.net/people/vetsel-patrice gpg key: 0x15c094db From micah at cowan.name Thu Sep 28 17:15:32 2006 From: micah at cowan.name (Micah Cowan) Date: Thu, 28 Sep 2006 10:15:32 -0700 Subject: updating pages In-Reply-To: <451B96C1.3050406@gmail.com> References: <451B96C1.3050406@gmail.com> Message-ID: <1159463733.4816.17.camel@schmendrick> On Thu, 2006-09-28 at 05:32 -0400, t u wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > hi, > can anyone with more knowledge then I have update the following pages: > https://wiki.ubuntu.com/HelpingWithBugs > https://wiki.ubuntu.com/Bugs/HowToTriage (referred from above page) > https://wiki.ubuntu.com/Bugs/Responses > https://wiki.ubuntu.com/SourcePackage > https://wiki.ubuntu.com/AdoptingPackages > https://wiki.ubuntu.com/BugSquashing (referred from > DrinkingFromTheFirehose page we have at HelpingWithBugs) > > These pages seem to contain some vague / outdated / invalid information. > > especially the outdated+vague info on BugResponses caused me some > trouble: https://launchpad.net/distros/ubuntu/+bug/62468 > > thanks a lot :) Well, realize that some of the trouble you had with that BugResponse is because you applied it inappropriately: the summary says "If it's a packaging request of new software not already in Debian". If it's a sync request from Debian, then the above clearly doesn't apply. However, I understand that it's easy to misread "Debian" as "Ubuntu" if you're not looking too closely. Perhaps that should be stressed a bit on that page. -Micah ---------------------------------- Barracuda Networks makes the best spam firewalls and web filters. www.barracudanetworks.com From micah at cowan.name Thu Sep 28 17:35:05 2006 From: micah at cowan.name (Micah Cowan) Date: Thu, 28 Sep 2006 10:35:05 -0700 Subject: updating pages In-Reply-To: <1159437699.5935.15.camel@localhost> References: <451B96C1.3050406@gmail.com> <1159437699.5935.15.camel@localhost> Message-ID: <1159464905.4816.38.camel@schmendrick> On Thu, 2006-09-28 at 11:01 +0100, Caroline Ford wrote: > I think the Responses page needs much more work to be usable. I note > that no-one seems to be using those stock responses - and this is a good > thing as I know I hate it when I get a stock response to technical > support emails ;) Stock responses to frequently-asked and sometimes misinformed questions are not inappropriate, though. What I /have/ seen, though, is that a lot of people write responses with a slightly more personal touch, that seem to be /based/ upon the Responses. I /do/ frequently use the Response for "aged Needs Info" bugs. In this case, nothing much would really be saved by tailoring a response anyway, as at this point it doesn't seem likely that the original reporter will actually be reading it (since they hadn't read it for at least a couple months after the status changed to "Needs Info"). I /would/ like to be able to use the other "bug is not described well" Response, but I agree that linking to a massive (though well-written) essay on bug reporting isn't likely to be productive. Perhaps we could summarize Mr Tatham's points on a page of our own? The link to http://wiki.ubuntu.com/DebuggingProcedures is also much too vague: better to hone it down to the specific set of DebuggingProcedures that applies to this case. Giving them a link to a page that includes how to debug GNOME or Firefox isn't helpful if their problem is a CLI app that dumps core. Also, it doesn't seem like it should generally be a bug reporter's responsibility to debug their problem: a bug reporter's responsibility is to describe the bug in a highly reproducible manner (which, of course, is unfortunately not always possible). Anything asked above and beyond that should be as gentle a request as possible. The "average joe" user is not going to be happy to be asked to download source packages, build them with debugging symbols, run it under gdb, and provide a stack trace--as extremely useful as those can often be. Requesting these is often necessary when the developers/debuggers can't reproduce the problems themselves, but folks should realize what they're asking of the reporter, and if a backtrace is not obtained from the reporter, the Reject comment should be as courteous as possible ("I'm sorry, but I am unable to reproduce the bug on my own, and would need more low-level information regarding what you're experiencing in order to proceed"). > That page implies that problems with translations are not bugs when they > are. The answer given - "fix it yourself!" is not helpful to bug > reporters or to translators who would like to know when there are > problems.. That's incorrect. What it actually says is that Malone is the wrong /forum/ for translation bugs, which belong on Rosetta. And I see nothing along the lines of "fix it yourself". That being said, Rosetta is /not/ the appropriate forum for a lot of these translation issues. Many of them ought to be handled by upstream, in which case Malone may be more appropriate (I don't know, I'm fairly new), or may be handled in a different way from what Rosetta is capable of doing. In any case, it may be best to let the bugsquad determine when a bug would be more appropriate to Rosetta, and forward the bug themselves, rather than tell the user "you goofed, wrong forum". -Micah ---------------------------------- Barracuda Networks makes the best spam firewalls and web filters. www.barracudanetworks.com From towsonu2003 at gmail.com Thu Sep 28 17:43:38 2006 From: towsonu2003 at gmail.com (t u) Date: Thu, 28 Sep 2006 13:43:38 -0400 Subject: updating pages In-Reply-To: <1159437699.5935.15.camel@localhost> References: <451B96C1.3050406@gmail.com> <1159437699.5935.15.camel@localhost> Message-ID: <451C09CA.5070302@gmail.com> Caroline Ford wrote: > I think the Responses page needs much more work to be usable. I note > that no-one seems to be using those stock responses well I do... and I came across many triaging people who did as well while I was reporting bugs. > > That page implies that problems with translations are not bugs when they > are. The answer given - "fix it yourself!" is not helpful to bug > reporters or to translators who would like to know when there are > problems.. any suggestions? > > Don't we also want to know about bugs in Dapper? It is not obsoleted by > Edgy. > I think unless it's a real serious bug, no. bc they won't fix it unless bug reporter can prove that it's occuring in edgy (and then edgy+1) thanks for the reply :) From towsonu2003 at gmail.com Thu Sep 28 17:43:53 2006 From: towsonu2003 at gmail.com (t u) Date: Thu, 28 Sep 2006 13:43:53 -0400 Subject: updating pages In-Reply-To: <1159463733.4816.17.camel@schmendrick> References: <451B96C1.3050406@gmail.com> <1159463733.4816.17.camel@schmendrick> Message-ID: <451C09D9.2000805@gmail.com> the summary says "If it's a > packaging request of new software not already in Debian". If it's a sync > request from Debian, then the above clearly doesn't apply. > hahaha lol. I changed the summary afterwards so others won't get the same bump on their heads. :) From towsonu2003 at gmail.com Thu Sep 28 18:04:19 2006 From: towsonu2003 at gmail.com (t u) Date: Thu, 28 Sep 2006 14:04:19 -0400 Subject: Proposal: assign people to specific jobs In-Reply-To: <1159446489.16721.5.camel@localhost> References: <451B40B8.7040509@gmail.com> <1159446489.16721.5.camel@localhost> Message-ID: <451C0EA3.4060803@gmail.com> Daniel Holbach wrote: snip > > I agree, though, that it'd be nice to have groups in the BugSquad that > focus on specific tasks or specific areas of bugs. For the Desktop Team > or Maintainer Teams (like Accessibility) we do this already and it's > quite natural to look at bugs that you have expertise with - it's easier > to have an overview over less bugs. New users joining the BugSquad will > also have an easier life, if they can join one group and get specific > instructions and not generic answers and 17000 open bugs to look at. > a sub-team of bugsquad that only assigns bugs to packages [no other triaging task involved] might work. the job of this squad would be to triage incoming (new) as well as old bugs without specified packages only to packages. it's fairly easy and works nice because package developers get feedback on bugs in a more efficient way. For example, a couple of bugs for which I only did this got their way up to 6.10 milestone. this also makes life easier for dupe-finders (which could be another sub-team) as they will only click on "bugs" link on the left side to look for dupes on a newly reported bug. one more team: xorg-crash-team could triage only bugs that report xorg is crashing for some reason (bad config, no driver, gnome screwing up something etc). thanks. From micah at cowan.name Thu Sep 28 18:10:10 2006 From: micah at cowan.name (Micah Cowan) Date: Thu, 28 Sep 2006 11:10:10 -0700 Subject: updating pages In-Reply-To: <451C09D9.2000805@gmail.com> References: <451B96C1.3050406@gmail.com> <1159463733.4816.17.camel@schmendrick> <451C09D9.2000805@gmail.com> Message-ID: <1159467011.4816.41.camel@schmendrick> On Thu, 2006-09-28 at 13:43 -0400, t u wrote: > the summary says "If it's a > > packaging request of new software not already in Debian". If it's a sync > > request from Debian, then the above clearly doesn't apply. > > > > hahaha lol. I changed the summary afterwards so others won't get the > same bump on their heads. :) ... /me makes a note to make a habit of checking the page histories ^_^ -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ ---------------------------------- Barracuda Networks makes the best spam firewalls and web filters. www.barracudanetworks.com From pandisv at yahoo.co.uk Thu Sep 28 18:28:06 2006 From: pandisv at yahoo.co.uk (Vassilis Pandis) Date: Thu, 28 Sep 2006 19:28:06 +0100 (BST) Subject: Proposal: assign people to specific jobs In-Reply-To: <451C0EA3.4060803@gmail.com> Message-ID: <20060928182806.74830.qmail@web25001.mail.ukl.yahoo.com> --- t u wrote: > a sub-team of bugsquad that only assigns bugs to packages [no other > triaging task involved] might work. the job of this squad would be to > triage incoming (new) as well as old bugs without specified packages > only to packages. it's fairly easy and works nice because package > developers get feedback on bugs in a more efficient way. For example, a > couple of bugs for which I only did this got their way up to 6.10 > milestone. > I can see your point with the unassigned packages. Is an entire team neccessary though? What about a hug day with only this target in mind, to clear up the backlog that has been created. After it's over, let's just try to put bugs where they belong (and if neccessary hold a similar hug day in a few months' time). PS: tu, sorry for sending this a gazillion times to you - accident :-/ ___________________________________________________________ All new Yahoo! Mail "The new Interface is stunning in its simplicity and ease of use." - PC Magazine http://uk.docs.yahoo.com/nowyoucan.html From towsonu2003 at gmail.com Thu Sep 28 20:11:22 2006 From: towsonu2003 at gmail.com (t u) Date: Thu, 28 Sep 2006 16:11:22 -0400 Subject: Proposal: assign people to specific jobs In-Reply-To: <20060928182529.83090.qmail@web25003.mail.ukl.yahoo.com> References: <20060928182529.83090.qmail@web25003.mail.ukl.yahoo.com> Message-ID: <451C2C6A.3050209@gmail.com> Vassilis Pandis wrote: > --- t u wrote: > > >> a sub-team of bugsquad that only assigns bugs to packages [no other >> triaging task involved] might work. the job of this squad would be to >> triage incoming (new) as well as old bugs without specified packages >> only to packages. it's fairly easy and works nice because package >> developers get feedback on bugs in a more efficient way. For example, a >> couple of bugs for which I only did this got their way up to 6.10 >> milestone. >> > > I can see your point with the unassigned packages. Is an entire team neccessary > though? What about a hug day with only this target in mind, to clear up the backlog > that has been created. After it's over, let's just try to put bugs where they > belong (and if neccessary hold a similar hug day in a few months' time). > well, as the sub-team will be voluntary, we can see how participation goes for a year-long review period. the backlog seems to be too much. this link https://launchpad.net/distros/ubuntu/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=Unconfirmed&assignee_option=any&field.assignee=&field.owner=&field.component-empty-marker=1&field.status_upstream=&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.tag=&field.has_no_package.used=&field.has_no_package=on&search=Search shows 1746 bugs for only unconfirmed ones. also, I expect that we are getting many no-package-specified bugs (we have a newbie user base) by the minute (exageration). It would be nice to have a team (I expect to have only 4-5 people sign up to such a team) that processes those bugs as they come, as fast as possible. just to clarify myself, this should be a sub-team. so anyone who is a member of that team will be a member of bugsquad, hence will do other bug work as well. but they will have in mind a primary goal: no no-package-bugs. all this team should need is a wiki page of "common cases". no email list etc is necessary as they can communicate via bugsquad email list -why not, we don't get much email anyway? or maybe I'm wrong-. chatroom isn't necessary either. this team would also be a great place for absolute newbies (me! ehueheh). all you need to know is which package is causing the bad behavior. From ubuntu at alexm.org Thu Sep 28 22:52:50 2006 From: ubuntu at alexm.org (Alex Muntada) Date: Fri, 29 Sep 2006 00:52:50 +0200 Subject: Proposal: assign people to specific jobs In-Reply-To: <20060928182806.74830.qmail@web25001.mail.ukl.yahoo.com> References: <451C0EA3.4060803@gmail.com> <20060928182806.74830.qmail@web25001.mail.ukl.yahoo.com> Message-ID: <20060928225250.GA14495@ac.upc.edu> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 * Vassilis Pandis : [2006-09-28 19:28:06 +0100] > What about a hug day with only this target in mind, to clear > up the backlog that has been created. After it's over, let's > just try to put bugs where they belong (and if neccessary hold > a similar hug day in a few months' time). I like this approach. Being myself a newbie in bugsquad, I can't help very often with untriaged bugs. Right now, I'd prefer to spend much more time with the bugs I found, reporting and trying to fix them somehow or finding their duplicates. That doesn't mean that I'm not going to participate in the triaging process ever; it's just that now I don't have the time to learn the details. However, a whole UbuntuBugDay mainly focused to a specific job sounds good enough. my $0.02; - -- Alex Muntada http://alexm.org/ -----BEGIN PGP SIGNATURE----- iD8DBQFFHFI9LdxCGS3zaBERAnAGAJ9+OlMAhBaMX/+ABAFU5syI85Om9QCgxlKr 1CXTL5E2ixk+441YzKtZ9zo= =Td0B -----END PGP SIGNATURE-----