![[PukiWiki]](skin/logo.png "[PukiWiki]"){kind=logo}
* Bug Reports [#v6e1b2cd] Before you report a bug, please search for existing bugs using the [[hts-users mailing list query page>Mailing List#Archives]]. If that fails, please send a report to the [[hts-users mailing list>Mailing List]]. We try to respond to most bug reports, but if we don't, it doesn't mean we are ignoring you; it may well be that the bug has been reported before. Some bugs are fixed quickly, some take a long time to get fixed. Please be patient if your bug is not acted upon quickly. > Before you report a bug, please search for existing bugs using the [[hts-users mailing list query page>Mailing List#Archives]]. If that fails, please send a report to the [[hts-users mailing list>Mailing List]]. We try to respond to most bug reports, but if we don't, it doesn't mean we are ignoring you; it may well be that the bug has been reported before. Some bugs are fixed quickly, some take a long time to get fixed. Please be patient if your bug is not acted upon quickly. Because HTS working group members are busy, the quality of your bug report can make a big difference in how soon your bug gets fixed. Following a few simple guidelines helps us to help you. Here are some resources on how to write a good bug report: > Because HTS working group members are busy, the quality of your bug report can make a big difference in how soon your bug gets fixed. Following a few simple guidelines helps us to help you. Here are some resources on how to write a good bug report: - Eric Raymond's and Rick Moen's [[How To Ask Questions The Smart Way:http://www.catb.org/~esr/faqs/smart-questions.html]] - mozilla.org's [[bug writing guidelines:http://www.mozilla.org/quality/bug-writing-guidelines.html]] - Simon Tatham's [[How to Report Bugs Effectively:http://www.chiark.greenend.org.uk/~sgtatham/bugs.html]]
