X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fwebserver%2Fdeveloper-manual%2Fintroduction.html;h=c6f41714c849eb94ffb12479dcc21ae17123b3f8;hb=d718332b42f884d9c3c2fd0cfa9b83f4973c6971;hp=b4bcd2ba74930961170a87d7dfda226e24a87e0f;hpb=0212c18282eaa5f73843cbbec12c9137ea596e1c;p=privoxy.git diff --git a/doc/webserver/developer-manual/introduction.html b/doc/webserver/developer-manual/introduction.html index b4bcd2ba..c6f41714 100644 --- a/doc/webserver/developer-manual/introduction.html +++ b/doc/webserver/developer-manual/introduction.html @@ -1,184 +1,64 @@ -
Privoxy, as an heir to - Junkbuster, is an Open Source project - and licensed under the GPL. 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, - and porting, are all important jobs as well. -
You'll need an account on Sourceforge to support our - development. Mail your ID to the list and wait until a - project manager has added you. -
For the time being (read, this section is under construction), please - refer to the extensive comments in the source code. -
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.
+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.
+