> All of the ideas are excellent. Concerning the bugs
> specifically, is there a way the current bugzilla could sort or categorize bugs so that
> they are loosely grouped by the discipline needed to fix them? For those that
> don't require an in-depth level of c++ knowledge, etc., it may help those
> willing to help wade through and find something they could handle.

Users can use the category header links to sort a list. There also is the advanced search.

Users can create and save various types of queries. I created one long ago but haven't spent much time exploring how to create killer queries. We probably could create some extensive queries and then provide links in the bugzilla header. Those new queries likely would provide what you ask.

Perhaps we all could take a look at creating various queries and then posting them to share.

> The submit patch, then review/approve is a great safeguard,
> but the review/approve still puts a significant demand on the
> reviewer/approver :)

Possibly, but right now there is no feedback whatsoever, which is my primary goal. As a somebody who has posted many bug reports and enhancement requests, if I were not on the team helping I'd be left wondering whether there is any action in Trinity development. Not good public relations or image. Tim is only one person and can't do everything. If users expect that he can or will then this project won't last. :(

> It would even be a help if those who know/review the current
> active bugs could dump a list of "need help with this" to help prioritize
> which should be attacked first.

I could select a dozen or two reports that people other than Tim likely could help resolve.

Many of the bug reports do not require years of C++ and Qt experience. I accept that everybody has busy lives, but a quiet commitment of helping with one or two bugs per week probably is not asking much.

I want Trinity to continue and succeed. Improving the feedback mechanism improves our image. I wonder how users feel about reports they filed long ago and have yet to receive a response? How do non team members know anything is happening or why their reports receive no attention?

Darrell