4 SPEC - Spec not finalized
24 =======================================================================
29 W - Finish implementation of directory overhead changes: have a set
30 of patches that you think work.
34 C * Get the MSI working and stable for Windows Tor installer.
35 ? - Teach our OSX installer to register its version on install
38 I - Periodic summaries of localization progress: both pootle and wml.
41 W - Finish testing, debugging, unit testing, etc the directory overhead
42 changes. Have it in the development version and in use.
43 o Roger writes a proposal unifying the or-dev discussions
44 ? * Somebody implements the proposal. Who?
45 E - Implement KDE Marble into Vidalia. In order to improve the user
46 interface for easier understanding of circuits and where traffic
47 travels, replacing the current Vidalia map with KDE's Marble
48 is desired. KDE's Marble widget gives a better quality map and
49 enables improved interactivity. This is the first step in allowing
50 users to choose an exit country, or being able to interact with
51 Tor circuits in new ways.
54 - Write first draft of research study for Paul's research problem.
55 R - Get the stuff in the wiki into a "report" we can show some
56 bureaucrat, for phase one.
57 I - Periodic summaries of localization progress: both pootle and wml.
60 S * Examine current load balancing issues and evaluate trade-offs
61 associated with other methods.
62 - For each potential routing improvement strategy...
63 - Explain method, calculate theoretical impact, estimate likely
65 - Establish implementation work plan
66 - Document strategy for metrics and evaluation
67 - Highlight which items on your list are doable in 2009.
69 N - Write a summary of progress toward Overlapped I/O on Windows.
71 S - Write a summary of progress toward understanding risks to relays
72 (and thus bridges) from letting attackers route traffic through
73 them. Eg, if relays have 100KB/s but set relaybandwidthrate to
74 10KB/s, do your interference attacks still work?
76 W - Download fewer descriptors
77 - Summarize progress so far, on all the different approaches to
78 reducing directory download overhead.
79 - Measure/estimate impact of each improvement.
80 - Build a plan and timeline for implementing the rest.
82 N - TLS arms race: Produce a list of likely avenues for blocking,
83 and for each avenue summarize a plan for how we should respond to
84 get Tor unblocked again.
86 I * Email auto-responder
87 - Document the design and spec.
88 - Describe auto-responder "commands"
89 - Describe DKIM requirement (and alternatives)
90 - Describe how we're going to localize the text
91 - Describe the workflow for a user that wants to know she's got
92 the right file. Digitally signed installer? Feed it to the
93 updater that recognizes signatures? Other options?
94 * How do we better support users with limited email
95 bandwidth? Multi-part download? Teach them how to reconnect
96 their gmail? Does downloading your gmail work when your network
100 * Gather and document monthly usage metrics, by country
101 - Using Roger's old method of counting users
102 - Using Nick's new method of counting users
103 - Start playing around with figuring out which one is more
104 accurate, or how to combine them to get better guesses,
106 o Roger should walk Karsten through applying (and maybe
107 updating) the patch for each method, and write a summary
108 of what we have tried/guessed so far.
109 * Automatically collect and document or publish other monthly
111 - Total data over time
112 - Number, availability and performance of relays
113 - Advertised capacity
114 - With Mike's help, use Torflow to start doing monthly rudimentary
115 performance evaluations:
116 - Circuit throughput and latency
117 - Measure via Broadband and dialup
118 - Make a few graphs of the most interesting public data
119 - Publish a report addressing key long-term metrics questions:
120 - What metrics should we present?
121 - What data are available for these metrics?
122 - What data are missing, and can collect them safely? Can we
124 - What systems are available to present this data?
126 E - Vidalia improvements
127 - Implement Vidalia presentation of plaintext port warnings
128 - Figure out a plan for presenting other Tor status warning events.
129 - Move Polipo into the main Vidalia -dev bundle.
130 - Vidalia displays by-country user summary for bridge operators
131 o Tor sends a status event or something so Vidalia knows what
132 to display: "clients_seen"
133 - Get the onion icons back into vidalia svn
134 - Find an OS X user who can do design who thinks the OS X onion
135 icons are crappy and need fixing
137 M - Network scanning and network health
138 - Implement some initial automated scans.
139 - Describe a roadmap for how to get from here to plausible,
140 long-term security scanning tests for Tor network
141 - Document a strategy for incorporating results into directory
142 consensus documents. At what phases will we be ready to automate
143 which parts? How will we recognize when we are ready?
145 M - Torbutton development
146 - Keep up with our bugfixes -- build a plan for (or resolve)
147 every item in Flyspray, and other known issues like the Google
149 - Build a strategy for how Torbutton and Vidalia can
150 communicate. E.g., what do we do with the 'new identity' button
152 * Make Torbutton happy on FF3, especially so TBB can drop FF2.
154 C - Transparent interception of connections on Windows
155 - Produce prototype, with screenshots for how to install and test.
156 - Document open issues, future work, things users need to be aware
159 S - Tor Browser bundle work
160 - Use native Vidalia (non-PortableFirefox) launcher for browser
161 - Close Browser on clean Vidalia exit
162 - Establish feasibility of simultaneous Firefox usage (also
163 considering implications for (OpenVPN-style or other) system-wide
165 - Switch Tor Browser Bundle to Firefox 3, once Torbutton is ready.
166 - Decide whether TBB should use Torbutton's "lock" feature.
167 http://archives.seul.org/or/cvs/Jun-2008/msg00186.html
168 I . Jake learns how to build the TBB and takes over doing new
171 S - Continue analyzing "traces" left on host machine by use of
172 Tor Browser, especially once we have our new launcher and have moved
173 to FF3. Write a summary of current progress, and what remains. Try
174 to solve some of the low-hanging fruit.
176 I - Periodic summaries of localization progress: both pootle and wml.
177 I - Collecting user stories
178 I - Revise the 'Tor mirror page' so it doesn't list obsolete-looking
179 timestamps. Just have two tables, "new enough" and "not new enough".
180 I * Get Tor Weather up, stable, and in use by some relay operators.
181 I d Get a relay operator mailing list going, with a plan and supporting