X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=TODO;h=bcdcc88f239a709d5837c1f9c8e542f1c46b206a;hb=c7da782c447e25210ca3a98a71e079b21fce7340;hp=d296c54ccf7e90ef1b6b12b643bf04c4eddc481e;hpb=0776d25431f66a2e2dfe61d1af22a89ac5e9cff4;p=privoxy.git

diff --git a/TODO b/TODO
index d296c54c..bcdcc88f 100644
--- a/TODO
+++ b/TODO
@@ -1,4 +1,4 @@
-$Id: TODO,v 1.117 2014/06/25 10:08:13 fabiankeil Exp $
+$Id: TODO,v 1.129 2014/12/19 12:35:30 fabiankeil Exp $
 
 Some Privoxy-related tasks, sorted by the time they
 have been added, not by priority.
@@ -6,6 +6,10 @@ have been added, not by priority.
 The latest version should be available at:
 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:
+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.
     Note that there is currently work in progress to leverage curl's
@@ -112,9 +116,9 @@ http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO
     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.
@@ -131,8 +135,6 @@ http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO
     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.
@@ -206,9 +208,6 @@ http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO
 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.
@@ -357,7 +356,7 @@ http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO
 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
@@ -381,6 +380,26 @@ http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO
 132) Provide a Tor hidden service to reach the Privoxy website.
      Interested donors: 1.
 
+133) Consider allowing bitcoin donations.
+     Interested donors: 1.
+
+134) Track the total number of bytes written to and received from a socket.
+
+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.
+
 ##########################################################################
 
 Hosting wish list (relevant for #53)