As well as the mechanism for automatically resolving some UNCONFIRMED bugs, mentioned in an earlier blogpost, we have some other ideas for trying to improve Bugzilla before the Firefox/Thunderbird 1.0 hurricane hits us.
- Build a “feedback webtool”, like Netscape’s, which feeds directly into a newsgroup or forum. This is to try and divert rants, support requests and other non-bugs away from Bugzilla. Asa and Kerz are working on this.
- Build a “Report a broken site” webtool which aggregates problem URLs and produces lists and reports, rather than having one bug per report. Robert Accettura is doing the hard work for us here.
- Redesign the b.m.o. front page to include links to these two tools and a better community link. I’ve done this; it’ll go live when the two webtools are online.
- Redo Bugzilla Helper to be clearer and have less text. Stop accepting bugs in anything other than the latest release.
- Change the search people do before filing bugs to search all bugs (including resolved ones) filed in the last two months, and use Myk’s “find a specific bug” feature to get better relevance.
- We currently have much more active people in the forums than Bugzilla. Try and convert more forum participants into QA triagers. Suggestions for how to do this are welcome. I think we need a good document which we can publicise. This one is OK but needs work.
- Give more people the “canconfirm” privilege by publicising how to get it more widely. Get triagers to suggest candidates based on good bug reports they’ve seen. (Some have suggested giving it to everyone by default.)
- Get some of the webtool-writing crew Blake recruited to to write tools to mine the database and suggest likely duplicates.
- Add a READY state which goes between NEW and ASSIGNED. Bugs move to READY when they could be picked up and fixed without further work. So they are clear, have steps to reproduce, and a testcase if applicable.
- Reorder the product list page to put Firefox and Thunderbird at the top.
- Check the b.m.o. Referer logs to see who links to us, and get the top ones to relink directly to the support pages.
What do you think? I’ve numbered them this time for ease of reference :-)
Other suggestions are welcome – please give them a number too, starting after mine. Remember, we are looking for low effort, low disruption, high impact. So blue-sky Bugzilla feature suggestions probably won’t fly.