\define{versionidfeedback} \versionid $Id$
-\A{feedback} Feedback and bug reporting
+\A{feedback} \ii{Feedback} and \i{bug reporting}
This is a guide to providing feedback to the PuTTY development team.
It is provided as both a web page on the PuTTY site, and an appendix
(\k{feedback-support}) are probably better sent to newsgroups, or
passed to a local expert if possible.
-The PuTTY contact email address is a private mailing list containing
+The PuTTY contact email address is a private \i{mailing list} containing
four or five core developers. Don't be put off by it being a mailing
list: if you need to send confidential data as part of a bug report,
you can trust the people on the list to respect that confidence.
\b Check the
\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/changes.html}{Change
Log} on the PuTTY website, and see if we have already fixed the bug
-in the development snapshots.
+in the \i{development snapshots}.
\b Check the
\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/faq.html}{FAQ}
report a bug to us, it is useful if you include some general
information:
-\b Tell us what version of PuTTY you are running. To find this out,
-use the "About PuTTY" option from the System menu. Please \e{do not}
-just tell us \q{I'm running the latest version}; e-mail can be
+\b Tell us what \i{version of PuTTY} you are running. To find this out,
+use the \q{About PuTTY} option from the System menu. Please \e{do
+not} just tell us \q{I'm running the latest version}; e-mail can be
delayed and it may not be obvious which version was the latest at
the time you sent the message.
have done, and exactly what it did do.
\b If you think you can, you're welcome to try to fix the problem
-yourself. A patch to the code which fixes a bug is an excellent
+yourself. A \i{patch} to the code which fixes a bug is an excellent
addition to a bug report. However, a patch is never a \e{substitute}
for a good bug report; if your patch is wrong or inappropriate, and
you haven't supplied us with full information about the actual bug,
way to get a feature implemented quickly, if it's a big one that we
don't have time to do ourselves.
-\H{feedback-support} Support requests
+\H{feedback-support} \ii{Support requests}
If you're trying to make PuTTY do something for you and it isn't
working, but you're not sure whether it's a bug or not, then
\H{feedback-webadmin} Web server administration
-If the PuTTY web site is down (Connection Timed Out), please don't
+If the PuTTY \i{web site} is down (Connection Timed Out), please don't
bother mailing us to tell us about it. Most of us read our e-mail on
the same machines that host the web site, so if those machines are
down then we will notice \e{before} we read our e-mail. So there's
\H{feedback-mirrors} Mirroring the PuTTY web site
+\#{This paragraph also in putty-website/mirrors.html}
Mirrors of the PuTTY web site are welcome, especially in regions not
-well covered by existing mirrors. Please don't bother asking us for
-permission before setting up a mirror. You already have permission. We
-are always happy to have more mirrors.
+well covered by existing mirrors. (However, if you're in a region that is
+already well served by mirrors, you should consider whether yet another one
+will be worth the effort.) Please don't bother asking us for permission before
+setting up a mirror. You already have permission.
If you mail us \e{after} you have set up the mirror and checked that
it works, and remember to let us know which country your mirror is in,