This bug is for tracking feedback and suggestions for this page.
I shouldn't be a necko QA contact for anything... You need to split out OPEN bugs form RESOLVED-but-not-VERIFIED, so that the counts are vaguely accurate.
I'll do a search-and-destroy for any bugs that you are qa assigned. The approach was to start from the very top of the bug totals and go downward. I invented the term "Open" to measure total amount of work needed. I'll be trying to create query categories that are more task/role oriented soon.
page is not linked from http://www.mozilla.org/quality/ can you also reformat the page to be more consistent w/ other QA home pages?
I'm trying to keep more status and current info on this page. That is not what I would say is the typical Netscape QA style of operating, but it has worked well for me thus far. This page is pretty consistenly updated, and has this format because I found the other QA pages were good as indexes, but were not really current or relevant. If you want to suggest a re-write, I'd be glad to get suggestions. If you feel there is a serious consistency problem, someone on mozilla staff needs to tell me to get in line. I'm seriously busy (see that row of bug totals at the top?), because I used to share that w/ someone, now it's just me. re #1: bradley - I've begun to consider doing that. Before I wanted to reflect bug totals, but now I care more about my verification list and less about the unfixed bug count. But I was trying to run as few regular queries as possible, so that was the original compromise.
Hmm, the page was last updated 2003-12-12 05:32. I guess I can make the page match the mozilla.org Markup Reference and Styleguide if you like.
Done. Do we still need this bug? Users can file bugs themselves if they think that page is not good.
I like to keep the feedback loop ope. It is sort of a home page for the work I have been doing. In the past, I have found, on other pages I maintain, that this gets more feedback than assuming readers know they can file in bugzilla. It also keeps the number of doc bugs lower.
This content has recently been archived. If this needs to be migrated back to a production site, I'd recommend posting it on QMO or MDC. Closing as wontfix.
RIP. I haven't been able to updated it for some time. I'm going to be spending the little time I have on doing MDC documentation, and less QA.