From daniel.holbach at ubuntu.com Thu Aug 3 14:58:17 2006 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Thu, 03 Aug 2006 16:58:17 +0200 Subject: Palm Testers in full effect! Message-ID: <1154617097.20934.8.camel@localhost> Hello everybody, we always had eager Palm users and Palm Testers in Ubuntu and we're grateful for that. Now we're trying to organise the efforts a bit and: * test hardware, * communicate with Upstream, * provide Howtos of best practices For this I created the https://launchpad.net/people/palmtesters and welcome every Palm user to add themselves to the team. Together we're going to monitor bugs of packages offering Palm support and try to report the issues to the upstream developers. I created some wiki pages at https://wiki.ubuntu.com/PalmTesters and hope they will help to organise the efforts. Edgy users might want to test a new version (2.0.14 prerelease) of gnome-pilot. I uploaded i386 and amd64 packages to http://people.ubuntu.com/~dholbach/pilot/ and hope they will work nicely for you. I also CCed Matt Davey who works on gnome-pilot himself. Have a nice day, Daniel From daniel.holbach at ubuntu.com Thu Aug 3 15:58:27 2006 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Thu, 03 Aug 2006 17:58:27 +0200 Subject: *PDA* Testers in full effect! In-Reply-To: <1154617097.20934.8.camel@localhost> References: <1154617097.20934.8.camel@localhost> Message-ID: <1154620708.30673.7.camel@localhost> Hello everybody, On Do, 2006-08-03 at 16:58 +0200, Daniel Holbach wrote: > For this I created the https://launchpad.net/people/palmtesters and > welcome every Palm user to add themselves to the team. ... > I created some wiki pages at https://wiki.ubuntu.com/PalmTesters and > hope they will help to organise the efforts. ... to make this all a bit more generic, I re-dubbed the team to PDA testers, so effectively the URLs above changed to: https://wiki.ubuntu.com/PDATesters https://launchpad.net/people/pdatesters Sorry for the noise, as apology I created https://wiki.ubuntu.com/CategoryPDA as well. Have a nice day, Daniel From johnmark at johnmark.org Thu Aug 3 16:53:29 2006 From: johnmark at johnmark.org (John Mark Walker) Date: Thu, 3 Aug 2006 09:53:29 -0700 Subject: *PDA* Testers in full effect! In-Reply-To: <1154620708.30673.7.camel@localhost> References: <1154617097.20934.8.camel@localhost> <1154620708.30673.7.camel@localhost> Message-ID: Hi there, Can somebody present on this at The UbuCon? Thanks, John Mark http://www.linuxpip.org/ubuconwiki On Aug 3, 2006, at 8:58 AM, Daniel Holbach wrote: > Hello everybody, > > On Do, 2006-08-03 at 16:58 +0200, Daniel Holbach wrote: >> For this I created the https://launchpad.net/people/palmtesters and >> welcome every Palm user to add themselves to the team. > ... >> I created some wiki pages at https://wiki.ubuntu.com/PalmTesters and >> hope they will help to organise the efforts. > ... > > to make this all a bit more generic, I re-dubbed the team to PDA > testers, so effectively the URLs above changed to: > > https://wiki.ubuntu.com/PDATesters > https://launchpad.net/people/pdatesters > > Sorry for the noise, as apology I created > https://wiki.ubuntu.com/CategoryPDA as well. > > Have a nice day, > Daniel > > > > -- > ubuntu-devel mailing list > ubuntu-devel at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel From daniel.holbach at ubuntu.com Mon Aug 7 09:27:04 2006 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Mon, 07 Aug 2006 11:27:04 +0200 Subject: Malone Tags Message-ID: <1154942825.16779.15.camel@localhost> Hello everybody, as much as I appreciate web2.0 coming to our part of town, I want to start a discussion about Tags in Malone. To get a good impression of what I'm talking about, see here: https://launchpad.net/distros/ubuntu/+bugs I want to propose a moderation queue for tags and get the current list completely cleaned up. Having a package tag (like 'firefox', 'epiphany' or 'gnome-panel') makes no sense at all. The same goes for 'gnome' and 'audio' - we have teams to handle this kind of bug. It'd be nice if we could use the tags to organize our workflow. What about tags like 'go-upstream' or 'easyfix'? The current list is messy and doesn't make things easier. In my opinion we might just need a more prominent list of teams. I propose to lock the 'add tag' UI and make it available to 'ubuntu-qa' or to whatever else team we can agree on. I look forward to hear more views on this because I think tags are a tool that 'can' make our life easier. Have a nice day, Daniel From daniel.holbach at ubuntu.com Mon Aug 7 09:45:38 2006 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Mon, 07 Aug 2006 11:45:38 +0200 Subject: T-Shirts! Message-ID: <1154943938.16779.25.camel@localhost> Hellas! as you can see at http://fridge.ubuntu.com/node/484 Canonical is looking for a fancy T-Shirt design for the next conference Shirt. Some of you might remember our own efforts at https://wiki.ubuntu.com/BugSquad/TShirtDesigns - we should try to add some crazy new designs to our own page and agree on one design ourselves. :-) Have a nice day, Daniel From daniel.holbach at ubuntu.com Mon Aug 7 10:09:32 2006 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Mon, 07 Aug 2006 12:09:32 +0200 Subject: Malone Tags In-Reply-To: <200608071159.33729.sistpoty@ubuntu.com> References: <1154942825.16779.15.camel@localhost> <200608071159.33729.sistpoty@ubuntu.com> Message-ID: <1154945372.16779.33.camel@localhost> Hello, On Mo, 2006-08-07 at 11:59 +0200, Stefan Potyra wrote: > One use case of tags might be for transitions, to tag all packages that need > to be transitioned. Or s.th. like tracking of unmet dependencies. if we were to do that, we should make sure we clean unneeded tags from the list after the transition. Steve Alexander pointed me to https://help.launchpad.net/TaggingLaunchpadBugs - which seems a sane approach to using tags. The current list of tags contains around 75 tags (Sébastien counted :-)) - I feel the list will continue to grow and in the end defeat the purpose of tags completely, as bugs won't be grouped as effectively as they could (in addition to the task of finding the correct tags). I hope we find a solution here and make the best use of this very cool feature. Have a nice day, Daniel From siretart at tauware.de Mon Aug 7 10:15:31 2006 From: siretart at tauware.de (Reinhard Tartler) Date: Mon, 07 Aug 2006 12:15:31 +0200 Subject: Malone Tags In-Reply-To: <1154942825.16779.15.camel@localhost> (Daniel Holbach's message of "Mon, 07 Aug 2006 11:27:04 +0200") References: <1154942825.16779.15.camel@localhost> Message-ID: <87vep4kg1o.fsf@hermes.olymp.tauware.de> Daniel Holbach writes: > I want to propose a moderation queue for tags and get the current list > completely cleaned up. Having a package tag (like 'firefox', 'epiphany' > or 'gnome-panel') makes no sense at all. The same goes for 'gnome' and > 'audio' - we have teams to handle this kind of bug. > > > It'd be nice if we could use the tags to organize our workflow. What > about tags like 'go-upstream' or 'easyfix'? The current list is messy > and doesn't make things easier. In my opinion we might just need a more > prominent list of teams. I think for the start a wikipage with a list of ``official'' tags along with a description what they are for would be a good start. At least until we have some ways to delete obsolete tags and moderate creation of new ones. Do we perhaps already have such a wiki page? -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 From mpt at canonical.com Mon Aug 7 10:35:09 2006 From: mpt at canonical.com (Matthew Paul Thomas) Date: Mon, 7 Aug 2006 22:35:09 +1200 Subject: Malone Tags In-Reply-To: <87vep4kg1o.fsf@hermes.olymp.tauware.de> References: <1154942825.16779.15.camel@localhost> <87vep4kg1o.fsf@hermes.olymp.tauware.de> Message-ID: <4c5bff2314c75c987571cdcbafdab58e@canonical.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Aug 7, 2006, at 10:15 PM, Reinhard Tartler wrote: > > Daniel Holbach writes: >> >> I want to propose a moderation queue for tags and get the current list >> completely cleaned up. There's a much easier solution ... >> Having a package tag (like 'firefox', 'epiphany' or 'gnome-panel') >> makes no sense at all. Agreed. (That's probably a design flaw in the form, though.) >> The same goes for 'gnome' and 'audio' - we have teams to handle this >> kind of bug. You use teams of people to classify bugs by topic? That's weird. >> It'd be nice if we could use the tags to organize our workflow. What >> about tags like 'go-upstream' or 'easyfix'? The current list is messy >> and doesn't make things easier. In my opinion we might just need a >> more >> prominent list of teams. > > I think for the start a wikipage with a list of ``official'' tags > along with a description what they are for would be a good start. At > least until we have some ways to delete obsolete tags and moderate > creation of new ones. > > Do we perhaps already have such a wiki page? > ... ... The much easier solution is to limit the list of tags to only the most common 50 or so, and present them as a normal tag cloud (or alternatively sort them by popularity). That way people can still add useless tags to individual bugs if they like, and it (usually) won't affect the list on the Bugs page. - -- Matthew Paul Thomas http://mpt.net.nz/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFE1xdi6PUxNfU6ecoRArR/AJ9xj9Ynv272IoFfF74aToT5CZDq3QCcCkxe mpgJ9jExuhlBffk/f04T8aY= =Pv8V -----END PGP SIGNATURE----- From m.drozdzynski at gmail.com Mon Aug 7 14:32:52 2006 From: m.drozdzynski at gmail.com (=?UTF-8?Q?Mateusz_Dro=C5=BCd=C5=BCy=C5=84ski?=) Date: Mon, 7 Aug 2006 16:32:52 +0200 Subject: Feature requests, support requests, bugs pointing out that a translation is wrong, requests for packaging new software, etc. Message-ID: <5e5da4dd0608070732r4220cef5jb35afc5e1e18fd6e@mail.gmail.com> Hi, I've got a question regarding the bug triaging process. What do we do about bugs that are feature requests, support requests, bugs pointing out that a translation is wrong, etc.? Should they be left as they are, what basically results in having numerous Unconfirmed bugs which we're trying to fight or should we mark them as rejected? Thanks for your responses. -- Best regards, Mateusz Drożdżyński From daniel.holbach at ubuntu.com Mon Aug 7 15:01:46 2006 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Mon, 07 Aug 2006 17:01:46 +0200 Subject: Feature requests, support requests, bugs pointing out that a translation is wrong, requests for packaging new software, etc. In-Reply-To: <5e5da4dd0608070732r4220cef5jb35afc5e1e18fd6e@mail.gmail.com> References: <5e5da4dd0608070732r4220cef5jb35afc5e1e18fd6e@mail.gmail.com> Message-ID: <1154962906.6942.10.camel@localhost> Hello Mateusz, On Mo, 2006-08-07 at 16:32 +0200, Mateusz Drożdżyński wrote: > What do we do > about bugs that are feature requests, support requests, bugs pointing > out that a translation is wrong, etc.? thanks for your question. Apart from some side cases we handle most of the bugs you mentioned as outlined in https://wiki.ubuntu.com/Bugs/Responses For translations we assign point people to Rosetta (http://launchpad.net/rosetta) and to their language team, for support requests we point them to the support tracker (http://launchpad.net/support), for feature requests we point them to the spec tracker (http://launchpad.net/specs). There are numerous other cases, where it's not exactly buggy behaviour the reporter describes and it should be easy to point them to a more appropriate forum. Hope that helps, have a nice day, Daniel From daniel.holbach at ubuntu.com Mon Aug 7 15:33:10 2006 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Mon, 07 Aug 2006 17:33:10 +0200 Subject: Feature requests, support requests, bugs pointing out that a translation is wrong, requests for packaging new software, etc. In-Reply-To: <5e5da4dd0608070827n78e42c3bl9fabea7c308b71ff@mail.gmail.com> References: <5e5da4dd0608070732r4220cef5jb35afc5e1e18fd6e@mail.gmail.com> <1154962906.6942.10.camel@localhost> <5e5da4dd0608070827n78e42c3bl9fabea7c308b71ff@mail.gmail.com> Message-ID: <1154964790.6942.21.camel@localhost> Hello Mateusz, On Mo, 2006-08-07 at 17:27 +0200, Mateusz Drożdżyński wrote: > I'm sorry, I wasn't clear enough. I was only curious about the status > that we should set. I already add comments as described in > https://wiki.ubuntu.com/Bugs/Responses, but I'm not sure if I should > for example reject the bug or not, after adding a comment. > Again, thanks for your reply. in the most cases it's ok to 'reject' it. If you're unsure, just ask somebody else to agree on your decision. Have a nice day, Daniel From lloydinho at gmail.com Mon Aug 14 13:39:52 2006 From: lloydinho at gmail.com (Andreas Lloyd) Date: Mon, 14 Aug 2006 15:39:52 +0200 Subject: Contribute doc and Bugsquad team page Message-ID: <44E07D28.505@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Bugsquad! I have been working on a new document for the Ubuntu Documentation on how to get involved with Ubuntu [1], and as part of that, I have been going through all the team wiki pages to gather basic information on how to get involved with each team. Unfortunately, not all of this information is organized or available in any easy way. To solve this, I have made a TeamPageTemplate [2] in the Ubuntu Wiki to offer a common structure for team wiki pages to make it easy for new contributors to get an overview of the information that they will need to get involved. I hope you are willing to adopt this structure for the Bugsquad page. I have already adapted the DocumentationTeam wiki page to this template [3] so that you can get an idea of what such a team wiki page can look like. If you wish, I can adapt the team page for you, but I think it would be best if the team members did this themselves. I would also like you to have a look at the ContributeToUbuntu section on the Bugsquad section [4] so that you can make sure that it properly reflects how you want people to get involved. Remember that this is to make it easy for new community members to get involved, so please let me know if you have any input or comments on the suggested structure. [1] https://wiki.ubuntu.com/ContributeToUbuntu [2] https://wiki.ubuntu.com/TeamPageTemplate?action=edit (note that there are comments for each section) [3] https://wiki.ubuntu.com/DocumentationTeam [4] https://wiki.ubuntu.com/ContributeToUbuntu#head-40fb9243aa177090012e0c844f80fb1fedda56c6 Cheers, Andreas - -- https://launchpad.net/people/lloydinho -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE4H0oY0tj6HNxlo4RArMMAJ9T6IJOslTwOgPPufwaoG7gRFw0AACgiGY6 r42NvRHcESiYDBdGrbimt60= =rHux -----END PGP SIGNATURE----- From carthik at gmail.com Tue Aug 15 17:44:13 2006 From: carthik at gmail.com (Carthik Sharma) Date: Tue, 15 Aug 2006 13:44:13 -0400 Subject: The BugSquad - rocking and rolling! In-Reply-To: <1153734769.6975.46.camel@localhost> References: <1153734769.6975.46.camel@localhost> Message-ID: <80f75db0608151044l1bfd3807p8ec9a2f8b0656d69@mail.gmail.com> Hi all, On 7/24/06, Daniel Holbach wrote: > Hello everybody, > * we have our own mailing list [4] > * most importantly: we want to have a meeting soon again. We want > to do this to create an opportunity to discuss how we keep the > pile of bugs low and how to fix processes. If you have new > ideas, please add them to [5] and we announce a meeting soon. > [6] might be a good start for this. I added a couple of questions to the meeting agenda. I guess a lot of other things could also be discussed at a meeting. A meeting would totally rock :) Regards, Carthik. > > Have a nice day, > Daniel (for the BugSquad) > > > [1] https://wiki.ubuntu.com/BugSquad/Meeting/Minutes/2006-03-28 > [2] https://launchpad.net/people/bugsquad > [3] https://wiki.ubuntu.com/CategoryBugSquad > [4] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > [5] https://wiki.ubuntu.com/BugSquad/Meeting > [6] https://wiki.ubuntu.com/BugSquad/Observations > [7] https://wiki.ubuntu.com/DesktopTeam/BugState > > > > -- > 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 pandisv at yahoo.co.uk Wed Aug 16 17:04:09 2006 From: pandisv at yahoo.co.uk (Vassilis Pandis) Date: Wed, 16 Aug 2006 18:04:09 +0100 (BST) Subject: Bug forwarding Message-ID: <20060816170409.62219.qmail@web25010.mail.ukl.yahoo.com> Hello everybody, Going through several bugs a day I see a pattern that tends to repeat itself often: User files bug, some questions are asked, info is collected and another person or two describe the same problem --> Bug is confirmed but nobody is really working on it. Given that Ubuntu doesn't have maintainers (so few people are very familiar with the code of a certain package) and that the bugs greatly outnumber the people that have the ability to fix them, most of these belong upstream. Forwarding a bug upstream though usually takes a significant amount of time because in most cases an account for the remote BTS should be created, activated, you have to log in and then report the bug. I understand that Launchpad was created exactly for this purpose - easy cooperation between Open Source projets. Unfortunately, few projects are using Malone as their BTS so cooperation is still a problem. To get to the point: 1. Are there any plans on implementing a quick way of bug forwarding from Launchpad in the near future? i.e. The ability to file bugs at a remote BTS without leaving the Malone (and not just keeping track of them). 2. If this is not possible, how feasible is it to set up a website where bug triagers can use a simple interface to forward bugs? Something like "Which bug do you want to forward to which BTS?". This will eliminate the need to create millions of accounts everywhere and make the process more official (i.e. the reporter will be something like ubuntu-forwarder at ubuntu.com and not random_guy19803 at random.com, the text written in the bug report will be consistent etc.) Thanks for reading this, Vassilis Pandis PS: If this belongs to another list, please don't hesitate to say so. ___________________________________________________________ Now you can scan emails quickly with a reading pane. Get the new Yahoo! Mail. http://uk.docs.yahoo.com/nowyoucan.html From seb128 at ubuntu.com Wed Aug 16 17:34:25 2006 From: seb128 at ubuntu.com (Sebastien Bacher) Date: Wed, 16 Aug 2006 19:34:25 +0200 Subject: Bug forwarding In-Reply-To: <20060816170409.62219.qmail@web25010.mail.ukl.yahoo.com> References: <20060816170409.62219.qmail@web25010.mail.ukl.yahoo.com> Message-ID: <1155749665.5867.6.camel@localhost.localdomain> Le mercredi 16 août 2006 à 18:04 +0100, Vassilis Pandis a écrit : > Hello everybody, Hi, > Going through several bugs a day Thank you for your bug triage work, that's appreciate ;) > I see a pattern that tends to repeat itself often: User files > bug, some questions are asked, info is collected and another person or two describe the same > problem --> Bug is confirmed but nobody is really working on it. Right, that's something which has been discussed during the summit to Paris in June, you can read https://blueprint.launchpad.net/products/malone/+spec/upstream-forwarding-workflow about that I'm not replying the points you mentioned because I think that the spec should be enough to reply to your questions, feel free to ask if there is something still not clear after reading it Cheers, Sebastien Bacher From kiko at async.com.br Tue Aug 15 21:35:00 2006 From: kiko at async.com.br (Christian Robottom Reis) Date: Tue, 15 Aug 2006 18:35:00 -0300 Subject: Malone Tags In-Reply-To: <1154945372.16779.33.camel@localhost> References: <1154942825.16779.15.camel@localhost> <200608071159.33729.sistpoty@ubuntu.com> <1154945372.16779.33.camel@localhost> Message-ID: <20060815213500.GM30057@anthem.async.com.br> On Mon, Aug 07, 2006 at 12:09:32PM +0200, Daniel Holbach wrote: > The current list of tags contains around 75 tags (Sébastien counted :-)) > - I feel the list will continue to grow and in the end defeat the > purpose of tags completely, as bugs won't be grouped as effectively as > they could (in addition to the task of finding the correct tags). Well, there are a few arguments that can be entertained here. a) That tags are light-weight, that any end-user can easily add one, and that the ones that really matter are the ones which are most used. If this is how it should work, then we should really only display N most used tags, and get on with life. b) That tags are light-weight, as above, but that we nudge people towards reusing existing tags instead of creating new ones. To do this, we could prompt people "Are you sure" when they are adding a tag which we've never seen before. We could display a list of existing tags so that people could choose from them rather than making up their own. We could also display counts next to the tags so that people could easily clean up one-off typos and tags which were actually unused. We could also offer a place where a product could define text or a URL to an "Official Tag Guide". c) That tags should be heavy-weight, that only product/project owners should be allowed to create them. End-users would be allowed only to select from existing defined tags. This is exactly how Bugzilla keywords work. d) That tags should be heavy-weight, as above, and that only privileged people should be allowed to set them. The approach so far has been pretty much a), but we are moving towards b), because we currently think it is the best compromise between ease-of-use, flexibility, low-startup-cost and effectiveness as a bug grouping mechanism. I'd be happy to hear opinions on this. -- Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3376 0125 From sfllaw at ubuntu.com Mon Aug 21 16:32:45 2006 From: sfllaw at ubuntu.com (Simon Law) Date: Mon, 21 Aug 2006 12:32:45 -0400 Subject: Ubuntu Bug Day on Wednesday 23 August 2006 Message-ID: <20060821163245.GY5196@law.yi.org> Hi everybody! A bunch of us are hanging out in a quaint little conference room in Wiesbaden, Germany. We're hacking away on Edgy Eft and trying to get as much done as possible. As part of this event, we're throwing a Bug Day this Wednesday. It will be at the same time (whenever it is Wednesday in your part of the world). And it will be in the same place (the #ubuntu-bugs IRC channel on irc.freenode.net). But what will be different is that we'll have as many developers as possible in participation. Yay! See https://wiki.ubuntu.com/UbuntuBugDay for more details. We'll be looking at the big issues that would block Edgy from releasing. These are: - Desktop bugs - Kernel bugs - X bugs But you can help with whatever bugs you like. As usual, we'll be giving out hugs for bugs. See you there. And happy hacking, -- Simon Law http://www.law.yi.org/~sfllaw/ From dennis at kaarsemaker.net Tue Aug 29 08:09:37 2006 From: dennis at kaarsemaker.net (Dennis Kaarsemaker) Date: Tue, 29 Aug 2006 10:09:37 +0200 Subject: on closing "old" and "inactive" bug reports In-Reply-To: <44F3F25C.4050101@ubuntu.com> References: <44F3F25C.4050101@ubuntu.com> Message-ID: <1156838977.6042.21.camel@mirage> On di, 2006-08-29 at 09:53 +0200, Matthias Klose wrote: > - don't close bug reports assigned to people (without testing or asking) > - don't close confirmed bug reports > - "old" or "inactive" should not be closed; if we really want to do > this, we could surely do this automatically. Couldn't agree more. The only bugs I can imagine that are suitable for closing due to inactivity are unreproducable "Needs Info" bugs where the reporter fails to provide the requested information. -- 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 daniel.holbach at ubuntu.com Tue Aug 29 13:42:24 2006 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Tue, 29 Aug 2006 15:42:24 +0200 Subject: on closing "old" and "inactive" bug reports In-Reply-To: <200608290831.38038.grasshopper@linuxkungfu.org> References: <44F3F25C.4050101@ubuntu.com> <200608290831.38038.grasshopper@linuxkungfu.org> Message-ID: <1156858944.7030.7.camel@localhost> Hello, Am Dienstag, den 29.08.2006, 08:31 -0500 schrieb Rocco Stanzione: > It was briefly discussed, then I was > advised to ask sfllaw, who promptly appeared. It was discussed some more, > and the idea received the blessing of the guy I was asked to ask, so I began. > I believe the vast majority of the tickets I closed should have been closed. > There was some volume, and it's certainly possible I closed a few that I > shouldn't have, but none that didn't meet the criteria we discussed. Simon: what were the criteria you mentioned to Rocco? Can we try to integrate these criteria to http://wiki.ubuntu.com/HelpingWithBugs ? 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: