First, congradulations Terry and Sam for an outstanding piece of software. Still getting to know it, but love it already. To business: A nice enhancement of Bugzilla would be to include the bug-writing-guidelines.html in the release. Bugzilla is kinda slight on documentation. IMHO ;-) It's up to you. Related bug: 4456

The problem is that that file is very specific to mozilla.org. Many of the things there would not apply to other installations.

Terry, before I rubber-stamp this as Verified/WONTFIX, I'd be happy to submit a generalized version of the bug writing guidelines (on my own time, of course) if you have an idea of what bug report content other bugzilla installations require. Or mhamby@logicon.com, if you feel like doing it...

No follow-up received from Terry from 1.18.00 offer to generalize bugwriting guidelines for Bugzilla; thus, rubber-stamping as Verified/WONTFIX.

Sorry I didn't respond. Of course I would like generic instructions. I don't have any good data for you on what other installations require, though. The directions need to be as generic as possible. Which maybe makes them useless, I dunno.

When I wrote this bug, I think I was referring to the fairly good set of instruction pages about Bugzilla located at http://www.mozilla.org/bugs and http://www.mozilla.org/quality/bug-writing-guidelines.html. I am requesting that these pages be included into Bugzilla distribution. 'As is' is better than not at all. I understand the configuration issues and all, but I am primarily thinking of other sites who want to use Bugzilla and would be modifying these files slightly any way. IMHO, once again.

It's just that this file has lots of references to sample bugs on our system, and guidelines for the Mozilla project, and things like that. But hacking all that stuff out of that page is probably a good idea.

terry, if you'd like me to sanitize the bug-writing-guidelines to remove the items you mention, just assign this bug to me and I'll do it on my own time at home.

[I didn't write the bugs.html document, and I'd rather not modify it, since I'd end up rewriting half the thing to improve the structure/style/etc.]

OK, it's a deal!

Initial document draft posted to netscape.public.mozilla.webtools for feedback.

Second, and expected to be final, document draft posted to netscape.public.mozilla.webtools.

checked into the trunk. zach, reassigning to you to figure out a good place to link to this document. the main index page perhaps?

Accepting bug. I think I will link from the index page, and link from the default header on the enter_bug.cgi page (set in defparams.cgi, maybe it's .pl) I can't do it right now (computer problems) but it should be done in the next few days.

actually, it's in the enter bug page. is that okay for you?

I think it's better in the defparams file, that way people with tweekparams can change it if they don't like it. Attaching patch in a minunte.

umm. DUH! How stupid of me. After looking at the code, I realized that it is in defparams.pl which is referenced by enter_bug.cgi. Marking fixed

Verified fixed.

In search of accurate queries.... (sorry for the spam)

Moving closed bugs to Bugzilla product