tor-webwml.git

@@ -86,8 +86,10 @@ and design documentation to aid would-be implementers.</li>

 <p><b>Code:</b> the goal of this phase is to produce a working

 implementation. You may use any of the sketches, graphics, or ideas from

-the first phase (with appropriate credit to

-their authors), or you can make your own. See the <a

+the <a

+href="http://wiki.noreply.org/noreply/TheOnionRouter/ContestEntries">first

+phase</a> (with appropriate credit to their authors), or you can make

+your own. See the <a

 href="http://wiki.noreply.org/noreply/TheOnionRouter/ContestSamples">Competition

 Samples</a> wiki page for some other images you can reuse.

 </p>

@@ -75,7 +74,7 @@ Harvard University</li>

 <ul>

 <li>Phase 1 deadline (sketches): November 30, 2005.</li>

-<li>Phase 2 deadline (code): February 28, 2006.</li>

+<li>Phase 2 deadline (code): April 30, 2006.</li>

 </ul>

 <p>Winners will be announced on the webpage and also at the SOUPS 2006

@@ -40,18 +39,27 @@

 <h2>News:</h2>

-<p>The <a

-href="http://wiki.noreply.org/noreply/TheOnionRouter/ContestEntries">phase

-one submissions</a> are in! Our judges are starting to review them now.</p>

+<p>2006-02: Phase two is now underway &mdash; developing actual interfaces

+for Tor. It's open to all who want to participate. We've set the new

+deadline to Apr 30 2006.

+</p>

-<p>Due to volume of interest, we've decided to push back the deadlines

-for the GUI competition by 4 weeks: so the first deadline is Nov 30 2005,

-and the second deadline is Feb 28 2006.</p>

+<p>2006-02: The <a

+href="http://wiki.noreply.org/noreply/TheOnionRouter/ContestEntries">the

+first design phase</a> is over, and we have two winners. Feel free to

+use their ideas if you like them:

+<ul>

+<li>Best overall: <a

+href="http://cups.cs.cmu.edu/pubs/TorGUIContest113005.pdf">CMU Usable

+Privacy and Security Laboratory</a></li>

+<li>Most aesthetically pleasing:

+<a href="http://www.april3rd.com/tor/">the April3rd team</a></li>

+</ul>

 <p>

-We're excited to have just added <a href="criteria.html">Edward Tufte

+2005-12: We're excited to have just added <a href="criteria.html">Edward Tufte

 and Bruce Schneier</a> to our already impressive list of judges. And don't

-forget the free T-shirt for every submission!

+forget the free Tor T-shirt for every submission!

 </p>

 <h2>Tor: GUI Competition Overview</h2>

@@ -59,8 +67,8 @@ forget the free T-shirt for every submission!

 <p>

 Tor is a decentralized network of computers on the Internet that increases

 privacy in Web browsing, instant messaging, and other applications. We

-estimate there are some 50,000 Tor users currently, routing their traffic

-through about 250 volunteer Tor servers on six continents. However, Tor's

+estimate there are some 200,000 Tor users currently, routing their traffic

+through about 400 volunteer Tor servers on six continents. However, Tor's

 current user interface approach — running as a service in the background

 — does a poor job of communicating network status and security levels

 to the user.

@@ -80,16 +88,15 @@ applications are using Tor safely.

 <br />

 <h2>Goals</h2>

-<p>Submitters will produce either sketches for a suggested user interface,

-or a work of <a

+<p>Submitters for phase two will produce a work of <a

 href="http://www.opensource.org/">Open Source Software</a>

 that will provide a user interface to the Tor system by way of the

-<a href="/cvs/control/doc/howto.txt">Tor Controller Protocol</a>.</p>

+<a href="<cvssandbox>control/doc/howto.txt">Tor Controller Protocol</a>.</p>

 <p>We are looking for a vision of how Tor can work in a user's everyday

 anonymous browsing experience.</p>

-<p>Entries will:</p>

+<p>Entries may:</p>

 <ul>

 <li>Allow the user to fully configure Tor rather than manually searching

 for and opening text files.</li>

@@ -101,7 +108,7 @@ and find out whether any of their applications are using it.</li>

 not-unusually-configured consumer-level machine.</li>

 </ul>

-<p>In addition, they may:</p>

+<p>Other ideas include:</p>

 <ul>

 <li>Provide detailed information about which

 applications, ports, or packets are (or are not!) passing through Tor,

@@ -112,7 +119,7 @@ additional statistics about the Tor connection.</li>

 of day or in other contexts (like operating as a server).</li>

 </ul>

-<p>Some examples of useful features include:</p>

+<p>More examples of useful features include:</p>

 <ul>

 <li>How much bandwidth is Tor using? How does this compare

 to the overall network traffic to/from the computer?</li>

@@ -60,7 +60,7 @@ href="http://wiki.noreply.org/noreply/TheOnionRouter/ContestFAQ#DefineFree">this

 FAQ entry</a> for clarification.</li>

 <li>Compiled binaries or bytecodes for at least one platform of choice.</li>

 <li>A design document (txt, html, pdf, or ps) providing an overview of

-what major functions to look for and what functions were implemented.</li>

+what major functions to look for and what functions are implemented.</li>

 </ul>

 <p>To submit your entry, make a web page with

@@ -41,19 +41,21 @@

 <h2>Technical Notes</h2>

-<p>Shortly before phase two begins, the Tor developers will release

-a canonical version of Tor. This is the version that will be used for

+<p>For phase two, the canonical version of Tor is going to be the

+upcoming 0.1.1.x release. This is the version that will be used for

 judging the competition; please ensure that you use this version. Bugfixes

-to this version of Tor will be announced to the competition web site.</p>

+to this version of Tor will be announced on the

+<a href="<page download>">Tor download page</a>.

+Let us know if you find bugs!

+</p>

 <p>The Tor developers will also release test rigs (libraries) in both Java

 and Python that demonstrate Tor's controller protocol. Code submissions

 may be able to save a lot of time by using this code as a skeleton. You

 can check out the <a href="http://tor.eff.org/cvs/control/">development

-versions of these libraries</a> now.

+versions of these libraries</a> now. Let us know if you find bugs!

 </p>

-

  </div><!-- #main -->

 #include <foot.wmi>