Calendar:Bugzilla Components:Goals

Goals for Calendar-Project Bugzilla categories and their names

Separate ownership: category owners receive less bug mail: One reason to have categories is to reduce the bug mail received by the owner of each category. Delegating ownership for a component is one reason to create a separate category for it.
Separate parallel components: contributors can filter unrelated bugs: A second reason to have categories is so bugs with similar descriptions can be differentiated. While working on, say the ICS calendar provider, a contributor may want to see other bugs on that component that might be related, and suppress bugs on parallel components, such as the local storage provider, that might have similar summary descriptions. Similarly, lightning and sunbird menu bugs may be in separate categories.
Separate contributor skills: contributors can filter bugs outside their expertise: A third reason to have separate categories is to make it easier for contributors to find bugs on which they can contribute. It often makes sense to put components written in different languages (html doc, css themes, JS/xul/xbl, C++/idl, sql, pl/sh/make,...) in different categories, so contributors can suppress bugs in areas outside their expertise. (However, note that some calendar components are implemented partly with several languages, such as a JS wrapper around a C++/idl core.)

Reporters understand categories: When a user reports a bug, which category fits the bug should be clear to the user reporting the bug.
This reduces work (and bug mail) triaging bugs in the wrong category, and improves the signal to noise ratio when searching for bugs by category.
For the this goal it would be nice to have categories based on end-user functionality, such as Display, Reminders, Networking, Import/Export.
(Negative example: categories based on what directory holds the implementation of a feature, which a user has no way to know.)
Reporters find best category: Related names can group closely related components such as provider: Local Storage, provider: CalDAV, provider: WebDAV/ICS, so a user can easily find and choose the correct one rather than stopping at a related category that seems close enough.