<!--#include virtual="/doctype.inc" -->
<head>
<title>
- i-scream support
+ Reporting bugs
</title>
<!--#include virtual="/style.inc" -->
</head>
<!--#include virtual="/header.inc" -->
<div id="contents">
<h1 class="top">
- i-scream Support
+ Reporting bugs
</h1>
<p>
- i-scream uses <a href="http://www.bestpractical.com/rt/">RT</a>
- to track support requests. We've set up two addresses
- to help seperate the two main types of requests.
+ i-scream makes uses of the GitHub issue trackers
+ associated with our projects over on
+ <a href="http://github.com/i-scream">GitHub</a>. If you've
+ found a bug with our software that's the best place to
+ report and discuss it. If you have a fix, you can make a
+ pull request there too.
</p>
- <h3>
- bugs@i-scream.org
- </h3>
<p>
- If you have found a bug or problem with an i-scream program
- send an email to this address. Your message will be logged
- and one of the developers will get back to you with more
- information. Hopefully we'll be able to fix the bug.
+ If you want some help using one of the projects or which
+ to discuss any other issues the best place to go to is the
+ users mailing list. You can find out more about our mailing
+ lists <a href="mailinglists.xhtml">here</a>.
</p>
- <h3>
- support@i-scream.org
- </h3>
<p>
- If you have any other query, please email this address. We
- prefer to use this mechanism over emailing us directly
- because it means we can't lose your email in the rafts of
- spam we unfortunately receive.
- </p>
- <p>
- Once your email has been received you will get an
- acknowledgement by email and details of how to view your
- tickets over the web.
+ If there issue needs to remain private, for example a
+ security issue, please contact Tim directly. His details
+ are on the <a href="who.xhtml">Who We Are</a> page. This
+ should only be used in exceptional circumstances - we
+ prefer all discussion to happen on public mailing lists or
+ bug trackers where possible.
</p>
</div>
<!--#include virtual="/footer.inc" -->