Browse code

Adding project summaries and a table to the volunteer page, with links to project pages, code repos, bug trackers, and project ideas. Also, a few other minor changes: - Adding a note that the usability project is a no-go for gsoc. - Dropping the "Improvements for Tor+Vidalia interaction on Linux/Unix platforms" task (chiiph mentioned that it's completed) - Adding Jake as a mentor for a couple other projects.

Damian Johnson authored on12/02/2011 10:42:44
Showing3 changed files
... ...
@@ -60,6 +60,7 @@
60 60
       certification, etc.</li>
61 61
     </ul>
62 62
     
63
+    <a id="irc"></a>
63 64
     Tor users and developers can also be found in the following channels on <a
64 65
     href="http://www.oftc.net/oftc/">oftc</a>:
65 66
     
... ...
@@ -323,3 +323,35 @@ table .name {
323 323
 	line-height: 18px;
324 324
 }
325 325
 
326
+/* PROJECTS TABLE ----*/
327
+
328
+#projects {
329
+  font-family: sans-serif;
330
+  width: 100%;
331
+  border-collapse: collapse;
332
+}
333
+
334
+#projects td, #projects th {
335
+  font-size: 1.2em;
336
+  border: 1px solid #98bf21;
337
+  padding: 3px 7px 2px 7px;
338
+}
339
+
340
+#projects th {
341
+  font-size: 1.4em;
342
+  text-align: left;
343
+  padding-top: 5px;
344
+  padding-bottom: 4px;
345
+  background-color: #A7C942;
346
+  color: #fff;
347
+}
348
+
349
+#projects tr.alt td {
350
+  color: #000;
351
+  background-color: #EAF2D3;
352
+}
353
+
354
+#projects a {
355
+  text-decoration: none;
356
+}
357
+
... ...
@@ -66,10 +66,476 @@ meetings around the world.</li>
66 66
     You are using Tor!" in any language.</li>
67 67
     </ol>
68 68
     
