X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fwebserver%2Fdeveloper-manual%2Fintroduction.html;h=468f2fa624e2cd6c994ad57acf0be64bfc2b3e2b;hp=a47acf89094e25c702b0ef0bcfb4bc9cac10556f;hb=07cf496b6edcbd3cf315ec7c48f2c94be27357b1;hpb=c01ca2fed6ffe149fba107a7896d80528dc9fbea diff --git a/doc/webserver/developer-manual/introduction.html b/doc/webserver/developer-manual/introduction.html index a47acf89..468f2fa6 100644 --- a/doc/webserver/developer-manual/introduction.html +++ b/doc/webserver/developer-manual/introduction.html @@ -1,123 +1,116 @@ - + + -
- -- Privoxy, as an heir to Junkbuster, is a Free Software project and the - code is licensed under the GNU General Public License version 2. 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 developer's mailing list. 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. -
-- 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). -
-- 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. -
-- Prev - | -- Home - | -- Next - | -
- Privoxy Developer Manual - | -- - | -- The CVS Repository - | -
Privoxy, as an heir to Junkbuster, is a Free Software project and the code + is licensed under the GNU General Public License version 2. 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 developer's mailing list. 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.
+ +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).
+ +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.