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