Your message dated Mon, 4 Jan 2010 23:07:47 +0100
with message-id <[email protected]>
and subject line Re: reportbug should improve it's existing bug checking
features
has caused the Debian Bug report #498268,
regarding reportbug should improve it's existing bug checking features
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
498268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498268
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: reportbug
Version: 3.45
Severity: important
When reporting bugs with reportbug as it stands the user is presented with,
generally, a long list of existing bugs before being filling in any details.
I feel that this interface is:
* Hard to use and confusing for new users
* Requires too much effort to read, leading to duplicate bugs
I think that the interface for checking existing bugs could be improved by:
* Letting the user describe the bug summary
* Peforming a full text search against the BTS with the summary
* Presenting the top 10 matches of similar bugs for the same package
* Allowing the user to add additional information for existing bugs, or enter
the detailed information for the new bug
This is very similar to the Ubuntu Launchpad bug reporting functionality.
I feel that this would:
* Make reportbug a lot easier for new users
* Improve the liklihood of people bothering to read existing bugs, thereby
* Reducing the number of duplicate bugs in the BTS, thereby
* Improving the happiness and productivity of DDs everywhere
-- Package-specific info:
** Environment settings:
EDITOR="emacs"
EMAIL="[email protected]"
INTERFACE="urwid"
** /home/nslater/.reportbugrc:
reportbug_version "3.45"
mode standard
ui urwid
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages reportbug depends on:
ii apt 0.7.14+b1 Advanced front-end for dpkg
ii python 2.5.2-2 An interactive high-level object-o
ii python-central 0.6.8 register and build utility for Pyt
reportbug recommends no packages.
Versions of packages reportbug suggests:
ii debconf-utils 1.5.23 debconf utilities
ii debsums 2.0.36 verification of installed package
ii dlocate 0.96.1 fast alternative to dpkg -L and dp
ii exim4 4.69-6 metapackage to ease Exim MTA (v4)
ii exim4-daemon-light [mail-tran 4.69-6 lightweight Exim MTA (v4) daemon
ii file 4.25-1 Determines file type using "magic"
ii gnupg 1.4.9-3 GNU privacy guard - a free PGP rep
ii python-urwid 0.9.8.3-1 curses-based UI/widget library for
-- no debconf information
--
Noah Slater, http://bytesexual.org/nslater
--- End Message ---
--- Begin Message ---
Hello Noah,
thanks for your report, that I'm going to close :)
On Mon, Sep 08, 2008 at 03:53:33PM +0100, Noah Slater wrote:
> Package: reportbug
> Version: 3.45
> Severity: important
>
> When reporting bugs with reportbug as it stands the user is presented with,
> generally, a long list of existing bugs before being filling in any details.
>
> I feel that this interface is:
>
> * Hard to use and confusing for new users
Ok it might not be the best way to present the list, but it's not that
confusing, and once you get how it works, it's not that bad :)
> * Requires too much effort to read, leading to duplicate bugs
you can use the filter function.
> I think that the interface for checking existing bugs could be improved by:
>
> * Letting the user describe the bug summary
> * Peforming a full text search against the BTS with the summary
> * Presenting the top 10 matches of similar bugs for the same package
> * Allowing the user to add additional information for existing bugs, or enter
> the detailed information for the new bug
On http://www.debian.org/Bugs/ there is a section named "Searching bug
reports" that lists several ways to search for bug reports: an
(experimental?) search engine in debian, gmane, google groups. If even
the bts suggests external resources, I think reportbug should adhere
to that decision, and don't implement something that's not hosted on
BTS.
> This is very similar to the Ubuntu Launchpad bug reporting functionality.
>
> I feel that this would:
>
> * Make reportbug a lot easier for new users
> * Improve the liklihood of people bothering to read existing bugs, thereby
> * Reducing the number of duplicate bugs in the BTS, thereby
> * Improving the happiness and productivity of DDs everywhere
That's (sadly) not true: either a user really wants to avoid
duplicates, and he'd search also on google & co, else he simply
doesn't care and go on report the bug and let the maint fix it,
eventually.
Regards,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--- End Message ---
_______________________________________________
Reportbug-maint mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/reportbug-maint
