[Adium-devl] Issue reporting good practices (was: AIM problems)

[Evan Schoenberg]

On Jan 26, 2007, at 3:44 PM, Andre-John Mas wrote:

> How about adding a sticky in the forums that describes
> what we like to see in an issue report? Maybe something
> like:
>
> Title: Issue reporting good practices
>
> Text: To help us help you better, it is important to have
> good background information on the issue, since so many
> factors can come into play. Useful information includes:
>
>  - MacOS X version
>  - PPC or Intel Mac
>  - Adium version
>  - Is it protocol specific or which protocol is affected
>    (Prototols are such things as AIM, MSN, Yahoo, Jabber, etc)
>  - What is going wrong?
>  - When did it start happening?
>  - What usually causes it?
>  - If it is a crash, then a crash log is handy
>    <some text on how to get the crash log>
>
> If is a communication error, such as MSN not connecting, then
> it is sometimes useful to see if the official client is able to
> connect.

Such specifics should be added to the ReportingBugs wiki page... I  
believe it's already stickied, for whatever that's worth.  A future  
trac enhancement could require going through the ReportingBugs page  
to get to file a ticket... though forums users are usually worse than  
trac folk with reports.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20070126/a134c2fd/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20070126/a134c2fd/attachment.sig>