[Adium-devl] Issue reporting good practices (was: AIM problems)
timber at lava.net
Sat Jan 27 01:07:34 UTC 2007
On Jan 26, 2007, at 12:58 PM, Evan Schoenberg wrote:
> 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
>> 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
> 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.
Trac isn't quite as bad. The one that gets the worst reports right now
is feedback at .
Maybe we should consider a better in-app bug reporting solution? It
might be nice to make trac editable only by developers, and have some
sort of other thing (?) where reports from inside Adium go. Kind of a
pipe dream, though :\
More practically, isn't there a way to set the body of a message with
the mailto: protocol? We could include that bug reporting information
there, when they hit "Report a bug" in Adium.
More information about the Adium-devl