X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fwebserver%2Fdeveloper-manual%2Fintroduction.html;h=c6f41714c849eb94ffb12479dcc21ae17123b3f8;hp=8900cfa4a32913bf8267454521efce0e4d15a2d8;hb=61a5d3fc15169d9f6b0c21e3a56d893f4d672eb4;hpb=659cbbc13f413ed0c5dacd4d03060f48eb500011 diff --git a/doc/webserver/developer-manual/introduction.html b/doc/webserver/developer-manual/introduction.html index 8900cfa4..c6f41714 100644 --- a/doc/webserver/developer-manual/introduction.html +++ b/doc/webserver/developer-manual/introduction.html @@ -1,206 +1,64 @@ - -Introduction
Privoxy Developer Manual
PrevNext

1. Introduction

Privoxy, as an heir to - Junkbuster, is a Free Software project. - As such, Privoxy development is potentially open - to anyone who has the time, knowledge, and desire to contribute - in any capacity. Our goals are simply to continue the mission, - to improve Privoxy, and - to make it available to as wide an audience as possible. -

One does not have to be a programmer to contribute. Packaging, testing, - documenting and porting, are all important jobs as well. -

1.1. Quickstart to Privoxy Development

The first step is to join the privoxy-devel mailing list. - You can submit your ideas or, even better, patches. - Patches can also be submitted to the - Sourceforge patch tracker. -

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). -

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. -


PrevHomeNext
Privoxy Developer Manual The Git Repository
\ No newline at end of file + + + + Introduction + + + + + + + + + +
+

1. Introduction

+

Privoxy, as an heir to Junkbuster, is a + Free Software project. As such, + Privoxy development is potentially open to anyone who has the time, knowledge, and + desire to contribute in any capacity. Our goals are simply to continue the mission, to improve Privoxy, and to make it available to as wide an audience as possible.

+

One does not have to be a programmer to contribute. Packaging, testing, documenting and porting, are all + important jobs as well.

+
+

1.1. Quickstart to Privoxy Development

+

The first step is to join the privoxy-devel mailing list. You can submit your ideas or, even better, patches. Patches can also be + submitted to the Sourceforge patch + tracker.

+

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).

+

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.

+
+
+ + +