Calendar Talk:Bugzilla Components: Difference between revisions
No edit summary |
m (link to establish component names) |
||
| Line 38: | Line 38: | ||
My comments: The less components, the better. More components will only create confusion, bugs moved between components, bugspam, useless comments etc. | My comments: The less components, the better. More components will only create confusion, bugs moved between components, bugspam, useless comments etc. | ||
I will see all bugs anyway. We don't have tons of very specialized developers, the devs we have will have to look at everything anyway. | I will see all bugs anyway. We don't have tons of very specialized developers, the devs we have will have to look at everything anyway. | ||
<blockquote><em>(This points out categories are not just for separation, but also for gathering bugs that might otherwise be filed under different terms. Added goal [http://wiki.mozilla.org/Calendar:Bugzilla_Components:Goals#establish-component-names establish component names]. [[User:Gekacheka|Gekacheka]] 20:59, 6 Oct 2005 (PDT))</em></blockquote> | |||
Revision as of 03:59, 7 October 2005
Process issues
Q. What happens to bugs in deleted categories?
- Are those bugs deleted?
- Are those bugs moved to another category, say General?
Q. What happens to bugs that belong in a created category?
- Are new categories empty? (ok for new components, not for reorg.)
- Will old bugs and enhancement requests be migrated into new categories immediately, or over time?
Goal Issues
Q. What are reasons for making change now?
- Provider: WebDav/ICS bugs don't fit into other categories.
- Why preference/options category now?
- Why day/week/multiweek/month view category now?
Q. What are goals for eventual categories?
- A set of proposed goals: Calendar:Bugzilla_Components:Goals
- A set of proposed eventual categories to meet these goals: Calendar:Bugzilla_Components:Proposal_By_Function
Particular component issues
Q. It's not clear what goes in 'base'? Should all UI be removed from it?
Q. Why do some UI parts/functions have separate category, while others do not?
- current proposal has separate category for preferences, and for day/week/multiweek/month view,
- but not say for list/search/filter views, date pickers, event/task dialog, nor for import/export, alarms, printing, ...
- at what time would it be appropriate to eventually add these categories?
Q. Is it ok to rename "Help Documentation" to "Web pages/documentation"?
- The category holds bugs about the web site, not the calendar online help, which is managed separately at the calendarhelp project.
Comments from mvl
My comments: The less components, the better. More components will only create confusion, bugs moved between components, bugspam, useless comments etc. I will see all bugs anyway. We don't have tons of very specialized developers, the devs we have will have to look at everything anyway.
(This points out categories are not just for separation, but also for gathering bugs that might otherwise be filed under different terms. Added goal establish component names. Gekacheka 20:59, 6 Oct 2005 (PDT))