TODO.external 8.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190
  1. $Id$
  2. Legend:
  3. SPEC!! - Not specified
  4. SPEC - Spec not finalized
  5. N - nick claims
  6. R - arma claims
  7. P - phobos claims
  8. S - Steven claims
  9. E - Matt claims
  10. M - Mike claims
  11. J - Jeff claims
  12. I - ioerror claims
  13. W - weasel claims
  14. K - Karsten claims
  15. C - coderman claims
  16. - Not done
  17. * Top priority
  18. . Partially done
  19. o Done
  20. d Deferrable
  21. D Deferred
  22. X Abandoned
  23. =======================================================================
  24. External constraints:
  25. - mid October
  26. W - Finish implementation of directory overhead changes: have a set
  27. of patches that you think work.
  28. - end of October
  29. - Auto update
  30. C * Get the MSI working and stable for Windows Tor installer.
  31. N o Come up with an interface to export the package/bundle gloss
  32. descriptions so Vidalia can display them.
  33. (Done; see thandy-client json2xml. Matt was fine with this,
  34. last I heard.)
  35. E * Vidalia calls Thandy, learns when to upgrade, requests the upgrade.
  36. ? - Teach our OSX installer to register its version on install
  37. - end of December
  38. I - Periodic summaries of localization progress: both pootle and wml.
  39. - mid January
  40. KS . Finish testing, debugging, unit testing, etc the hidden service
  41. changes. Have it in the development version and in use.
  42. W - Finish testing, debugging, unit testing, etc the directory overhead
  43. changes. Have it in the development version and in use.
  44. R - Roger writes a proposal unifying the or-dev discussions
  45. ? - Somebody implements the proposal. Who?
  46. E - Implement KDE Marble into Vidalia. In order to improve the user
  47. interface for easier understanding of circuits and where traffic
  48. travels, replacing the current Vidalia map with KDE's Marble
  49. is desired. KDE's Marble widget gives a better quality map and
  50. enables improved interactivity. This is the first step in allowing
  51. users to choose an exit country, or being able to interact with
  52. Tor circuits in new ways.
  53. - end of January
  54. NSE - Write first draft of research study for Paul's research problem.
  55. I - Periodic summaries of localization progress: both pootle and wml.
  56. - mid February
  57. S * Examine current load balancing issues and evaluate trade-offs
  58. associated with other methods.
  59. - For each potential routing improvement strategy...
  60. - Explain method, calculate theoretical impact, estimate likely
  61. impact, prioritize
  62. - Establish implementation work plan
  63. - Document strategy for metrics and evaluation
  64. - Highlight which items on your list are doable in 2009.
  65. N - Write a summary of progress toward Overlapped I/O on Windows.
  66. S - Write a summary of progress toward understanding risks to relays
  67. (and thus bridges) from letting attackers route traffic through
  68. them. Eg, if relays have 100KB/s but set relaybandwidthrate to
  69. 10KB/s, do your interference attacks still work?
  70. R * Revise and publish incentive draft paper
  71. - Write an explanation for its current flaws
  72. - Gather comments, search for new designs
  73. - Write up a summary of recommendations and next steps
  74. W - Download fewer descriptors
  75. - Summarize progress so far, on all the different approaches to
  76. reducing directory download overhead.
  77. - Measure/estimate impact of each improvement.
  78. - Build a plan and timeline for implementing the rest.
  79. N - TLS arms race: Produce a list of likely avenues for blocking,
  80. and for each avenue summarize a plan for how we should respond to
  81. get Tor unblocked again.
  82. I * Email auto-responder
  83. - Document the design and spec.
  84. - Describe auto-responder "commands"
  85. - Describe DKIM requirement (and alternatives)
  86. - Describe how we're going to localize the text
  87. - Describe the workflow for a user that wants to know she's got
  88. the right file. Digitally signed installer? Feed it to the
  89. updater that recognizes signatures? Other options?
  90. * How do we better support users with limited email
  91. bandwidth? Multi-part download? Teach them how to reconnect
  92. their gmail? Does downloading your gmail work when your network
  93. keeps dying?
  94. K - Metrics.
  95. * Gather and document monthly usage metrics, by country
  96. - Using Roger's old method of counting users
  97. - Using Nick's new method of counting users
  98. - Start playing around with figuring out which one is more
  99. accurate, or how to combine them to get better guesses,
  100. or something.
  101. R * Roger should walk Karsten through applying (and maybe
  102. updating) the patch for each method, and write a summary
  103. of what we have tried/guessed so far.
  104. * Automatically collect and document or publish other monthly
  105. statistics
  106. - Total data over time
  107. - Number, availability and performance of relays
  108. - Advertised capacity
  109. - With Mike's help, use Torflow to start doing monthly rudimentary
  110. performance evaluations:
  111. - Circuit throughput and latency
  112. - Measure via Broadband and dialup
  113. - Make a few graphs of the most interesting public data
  114. - Publish a report addressing key long-term metrics questions:
  115. - What metrics should we present?
  116. - What data are available for these metrics?
  117. - What data are missing, and can collect them safely? Can we
  118. publish them safely?
  119. - What systems are available to present this data?
  120. E - Vidalia improvements
  121. - Implement Vidalia presentation of plaintext port warnings
  122. - Figure out a plan for presenting other Tor status warning events.
  123. - Move Polipo into the main Vidalia -dev bundle.
  124. - Vidalia displays by-country user summary for bridge operators
  125. o Tor sends a status event or something so Vidalia knows what
  126. to display: "clients_seen"
  127. M - Network scanning and network health
  128. - Implement some initial automated scans.
  129. - Describe a roadmap for how to get from here to plausible,
  130. long-term security scanning tests for Tor network
  131. - Document a strategy for incorporating results into directory
  132. consensus documents. At what phases will we be ready to automate
  133. 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
  137. captcha issue.
  138. - Build a strategy for how Torbutton and Vidalia can
  139. communicate. E.g., what do we do with the 'new identity' button
  140. in Vidalia?
  141. * Make Torbutton happy on FF3, especially so TBB can drop FF2.
  142. C - Transparent interception of connections on Windows
  143. - Produce prototype, with screenshots for how to install and test.
  144. - Document open issues, future work, things users need to be aware
  145. of, etc.
  146. S - Tor Browser bundle work
  147. - Use native Vidalia (non-PortableFirefox) launcher for browser
  148. - Close Browser on clean Vidalia exit
  149. - Establish feasibility of simultaneous Firefox usage (also
  150. considering implications for (OpenVPN-style or other) system-wide
  151. Tor interception)
  152. - Switch Tor Browser Bundle to Firefox 3, once Torbutton is ready.
  153. - Decide whether TBB should use Torbutton's "lock" feature.
  154. http://archives.seul.org/or/cvs/Jun-2008/msg00186.html
  155. I . Jake learns how to build the TBB and takes over doing new
  156. releases.
  157. S - Continue analyzing "traces" left on host machine by use of
  158. Tor Browser, especially once we have our new launcher and have moved
  159. to FF3. Write a summary of current progress, and what remains. Try
  160. to solve some of the low-hanging fruit.
  161. I - Periodic summaries of localization progress: both pootle and wml.
  162. I - Collecting user stories
  163. I - Revise the 'Tor mirror page' so it doesn't list obsolete-looking
  164. timestamps. Just have two tables, "new enough" and "not new enough".
  165. I * Get Tor Weather up, stable, and in use by some relay operators.
  166. I - Get a relay operator mailing list going, with a plan and supporting
  167. scripts and so on.