tor-webwml.git

@@ -97,6 +97,7 @@ might also be short on developers. If you think you can help out, <a href="<page

 <ol>

+<!-- Mike is already working on this.

 <li>

 <b>Tor Node Scanner improvements</b>

 <br />

@@ -123,6 +124,7 @@ scanner would also report information on oddly-behaving nodes to

 the Directory Authorities, but a communication channel for this

 currently does not exist and would need to be developed as well.

 </li>

+-->

 <li>

 <b>Help track the overall Tor Network status</b>

@@ -145,6 +147,7 @@ kept separate. Speaking of the Tor Status pages, take a look at Roger's

 Status wish list</a>.

 </li>

+<!-- Is this still a useful project? If so, move it to another section.

 <li>

 <b>Better Debian/Ubuntu Packaging for Tor+Vidalia</b>

 <br />

@@ -188,6 +191,7 @@ A person undertaking this project should have prior knowledge of

 Debian package management and some C++ development experience. Previous

 experience with Qt is helpful, but not required.

 </li>

+-->

 <li>

 <b>Improving Tor's ability to resist censorship</b>

@@ -216,6 +220,7 @@ resist an adversary even after the adversary knows the design, and

 then trading off censorship resistance with usability and robustness.

 </li>

+<!-- This should be mostly done.

 <li>

 <b>Tor/Polipo/Vidalia Auto-Update Framework</b>

 <br />

@@ -249,7 +254,9 @@ is also important for this project, since a vital step of the project

 will be producing a design document to review and discuss

 with others prior to implementation.

 </li>

+-->

+<!-- Matt already made good progress on this.

 <li>

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

 <br />

@@ -275,6 +282,7 @@ A person undertaking this project should have good C++ development

 experience. Previous experience with Qt and CMake is helpful, but not

 required.

 </li>

+-->

 <li>

 <b>Tor Controller Status Event Interface</b>

@@ -311,6 +319,7 @@ be understandable by non-technical users. Bonus points for some graphic

 design/Photoshop fu, since we might want/need some shiny new icons too.

 </li>

+<!-- Jake already did most of this.

 <li>

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

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

@@ -333,7 +342,9 @@ and involve more design and coding, take a look at <a

 href="<svnsandbox>doc/spec/proposals/131-verify-tor-usage.txt">proposal

 131-verify-tor-usage.txt</a>.

 </li>

+-->

+<!-- If we decide to switch to the exit list in TorStatus, this is obsolete.

 <li>

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

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

@@ -354,7 +365,9 @@ own documentation at the very least. Furthermore, it would be useful

 if they were interested in Haskell and wanted to implement more of the

 torel-design.txt suggestions.

 </li>

+-->

+<!-- Nobody wanted to keep this.

 <li>

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

 <br />

@@ -376,7 +389,9 @@ should help them to fix the problem or direct them to the proper support

 channels. The person should also be closely familiar with using Tor and how

 to prevent Tor information leakage.

 </li>

+-->

+<!-- Nick did quite some work here. Is this project still required then?

 <li>

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

 <br />

@@ -392,6 +407,7 @@ missing functionality to Libevent as needed — most difficult likely

 will be adding OpenSSL support on top of Libevent's buffer abstraction.

 Also tricky will be adding rate-limiting to Libevent.

 </li>

+-->

 <li>

 <b>Tuneup Tor!</b>

@@ -506,6 +522,7 @@ project is one part about identifying requirements to such a

 tool and designing its interface, and one part lots of coding.

 </li>

+<!-- Removed, unless Mike still wants this to be in.

 <li>

 <b>Torbutton improvements</b>

 <br />

@@ -524,6 +541,7 @@ This work would be independent coding in Javascript and the fun world of <a

 href="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul">XUL</a>,

 with not too much involvement in the Tor internals.

 </li>

+-->

 <li>

 <b>Porting Polipo to Windows</b>

@@ -544,25 +562,7 @@ and reporting tool, bonus if it has a systray icon with right clickable

 menu options. Double bonus if it's cross-platform compatible.

 </li>

-<li>

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

-<br />

-We need a way to generate the website diagrams (for example, the "How

-Tor Works" pictures on the <a href="<page overview>">overview page</a>

-from source, so we can translate them as UTF-8 text rather than edit

-them by hand with Gimp. We might want to

-integrate this as an wml file so translations are easy and images are

-generated in multiple languages whenever we build the website. 

-</li>

-

-<li>

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

-<br />

-How can we make the <a

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

-easier to maintain, improve, and document?

-</li>

-

+<!-- Is Blossom development still happening?

 <li>

 <b>Rework and extend Blossom</b>

 <br />

@@ -611,6 +611,7 @@ interest in network neutrality is important as well, since the

 principles of evaluating and understanding internet inconsistency are at

 the core of the Blossom effort.

 </li>

+-->

 <li>

 <b>Bring up new ideas!</b>

@@ -677,6 +678,17 @@ UDP</a> &mdash; please let us know what's wrong with it.</li>

 <li>We're not that far from having IPv6 support for destination addresses

 (at exit nodes). If you care strongly about IPv6, that's probably the

 first place to start.</li>

+

+<li>We need a way to generate the website diagrams (for example, the "How

+Tor Works" pictures on the <a href="<page overview>">overview page</a>

+from source, so we can translate them as UTF-8 text rather than edit

+them by hand with Gimp. We might want to

+integrate this as an wml file so translations are easy and images are

+generated in multiple languages whenever we build the website.</li>

+

+<li>How can we make the <a

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

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

 </ol>

 <a id="Research"></a>