69
+    <a id="Projects"></a>
70
+    <h2><a class="anchor" href="#Projects">Projects</a></h2>
71
+    
72
+    <p>
73
+    Below are a list of Tor related projects we're developing and/or
74
+    maintaining. Most discussions happen on IRC so if you're interested in any
75
+    of these (or you have a project idea of your own), then please <a
76
+    href="<page about/contact>#irc">join us in #tor-dev</a>. Project
77
+    contributors are listed by their IRC nicks.
78
+    </p>
79
+    
80
+    <table id="projects">
81
+      <tr>
82
+        <th>Name</th>
83
+        <th>Category</th>
84
+        <th>Language</th>
85
+        <th>Activity</th>
86
+        <th>Contributors</th>
87
+      </tr>
88
+      
89
+      <tr>
90
+        <td><a href="#project-tor">Tor</a></td>
91
+        <td>Core</td>
92
+        <td>C</td>
93
+        <td>Heavy</td>
94
+        <td>nickm, arma, etc</td>
95
+      </tr>
96
+      
97
+      <tr class="alt">
98
+        <td><a href="#project-tbb">TBB</a></td>
99
+        <td>Usability</td>
100
+        <td>Multiple</td>
101
+        <td>Heavy</td>
102
+        <td>helix</td>
103
+      </tr>
104
+      
105
+      <tr>
106
+        <td><a href="#project-torsocks">Torsocks</a></td>
107
+        <td>Usability</td>
108
+        <td>C</td>
109
+        <td>Light</td>
110
+        <td>mwenge</td>
111
+      </tr>
112
+      
113
+      <tr class="alt">
114
+        <td>*<a href="#project-torouter">Torouter</a></td>
115
+        <td>Usability</td>
116
+        <td>None</td>
117
+        <td>Light</td>
118
+        <td>ioerror, Runa</td>
119
+      </tr>
120
+      
121
+      <tr>
122
+        <td><a href="#project-vidalia">Vidalia</a></td>
123
+        <td>User Interface</td>
124
+        <td>C++, Qt</td>
125
+        <td>Light</td>
126
+        <td>chiiph</td>
127
+      </tr>
128
+      
129
+      <tr class="alt">
130
+        <td><a href="#project-arm">Arm</a></td>
131
+        <td>User Interface</td>
132
+        <td>Python, Curses</td>
133
+        <td>Heavy</td>
134
+        <td>atagar</td>
135
+      </tr>
136
+      
137
+      <tr>
138
+        <td><a href="#project-orbot">Orbot</a></td>
139
+        <td>User Interface</td>
140
+        <td>Java</td>
141
+        <td>None</td>
142
+        <td>n8fr8</td>
143
+      </tr>
144
+      
145
+      <tr class="alt">
146
+        <td><a href="#project-torbutton">Torbutton</a></td>
147
+        <td>Browser Add-on</td>
148
+        <td>Javascript</td>
149
+        <td>Moderate</td>
150
+        <td>mikeperry</td>
151
+      </tr>
152
+      
153
+      <tr>
154
+        <td>*<a href="#project-thandy">Thandy</a></td>
155
+        <td>Updater</td>
156
+        <td>Python</td>
157
+        <td>Light</td>
158
+        <td>Sebastian, helix</td>
159
+      </tr>
160
+      
161
+      <tr class="alt">
162
+        <td><a href="#project-torctl">TorCtl</a></td>
163
+        <td>Library</td>
164
+        <td>Python</td>
165
+        <td>Light</td>
166
+        <td>mikeperry</td>
167
+      </tr>
168
+      
169
+      <tr>
170
+        <td>*<a href="#project-jtor">JTor</a></td>
171
+        <td>Library</td>
172
+        <td>Java</td>
173
+        <td>None</td>
174
+        <td></td>
175
+      </tr>
176
+      
177
+      <tr class="alt">
178
+        <td><a href="#project-metrics">Metrics</a></td>
179
+        <td>Client Service</td>
180
+        <td>Java</td>
181
+        <td>Heavy</td>
182
+        <td>karsten</td>
183
+      </tr>
184
+      
185
+      <tr>
186
+        <td><a href="#project-torstatus">TorStatus</a></td>
187
+        <td>Client Service</td>
188
+        <td>PHP</td>
189
+        <td>None</td>
190
+        <td></td>
191
+      </tr>
192
+      
193
+      <tr class="alt">
194
+        <td><a href="#project-weather">Weather</a></td>
195
+        <td>Client Service</td>
196
+        <td>Python</td>
197
+        <td>Light</td>
198
+        <td>kaner</td>
199
+      </tr>
200
+      
201
+      <tr>
202
+        <td><a href="#project-gettor">GetTor</a></td>
203
+        <td>Client Service</td>
204
+        <td>Python</td>
205
+        <td>None</td>
206
+        <td></td>
207
+      </tr>
208
+      
209
+      <tr class="alt">
210
+        <td><a href="#project-torcheck">TorCheck</a></td>
211
+        <td>Client Service</td>
212
+        <td>Python, Perl</td>
213
+        <td>None</td>
214
+        <td></td>
215
+      </tr>
216
+      
217
+      <tr>
218
+        <td><a href="#project-bridgedb">BridgeDB</a></td>
219
+        <td>Backend Service</td>
220
+        <td>Python</td>
221
+        <td>None</td>
222
+        <td>kaner</td>
223
+      </tr>
224
+      
225
+      <tr class="alt">
226
+        <td><a href="#project-torflow">TorFlow</a></td>
227
+        <td>Backend Service</td>
228
+        <td>Python</td>
229
+        <td>None</td>
230
+        <td>mikeperry</td>
231
+      </tr>
232
+      
233
+      <tr>
234
+        <td>*<a href="#project-torbel">TorBEL</a></td>
235
+        <td>Backend Service</td>
236
+        <td>Python</td>
237
+        <td>None</td>
238
+        <td>Sebastian</td>
239
+      </tr>
240
+    </table>
241
+    
242
+    <sub>
243
+    * Project is still in an alpha state.
244
+    </sub>
245
+    
246
+    <br /><br />
247
+    
248
+    <a id="project-tor"></a>
249
+    <h3>Tor (<a href="https://gitweb.torproject.org/tor.git">code</a>, <a
250
+    href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Tor+Client&component=Tor+Relay&component=vidalia&order=priority">bug
251
+    tracker</a>)</h3>
252
+    
253
+    <p>
254
+    Central project, providing the core software for using and participating in
255
+    the Tor network. Numerous people contribute to the project to varying
256
+    extents, but the chief architects are Nick Mathewson and Roger Dingledine.
257
+    </p>
258
+    
259
+    <p>
260
+    <b>Project Ideas:</b><br />
261
+    <i><a href="#resistCensorship">Improving Tor's ability to resist
262
+    censorship</a></i><br />
263
+    <i><a href="#unitTesting">Improve our unit testing process</a></i><br />
264
+    <i><a href="#simulateSlowConnections">Simulator for slow Internet connections</a></i>
265
+    </p>
266
+    
267
+    <a id="project-tbb"></a>
268
+    <h3><a href="<page projects/torbrowser>">Tor Browser Bundle</a> (<a
269
+    href="https://gitweb.torproject.org/torbrowser.git">code</a>, <a
270
+    href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Tor+bundles/installation&order=priority">bug
271
+    tracker</a>)</h3>
272
+    
273
+    <p>
274
+    The Tor Browser Bundle is an easy-to-use portable package of Tor, Vidalia,
275
+    and Firefox preconfigured to work together out of the box. This is actively
276
+    being worked on by Erinn Clark.
277
+    </p>
278
+    
279
+    <p>
280
+    <b>Project Ideas:</b><br />
281
+    <i><a href="#auditTBB">Audit Tor Browser Bundles for data leaks</a></i><br />
282
+    <i><a href="#usabilityTesting">Usability testing of Tor</a></i>
283
+    </p>
284
+    
285
+    <a id="project-torsocks"></a>
286
+    <h3><a href="http://code.google.com/p/torsocks/">Torsocks</a> (<a
287
+    href="https://gitweb.torproject.org/torsocks.git">code</a>, <a
288
+    href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torify&order=priority">bug
289
+    tracker</a>)</h3>
290
+    
291
+    <p>
292
+    Utility for adapting other applications to work with Tor. Development has
293
+    slowed and compatibility issues remain with some platforms, but it's
294
+    otherwise feature complete.
295
+    </p>
296
+    
297
+    <p>
298
+    <b>Project Ideas:</b><br />
299
+    <i><a href="#torsocksForOSX">Make torsocks/dsocks work on OS X</a></i>
300
+    </p>
301
+    
302
+    <a id="project-torouter"></a>
303
+    <h3><a
304
+    href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/Torouter">Torouter</a> (<a
305
+    href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torouter&order=priority">bug
306
+    tracker</a>)</h3>
307
+    
308
+    <p>
309
+    Project to provide an easy-to-use, embedded Tor instance for routers. This
310
+    had a couple months of high activity, but has since been rather quiet.
311
+    </p>
312
+    
313
+    <a id="project-vidalia"></a>
314
+    <h3><a href="<page projects/vidalia>">Vidalia</a> (<a
315
+    href="https://svn.torproject.org/vidalia/vidalia/trunk/">code</a>, <a
316
+    href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Vidalia&order=priority">bug
317
+    tracker</a>)</h3>
318
+    
319
+    <p>
320
+    The most commonly used user interface for Tor. Matt Edman started the
321
+    project in 2006 and brought it to its current stable state. Development
322
+    slowed for several years, though Tomás Touceda has since taken a lead with
323
+    pushing the project forward.
324
+    </p>
325
+    
326
+    <p>
327
+    <b>Project Ideas:</b><br />
328
+    <i><a href="#vidaliaStatusEventInterface">Tor Controller Status Event Interface for Vidalia</a></i><br />
329
+    <i><a href="#vidaliaNetworkMap">An Improved and More Usable Network Map in Vidalia</a></i>
330
+    </p>
331
+    
332
+    <a id="project-arm"></a>
333
+    <h3><a href="http://www.atagar.com/arm/">Arm</a> (<a
334
+    href="https://svn.torproject.org/svn/arm/trunk/">code</a>, <a
335
+    href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=arm&order=priority">bug
336
+    tracker</a>)</h3>
337
+    
338
+    <p>
339
+    Command-line monitor for Tor. This has been under very active development
340
+    by its author, Damian Johnson, since early 2009 to make it a better
341
+    general-purpose controller for *nix environments.
342
+    </p>
343
+    
344
+    <p>
345
+    <b>Project Ideas:</b><br />
346
+    <i><a href="#armClientMode">Client Mode Use Cases for Arm</a></i>
347
+    </p>
348
+    
349
+    <a id="project-orbot"></a>
350
+    <h3><a href="https://guardianproject.info/apps/orbot/">Orbot</a> (<a
351
+    href="https://svn.torproject.org/svn/projects/android/trunk/Orbot/">code</a>, <a
352
+    href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Orbot&order=priority">bug
353
+    tracker</a>)</h3>
354
+    
355
+    <p>
356
+    Provides Tor on the Android platform. This was under very active
357
+    development up through Fall 2010, after which things have been quiet.
358
+    </p>
359
+    
360
+    <p>
361
+    <b>Project Ideas:</b><br />
362
+    <i><a href="#orbotDevelopment">More on Orbot & Android OS-specific development</a></i>
363
+    </p>
364
+    
365
+    <a id="project-torbutton"></a>
366
+    <h3><a href="<page torbutton/index>">Torbutton</a> (<a
367
+    href="https://gitweb.torproject.org/torbutton.git">code</a>, <a
368
+    href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torbutton&order=priority">bug
369
+    tracker</a>)</h3>
370
+    
371
+    <p>
372
+    Firefox addon that addresses many of the client-side threats to browsing
373
+    the Internet anonymously. Mike has since continued to adapt it to new
374
+    threats, updated versions of Firefox, and possibly <a
375
+    href="https://blog.torproject.org/blog/google-chrome-incognito-mode-tor-and-fingerprinting">Chrome
376
+    as well</a>.
377
+    </p>
378
+    
379
+    <p>
380
+    <b>Project Ideas:</b><br />
381
+    <i><a href="#torbuttonForThunderbird">Torbutton equivalent for Thunderbird</a></i>
382
+    </p>
383
+    
384
+    <a id="project-thandy"></a>
385
+    <h3>Thandy (<a
386
+    href="https://gitweb.torproject.org/thandy.git">code</a>)</h3>
387
+    
388
+    <p>
389
+    Updater for Tor. The project began in the Summer of 2008 but wasn't
390
+    completed. Recently interest in it has been rekindled and many aspects of
391
+    its design (including the language it'll be in) are currently in flux.
392
+    </p>
393
+    
394
+    <a id="project-torctl"></a>
395
+    <h3>TorCtl (<a
396
+    href="https://gitweb.torproject.org/pytorctl.git">code</a>, <a
397
+    href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torctl&order=priority">bug
398
+    tracker</a>)</h3>
399
+    
400
+    <p>
401
+    Python bindings and utilities for using the Tor control port. It has been
402
+    stable for several years, with only minor revisions.
403
+    </p>
404
+    
405
+    <a id="project-jtor"></a>
406
+    <h3><a href="https://github.com/brl/JTor/wiki">JTor</a> (<a
407
+    href="https://github.com/brl/JTor">code</a>, <a
408
+    href="https://github.com/brl/JTor/issues">bug
409
+    tracker</a>)</h3>
410
+    
411
+    <p>
412
+    Java implementation of Tor. This project isn't yet complete, and has been
413
+    inactive since Fall 2010.
414
+    </p>
415
+    
416
+    <a id="project-metrics"></a>
417
+    <h3><a href="https://metrics.torproject.org/">Metrics</a> (code: <a
418
+    href="https://gitweb.torproject.org/metrics-db.git">db</a>, <a
419
+    href="https://gitweb.torproject.org/metrics-utils.git">utils</a>, <a
420
+    href="https://gitweb.torproject.org/metrics-web.git">web</a>, <a
421
+    href="https://gitweb.torproject.org/metrics.git">general</a>, <a
422
+    href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Metrics&order=priority">bug
423
+    tracker</a>)</h3>
424
+    
425
+    <p>
426
+    Processing and analytics of consensus data, provided to users via the
427
+    metrics portal. This has been under active development for several years by
428
+    Karsten Loesing.
429
+    </p>
430
+    
431
+    <p>
432
+    <b>Project Ideas:</b><br />
433
+    <i><a href="#trackNetworkStatus">Help track the overall Tor Network status</a></i>
434
+    </p>
435
+    
436
+    <a id="project-torstatus"></a>
437
+    <h3><a href="https://trac.torproject.org/projects/tor/wiki/projects/TorStatus">TorStatus</a> (<a
438
+    href="https://svn.torproject.org/svn/torstatus/trunk/">code</a>)</h3>
439
+    
440
+    <p>
441
+    Portal providing an overview of the Tor network, and details on any of its
442
+    current relays. Though very actively used, this project has been
443
+    unmaintained for a long while.
444
+    </p>
445
+    
446
+    <a id="project-weather"></a>
447
+    <h3><a href="https://trac.torproject.org/projects/tor/wiki/projects/Weather">Weather</a> (<a
448
+    href="https://gitweb.torproject.org/weather.git">code</a>, <a
449
+    href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Tor+Weather&order=priority">bug
450
+    tracker</a>)</h3>
451
+    
452
+    <p>
453
+    Provides automatic notification to subscribed relay operators when their
454
+    relay's unreachable. This underwent a rewrite by the <a
455
+    href="http://hfoss.wesleyan.edu/">Wesleyan HFOSS team</a>, which went live
456
+    in early 2011.
457
+    </p>
458
+    
459
+    <a id="project-gettor"></a>
460
+    <h3><a href="https://trac.torproject.org/projects/tor/wiki/projects/EmailAutoResponder">GetTor</a> (<a
461
+    href="https://svn.torproject.org/svn/projects/gettor/">code</a>, <a
462
+    href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=GetTor&order=priority">bug
463
+    tracker</a>)</h3>
464
+    
465
+    <p>
466
+    E-mail autoresponder providing Tor's packages over SMTP. This has been
467
+    relatively unchanged for quite a while.
468
+    </p>
469
+    
470
+    <a id="project-torcheck"></a>
471
+    <h3><a href="https://trac.torproject.org/projects/tor/wiki/projects/TorCheck">TorCheck</a> (<a
472
+    href="https://svn.torproject.org/svn/check/trunk/">code</a>, <a
473
+    href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Tor+Check&order=priority">bug
474
+    tracker</a>)</h3>
475
+    
476
+    <p>
477
+    Provides a simple site for determining if the visitor is using Tor or not.
478
+    This has been relatively unchanged for quite a while.
479
+    </p>
480
+    
481
+    <a id="project-bridgedb"></a>
482
+    <h3><a href="https://trac.torproject.org/projects/tor/wiki/projects/BridgeDB">BridgeDB</a> (<a
483
+    href="https://gitweb.torproject.org/bridgedb.git">code</a>, <a
484
+    href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=BridgeDB&order=priority">bug
485
+    tracker</a>)</h3>
486
+    
487
+    <p>
488
+    Backend bridge distributor, handling the various pools they're distributed
489
+    in. This was actively developed until Fall of 2010.
490
+    </p>
491
+    
492
+    <a id="project-torflow"></a>
493
+    <h3><a href="https://trac.torproject.org/projects/tor/wiki/projects/TorFlow">TorFlow</a> (<a
494
+    href="https://gitweb.torproject.org/torflow.git">code</a>, <a
495
+    href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Torflow&order=priority">bug
496
+    tracker</a>)</h3>
497
+    
498
+    <p>
499
+    Library and collection of services for actively monitoring the Tor network.
500
+    These include the Bandwidth Scanners (measuring throughput of relays) and
501
+    SoaT (scans for malicious or misconfigured exit nodes). SoaT was last
502
+    actively developed in the Summer of 2010, and the Bandwidth Scanners a few
503
+    months later. Both have been under active use since then, but development
504
+    has stopped.
505
+    </p>
506
+    
507
+    <a id="project-torbel"></a>
508
+    <h3><a
509
+    href="https://trac.torproject.org/projects/tor/wiki/projects/TorBulkExitlist">TorBEL</a> (<a
510
+    href="https://gitweb.torproject.org/tordnsel.git">code</a>, <a
511
+    href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=TorDNSEL/TorBEL&order=priority">bug
512
+    tracker</a>)</h3>
513
+    
514
+    <p>
515
+    The Tor Bulk Exitlist provides a method of identifying if IPs belong to
516
+    exit nodes or not. This is a replacement for TorDNSEL which is a stable
517
+    (though unmaintained) Haskell application for this purpose. The initial
518
+    version of TorBEL was started in GSOC 2010 but since then the project has
519
+    been inactive.
520
+    </p>
521
+    
522
+    <!--
523
+    Copy and fill out the following for new projects:
524
+    
525
+    <a id="project-"></a>
526
+    <h3><a href=""></a> (<a
527
+    href="">code</a>, <a
528
+    href="">bug
529
+    tracker</a>)</h3>
530
+    
531
+    <p>
532
+    </p>
533
+    
534
+    -->
535
+    
69 536
     <a id="Coding"></a>
70 537
     <a id="Summer"></a>
71
-    <a id="Projects"></a>
72
-    <h2><a class="anchor" href="#Projects">Good Coding Projects</a></h2>
538
+    <h2><a class="anchor" href="#Coding">Project Ideas</a></h2>
73 539
     
74 540
     <p>
75 541
     You may find some of these projects to be good <a href="<page
... ...
@@ -86,6 +552,7 @@ meetings around the world.</li>
86 552
     
87 553
     <ol>
88 554
     
555
+    <a id="auditTBB"></a>
89 556
     <li>
90 557
     <b>Audit Tor Browser Bundles for data leaks</b>
91 558
     <br>
... ...
@@ -112,6 +579,7 @@ meetings around the world.</li>
112 579
     TBB, please contact Erinn.</p>
113 580
     </li>
114 581
     
582
+    <a id="trackNetworkStatus"></a>
115 583
     <li>
116 584
     <b>Help track the overall Tor Network status</b>
117 585
     <br>
... ...
@@ -140,6 +608,7 @@ meetings around the world.</li>
140 608
     Status wish list</a>.</p>
141 609
     </li>
142 610
     
611
+    <a id="resistCensorship"></a>
143 612
     <li>
144 613
     <b>Improving Tor's ability to resist censorship</b>
145 614
     <br>
... ...
@@ -149,7 +618,7 @@ meetings around the world.</li>
149 618
     <br>
150 619
     Skill Level: <i>High</i>
151 620
     <br>
152
-    Likely Mentors: <i>Roger, Nick, Steven</i>
621
+    Likely Mentors: <i>Roger, Nick, Steven, Jake</i>
153 622
     <p>The Tor 0.2.1.x series makes <a
154 623
     href="<svnprojects>design-paper/blocking.html">significant
155 624
     improvements</a> in resisting national and organizational censorship.
... ...
@@ -180,6 +649,7 @@ meetings around the world.</li>
180 649
     robustness.</p>
181 650
     </li>
182 651
     
652
+    <a id="armClientMode"></a>
183 653
     <li>
184 654
     <b>Client Mode Use Cases for Arm</b>
185 655
     <br>
... ...
@@ -243,6 +713,7 @@ meetings around the world.</li>
243 713
     href="https://svn.torproject.org/svn/arm/trunk/TODO">TODO</a>.</p>
244 714
     </li>
245 715
     
716
+    <a id="unitTesting"></a>
246 717
     <li>
247 718
     <b>Improve our unit testing process</b>
248 719
     <br>
... ...
@@ -269,6 +740,7 @@ meetings around the world.</li>
269 740
     changes in performance on machines in different roles automatically.</p>
270 741
     </li>
271 742
     
743
+    <a id="orbotDevelopment"></a>
272 744
     <li>
273 745
     <b>More on Orbot &amp; Android OS-specific development</b>
274 746
     <br/>
... ...
@@ -279,7 +751,7 @@ meetings around the world.</li>
279 751
     <br>
280 752
     Skill Level: <i>Medium to High</i>
281 753
     <br>
282
-    Likely Mentors: <i>Nathan</i>
754
+    Likely Mentors: <i>Nathan, Jake</i>
283 755
     <p><b>Android Java UI work:</b> Improved home screen to show better
284 756
     statistics about data transferred (up/down), number of circuits
285 757
     connected, quality of connection and so on. The "Tether Wifi"
... ...
@@ -323,6 +795,7 @@ meetings around the world.</li>
323 795
     from 2G to 3G to Wifi, and so forth.</p>
324 796
     </li>
325 797
     
798
+    <a id="simulateSlowConnections"></a>
326 799
     <li>
327 800
     <b>Simulator for slow Internet connections</b>
328 801
     <br>
... ...
@@ -358,6 +831,7 @@ meetings around the world.</li>
358 831
     </p>
359 832
     </li>
360 833
     
834
+    <a id="torbuttonForThunderbird"></a>
361 835
     <li>
362 836
     <b>Torbutton equivalent for Thunderbird</b>
363 837
     <br>
... ...
@@ -377,68 +851,7 @@ meetings around the world.</li>
377 851
     </p>
378 852
     </li>
379 853
     
380
-    <li>
381
-    <b>Improvements for Tor+Vidalia interaction on Linux/Unix platforms</b>
382
-    <br>
383
-    Priority: <i>Medium</i>
384
-    <br>
385
-    Effort Level: <i>Medium</i>
386
-    <br>
387
-    Skill Level: <i>Medium</i>
388
-    <br>
389
-    Likely Mentors: <i>Erinn, Peter</i>
390
-    <p>
391
-    Vidalia currently doesn't play nicely with Tor on Linux and Unix platforms.
392
-    Currently, on Debian and Ubuntu, there is a configuration mechanism which
393
-    allows Vidalia to override Tor's ability to start on boot (by sourcing
394
-    <code>/etc/default/tor.vidalia</code> which sets <code>RUN_DAEMON=no</code> at the user's
395
-    request), but full implementation of <a href="<gitblob>doc/spec/control-spec.txt">ControlPort</a> 
396
-    communication is still required.
397
-    </p>
398
-    
399
-    <p>
400
-    A better solution on Linux and Unix platforms would be to use Tor's
401
-    ControlSocket, which allows Vidalia to talk to Tor via a Unix domain socket,
402
-    and could possibly be enabled by default in Tor's distribution packages.
403
-    Vidalia can then authenticate to Tor using filesystem-based (cookie)
404
-    authentication if the user running Vidalia is also in the distribution-specific
405
-    tor group.
406
-    </p>
407
-    
408
-    <p>
409
-    This project will first involve adding support for Tor's ControlSocket to
410
-    Vidalia. The student will then develop and test this support on various
411
-    distributions to make sure it behaves in a predictable and consistent manner on
412
-    all of them.
413
-    </p>
414
-    
415
-    <p>
416
-    The next challenge would be to find an intuitive and usable way for Vidalia to be
417
-    able to change Tor's configuration (torrc) even though it is located in
418
-    <code>/etc/tor/torrc</code> and thus immutable. In Debian and Ubuntu we handle
419
-    this with the aforementioned <code>/etc/default/tor.vidalia</code> but this
420
-    functionality could (or should) be less distribution-specific.
421
-    </p>
422
-    
423
-    <p>
424
-    The best idea we've come up with so far is to feed Tor a new configuration via
425
-    the ControlSocket when Vidalia starts, but that's bad because if the user is not
426
-    using the latest Debian/Ubuntu packages, they may not have disabled Tor's
427
-    ability to run on boot and will end up with a configuration that is different
428
-    from what they want. The second best idea we've come up with is for Vidalia to
429
-    write out a temporary torrc file and ask the user to manually move it to
430
-    <code>/etc/tor/torrc</code>, but that's bad because users shouldn't have to
431
-    mess with files directly.
432
-    </p>
433
-    
434
-    <p>
435
-    A person undertaking this project should have prior knowledge of various Linux
436
-    distributions and their packaging mechanisms as well as some C++ development
437
-    experience. Previous experience with Qt is helpful, but not required.
438
-    </p>
439
-    </li>
440
-    
441
-    
854
+    <a id="usabilityTesting"></a>
442 855
     <li>
