[or-cvs] [metrics/master] Mark one task partly done and add a whole bunch of new tasks.

[karsten@xxxxxxxx]

Author: Karsten Loesing <karsten.loesing@xxxxxxx>
Date: Wed, 24 Jun 2009 20:22:24 +0200
Subject: Mark one task partly done and add a whole bunch of new tasks.
Commit: 3f58f1610288012cf24b0c6d60be519db411b183

---
 TODO |   16 ++++++++++++++--
 1 files changed, 14 insertions(+), 2 deletions(-)

diff --git a/TODO b/TODO
index 1d62ed4..7b56b60 100644
--- a/TODO
+++ b/TODO
@@ -19,10 +19,15 @@ Tasks for June:
      GeoIP database as country '??'.
 *  . June 30: Analyze geoip-stats files from folks. Come up with a more
 *    automated way of analyzing these files than before.
+   - Figure out why estimations are that far off. Could it be that
+     directories see larger shares of requests than they report, because
+     many others don't return successful replies?
+   - Find out why some directories write empty geoip-stats files.
 *  - June 30: Decide if statistics should be measured in the future in
 *    aggregate form. Write proposal for including client request statistics
 *    in extra-info documents. Consider adding the GeoIP database version
-*    string, too.
+*    string, too. Make sure that we don't miss a day in case directories
+*    fail to upload their descriptor.
    d Unskew v2 requests by finding out what fraction of requests results in
      503 depending on the directory's advertised bandwidth.
    d Figure out if there are better GeoIP databases available that focus
@@ -105,7 +110,7 @@ Tasks for June:
      documents.
 
  d Exiting traffic by port
-   - Write outgoing traffic by port to logs. Also measure statistics in
+   . Write outgoing traffic by port to logs. Also measure statistics in
      Tor.
 *  - May 31: Run on one of Jake's nodes, compare the results.
 *  - June 30: Decide if statistics should be measured in the future in
@@ -144,9 +149,16 @@ Tasks for July:
  - Bridge archives
 *  - July 31: Investigate bridge churn to determine how many bridges users
 *    need.
+   - Look through the bridge relay stats and see how much churn there is.
+     Roger is guessing that the 400-some bridges we have running by end of
+     June do not indicate that only 400-some people set up bridges. Rather
+     they indicate that only 400-some of them have their bridge still up
+     and reachable right now.
    - Are bridges known to be available when users receive their addresses?
      In one reported case, 9 bridges were unavailable only 2 hours after
      receiving their addresses.
+   - Estimate how many bridge users we're skipping because only
+     super-stable bridges report any stats.
 
  - Measure throughput and latency between relays
 *  - May 31: Implement opportunistic measuring of cell transfer times and
-- 
1.5.6.5