X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=TODO;h=70d726652dba4b3eca8d0d94799c2e6d1e68502e;hb=5187adebdcfc7b1ee7c2d913ae8a74444963350e;hp=be8f6f5f074c02c8e1bf5cfe3031031153fe73d5;hpb=87555cc0159e530f47443d2773e1863d53fbef47;p=privoxy.git diff --git a/TODO b/TODO index be8f6f5f..70d72665 100644 --- a/TODO +++ b/TODO @@ -1,4 +1,4 @@ -$Id: TODO,v 1.101 2014/05/11 13:17:08 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. @@ -6,10 +6,19 @@ have been added, not by priority. The latest version should be available at: http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO -1) Add some regression tests. Filters should be tested automatically +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 - test suite which could be used for this as well. + test suite, patches have been submitted upstream: + http://curl.haxx.se/mail/lib-2014-06/0070.html 3) Fix some more XXX: comments. @@ -120,6 +129,11 @@ http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO It would probably also make sense to look into what other projects did when migrating away from SF. + 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 @@ -127,14 +141,6 @@ http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO 55) Apply for Coverity scans: http://scan.coverity.com/ -56) Apply for the "free online access for qualified open-source - software projects" for the Co-Advisor HTTP compliance tests: - http://coad.measurement-factory.com/details.html#pricing - -57) Allow piping into external programs to allow more powerful - filters and policy decisions. Incomplete support available - in Fabian's popen branch. - 58) Move more template strings from the code into the actual templates. 59) Import the German template translation. @@ -346,10 +352,93 @@ http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO 122) Allow customized log messages. -123) Allow to decrypt encrypted traffic using the - voluntarily-disclose-session-keys option in Firefox. - Depends on #16. +123) Evaluate if the voluntarily-disclose-session-keys option in Firefox + (and other browsers) can be leveraged. Probably depends on #16. -124) Add Capsicum support. +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 + the rest. + Note that Privoxy developers qualified for free account upgrades: + http://coad.measurement-factory.com/details.html#pricing + +127) Add "real" CGI support (serve program output instead of forwarding + the request). The work is mostly done due to +external-filter{}. + +128) Add a config directive to control the stack limit. + +129) Completely implement RFC 7230 4.1 (Chunked Transfer Coding). + Currently Privoxy doesn't properly deal with trailers which + are rarely used in the real world but should be supported anyway. + +130) Move header_tagger() out of the parser structs and let it execute + taggers one-by-one against all headers so the header order has less + influence on the tagging result. As a bonus, dynamic taggers would + have to be compiled less often. + +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. + +########################################################################## + +Hosting wish list (relevant for #53) + +What we need: + +- Bug tracker +- Mailinglists (Mailman with public archives preferred) +- Webspace (on a Unix-like OS that works with the webserver targets + in GNUMakefile) +- Source code repositories (currently CVS, but migrating away + from it is TODO #54 anyway and shouldn't be too much trouble) +- Commit mails (preferably with unified diffs) + +(Unsorted) details to look at when evaluating hosters: + +1. Preferably no third-party ads and trackers. + External images, CSS and JavaScript may count as trackers + but texts like "supported by company XYZ" may be acceptable. + +2. JavaScript should be optional or not used at all. + +3. Services we don't need shouldn't be enabled anyway. + (We currently don't use Web forums, wikis, surveys etc.) + +4. It would be preferable if the hoster didn't have a bad track + record as far as user experience, security and privacy are + concerned and if the terms of service are "reasonable" and + haven't changed too often in the past. Updates in the past + should have been improvements and not regressions. + +5. It would be preferable if most of the server administration + is done by a trusted third-party (or at least not a lot of work + for us). + +6. The server(s) should be located in a country with laws we can + understand and follow (or at least not unintentionally violate). + +7. A server location in a country with some kind of due process + and strong data protection laws (at least on paper) would be + preferable. + +8. Given that Privoxy is a free software project it would be + preferable if the hoster would use free software where possible. + +9. Migrating away from the hoster in the future without losing + any important data should be possible without writing web + scrapers first.