Bugzilla components proposal

This table is a proposed list of changes to Chandler's bugzilla components, as of the 0.7 timeframe. We hope this list doesn't change radically from release to release, but changes will happen as we continue to get the design and the architecture in place.

• Full list of current bugzilla components with descriptions.

I'm assuming these goals for bugzilla components:

• bugzilla components should be long-lived (not release or tenet specific)
• bugzilla components should be consistent with the architecture document, using the same terminology
• we do not need to maintain a 1:1 mapping to python modules, packages or eggs
• large buckets are good (easier to categorize)
• limiting the # of buckets is good (again, easier to categorize)
• pieces of ui that users can identify should be represented here (end users will pick these when logging bugs, if they make any attempt to classify the bug)
• not all bugzilla components need to map to ui, as these components serve multiple needs
• bugzilla components should be consistent with current owners/drivers (as per governance model)