dwx wrote:
> Minh Truong wrote:
> 
>> I think that the best way to reduce duplicates is to link/list 
>> summaries of bugs together. For example, the summary of bug A is 
>> "[RFE]linking and delinking tabs and windows." A duplicate bug (B) has 
>> the summary of "docking and undocking windows and tabs." Everyone word 
>> each summary differently and that is the reason why duplicates are 
>> hard to find to the novice user. So Bugzilla should add a second line 
>> to the summary in Bug A that contains the summary from bug B. The is a 
>> finite number of permutation of wording. Over time, as Bug A's summary 
>> gets longer, it will turn up more positive results in a search. Thus, 
>> reducing duplicates. Also, we could make a search mandatory before 
>> filing a bug.
>>
>> What do you guys think?
>>
> I disagree, and I think these RFEs are irrevelent to my system. What I
> want is to create a *supporting* system of procedures, guidelines, tools,
> and supporting personels to support Mozilla developers in existing
> communication forums (Bugzilla, newsgroup, etc.) Instead of changing these
> forums, I want to change the way we communicate.

Stop dissing my puny wishlist project. :-p
Anyway, I wasn't talking about RFE, I was talking about all bugs in 
general. I just happen to use an RFE as an example because I'm partial. 
double :-p

> Now as part of the proposed supporting system, we could instead
> rephrase summaries of active bugs to make them easier to search.
> We should remove garbages that could turn up in irrevelent search
> queries. When appropriate, we should also add alternative terms
> (e.g. "dropdown list (combobox)" and "popup menu (context menu)").

I agree with you on that :).

-- 
http://wishlist.mozdev.org - Wishlist FAQ Project
Please visit and contribute.


Reply via email to