-$Id: TODO,v 1.9 2010/01/20 21:17:30 fabiankeil Exp $
+$Id: TODO,v 1.14 2010/01/24 15:39:32 fabiankeil Exp $
Some Privoxy related task, not ordered in any way.
the FAQ and other stuff, too. Consider changing the port
for "same origin policy" issues.
-53) Find a more reliable hoster.
+53) Find a more reliable hoster. Involves finding out what our
+ requirements are and which SF alternatives fulfil them.
+ It would probably also make sense to look into what other
+ projects did when migrating away from SF.
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 pretents
+ to support it, so we could do it independently from 53).
55) Apply for Coverity scans: http://scan.coverity.com/
64) Use proper copyright attribution. "Privoxy Developers"
is no legal entity.
-65) Polish Website.
+65) Polish Website. Probably involves ditching the Docbook
+ mess in favour of wml. There should be already some threads
+ in the mailinglists archives about this.
66) Increase maximum number of action and filter files.
71) Allow to listen on multiple addresses without having to
bind to all.
-73) Factor FEATURE_CONNECTION_SHARING out of
- FEATURE_CONNECTION_KEEP_ALIVE so the later can be enabled
- on platforms without mutex support as well.
-
74) Let Privoxy-Regression-Test optionally check that action
sections which disable actions actually are preceded by
sections that enable said actions.
+
+75) Create a tool that creates Privoxy action (and filter?) files
+ out of adblock files. Could be implemented as option for
+ url-pattern-translator.pl.
projects / privoxy.git / blobdiff