2 File : $Source: /cvsroot/ijbswa/current/doc/source/contacting.sgml,v $
4 Purpose : Entity included in other project documents.
6 $Id: contacting.sgml,v 2.12 2007/11/19 17:31:05 fabiankeil Exp $
8 Copyright (C) 2001-2008 Privoxy Developers http://www.privoxy.org/
11 ======================================================================
12 This file used for inclusion with other documents only.
13 ======================================================================
15 This file is included into:
27 <!-- Careful of the literallayout tags and finished formatting -->
30 We value your feedback. In fact, we rely on it to improve
31 <application>Privoxy</application> and its configuration.
32 However, please note the following hints, so we can
33 provide you with the best support:
36 <sect2 id="contact-support"><title>Get Support</title>
39 <ulink url="http://sourceforge.net/tracker/?group_id=11118&atid=211118">support forum at SourceForge</ulink>
40 is probably best suited:
41 <ulink url="http://sourceforge.net/tracker/?group_id=11118&atid=211118">http://sourceforge.net/tracker/?group_id=11118&atid=211118</ulink>
45 All users are of course welcome to discuss their issues on the <ulink
46 url="http://lists.sourceforge.net/lists/listinfo/ijbswa-users">users
47 mailing list</ulink>, where the developers also hang around.
51 Note that the Privoxy mailing lists are moderated. Posts from unsubscribed
52 addresses have to be accepted manually by a moderator. This may cause a
53 delay of several days and if you use a subject that doesn't clearly
54 mention Privoxy or one of its features, your message may be accidentally
59 If you aren't subscribed, you should therefore spend a few seconds
60 to come up with a proper subject. Additionally you should make it clear
61 that you want to get CC'd. Otherwise some responses will be directed to
62 the mailing list only, and you won't see them.
67 <sect2 id="reporting"><title>Reporting Problems</title>
69 <quote>Problems</quote> for our purposes, come in two forms:
75 Configuration issues, such as ads that slip through, or sites that
76 don't function properly due to one <application>Privoxy</application>
77 <quote>action</quote> or another being turned <quote>on</quote>.
83 <quote>Bugs</quote> in the programming code that makes up
84 <application>Privoxy</application>, such as that might cause a crash.
90 <sect3 id="contact-ads"><title>Reporting Ads or Other Configuration Problems</title>
92 Please send feedback on ads that slipped through, innocent images that were
93 blocked, sites that don't work properly, and other configuration related problem of
94 <filename>default.action</filename> file, to
95 <ulink url="http://sourceforge.net/tracker/?group_id=11118&atid=460288">
96 http://sourceforge.net/tracker/?group_id=11118&atid=460288</ulink>,
97 the Actions File Tracker.
101 New, improved <filename>default.action</filename> files may occasionally be made
102 available based on your feedback. These will be announced on the <ulink
103 url="http://lists.sourceforge.net/lists/listinfo/ijbswa-announce">ijbswa-announce</ulink>
104 list and available from our the <ulink
105 url="http://sourceforge.net/project/showfiles.php?group_id=11118">files section</ulink> of
106 our <ulink url="http://sf.net/projects/ijbswa/">project page</ulink>.
111 <sect3 id="contact-bugs"><title>Reporting Bugs</title>
113 Please report all bugs through our bug tracker:
114 <ulink url="http://sourceforge.net/tracker/?group_id=11118&atid=111118">http://sourceforge.net/tracker/?group_id=11118&atid=111118</ulink>.
118 Before doing so, please make sure that the bug has <emphasis>not already been submitted</emphasis>
119 and observe the additional hints at the top of the <ulink
120 url="http://sourceforge.net/tracker/?func=add&group_id=11118&atid=111118">submit
121 form</ulink>. If already submitted, please feel free to add any info to the
122 original report that might help to solve the issue.
126 Please try to verify that it is a <application>Privoxy</application> bug,
127 and not a browser or site bug or documented behaviour that just happens
128 to be different than what you expected. If unsure,
129 try <ulink url="http://config.privoxy.org/toggle?set=disable">toggling
130 off</ulink> <application>Privoxy</application>, and see if the problem persists.
134 If you are using your own custom configuration, please try
135 the stock configs to see if the problem is configuration related.
136 If you're having problems with a feature that is disabled by default,
137 please ask around on the mailing list if others can reproduce the problem.
141 If you aren't using the latest Privoxy version, the bug may have been found
142 and fixed in the meantime. We would appreciate if you could take the time
143 to <ulink url="http://www.privoxy.org/user-manual/installation.html">upgrade
144 to the latest version</ulink> (or even the latest CVS snapshot) and verify
145 that your bug still exists.
148 Please be sure to provide the following information:
155 The exact <application>Privoxy</application> version you are using
156 (if you got the source from CVS, please also provide the source code revisions
157 as shown in <ulink url="http://config.privoxy.org/show-version">http://config.privoxy.org/show-version</ulink>).
163 The operating system and versions you run
164 <application>Privoxy</application> on, (e.g. <application>Windows
165 XP SP2</application>), if you are using a Unix flavor,
166 sending the output of <quote>uname -a</quote> should do,
167 in case of GNU/Linux, please also name the distribution.
173 The name, platform, and version of the <application>browser</application>
174 you were using (e.g. <application>Internet Explorer v5.5</application> for Mac).
180 The URL where the problem occurred, or some way for us to duplicate the
181 problem (e.g. <literal>http://somesite.example.com/?somethingelse=123</literal>).
187 Whether your version of <application>Privoxy</application> is one supplied
188 by the <application>Privoxy</application> developers via SourceForge,
189 or if you got your copy somewhere else.
195 Whether you are using <application>Privoxy</application> in tandem with
196 another proxy such as <application>Tor</application>. If so, please
197 temporary disable the other proxy to see if the symptoms change.
203 Whether you are using a personal firewall product. If so, does
204 <application>Privoxy</application> work without it?
210 Any other pertinent information to help identify the problem such as config
211 or log file excerpts (yes, you should have log file entries for each
220 You don't have to tell us your actual name when filing a problem
221 report, but please use a nickname so we can differentiate between
222 your messages and the ones entered by other "anonymous" users that
223 may respond to your request if they have the same problem or already
228 Please also check the status of your request a few days after submitting
229 it, as we may request additional information. If you use a SF id,
230 you should automatically get a mail when someone responds to your request.
234 The <ulink url="http://www.privoxy.org/user-manual/appendix.html#ACTIONSANAT">appendix
235 of the Privoxy User Manual</ulink> also has helpful information
236 on understanding <literal>actions</literal>, and <literal>action</literal> debugging.
241 <sect2 id="contact-feature"><title>Request New Features</title>
243 You are welcome to submit ideas on new features or other proposals
244 for improvement through our feature request tracker at
245 <ulink url="http://sourceforge.net/tracker/?atid=361118&group_id=11118">http://sourceforge.net/tracker/?atid=361118&group_id=11118</ulink>.
249 <sect2 id="contact-other"><title>Other</title>
251 For any other issues, feel free to use the mailing lists. Technically interested users
252 and people who wish to contribute to the project are also welcome on the developers list!
253 You can find an overview of all <application>Privoxy</application>-related mailing lists,
254 including list archives, at:
255 <ulink url="http://sourceforge.net/mail/?group_id=11118">http://sourceforge.net/mail/?group_id=11118</ulink>.