Re: [Nautilus-list] Bug buddy
- From: Rebecca Schulman <rebecka eazel com>
- To: Tom Musgrove <TomM pentstar com>
- Cc: Adam Sleight <adams linearcorp com>, Nautilus-list lists eazel com
- Subject: Re: [Nautilus-list] Bug buddy
- Date: Mon, 13 Nov 2000 12:48:47 -0800
Tom Musgrove wrote:
> A long while ago I suggested some advanced search functionality that would
> be cool to add to Gnome/nautilus. I think that it would be ideal for
> something like this as well.
>
> Specifically the synonym/clustering stuff. Do a scan of the keywords
> entered by the user and find which ones are frequent and/or unique. This
> will likely give a initial grouping for the bug report. Then do a synonym
> search. The synonyms would be defined by the bug database people, thus if I
> type URL entry problem, and someone else types Address location bar error,
> then the programmer would map problem to error, and Address location to URL
> entry. Then future reports/errors could then be ranked on their
> nearness/match to the new report, and the user could select a matching bug
> report. This would save the programmers and bug submitters ENORMOUS amounts
> of time.
Thanks for sending ideas to nautilus list. Helping people contribute to and
use the bug database would indeed improve productivity for everyone.
You are right that a search mechanism that was more accurate could save
programmers
and bug submitters time. The bug database right now, however is not very
large ,and the time spent looking for bugs isn't all that large on a long term
basis. Since there are only a few thousand bugs, you can easily do a search
that is too vague and scan through 10 or 20 possibilities with little time
wasted. Additionally, frequent users of the bug database often develop a
familiarity with the contents relevant to him or her, which makes searching
much easier.
One problem with synonym searching is that there is no ready made database of
synonyms for a situation. This means that such a database would have to be
made by hand, and updated as the concepts surrounding our software change. The
nautilus team, however, has worked very hard at standardizing and clarifying
our names for things. Perhaps the time creating and updating a database for
searching could be better spent creating a naming introduction for bug database
users, and other would be members of the nautilus development community.
Rebecca
>
>
> I'd be willing to bet that the above system could cut the time spent
> locating duplicate bugs by 50-75% easily.
>
> Another suggestion for bug reports, would be a program that tracked
> application usage/keystrokes, software and hardware environment etc. The
> user would have the option of attaching this information to the bug report
> to aid the debugging effort. There are some privacy concerns, but as long
> as it is opt in, I'm sure that many Free Software users would be happy to
> help.
>
> I would also make the feature requesting separate from bug reporting
> database, and make the feature requests more visible (i.e. a separate
> subsystem). A tool for user voting for future features would be really cool
> also. (I've written elsewhere about this more in depth, I'll post more info
> if desired...)
>
> ttyl,
>
> Tom M.
> TomM Pentstar com
>
> -----Original Message-----
> From: nautilus-list-admin lists eazel com
> [mailto:nautilus-list-admin lists eazel com]On Behalf Of Adam Sleight
> Sent: Thursday, November 09, 2000 1:21 PM
> To: Nautilus-list lists eazel com
> Subject: Re: [Nautilus-list] Bug buddy
>
> On Thu, 09 Nov 2000 08:58:25 -0800
> Darin Adler <darin eazel com> wrote:
> | on 11/9/00 2:10 AM, Ross Burton at r burton 180sw com wrote:
> |
> | > How about integrating bug buddy into Nautilus (a la Evolution) so that
> | > bug reporting is easier?
> |
> | We'd like to have bug buddy work with Nautilus. But the current bug
> buddy
> | results in a lot of backtraces with minimal additional comments -- not
> what
> | I really consider bug reports.
> |
> the biggest improvement to bug-buddy from an end-user's point is how in the
> heck
> are we supposed to know if the bug has already been reported or not? We're
> supposed to check the website and browse around for ages looking for it.
> It'd
> be ideal if we choose the (like we currently do in bug-buddy) the app and
> what
> specific category and then have a web-link taking us to that area on the
> website
> when we can quickly glance whether it's been reported or not.
>
> ___________________________________________
> adam http://www.kaikun.org 4,000+ photos
> ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ
>
> _______________________________________________
> Nautilus-list mailing list
> Nautilus-list lists eazel com
> http://lists.eazel.com/mailman/listinfo/nautilus-list
>
> _______________________________________________
> Nautilus-list mailing list
> Nautilus-list lists eazel com
> http://lists.eazel.com/mailman/listinfo/nautilus-list
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]