[IMC-NYC-Editorial] how to write a useful bug report

[mike castleman]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

if you notice a problem with the site, it would aid immensely in fixing 
the problem if you be sure to include three things:

1. what you did
2. what happened as a result
3. what you expected to happen instead

other potentially useful information includes if the problem is new or
if you've seen it before, and if you can reliably reproduce the problem
or if it only happens sometimes. if the problem is a layout or display 
issue (that is, the site comes up but doesn't look right), it might be 
helpful to know what web browser and operating system you are using.

if you have an idea as to what might be causing the problem, please 
include it, but do not omit the information requested above.

one-line messages that just say "things don't work right!" are rarely 
useful.

love,
mike

p.s. this is generally good advice for reporting problems with
non-indymedia websites, too, if you do that sort of thing.

- -- 
mike castleman, m at mlcastle.net
http://mlcastle.net/ - tel:+1-646-382-7220
students for an orwellian society: http://www.studentsfororwell.org/
because 2004 is 20 years too late.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBhrS1rbXc6n5AevkRAnUpAJ9ROjhADD5s/kHubSYN1lwbskzHUwCfbp+2
BiG3CyoQlXCbZZz0/wAxXvA=
=syle
-----END PGP SIGNATURE-----