Oops, quite forgot about that: On Tue, May 8, 2012 at 1:52 PM, Anne-Marie Mahfouf <[email protected]> wrote: > On 05/06/2012 10:19 PM, David Edmundson wrote: >> >> On Thu, May 3, 2012 at 2:37 PM, Anne-Marie Mahfouf >> <[email protected]> wrote: >> >>> > On 05/03/2012 01:42 PM, Martin Gräßlin wrote: >>>> ... >> >>> > - when can we train the testers? will we do some IRC training? I think >>> > the >>> > emphasis should go on the steps to reproduce the bug. What existing >>> > material >>> > do we have to start with in the forums? >> >> We should start a guide "Bugzilla for testers" (as opposed to >> developers). This will be be useful forever, and I'm sure there's a >> lot of content out there already. >> >> Useful existing information/guides that we should link to/copy bits from: >> >> >> http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports >> https://wiki.kubuntu.org/Kubuntu/Bugs/Reporting (has some Kubuntu >> specific parts, but the topic "how to write good reports" is still >> valid) >> http://aseigo.blogspot.co.uk/2009/01/bugskdeorg.html >> >> http://itscommonsensestupid.blogspot.co.uk/2008/07/tips-to-write-good-bug-report.html
I wrote a blog about that as well: http://blogs.fsfe.org/myriam/2011/10/when-is-a-bug-report-useful/ it has quite a few links at the bottom that are useful. Regards, Myriam -- Proud member of the Amarok and KDE Community Protect your freedom and join the Fellowship of FSFE: http://www.fsfe.org Please don't send me proprietary file formats, use ISO standard ODF instead (ISO/IEC 26300) _______________________________________________ Kde-testing mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-testing
