make a new summer projects section on the volunteer page. swipe some of the items from the coding section, which will eventually vanish.
Roger Dingledine commited on 2008-03-10 07:59:11
Zeige 1 geänderte Dateien mit 34 Einfügungen und 21 Löschungen.
- en/volunteer.wml 3d5b0097c..0f0a54605
| ... | ... |
@@ -87,6 +87,40 @@ guidelines</a> if you want to help out. We especially need Arabic or |
| 87 | 87 |
Farsi translations, for the many Tor users in censored areas.</li> |
| 88 | 88 |
</ol> |
| 89 | 89 |
|
| 90 |
+<a id="Summer"></a> |
|
| 91 |
+<a id="Projects"></a> |
|
| 92 |
+<h2><a class="anchor" href="#Projects">Good Summer Projects</a></h2> |
|
| 93 |
+<ol> |
|
| 94 |
+ |
|
| 95 |
+<li>Help Mike Perry on his <a |
|
| 96 |
+href="https://www.torproject.org/svn/torflow/">TorFlow</a> |
|
| 97 |
+library (<a href="https://www.torproject.org/svn/torflow/TODO">TODO</a>): |
|
| 98 |
+it's a python library that uses the <a |
|
| 99 |
+href="https://www.torproject.org/svn/torctl/doc/howto.txt">Tor controller |
|
| 100 |
+protocol</a> to instruct Tor to build circuits in a variety of ways, |
|
| 101 |
+and then it measures performance and tries to detect anomalies.</li> |
|
| 102 |
+<li>Torflow / soat to detect bad relays and automatically get that |
|
| 103 |
+info to the directory authorities for realtime blacklisting</li> |
|
| 104 |
+<li>Torstatus. Set up an automated system for tracking network health |
|
| 105 |
+over time, graphing it, etc. Better metrics for assessing network |
|
| 106 |
+health and growth.</li> |
|
| 107 |
+<li>vidalia and upnp</li> |
|
| 108 |
+<li>nymble</li> |
|
| 109 |
+<li>polipo on windows</li> |
|
| 110 |
+<li>How can we make the <a |
|
| 111 |
+href="http://anonymityanywhere.com/incognito/">Incognito LiveCD</a> |
|
| 112 |
+easier to maintain, improve, and document?</li> |
|
| 113 |
+<li>We need a distributed testing framework. We have unit tests, |
|
| 114 |
+but it would be great to have a script that starts up a Tor network, uses |
|
| 115 |
+it for a while, and verifies that at least parts of it are working.</li> |
|
| 116 |
+ |
|
| 117 |
+<li>Don't like any of these? Look at the <a |
|
| 118 |
+href="<svnsandbox>doc/design-paper/roadmap-future.pdf">Tor development |
|
| 119 |
+roadmap</a> for more ideas.</li> |
|
| 120 |
+<li>Don't see your idea here? We probably need it anyway! Contact |
|
| 121 |
+us and find out.</li> |
|
| 122 |
+</ol> |
|
| 123 |
+ |
|
| 90 | 124 |
<a id="Coding"></a> |
| 91 | 125 |
<h2><a class="anchor" href="#Coding">Coding and Design</a></h2> |
| 92 | 126 |
<ol> |
| ... | ... |
@@ -102,12 +136,6 @@ overlapped IO rather than select() on Windows, and then adapt Tor to |
| 102 | 136 |
the new libevent interface. Christian King made a |
| 103 | 137 |
<a href="https://tor-svn.freehaven.net/svn/libevent-urz/trunk/">good |
| 104 | 138 |
start</a> on this last summer.</li> |
| 105 |
-<li>How can we make the <a |
|
| 106 |
-href="http://anonymityanywhere.com/incognito/">Incognito LiveCD</a> |
|
| 107 |
-easier to maintain, improve, and document?</li> |
|
| 108 |
-<li>Our preferred graphical front-end for Tor, named |
|
| 109 |
-<a href="http://vidalia-project.net/">Vidalia</a>, needs all sorts |
|
| 110 |
-of development work.</li> |
|
| 111 | 139 |
<li>We need to actually start building our <a href="<page |
| 112 | 140 |
documentation>#DesignDoc">blocking-resistance design</a>. This involves |
| 113 | 141 |
fleshing out the design, modifying many different pieces of Tor, adapting |
| ... | ... |
@@ -122,16 +150,6 @@ giving a reasonable answer? This will spur a lot of new research. |
| 122 | 150 |
See the entry <a href="#Research">below</a> on confirmation attacks for |
| 123 | 151 |
details on the research side of this task — who knows, when it's |
| 124 | 152 |
done maybe you can help write a paper or three also.</li> |
| 125 |
-<li>We need a distributed testing framework. We have unit tests, |
|
| 126 |
-but it would be great to have a script that starts up a Tor network, uses |
|
| 127 |
-it for a while, and verifies that at least parts of it are working.</li> |
|
| 128 |
-<li>Help Mike Perry on his <a |
|
| 129 |
-href="https://www.torproject.org/svn/torflow/">TorFlow</a> |
|
| 130 |
-library (<a href="https://www.torproject.org/svn/torflow/TODO">TODO</a>): |
|
| 131 |
-it's a python library that uses the <a |
|
| 132 |
-href="https://www.torproject.org/svn/torctl/doc/howto.txt">Tor controller |
|
| 133 |
-protocol</a> to instruct Tor to build circuits in a variety of ways, |
|
| 134 |
-and then it measures performance and tries to detect anomalies.</li> |
|
| 135 | 153 |
<li>Tor 0.1.1.x and later include support for hardware crypto accelerators |
| 136 | 154 |
via OpenSSL. Nobody has ever tested it, though. Does somebody want to get |
| 137 | 155 |
a card and let us know how it goes?</li> |
| ... | ... |
@@ -152,11 +170,6 @@ UDP</a> — please let us know what's wrong with it.</li> |
| 152 | 170 |
<li>We're not that far from having IPv6 support for destination addresses |
| 153 | 171 |
(at exit nodes). If you care strongly about IPv6, that's probably the |
| 154 | 172 |
first place to start.</li> |
| 155 |
-<li>Don't like any of these? Look at the <a |
|
| 156 |
-href="<svnsandbox>doc/design-paper/roadmap-future.pdf">Tor development |
|
| 157 |
-roadmap</a> for more ideas.</li> |
|
| 158 |
-<li>Don't see your idea here? We probably need it anyway! Contact |
|
| 159 |
-us and find out.</li> |
|
| 160 | 173 |
</ol> |
| 161 | 174 |
|
| 162 | 175 |
<a id="Research"></a> |
| 163 | 176 |