101
edits
Calendar:Bugzilla Components:Goals: Difference between revisions
Calendar:Bugzilla Components:Goals (view source)
Revision as of 03:40, 7 October 2005
, 7 October 2005add Establish component names
((wikify headings, add "who uses categories?")) |
(add Establish component names) |
||
| Line 9: | Line 9: | ||
<dl> | <dl> | ||
<dt id="establish-component-names">Establish component names: bug | |||
searchers and filers can choose from component list rather than guess | |||
key words.</dt> | |||
<dd>Without component categories, component bugs are filed under many | |||
variant names. For example, task list bugs may be titled "task" or | |||
"todo" or "to-do", with "unifinder" or "list" or "table" or "tree". | |||
Reporters guess only one or two of the variations and miss duplicate | |||
bugs. Even experienced developers that know all the variations must | |||
make multiple searches to return all the bugs. | |||
With component categories, the component list gives reporters a menu | |||
of established component names. New bugs will be filed under an | |||
established component name. Searches more reliably return all the | |||
related component bugs, especially for reporters who didn't know the | |||
established name before. (When previous reports are found, new | |||
contributors can spend their time building on knowledge of an existing | |||
bug, rather than filing a report only to be later discouraged to find | |||
that they didn't know enough even to find the previous report, and | |||
wasted their time filing a duplicate.) | |||
</dd> | |||
<dt id="separate-parallel-components">Separate parallel components: | <dt id="separate-parallel-components">Separate parallel components: | ||