443 856
     <b>Usability testing of Tor</b>
444 857
     <br>
... ...
@@ -455,8 +868,14 @@ meetings around the world.</li>
455 868
     fixes or new features. We get this informally at the moment, but a more
456 869
     structured process would be better.
457 870
     </p>
871
+    
872
+    <p>
873
+    Please note that since this isn't a coding project, it isn't suitable for
874
+    Google Summer of Code.
875
+    </p>
458 876
     </li>
459 877
     
878
+    <a id="authenticatingIrcProxy"></a>
460 879
     <li>
461 880
     <b>An authenticating IRC proxy</b>
462 881
     <br>
... ...
@@ -494,6 +913,7 @@ meetings around the world.</li>
494 913
     </p>
495 914
     </li>
496 915
     
916
+    <a id="torsocksForOSX"></a>
497 917
     <li>
498 918
     <b>Make torsocks/dsocks work on OS X</b>
499 919
     <br>
... ...
@@ -524,6 +944,7 @@ meetings around the world.</li>
524 944
     </p>
525 945
     </li>
526 946
     
947
+    <a id="vidaliaStatusEventInterface"></a>
527 948
     <li>
528 949
     <b>Tor Controller Status Event Interface for Vidalia</b>
529 950
     <br>
... ...
@@ -564,6 +985,7 @@ meetings around the world.</li>
564 985
     design/Photoshop fu, since we might want/need some shiny new icons too.</p>
