tor-webwml.git

@@ -134,6 +134,14 @@ with the student prior to implementation.

 <li>

 <b>An Improved and More Usable Network Map</b>

 <br />

+Priority: <i>Medium</i>

+<br />

+Effort Level: <i>Medium</i>

+<br />

+Skill Level: <i>Medium to High</i>

+<br />

+Likely Mentors: <i>Matt, others</i>

+<br />

 One of Vidalia's existing features is a network map that shows the user

 the approximate geographic location of relays in the Tor network and

 plots the paths the user's traffic takes as it is tunneled through the

@@ -160,6 +168,14 @@ required.

 <li>

 <b>Better Debian Packaging and Debian Packaging Support</b>

 <br />

+Priority: <i>High</i>

+<br />

+Effort Level: <i>Medium</i>

+<br />

+Skill Level: <i>Medium</i>

+<br />

+Likely Mentors: <i>Weasel, Matt, others</i>

+<br />

 Vidalia currently doesn't play nicely on Debian and Ubuntu with the

 default Tor packages. The current Tor packages automatically start Tor

 as a daemon running as the debian-tor user and (sensibly) do not have a

@@ -192,6 +208,14 @@ experience with Qt is helpful, but not required.

 <li>

 <b>Tor Status Event Interface</b>

 <br />

+Priority: <i>Medium</i>

+<br />

+Effort Level: <i>Medium</i>

+<br />

+Skill Level: <i>Medium</i>

+<br />

+Likely Mentors: <i>Matt, others</i>

+<br />

 There may are a number of status changes of which the user may need

 to be informed. For example, if the user is trying to set up a Tor

 relay and Tor decides the user's relay is not reachable from outside

@@ -227,6 +251,14 @@ design/Photoshop fu, since we might want/need some shiny new icons too.

 <li>

 <b>A Translation Wiki</b>

 <br />

+Priority: <i>High</i>

+<br />

+Effort Level: <i>Medium</i>

+<br />

+Skill Level: <i>Medium</i>

+<br />

+Likely Mentors: <i>Jacob, others</i>

+<br />

 We require a way to edit and translate sections of the website —

 possibly resulting in a patch for the official svn tree. The current

 "cost" of publication of website changes is quite high even for English

@@ -246,6 +278,14 @@ with the software, only the documentation on the website.

 <b>Improvements on our active browser configuration tester</b> - 

 <a href="https://check.torproject.org">https://check.torproject.org</a>

 <br />

+Priority: <i>Medium</i>

+<br />

+Effort Level: <i>Low</i>

+<br />

+Skill Level: <i>Low to Medium</i>

+<br />

+Likely Mentors: <i>Jacob, others</i>

+<br />

 We currently have a functional web page to detect if Tor is working. It

 is has a few places where it falls short. It requires improvements with

 regard to default languages and functionality. It currently only responds

@@ -263,6 +303,14 @@ to interact minimally with Tor to test their code.

 <b>Improvements on our DNS Exit List service</b> - 

 <a href="http://exitlist.torproject.org">http://exitlist.torproject.org</a>

 <br />

+Priority: <i>Medium</i>

+<br />

+Effort Level: <i>Low</i>

+<br />

+Skill Level: <i>Low</i>

+<br />

+Likely Mentors: <i>Jacob, Tup, others</i>

+<br />

 The exitlist software is written by our fabulous anonymous

 contributer Tup. It's a DNS server written in Haskell that supports part of our <a

 href="https://www.torproject.org/svn/trunk/doc/contrib/torel-design.txt">exitlist

@@ -282,6 +330,14 @@ torel-design.txt suggestions.

 <li>

 <b>Testing integration of Tor with web browsers for our end users</b>

 <br />

+Priority: <i>Medium</i>

+<br />

+Effort Level: <i>Medium</i>

+<br />

+Skill Level: <i>Medium</i>

+<br />

+Likely Mentors: <i>Jacob, Mike, others</i>

+<br />

 The Tor project currently lacks a solid test to ensure that a

 user has a properly configured web browser. It should test for as

 many known issues as possible. It should attempt to decloak the

@@ -303,6 +359,14 @@ to prevent Tor leakage.

 <li>

 <b>Improving our ability to be resistant to censorship</b>

 <br />

+Priority: <i>High</i>

+<br />

+Effort Level: <i>High</i>

+<br />

+Skill Level: <i>Medium to High</i>

+<br />

+Likely Mentors: <i>Roger, others</i>

+<br />

 Tor needs even better censorship resistance mechanisms.  There are

 several mechanisms that can help.  Tor should be able listen on multiple

 addresses and ports, and allow clients to connect to all of them.

@@ -313,6 +377,14 @@ contacted by port-scanning tools.

 <li>

 <b>Libevent and Tor integration improvements</b>

 <br />

+Priority: <i>Medium</i>

+<br />

+Effort Level: <i>High</i>

+<br />

+Skill Level: <i>Medium to High</i>

+<br />

+Likely Mentors: <i>Nick, others</i>

+<br />

 Tor should make better use of the more recent features of Niels Provos's

 Libevent library.  Libevent already provides HTTP and socket buffers;

 Tor's code for those could be replaced.  We'll need to improve libevent's

@@ -323,6 +395,14 @@ libevent's buffer abstraction.

 <li>

 <b>Tuneup Tor!</b>

 <br />

