aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2011-03-01 20:24:31 -0500
committerNick Mathewson <nickm@torproject.org>2011-03-01 20:24:31 -0500
commita87aeacf9a069f6ddd12b7725b299f2cd79174cd (patch)
tree71db75c53d0abcdaff5a9dcf6e73328b19c05266
parent70e35e2249e9128d544e6617528097860c6c3358 (diff)
downloadchutney-a87aeacf9a069f6ddd12b7725b299f2cd79174cd.tar
chutney-a87aeacf9a069f6ddd12b7725b299f2cd79174cd.tar.gz
document more to-do items
-rw-r--r--TODO21
1 files changed, 14 insertions, 7 deletions
diff --git a/TODO b/TODO
index ca3e7f5..d996d2a 100644
--- a/TODO
+++ b/TODO
@@ -1,9 +1,4 @@
-- Rename this. "onionsalad"? "onionchutney?" "kachumber"? "chutney"?
- "pyaaz"? "ganda"? "piaz ka catni"?
-
-
-
- Have ability to override default parameter values.
Search order for configuration values:
- command line
@@ -22,7 +17,19 @@
- Right now we assume that we're acting like a fooctl startup/shutdown script
series. Instead we could run in a managed mode.
-- Document everything
+- Pipe stdout to a file, not to nowhere with "quiet"
+
+- Log stuff.
-- Get it into git
+- Split TorNode into a class that *just* holds the nodes configuration, and
+ implements some methods that create other classes for the stuff we really
+ need (node configurer, rc.d-like launcher, etc)
+
+- Have launcher check for configuration
+
+- Resolve XXXX comments
+
+- Document everything
+- Start writing passive "tests" like "did it bootstrap?" or "any
+ warnings in the logs?", etc