565 986
     </li>
566 987
     
988
+    <a id="vidaliaNetworkMap"></a>
567 989
     <li>
568 990
     <b>An Improved and More Usable Network Map in Vidalia</b>
569 991
     <br>
... ...
@@ -632,6 +1054,69 @@ meetings around the world.</li>
632 1054
     </li>
633 1055
     -->
634 1056
 
1057
+    <!--
1058
+    <li>
1059
+    <b>Improvements for Tor+Vidalia interaction on Linux/Unix platforms</b>
1060
+    <br>
1061
+    Priority: <i>Medium</i>
1062
+    <br>
1063
+    Effort Level: <i>Medium</i>
1064
+    <br>
1065
+    Skill Level: <i>Medium</i>
1066
+    <br>
1067
+    Likely Mentors: <i>Erinn, Peter</i>
1068
+    <p>
1069
+    Vidalia currently doesn't play nicely with Tor on Linux and Unix platforms.
1070
+    Currently, on Debian and Ubuntu, there is a configuration mechanism which
1071
+    allows Vidalia to override Tor's ability to start on boot (by sourcing
1072
+    <code>/etc/default/tor.vidalia</code> which sets <code>RUN_DAEMON=no</code> at the user's
1073
+    request), but full implementation of <a href="<gitblob>doc/spec/control-spec.txt">ControlPort</a> 
1074
+    communication is still required.
1075
+    </p>
1076
+    
1077
+    <p>
1078
+    A better solution on Linux and Unix platforms would be to use Tor's
1079
+    ControlSocket, which allows Vidalia to talk to Tor via a Unix domain socket,
1080
+    and could possibly be enabled by default in Tor's distribution packages.
1081
+    Vidalia can then authenticate to Tor using filesystem-based (cookie)
1082
+    authentication if the user running Vidalia is also in the distribution-specific
1083
+    tor group.
1084
+    </p>
1085
+    
1086
+    <p>
1087
+    This project will first involve adding support for Tor's ControlSocket to
1088
+    Vidalia. The student will then develop and test this support on various
1089
+    distributions to make sure it behaves in a predictable and consistent manner on
1090
+    all of them.
1091
+    </p>
1092
+    
1093
+    <p>
1094
+    The next challenge would be to find an intuitive and usable way for Vidalia to be
1095
+    able to change Tor's configuration (torrc) even though it is located in
1096
+    <code>/etc/tor/torrc</code> and thus immutable. In Debian and Ubuntu we handle
1097
+    this with the aforementioned <code>/etc/default/tor.vidalia</code> but this
1098
+    functionality could (or should) be less distribution-specific.
1099
+    </p>
1100
+    
1101
+    <p>
1102
+    The best idea we've come up with so far is to feed Tor a new configuration via
1103
+    the ControlSocket when Vidalia starts, but that's bad because if the user is not
1104
+    using the latest Debian/Ubuntu packages, they may not have disabled Tor's
1105
+    ability to run on boot and will end up with a configuration that is different
1106
+    from what they want. The second best idea we've come up with is for Vidalia to
1107
+    write out a temporary torrc file and ask the user to manually move it to
1108
+    <code>/etc/tor/torrc</code>, but that's bad because users shouldn't have to
1109
+    mess with files directly.
1110
+    </p>
1111
+    
1112
+    <p>
1113
+    A person undertaking this project should have prior knowledge of various Linux
1114
+    distributions and their packaging mechanisms as well as some C++ development
1115
+    experience. Previous experience with Qt is helpful, but not required.
1116
+    </p>
1117
+    </li>
1118
+    -->
1119
+    
635 1120
     <li>
636 1121
     <b>Bring up new ideas!</b>
637 1122
     <br>