-$Id: TODO,v 1.115 2014/06/16 10:17:38 fabiankeil Exp $
+$Id: TODO,v 1.120 2014/07/03 10:19:47 fabiankeil Exp $
Some Privoxy-related tasks, sorted by the time they
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.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).
+
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
2014-05-13: Work in progress. Hosting wish list at the end
of this file.
+ Interested donors: 1.
+
54) Move away from CVS to a more modern revision control system.
Find out if there are any objection against going with Git.
Using Git would also have the advantage that SF now pretends
124) Add support for the "lightweight OS capability and sandbox framework"
Capsicum. http://www.cl.cam.ac.uk/research/security/capsicum/
+ Interested donors: 1.
125) Allow clients to HTTPS-encrypt the proxy connection.
+ Interested donors: 1.
126) Run the Co-Advisor HTTP compliance tests, evaluate the results,
fix the compliance issues that aren't by design and document
131) The handle-as-empty-doc-returns-ok directive should be replaced with
an action so the behaviour can be enabled on a per-request basis.
+ Interested donors: 1.
+
+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.
##########################################################################