Gregory Pittman wrote: > Cedric Sagne wrote: > >> I am actually thinking of writing a white paper on problem determination >> (technical support training). Do you guys think it would be good as "what to >> do when you have found a bug?" in the bug tracker intro? >> >> > Sounds like a great idea for the Wiki. > To expand on what I just said, some elements that I think need to be addressed would be: 1. How to know whether you have a bug vs. something else, + the related, how to know whether what you have is a Scribus bug or someone else's. 2. Searching the bug tracker to see if it's already been reported -- some hints about how to search efficiently would be helpful. 3. Knowing your setup, ie, what is your platform, Scribus version, other pertinent features you need to report. 4. How/where to ask for help with all of this.
Greg
