[ham] Goals for 2.22?

[David Miller]

Kevin Benton wrote:

> What I do to help me plan overall decisions that aren't necessarily
> time-based is to use a 7-habits method of priority setting.  It's a two-part
> prioritization method that categorizes priorities based on urgency and
> importance, then task sequence.

Bugzilla does provide ways to indicate this on the bugs, by way of the 
priority and severity fields.  And this is indeed a great way to 
prioritize the work, but as with many open source projects, getting 
people to work on the high priority bugs isn't always easy.  Very few 
people are paid to hack Bugzilla, and most folks will attack bugs that 
are easy to fix or that they have a personal interest in, and even 
though much of the community agrees that "issue A" is a really high 
priority, everyone avoids it like the plague because it's difficult to 
implement.

Some classic examples:  enforcing a character set (which in itself is 
easy, but upgrading an existing system is a very complex problem) and 
email address privacy.

That said, just because we have trouble getting people to work on the 
high-priority issues doesn't mean we should give up on it.  Perhaps we 
just need to change the tactics of how we solicit help for such things. 
  Perhaps a web page containing a list of high-priority bugs which are 
not getting enough attention, to let people know that just because we 
have a bug on the issue doesn't mean it's being worked on?

-- 
Dave Miller      Project Leader, Bugzilla Bug Tracking System
http://www.justdave.net/             http://www.bugzilla.org/