Difference between revisions of "Bug or Suggestion"
(There's an art to it.) |
m (→Bug) |
||
| Line 16: | Line 16: | ||
=Bug= | =Bug= | ||
| − | Something that is broken (not functioning as designed). | + | * Something that is broken (not functioning as designed). |
| − | Something that is broken-as-designed (is functioning as designed, but how it is designed is bad). | + | * Something that is broken-as-designed (is functioning as designed, but how it is designed is bad). |
| − | Straightforward items that do not require community discussion. | + | * Straightforward items that do not require community discussion. |
Revision as of 13:49, 21 September 2011
Dreamwidth has a few workflows for submitting items to Bugzilla. The ideal workflow to use depends on the exact situation.
Suggestion
Dreamwidth solicits a wide range of user opinions on many proposed changes before approving an item for implementation. A relatively small percentage of the active user population of Dreamwidth is comfortable using Bugzilla, compared to the users who follow the ![[info]](http://wiki.dreamwidth.net/wiki/extensions/LJ/images//dw/user.png){kind=small}
dw_suggestions community.
The following types of changes are particularly likely to be referred to the whole user community (not just staff, contractors, and developers) for discussion:
New Feature
An entirely new feature that does not currently exist.
Enhancement
Changes to improve an existing feature.
Preferred Implementation
Some new features, enhancements, and outright bug fixes require a decision about how best to do it out of two or more possible ways. The dw_suggestions participants can also provide feedback for this.
Bug
- Something that is broken (not functioning as designed).
- Something that is broken-as-designed (is functioning as designed, but how it is designed is bad).
- Straightforward items that do not require community discussion.
