1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
8 CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
10 TITLE="Privoxy Developer Manual"
11 HREF="index.html"><LINK
13 TITLE="Privoxy Developer Manual"
14 HREF="index.html"><LINK
16 TITLE="The Git Repository"
20 HREF="../p_doc.css"><META
21 HTTP-EQUIV="Content-Type"
23 charset=ISO-8859-1"></HEAD
34 SUMMARY="Header navigation table"
43 >Privoxy Developer Manual</TH
91 HREF="https://www.privoxy.org/user-manual/copyright.html"
98 > development is potentially open
99 to anyone who has the time, knowledge, and desire to contribute
100 in any capacity. Our goals are simply to continue the mission,
105 to make it available to as wide an audience as possible.
108 > One does not have to be a programmer to contribute. Packaging, testing,
109 documenting and porting, are all important jobs as well.
117 >1.1. Quickstart to Privoxy Development</A
120 > The first step is to join the <A
121 HREF="https://lists.privoxy.org/mailman/listinfo/privoxy-devel"
123 >privoxy-devel mailing list</A
125 You can submit your ideas or, even better, patches.
126 Patches can also be submitted to the
128 HREF="https://sourceforge.net/p/ijbswa/patches/"
130 >Sourceforge patch tracker</A
134 > You will also need to have a git package installed,
135 in order to access the git repository.
136 Having the GNU build tools is also going to be important (particularly,
140 > For the time being (read, this section is under construction), you can
141 also refer to the extensive comments in the source code. In fact,
142 reading the code is recommended in any case.
151 SUMMARY="Footer navigation table"
190 >Privoxy Developer Manual</TD
200 >The Git Repository</TD