+Priority: <i>Medium</i>

+<br />

+Effort Level: <i>Medium</i>

+<br />

+Skill Level: <i>Medium to High</i>

+<br />

+Likely Mentors: <i>Roger, others</i>

+<br />

 Tor should possibly measure bandwidth in a distributed way, as in the

 <a href="http://freehaven.net/anonbib/">"A Tuneup for Tor"</a> paper

 by Snader and Borisov.  A student could use current testing code to

@@ -335,6 +415,14 @@ at the directory authorities.

 <li>

 <b>Improving the Tor QA process: Continuous Integration for Windows builds</b>

 <br />

+Priority: <i>High</i>

+<br />

+Effort Level: <i>Medium</i>

+<br />

+Skill Level: <i>Medium</i>

+<br />

+Likely Mentors: <i>Jacob, Phobos, others</i>

+<br />

 It would be useful to have automated build processes for Windows and

 probably other platforms. The purpose of having a continuous integration

 build environment is to ensure that Windows isn't left behind for any of

@@ -363,6 +451,14 @@ changes in performance on machines in different roles automatically.<br />

 <li>

 <b>Improve our unit testing process</b>

 <br />

+Priority: <i>Medium</i>

+<br />

+Effort Level: <i>Medium</i>

+<br />

+Skill Level: <i>Medium</i>

+<br />

+Likely Mentors: <i>Nick, others</i>

+<br />

 Tor needs to be far more tested.  This is a multi-part effort.  To start

 with, our unit test coverage should rise substantially, especially in

 the areas outside the utility functions.  This will require significant

@@ -380,6 +476,14 @@ changes in performance on machines in different roles automatically.<br />

 <li>

 <b>Help revive the Java community around Tor</b>

 <br />

+Priority: <i>High</i>

+<br />

+Effort Level: <i>High</i>

+<br />

+Skill Level: <i>Medium to High</i>

+<br />

+Likely Mentors: <i>Karsten, others</i>

+<br />

 Reanimate one of the approaches to implement a Tor client in Java,

 e.g. the <a href="http://onioncoffee.sourceforge.net/">OnionCoffee

 project</a>, and make it run on <a

@@ -400,6 +504,14 @@ to a small degree about design.

 <li>

 <b>Become the PuppeTor Master</b>

 <br />

+Priority: <i>Medium</i>

+<br />

+Effort Level: <i>Medium</i>

+<br />

+Skill Level: <i>Medium</i>

+<br />

+Likely Mentors: <i>Roger, others</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>

@@ -420,6 +532,14 @@ about design and partly about coding.

 <li>

 <b>Bring moniTor to life</b>

 <br />

+Priority: <i>Medium</i>

+<br />

+Effort Level: <i>Medium</i>

+<br />

+Skill Level: <i>Low to Medium</i>

+<br />

+Likely Mentors: <i>Karsten, Jacob, others</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

 to monitor a local Tor relay via its control port and include useful

@@ -475,9 +594,9 @@ setting.

 <br />

 Priority: <i>Medium</i>

 <br />

-Effort Level: <i>Medium-High</i>

+Effort Level: <i>Medium to High</i>

 <br />

-Skill Level: <i>Medium-High</i>

+Skill Level: <i>Medium to High</i>

 <br />

 Likely Mentors: <i>Mike Perry</i>

 <br />

@@ -509,7 +628,7 @@ currently does not exist and would need to be developed as well.

 <br />

 Priority: <i>High</i>

 <br />

-Effort Level: <i>Low-Medium</i>

+Effort Level: <i>Low to Medium</i>

 <br />

 Skill Level: <i>High</i>

 <br />

@@ -580,6 +697,14 @@ health and growth. Make it short and simple. Unbloated and easy to audit.

 <li>

 <b>Porting Polipo to Windows</b>

 <br />

+Priority: <i>High</i>

+<br />

+Effort Level: <i>High</i>

+<br />

+Skill Level: <i>Medium to High</i>

+<br />

+Likely Mentors: <i>Roger, others</i>

+<br />

 Help port <a

 href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> to

 Windows. 1) handle spaces in path names and understand the filesystem

@@ -598,6 +723,14 @@ menu options. Double bonus if it's cross-platform compatible.

 <li>

 <b>Make our diagrams beautiful and automated</b>

 <br />

+Priority: <i>High</i>

+<br />

+Effort Level: <i>Low</i>

+<br />

+Skill Level: <i>Low</i>

+<br />

+Likely Mentors: <i>Roger, others</i>

+<br />

 a way to generate the website diagrams from source, so we can translate

 them as utf-8 text rather than with gimp. (svg? or imagemagick?)

 integrate this with a wml file so translations are easy and images are

@@ -607,6 +740,14 @@ generated in multiple languages at web publish

 <li>

 <b>Improve the LiveCD offerings for the Tor community</b>

 <br />

+Priority: <i>Low</i>

+<br />

+Effort Level: <i>Low</i>

+<br />

+Skill Level: <i>Medium to High</i>

+<br />

+Likely Mentors: <i>Roger, others</i>

+<br />

 How can we make the <a

 href="http://anonymityanywhere.com/incognito/">Incognito LiveCD</a>

 easier to maintain, improve, and document?</li>