- <h2 class="SECT2"><a name="QUICKSTART" id="QUICKSTART">1.1. Quickstart
- to Privoxy Development</a></h2>
-
- <p>The first step is to join the <a href=
- "mailto:ijbswa-developers@lists.sourceforge.net" target=
- "_top">developer's mailing list</a>. You can submit your ideas, or even
- better patches. Patches are best submitted to the Sourceforge tracker
- set up for this purpose, but can be sent to the list for review
- too.</p>
-
- <p>You will also need to have a cvs package installed, which will
- entail having ssh installed as well (which seems to be a requirement of
- SourceForge), in order to access the cvs repository. Having the GNU
- build tools is also going to be important (particularly, autoconf and
- gmake).</p>
-
- <p>For the time being (read, this section is under construction), you
- can also refer to the extensive comments in the source code. In fact,
- reading the code is recommended in any case.</p>
+ <h2 class="SECT2"><a name="QUICKSTART" id="QUICKSTART">1.1. Quickstart to Privoxy Development</a></h2>
+ <p>The first step is to join the <a href="https://lists.privoxy.org/mailman/listinfo/privoxy-devel" target=
+ "_top">privoxy-devel mailing list</a>. You can submit your ideas or, even better, patches. Patches can also be
+ submitted to the <a href="https://sourceforge.net/p/ijbswa/patches/" target="_top">Sourceforge patch
+ tracker</a>.</p>
+ <p>You will also need to have a git package installed, in order to access the git repository. Having the GNU
+ build tools is also going to be important (particularly, autoconf and gmake).</p>
+ <p>For the time being (read, this section is under construction), you can also refer to the extensive comments in
+ the source code. In fact, reading the code is recommended in any case.</p>