[or-cvs] r18835: {website} Put in links to the TorFlow README, now that the TorFlow/sca (website/trunk/en)

[kloesing at seul.org]

Author: kloesing
Date: 2009-03-09 21:21:27 -0400 (Mon, 09 Mar 2009)
New Revision: 18835

Modified:
   website/trunk/en/volunteer.wml
Log:
Put in links to the TorFlow README, now that the TorFlow/scanner item is gone.


Modified: website/trunk/en/volunteer.wml
===================================================================
--- website/trunk/en/volunteer.wml	2009-03-10 01:04:23 UTC (rev 18834)
+++ website/trunk/en/volunteer.wml	2009-03-10 01:21:27 UTC (rev 18835)
@@ -138,7 +138,8 @@
 people collect brief snapshots, but where it gets really interesting is
 when we start tracking data points over time.
 <br />
-Data could be collected from the "Tor Node Scanner" item above, from
+Data could be collected from the Tor Network Scanners in <a
+href="https://svn.torproject.org/svn/torflow/trunk/README">TorFlow</a>, from
 the server descriptors that each relay publishes, and from other
 sources. Results over time could be integrated into one of the <a
 href="https://torstatus.blutmagie.de/">Tor Status</a> web pages, or be
@@ -474,8 +475,8 @@
 Additionally, we need to automate our performance testing. We've got
 buildbot to automate our regular integration and compile testing already
 (though we need somebody to set it up on Windows),
-but we need to get our network simulation tests (as built in TorFlow: see
-the "Tor Node Scanner improvements" item)
+but we need to get our network simulation tests (as built in <a
+href="https://svn.torproject.org/svn/torflow/trunk/README">TorFlow</a>)
 updated for more recent versions of Tor, and designed to launch a test
 network either on a single machine, or across several, so we can test
 changes in performance on machines in different roles automatically.