[Adium-devl] Issue reporting good practices (was: AIM problems)
Chris Forsythe
chris at growl.info
Fri Jan 26 20:46:37 UTC 2007
The users that tend to need this usually don't read stickies.
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.
>
>Andre
>
>Christopher Forsythe <chris at adiumx.com> wrote:
>
>
>>On Jan 25, 2007, at 10:04 PM, Colin Barrett wrote:
>>
>>
>>
>>>We have been getting a lot of emails from users saying that there have
>>>been problems with AIM. We don't know what it is yet, sadly. Should I
>>>go ahead and write up a blog post about how to help us debug this?
>>>(basically, the steps we've been telling people to follow on
>>>feedback@)
>>>
>>>
>>>
>>A blog post at least telling people that we know about it might help.
>>I'm busy deleting the 20ish spam comments Eric found in one of the
>>posts, so if you get any errors it might be due to that (I wouldn't
>>put it past blogger)
>>
>>
>>
>>>In general though, I think the quality of the reports we've been
>>>getting on feedback@ has been really low. Where are users getting that
>>>email address from? Can we gateway it to give some instructions on
>>>what sort of information to include in a good feedback report?
>>>
>>>
>>It seems to be normal to be honest. However, help/send feedback is
>>probably where a large majority of it comes from.
>>
>>Chris
>>
>>
More information about the devel
mailing list