Two forked copies of bug writing guidelines

--===============1695731771==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="PNTmBPCT7hxwcZjr"
Content-Disposition: inline


--PNTmBPCT7hxwcZjr
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

I just discovered we have two copies of the bug writing guidelines:

https://bugzilla.mozilla.org/page.cgi?id=3Dbug-writing.html
http://developer.mozilla.org/en/docs/Bug_writing_guidelines

and different people have been making improvements on each copy.  We
should probably try to merge these improvements (and make more).

(One of them still suggests putting stack traces and logs in the
comments field, rather than in attachments!)

This is a pretty important document, and I think some of the
problems in it lead to repeated problems in Bugzilla that could be
easily avoided.


Where *should* the bug writing guidelines live?  (And how would one
edit the copy on bugzilla.mozilla.org if that's the chosen
location?)

-David

--=20
L. David Baron                                <URL: http://dbaron.org/ >
           Technical Lead, Layout & CSS, Mozilla Corporation

--PNTmBPCT7hxwcZjr
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFF8ga2A17gpBIYPJsRAi0IAJ4mWlsTPbTsL0BmOV5ERbzRLAdZkACbBVkT
G+p0MOYJYChB/AyPD4DLmZQ=
=gYfC
-----END PGP SIGNATURE-----

--PNTmBPCT7hxwcZjr--

--===============1695731771==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
dev-documentation mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-documentation

--===============1695731771==--