[or-cvs] r14272: update the application numbers. but this is probably still n (website/trunk/en)

arma at seul.org arma at seul.org
Tue Apr 1 01:24:04 UTC 2008


Author: arma
Date: 2008-03-31 21:24:04 -0400 (Mon, 31 Mar 2008)
New Revision: 14272

Modified:
   website/trunk/en/volunteer.wml
Log:
update the application numbers. but this is probably still not the
best way to explain which ones are 'claimed'.


Modified: website/trunk/en/volunteer.wml
===================================================================
--- website/trunk/en/volunteer.wml	2008-03-31 21:12:56 UTC (rev 14271)
+++ website/trunk/en/volunteer.wml	2008-04-01 01:24:04 UTC (rev 14272)
@@ -117,7 +117,7 @@
 <br />
 Likely Mentors: <i>Mike</i>
 <br />
-Applications as of 30 Mar 20:50 UTC: <i>3</i>
+Applications as of 1 Apr 00:00 UTC: <i>5</i>
 <br />
 The Tor exit node scanner 'SoaT', part of the <a
 href="<svnsandbox>torflow/">Torflow project</a>, makes connections out
@@ -157,7 +157,7 @@
 <br />
 Likely Mentors: <i>Mike</i>
 <br />
-Applications as of 30 Mar 20:50 UTC: <i>1</i>
+Applications as of 1 Apr 00:00 UTC: <i>1</i>
 <br />
 Similar to the exit scanner (or perhaps even during exit scanning),
 statistics can be gathered about the reliability of nodes. Nodes that
@@ -223,7 +223,7 @@
 <br />
 Likely Mentors: <i>Roger, Nick, Mike</i>
 <br />
-Applications as of 30 Mar 20:50 UTC: <i>2</i>
+Applications as of 1 Apr 00:00 UTC: <i>3</i>
 <br />
 Some simple improvements can be made to Tor's path selection to vastly
 improve Tor speed. For instance, some of the (unofficial) <a
@@ -291,7 +291,7 @@
 <br />
 Likely Mentors: <i>Peter, Matt</i>
 <br />
-Applications as of 30 Mar 20:50 UTC: <i>1</i>
+Applications as of 1 Apr 00:00 UTC: <i>1</i>
 <br />
 Vidalia currently doesn't play nicely on Debian and Ubuntu with the
 default Tor packages. The current Tor packages automatically start Tor
@@ -500,6 +500,8 @@
 <br />
 Likely Mentors: <i>Jacob, Steven</i>
 <br />
+Applications as of 1 Apr 00:00 UTC: <i>1</i>
+<br />
 We currently have a functional web page to detect if Tor is working. It
 has a few places where it falls short. It requires improvements with
 regard to default languages and functionality. It currently only responds
@@ -559,6 +561,8 @@
 <br />
 Likely Mentors: <i>Jacob, Mike, Greg</i>
 <br />
+Applications as of 1 Apr 00:00 UTC: <i>1</i>
+<br />
 The Tor project currently lacks a solid test suite to ensure that a
 user has a properly and safely configured web browser. It should test for as
 many known issues as possible. It should attempt to decloak the
@@ -710,7 +714,7 @@
 <br />
 Likely Mentors: <i>Karsten, Nick</i>
 <br />
-Applications as of 30 Mar 20:50 UTC: <i>4</i>
+Applications as of 1 Apr 00::00 UTC: <i>4</i>
 <br />
 Reanimate one of the approaches to implement a Tor client in Java,
 e.g. the <a href="http://onioncoffee.sourceforge.net/">OnionCoffee
@@ -741,6 +745,8 @@
 <br />
 Likely Mentors: <i>Karsten, Nick, Roger</i>
 <br />
+Applications as of 1 Apr 00:00 UTC: <i>2</i>
+<br />
 Write a tool that runs automatic system tests in addition
 to the existing unit tests. The Java-based Tor simulator <a
 href="https://tor-svn.freehaven.net/svn/puppetor/trunk/">PuppeTor</a>
@@ -771,7 +777,7 @@
 <br />
 Likely Mentors: <i>Karsten, Jacob</i>
 <br />
-Applications as of 30 Mar 20:50 UTC: <i>2</i>
+Applications as of 1 Apr 00::00 UTC: <i>2</i>
 <br />
 Implement a <a href="http://www.ss64.com/bash/top.html">top-like</a>
 management tool for Tor relays. The purpose of such a tool would be



More information about the tor-commits mailing list