Add #142: Remove or update the "internal" pcre version

[privoxy.git] / TODO

diff --git a/TODO b/TODO
index a594888..1ad3d6d 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,4 +1,4 @@
-$Id: TODO,v 1.121 2014/07/25 11:54:28 fabiankeil Exp $
+$Id: TODO,v 1.132 2015/08/12 10:38:16 fabiankeil Exp $

 
 Some Privoxy-related tasks, sorted by the time they
 have been added, not by priority.
 
 Some Privoxy-related tasks, sorted by the time they
 have been added, not by priority.


@@ -8,11 +8,7 @@ http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO
 
 There's work in progress to fund development on these items using
 donations. If you want to donate, please have a look at:
 
 There's work in progress to fund development on these items using
 donations. If you want to donate, please have a look at:

-http://www.spi-inc.org/donations/
-
-If you have any questions regarding donations please either mail to
-the public user mailing list (ijbswa-users@lists.sourceforge.net) or
-to Privoxy's SPI liason Fabian (fk@fabiankeil.de).
+http://www.privoxy.org/faq/general.html#DONATE

 
 1)  Add more regression tests. Filters should be tested automatically
     (variables too). Could probably reuse large parts of Privoxy-Filter-Test.
 
 1)  Add more regression tests. Filters should be tested automatically
     (variables too). Could probably reuse large parts of Privoxy-Filter-Test.


@@ -120,9 +116,9 @@ to Privoxy's SPI liason Fabian (fk@fabiankeil.de).
     macros with strstr() before compiling pcrs commands.
     Investigated, needs some restructuring but is probably worth it.
 
     macros with strstr() before compiling pcrs commands.
     Investigated, needs some restructuring but is probably worth it.
 

-51) Make user-manual directive more generic to allow serving
-    the FAQ and other stuff, too. Consider changing the port
-    for "same origin policy" issues.
+51) Make user-manual directive more generic to allow serving the FAQ
+    and files from user-specified directories. Consider changing the
+    port for "same origin policy" issues.

 
 53) Find a more reliable hoster. Involves finding out what our
     requirements are and which SF alternatives fulfil them.
 
 53) Find a more reliable hoster. Involves finding out what our
     requirements are and which SF alternatives fulfil them.


@@ -139,8 +135,6 @@ to Privoxy's SPI liason Fabian (fk@fabiankeil.de).
     Using Git would also have the advantage that SF now pretends
     to support it, so we could do it independently from 53).
 
     Using Git would also have the advantage that SF now pretends
     to support it, so we could do it independently from 53).
 

-55) Apply for Coverity scans: http://scan.coverity.com/
-

 58) Move more template strings from the code into the actual templates.
 
 59) Import the German template translation.
 58) Move more template strings from the code into the actual templates.
 
 59) Import the German template translation.


@@ -214,9 +208,6 @@ to Privoxy's SPI liason Fabian (fk@fabiankeil.de).
 82) Detect if the system time goes back in time let the user
     know if it caused any connections to get closed.
 
 82) Detect if the system time goes back in time let the user
     know if it caused any connections to get closed.
 

-84) Flesh out the user-manual delivery to serve pages from
-    other directories, too.
-

 85) Once #84 is done, write a script that populates a directory with
     various common third-party icons (stumbleupon.png, facebook.png ...)
     and redirect requests for them to Privoxy.
 85) Once #84 is done, write a script that populates a directory with
     various common third-party icons (stumbleupon.png, facebook.png ...)
     and redirect requests for them to Privoxy.


@@ -365,7 +356,7 @@ to Privoxy's SPI liason Fabian (fk@fabiankeil.de).
 126) Run the Co-Advisor HTTP compliance tests, evaluate the results,
      fix the compliance issues that aren't by design and document
      the rest.
 126) Run the Co-Advisor HTTP compliance tests, evaluate the results,
      fix the compliance issues that aren't by design and document
      the rest.

-     Note that Privoxy developers qualified for free account upgrades:
+     Note that Privoxy developers qualify for free account upgrades:

      http://coad.measurement-factory.com/details.html#pricing
 
 127) Add "real" CGI support (serve program output instead of forwarding
      http://coad.measurement-factory.com/details.html#pricing
 
 127) Add "real" CGI support (serve program output instead of forwarding


@@ -387,6 +378,9 @@ to Privoxy's SPI liason Fabian (fk@fabiankeil.de).
      Interested donors: 1.
 
 132) Provide a Tor hidden service to reach the Privoxy website.
      Interested donors: 1.
 
 132) Provide a Tor hidden service to reach the Privoxy website.

+     Work in progress: http://jvauzb4sb3bwlsnc.onion/
+     This hidden service serves a copy of the www.privoxy.org content
+     (filtered through Privoxy to replace some absolute URLs).

      Interested donors: 1.
 
 133) Consider allowing bitcoin donations.
      Interested donors: 1.
 
 133) Consider allowing bitcoin donations.


@@ -396,6 +390,24 @@ to Privoxy's SPI liason Fabian (fk@fabiankeil.de).
 
 135) Add OpenBSM audit support.
 
 
 135) Add OpenBSM audit support.
 

+136) Make builds reproducible.
+
+137) Add a (preferably vector-based) logo.
+
+138) Bring back the scripts to provide actions file feedback.
+
+     Once upon a time (~2003) there were scripts on the webserver
+     to make reporting action file feedback more convenient for the
+     user and the actual reports more useful for the developers.
+     They have been unusable for years and have thus been disabled,
+     but making the reporting mechanism available again would be a
+     good idea.
+
+141) Port Privoxy to CloudABI, which, despite the name, is actually
+     rather neet. https://github.com/NuxiNL/cloudlibc
+
+142) Remove or update the "internal" pcre version.
+

 ##########################################################################
 
 Hosting wish list (relevant for #53)
 ##########################################################################
 
 Hosting wish list (relevant for #53)