[or-cvs] revamp the gui contest page
arma at seul.org
arma at seul.org
Wed Jul 20 22:02:48 UTC 2005
Update of /home2/or/cvsroot/website
In directory moria:/home/arma/work/onion/cvs/website
Modified Files:
gui-contest.html
Log Message:
revamp the gui contest page
Index: gui-contest.html
===================================================================
RCS file: /home2/or/cvsroot/website/gui-contest.html,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -d -r1.14 -r1.15
--- gui-contest.html 15 Jul 2005 22:19:37 -0000 1.14
+++ gui-contest.html 20 Jul 2005 22:02:46 -0000 1.15
@@ -41,10 +41,10 @@
<h2>Tor GUI Contest</h2>
<hr />
-<p>DRAFT IN PROGRESS -- ALL OF THIS STUFF IS IN FLUX AND SHOULD BE
-CONSIDERED WRONG.</p>
+<p>DRAFT IN PROGRESS</p>
<hr />
-<h3>Overview</h3>
+<a id="Overview"></a>
+<h3><a class="anchor" href="#Overview">Overview</a></h3>
<p>
Tor is a decentralized network of computers on the Internet that increases
@@ -69,7 +69,8 @@
</p>
<hr />
-<h3>Goals</h3>
+<a id="Goals"></a>
+<h3><a class="anchor" href="#Goals">Goals</a></h3>
<p>Contestants will produce a work of <a
href="http://www.fsf.org/licensing/essays/free-sw.html">Free Software</a>
@@ -85,11 +86,12 @@
<ul>
<li>Allow the user to fully configure Tor rather than manually searching
for and opening text files.</li>
-<li>Let users learn about the current state of their Tor connection (including
-which servers they are connected to, and how many of them), and find
-out whether any of their applications are using it.</li>
-<li>Make alerts and error conditions visible on screen.</li>
-<li>Run on at least one of Windows, Linux, and OS X, on a
+<li>Let users learn about the current state of their Tor connection
+(including which servers they are connected to, and how many connections
+they have), and find out whether any of their applications are using
+it.</li>
+<li>Make alerts and error conditions visible to the user.</li>
+<li>Run on at least one of Windows, Linux, and OS X, on a
not-unusually-configured consumer-level machine.</li>
</ul>
@@ -97,7 +99,7 @@
<ul>
<li>Provide detailed information about which
applications, ports, or packets are (or are not!) passing through Tor,
-including accounting for both Tor- and non-Tor traffic</li>
+including accounting for both Tor- and non-Tor traffic.</li>
<li>Provide
additional statistics about the Tor connection.</li>
<li>Give users more control over how their Tor behaves at certain times
@@ -106,13 +108,13 @@
<p>Some examples of useful features include:</p>
<ul>
-<li>How much bandwidth is the user using via Tor? How does this compare
+<li>How much bandwidth is Tor using? How does this compare
to the overall network traffic to/from the computer?</li>
<li>Is there network traffic from ports or applications that the user
intended to be anonymized?</li>
<li>What Tor servers does the user know about on the network? Where are
they? How available are they?</li>
-<li>Provide an interface for displaying or controlling Tor paths:
+<li>An interface for displaying or controlling Tor paths:
"show me the network from Africa by way of Asia". Think of the global
satellite map from the movie <i>Sneakers</i>.</li>
<li>Configure other running applications to use Tor (for example,
@@ -126,34 +128,42 @@
<li>Provide application-level anonymity -- that is, not just paying
attention to transport anonymity on the level of Tor, but also paying
attention to the anonymity of the http headers, cookies, etc.</li>
-<li>Let the user specify different config option sets depending on
+<li>Let the user specify different Tor config option sets depending on
time of day (e.g. daytime vs. nighttime).</li>
<li>Provide useful controller functions for Tor servers too --
-for example, recommended bandwidth configurations.</li>
+for example, walk the user through recommended bandwidth configurations
+and exit policies.</li>
<li>Have a "minimized view" of your GUI for common use, and then a more
detailed view or set of windows when the user wants more detail.</li>
<li>Provide a button or some automatically updating interface to let
-the user learn whether Tor is working currently; and give useful
-messages and recommendations if it doesn't seem to be working.</li>
+the user learn whether Tor is working currently, perhaps by accessing an
+external what's-my-IP site and seeing if it thinks you're a Tor server;
+and give useful messages and recommendations if it doesn't seem to
+be working.</li>
<li>Provide a way to automatically configure local firewalls (ipchains,
-Windows ones, etc) to let Tor traffic out (and in, for Tor servers).</li>
+Windows firewalls, etc) to let Tor traffic out (and in, for Tor
+servers). As a bonus, configure it to prevent non-Tor traffic from
+leaving (and notify when it tries).</li>
</ul>
<hr />
-<h3>Contest categories</h3>
+<a id="Categories"></a>
+<h3><a class="anchor" href="#Categories">Contest Categories</a></h3>
<p>
-The design contest will proceed in two stages: first sketches and
-then code. For each stage, our panel of judges will recognize the best
-submissions. All qualifying entries will receive an EFF Tor t-shirt,
-subject to availability. The best functional implementations will be
-published on the Tor website.
+The design contest will proceed in two stages: first sketches and then
+working code. For each stage, our panel of judges will recognize the
+best submissions. All qualifying entries will receive an EFF Tor T-shirt
+(subject to availability). The best sketches and working implementations
+will be published on the Tor website.
</p>
<p><b>Sketches:</b>
-the goal of this stage is to produce a mock-up of a functioning interface,
-with graphical elements that can be used by programmers and design
-documents describing how the interface should function.</p>
+the goal of this stage is to produce a mock-up of a functioning interface.
+This should include design documents describing how the interface should
+function. If you want, it should also include graphical elements that
+can be used by programmers.
+</p>
<p>
A qualifying sketch will present an informal specification for a
@@ -161,7 +171,7 @@
of the major interfaces that we might expect to encounter, all of the
major functionality for the interface, and a reasonable story about
how it would be integrated into currently-existing tools (if, indeed,
-it would be). An example, with more detail than we would require, is
+it would be). One example, with more detail than we would require, is
<a href="http://ui.netbeans.org/docs/ui/junits/promo_f.html">the NetBeans
UI for JUnit</a>. Note that it walks through multiple interfaces,
highlighting the features and functions of the various buttons.
@@ -170,7 +180,7 @@
<ul>
<li><b>Most featureful interface</b> will be awarded to the graphic design
that would provide usable, clear access to the most aspects of the Tor
-system, covering many or most of the categories on the "additional"
+system, covering many or most of the categories on the "useful features"
list.</li>
<li><b>Most usable experience</b> will be awarded to the graphic
design that would provide the most unobtrusive Tor experience while still
@@ -188,9 +198,9 @@
<p>
An acceptable entry will be a package of free software that builds and
-runs. It can be a standalone application, or it can act as an extension
+runs. It can be a stand-alone application, or it can act as an extension
or plugin to other broadly-available free software. The entry will
-demonstrate the points in the judging section: that is, it will be able
+demonstrate the points in the Goals section: that is, it will be able
to control, display, and maintain awareness as discussed above.
</p>
@@ -203,18 +213,19 @@
still covering all criteria (working, perhaps, on the "no news is good
news" theory).</li>
<li><b>Most flexible</b> will be awarded to the best system that runs
-smoothly on all three of Windows, Linux, and OS X; extra points will be
+smoothly on all three of Windows, Linux, and OS X; extra points will be
awarded for additional systems.</li>
</ul>
<p>We reserve the right to award other awards as the entries deserve.</p>
<hr />
-<h3>How to Submit</h3>
+<a id="Submit"></a>
+<h3><a class="anchor" href="#Submit">How to Submit</a></h3>
<p>Submissions for phase one (sketches) should come as:</p>
<ul>
-<li>foo<li>
+<li>TBD (please help me decide what this should say)<li>
</ul>
<p>Submissions for phase two (code) should come as:</p>
@@ -227,12 +238,13 @@
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 providing an overview of what major functions
-to look for and what functions were implemented.</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>
</ul>
<hr />
-<h3>Criteria</h3>
+<a id="Criteria"></a>
+<h3><a class="anchor" href="#Criteria">Criteria</a></h3>
<p>Awards will be granted on the basis of (in rough preference order):</p>
@@ -251,13 +263,15 @@
</ul>
<hr />
-<h3>Judges</h3>
+<a id="Judges"></a>
+<h3><a class="anchor" href="#Judges">Judges</a></h3>
<p>Judging will be led by a panel of N prominent specialists in usability
and security (to be announced).</p>
<hr />
-<h3>Timeline</h3>
+<a id="Timeline"></a>
+<h3><a class="anchor" href="#Timeline">Timeline</a></h3>
<ul>
<li>Stage 1 deadline (sketches): October 31.</li>
@@ -266,15 +280,19 @@
</ul>
<p>Winners will be announced on the webpage and also at the SOUPS 2006
-conference. (Here's a suggestion on <a
+conference. (Here's a suggestion on one approach to <a
href="http://wiki.noreply.org/noreply/TheOnionRouter/ContestFAQ#AcademicResearch">academic
usability research on Tor</a>.)</p>
<hr />
-<h3>Questions and clarifications</h3>
+<a id="Clarifications"></a>
+<h3><a class="anchor" href="#Clarifications">Questions and Clarifications</a></h3>
-<p>We will have a public website and wiki up shortly for FAQ entries,
-clarifications, etc.</p>
+<p>Check back <a
+href="http://tor.eff.org/gui-contest.html#Clarifications">here</a>
+periodically, and look at the <a
+href="http://wiki.noreply.org/noreply/TheOnionRouter/ContestFAQ">Contest
+FAQ wiki</a>, for FAQ entries, clarifications, etc.</p>
<!--
<hr />
@@ -295,7 +313,8 @@
-->
<hr />
-<h3>Technical Notes</h3>
+<a id="Technical"></a>
+<h3><a class="anchor" href="#Technical">Technical Notes</a></h3>
<p>Shortly before phase two begins, the Tor developers will release
a canonical code version. This is the version that will be used for
@@ -304,10 +323,14 @@
<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.</p>
+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.
+</p>
<hr />
-<h3>Legal Notes</h3>
+<a id="Legal"></a>
+<h3><a class="anchor" href="#Legal">Legal Notes</a></h3>
<p>By submitting your entry to be considered in the Tor GUI contest, you
hereby:</p>
@@ -322,16 +345,17 @@
perpetual license to reproduce, edit, perform, display, publish, make
derivative works, and otherwise use the entry as we see fit,
including without limitation, incorporating (in whole or in part)
-into the Tor software, and to sublicense such rights; OR, (2) provide
-the entry pursuant to a license that complies with the Open Source
-Definition (http://www.opensource.org/docs/definition.php), such as
-the 3-clause BSD, MIT, or GPL licenses, or (where applicable) the Creative
-Commons Attribution (http://creativecommons.org/licenses/by/2.5/)
-license. If you provide the entry pursuant to such a license, you
-must include the applicable information in your submission.</li>
+into the Tor software, and to sublicense such rights; OR, (2)
+provide the entry pursuant to a license that complies with the
+<a href="http://www.opensource.org/docs/definition.php">Open
+Source Definition</a>, such as the 3-clause BSD, MIT, or
+GPL licenses, or (where applicable) provide the entry licensed under
+the <a href="http://creativecommons.org/licenses/by/2.5/">Creative
+Commons Attribution</a> license. If you provide the entry pursuant to
+such a license, you must include the applicable information in your
+submission.</li>
</ul>
-
</div><!-- #main -->
</div>
<div class="bottom" id="bottom">
More information about the tor-commits
mailing list