First, I think it's great (and really appreciate) that links to the Bug Writing Guidelines are starting to appear where folks will notice it, *before* writing up bugs. I would suggest that the language used when referencing the bug writing guideslines be less passive and wimpy. ;) For example, on http:// www.bugzilla.org: "Read the Bug Reporting Guidelines for other tips on writing clear bug reports that lead to bug fixes." My understanding is that perception among Mozilla QA is that the bug writing guidelines do not merely comprise _tips_ on writing clear bug reports that get looked at. Rather, they comprise _how_ contributors should be writing bug reports if they'd like them to be given serious and prompt attention, period. (Barring white box/ code-level issues.) Perhaps if it were stated more directly, more people might get the message? e.g. "Read the Bug Reporting Guidelines to learn how to write bug reports that get fixed."

Doh. swap 'www.bugzilla.org' with 'bugzilla.mozilla.org'

Our bug reporting guidelines explain how to write clear bug reports that lead to fixed bugs. also moved this item to the second position after the item to consult the list of requently reported bugs.

Looks good..thanks! marking Verified.

Re-opening. Matthew, I knew I should have mentioned this to you before you checked in your new page, but spaced on it. Could you please replace the text with Dawn's text? (I think it could still be more direct/assertive/jwz-like-bordering-on-annoying ;), e.g. "Our bug reporting guidelines explain how to write clear bug reports that lead to fixed bugs. Read them. <B>Follow them.</B>")

[For the innocent bystanders, it was in fact fixed when Jan verified it. However, the Bugzilla page was shortly thereafter replaced by a new, spiffier one crafted by Matthew, which didn't contain the altered text.]

As I've said elsewhere, I think appealing to enlightened self-interest works better than barking out orders. So how about: "... If you follow these simple guidelines, you allow us to help you, and process your bug report quicker. Mozilla QA has limited resources."

I think it's clear enough, and further ranting belongs on the bug reporting page itself. I'm tempted to mark this as a dup of bug 16546.

Err, more specifically, Dawn changed the Bugzilla page to say: "Read the Bug Reporting Guidelines to learn how to write bug reports that get fixed." rather than what it says now, which is roughly what it used to say before Dawn changed it: "Read the bug reporting guidelines for tips on writing clear bug reports that lead to bug fixes." As explained in the bug report. As stated above: "My understanding is that perception among Mozilla QA is that the bug writing guidelines do not merely comprise _tips_ on writing clear bug reports that get looked at. Rather, they comprise _how_ contributors should be writing bug reports if they'd like them to be given serious and prompt attention, period. (Barring white box/ code-level issues.)" Thanks.

I changed the text back to my original fix.

Doh. I feel stupid. I pasted the wrong text in the 11.24.99 comment Re: what Dawn had changed it to; instead of pasting her altered text, I supplied my unedited text. I'm not going to re-open this bug and bother Dawn again, but if she feels like changing it, I won't protest.

Moving to Bugzilla product