[or-cvs] r18815: {website} Comment some of the not-so-good-anymore GSoC coding projects (website/trunk/en)

kloesing at seul.org kloesing at seul.org
Mon Mar 9 02:46:18 UTC 2009


Author: kloesing
Date: 2009-03-08 22:46:18 -0400 (Sun, 08 Mar 2009)
New Revision: 18815

Modified:
   website/trunk/en/volunteer.wml
Log:
Comment some of the not-so-good-anymore GSoC coding projects out, and move two of them to another section. Now we have, uhm, 8 ideas left.


Modified: website/trunk/en/volunteer.wml
===================================================================
--- website/trunk/en/volunteer.wml	2009-03-09 00:56:22 UTC (rev 18814)
+++ website/trunk/en/volunteer.wml	2009-03-09 02:46:18 UTC (rev 18815)
@@ -97,6 +97,7 @@
 
 <ol>
 
+<!-- Mike is already working on this.
 <li>
 <b>Tor Node Scanner improvements</b>
 <br />
@@ -123,6 +124,7 @@
 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 @@
 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 @@
 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 @@
 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 @@
 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 @@
 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 @@
 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 @@
 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 @@
 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 @@
 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 @@
 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 @@
 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 @@
 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,26 +562,8 @@
 menu options. Double bonus if it's cross-platform compatible.
 </li>
 
+<!-- Is Blossom development still happening?
 <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>
-
-<li>
 <b>Rework and extend Blossom</b>
 <br />
 Rework and extend Blossom (a tool for monitoring and
@@ -611,6 +611,7 @@
 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 @@
 <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>



More information about the tor-commits mailing list