[Dev] bugzilla components proposal

[Katie Capps Parlante]

I think now is a good time to revisit bugzilla components: we're in the 
early stages of a release, we know a lot more about the design as well 
as the architecture of the app, etc.

Working with Philippe and others, we came up with a proposal:
http://wiki.osafoundation.org/bin/view/Projects/BugzillaComponentsZeroPointSeven

The wiki page includes a table listing all existing components + 
suggested changes, as well as proposed new components.

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)

Some components are not active (e.g. agent framework, simple canvas). It 
would be great to remove these components, but the bugs need to be 
dumped somewhere. Can we create one catchall to limit the number of 
extraneous historical categories, "historical" or something like that?

Please take a moment to review the list and send feedback if you have 
any -- it would be great to get this ironed out on the wiki before we go 
make the changes.

Cheers,
Katie