Put in links to the TorFlow README, now that the TorFlow/scanner item is gone.
Karsten Loesing commited on 2009-03-10 02:21:27
Zeige 1 geänderte Dateien mit 4 Einfügungen und 3 Löschungen.
- en/volunteer.wml 0fbfd78e7..ef5058132
| ... | ... |
@@ -138,7 +138,8 @@ in terms of new relays showing up and relays shutting off? Periodically |
| 138 | 138 |
people collect brief snapshots, but where it gets really interesting is |
| 139 | 139 |
when we start tracking data points over time. |
| 140 | 140 |
<br /> |
| 141 |
-Data could be collected from the "Tor Node Scanner" item above, from |
|
| 141 |
+Data could be collected from the Tor Network Scanners in <a |
|
| 142 |
+href="https://svn.torproject.org/svn/torflow/trunk/README">TorFlow</a>, from |
|
| 142 | 143 |
the server descriptors that each relay publishes, and from other |
| 143 | 144 |
sources. Results over time could be integrated into one of the <a |
| 144 | 145 |
href="https://torstatus.blutmagie.de/">Tor Status</a> web pages, or be |
| ... | ... |
@@ -474,8 +475,8 @@ as possible from globals. |
| 474 | 475 |
Additionally, we need to automate our performance testing. We've got |
| 475 | 476 |
buildbot to automate our regular integration and compile testing already |
| 476 | 477 |
(though we need somebody to set it up on Windows), |
| 477 |
-but we need to get our network simulation tests (as built in TorFlow: see |
|
| 478 |
-the "Tor Node Scanner improvements" item) |
|
| 478 |
+but we need to get our network simulation tests (as built in <a |
|
| 479 |
+href="https://svn.torproject.org/svn/torflow/trunk/README">TorFlow</a>) |
|
| 479 | 480 |
updated for more recent versions of Tor, and designed to launch a test |
| 480 | 481 |
network either on a single machine, or across several, so we can test |
| 481 | 482 |
changes in performance on machines in different roles automatically. |
| 482 | 483 |