first draft cut of the gui stuff. both the content and the layout need to be cleaned up a lot.
Roger Dingledine commited on 2005-05-19 13:28:28
Zeige 1 geänderte Dateien mit 228 Einfügungen und 0 Löschungen.
- gui-contest.html 000000000..b42f36d44
| ... | ... |
@@ -0,0 +1,228 @@ |
| 1 |
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" |
|
| 2 |
+"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> |
|
| 3 |
+ |
|
| 4 |
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> |
|
| 5 |
+<head> |
|
| 6 |
+ <title>Tor GUI Contest</title> |
|
| 7 |
+ <meta name="Author" content="Roger Dingledine" /> |
|
| 8 |
+ <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1" /> |
|
| 9 |
+ <link rel="stylesheet" type="text/css" href="stylesheet.css" /> |
|
| 10 |
+ <link rel="shortcut icon" type="image/x-icon" href="/favicon.ico" /> |
|
| 11 |
+</head> |
|
| 12 |
+ |
|
| 13 |
+<body> |
|
| 14 |
+ |
|
| 15 |
+<!-- TITLE BAR & NAVIGATION --> |
|
| 16 |
+ |
|
| 17 |
+<table class="banner" border="0" cellpadding="0" cellspacing="0"> |
|
| 18 |
+ <tr> |
|
| 19 |
+ <td class="banner-left"></td> |
|
| 20 |
+ <td class="banner-middle"> |
|
| 21 |
+ <a href="index.html">Home</a> |
|
| 22 |
+ | <a href="howitworks.html">How It Works</a> |
|
| 23 |
+ | <a href="download.html">Download</a> |
|
| 24 |
+ | <a href="documentation.html">Docs</a> |
|
| 25 |
+ | <a href="users.html">Users</a> |
|
| 26 |
+ | <a href="faq.html">FAQs</a> |
|
| 27 |
+ | <a href="contribute.html">Contribute</a> |
|
| 28 |
+ | <a href="developers.html">Developers</a> |
|
| 29 |
+ | <a href="research.html">Research</a> |
|
| 30 |
+ | <a href="people.html">People</a> |
|
| 31 |
+ </td> |
|
| 32 |
+ <td class="banner-right"></td> |
|
| 33 |
+ </tr> |
|
| 34 |
+</table> |
|
| 35 |
+ |
|
| 36 |
+<!-- END TITLE BAR & NAVIGATION --> |
|
| 37 |
+ |
|
| 38 |
+<div class="center"> |
|
| 39 |
+ |
|
| 40 |
+<div class="main-column"> |
|
| 41 |
+ |
|
| 42 |
+<h2>Tor GUI Contest</h2> |
|
| 43 |
+<hr /> |
|
| 44 |
+<p>DRAFT IN PROGRESS -- ALL OF THIS STUFF IS IN FLUX AND SHOULD BE |
|
| 45 |
+CONSIDERED WRONG.</p> |
|
| 46 |
+<hr /> |
|
| 47 |
+<h3>Overview</h3> |
|
| 48 |
+ |
|
| 49 |
+<p> |
|
| 50 |
+Tor is a decentralized network of computers on the Internet that increases |
|
| 51 |
+privacy in Web browsing, instant messaging, and other applications. We |
|
| 52 |
+estimate there are some 20,000 Tor users currently, routing their traffic |
|
| 53 |
+through about 150 volunteer Tor servers on five continents. However, Tor's |
|
| 54 |
+current user interface approach --- running as a daemon in the background |
|
| 55 |
+--- does a poor job of communicating network status and security levels |
|
| 56 |
+to the user. The Tor project, affiliated with the Electronic Frontier |
|
| 57 |
+Foundation, is running a UI contest to develop a vision of how Tor can |
|
| 58 |
+work in a user's everyday anonymous browsing experience. Some of the |
|
| 59 |
+challenges include how to make alerts and error conditions visible on |
|
| 60 |
+screen; how to let the user configure Tor to use certain paths or avoid |
|
| 61 |
+certain paths; how to learn about the current state of a Tor connection, |
|
| 62 |
+including which servers it uses; and how to find out whether (and which) |
|
| 63 |
+applications are using Tor safely. |
|
| 64 |
+</p> |
|
| 65 |
+ |
|
| 66 |
+<hr /> |
|
| 67 |
+<h3>Goals</h3> |
|
| 68 |
+ |
|
| 69 |
+<p>Contestants will produce a work of Free software that will |
|
| 70 |
+provide a user interface to the Tor system by way of the <a |
|
| 71 |
+href="http://tor.eff.org/cvs/tor/doc/control-spec.txt">Tor Controller |
|
| 72 |
+Protocol</a>.</p> |
|
| 73 |
+ |
|
| 74 |
+<p>We are looking for a vision of how Tor can work in a user's everyday |
|
| 75 |
+anonymous browsing experience.</p> |
|
| 76 |
+ |
|
| 77 |
+<p>Successful entries will:</p> |
|
| 78 |
+<ul> |
|
| 79 |
+<li>Allow the user to fully configure Tor without directly editing |
|
| 80 |
+configuration files.</li> |
|
| 81 |
+<li>Learn about the current state of their Tor connection (including |
|
| 82 |
+which servers they are connected to, and how many of them), and find |
|
| 83 |
+out whether and how any of their applications are using it.</li> |
|
| 84 |
+<li>Make alerts and error conditions visible on screen.</li> |
|
| 85 |
+<li>Run on at least one of Windows, Linux, and OS/X, on a |
|
| 86 |
+not-unusually-configured consumer-level machine.</li> |
|
| 87 |
+</ul> |
|
| 88 |
+ |
|
| 89 |
+<p>In addition, entries may a) Provide detailed information about which |
|
| 90 |
+applications, ports, or packets are (or are not!) passing through Tor, |
|
| 91 |
+including accounting for both Tor- and non-Tor traffic; and b) Provide |
|
| 92 |
+additional statistics about the Tor connection.</p> |
|
| 93 |
+ |
|
| 94 |
+<p>Examples include:</p> |
|
| 95 |
+<ul> |
|
| 96 |
+<li>How much bandwidth am I using?</li> |
|
| 97 |
+<li>What servers do I know about on the network? Where are they? How |
|
| 98 |
+available are they?</li> |
|
| 99 |
+<li>Provide an interface for controlling Tor connections: "show me |
|
| 100 |
+the network from Africa by way of Asia". Think of the global satellite |
|
| 101 |
+map from the movie <i>Sneakers</i>.</li> |
|
| 102 |
+<li>Configure other running applications to use Tor (for example, |
|
| 103 |
+by modifying or working through the network stack, and/or by altering |
|
| 104 |
+application configurations).</li> |
|
| 105 |
+<li>Provide an elegant installer for both Tor and the application.</li> |
|
| 106 |
+<li>Provide meaningful defaults for a good Tor experience.</li> |
|
| 107 |
+<li>Implement Privoxy-like functionality -- that is, not just paying |
|
| 108 |
+attention to transport anonymity on the level of Tor, but also paying |
|
| 109 |
+attention to the anonymity of the http headers, cookies, etc.</li> |
|
| 110 |
+</ul> |
|
| 111 |
+ |
|
| 112 |
+<hr /> |
|
| 113 |
+<h3>Contest categories</h3> |
|
| 114 |
+ |
|
| 115 |
+<p>Three categories of interface will be awarded:</p> |
|
| 116 |
+<ul> |
|
| 117 |
+<li><b>Most featureful interface</b> will be awarded to the application that |
|
| 118 |
+provides usable, clear access to the most aspects of the Tor system, |
|
| 119 |
+covering many or most of the goals above.</li> |
|
| 120 |
+<li><b>Best usability</b> will be awarded to the application |
|
| 121 |
+that provides the most unobtrusive Tor experience while still covering |
|
| 122 |
+all criteria (working, perhaps, on the "no news is good news" theory).</li> |
|
| 123 |
+<li><b>Most flexible</b> will be awarded to the best system that runs smoothly |
|
| 124 |
+on all three of Windows, Linux, and Mac OS X; extra points will be awarded |
|
| 125 |
+for additional systems.</li> |
|
| 126 |
+</ul> |
|
| 127 |
+ |
|
| 128 |
+<p>We may decide to award other awards as the entries deserve.</p> |
|
| 129 |
+ |
|
| 130 |
+<hr /> |
|
| 131 |
+<h3>Judging criteria</h3> |
|
| 132 |
+ |
|
| 133 |
+<p>Awards will be granted on the basis of (in rough preference order):</p> |
|
| 134 |
+ |
|
| 135 |
+<ul> |
|
| 136 |
+<li>Usability (<a |
|
| 137 |
+href="http://wiki.noreply.org/noreply/TheOnionRouter/ContestFAQ#DefineUsable">what |
|
| 138 |
+does this mean?</a>)</li> |
|
| 139 |
+<li>Informativeness: can the user learn what they need to know?</li> |
|
| 140 |
+<li>Total user experience</li> |
|
| 141 |
+<li>Aesthetics</li> |
|
| 142 |
+<li>Responsiveness</li> |
|
| 143 |
+<li>Stability and robustness</li> |
|
| 144 |
+<li>Installation experience</li> |
|
| 145 |
+</ul> |
|
| 146 |
+ |
|
| 147 |
+<hr /> |
|
| 148 |
+<h3>Testing criteria</h3> |
|
| 149 |
+ |
|
| 150 |
+<p>To check for basic acceptability, the contest will be judged |
|
| 151 |
+with several major tests. For example, the system designer should expect:</p> |
|
| 152 |
+ |
|
| 153 |
+<ul> |
|
| 154 |
+<li>A minimal test: does it work?</li> |
|
| 155 |
+<li>Several parameters, both obscure and obvious, will be configured. Is |
|
| 156 |
+it possible and easy to do so?</li> |
|
| 157 |
+<li>A network will be connected once the system is running. Can the |
|
| 158 |
+user tell that the network is now live?</li> |
|
| 159 |
+<li>The network will be disconnected or interrupted. Can the user tell |
|
| 160 |
+that the network has an error?</li> |
|
| 161 |
+</ul> |
|
| 162 |
+ |
|
| 163 |
+<hr /> |
|
| 164 |
+<h3>Submissions</h3> |
|
| 165 |
+ |
|
| 166 |
+<p>Submissions should come as:</p> |
|
| 167 |
+ |
|
| 168 |
+<ul> |
|
| 169 |
+<li>Source code, with appropriate makefiles or documentation explaining |
|
| 170 |
+how to build it. Must be licensed under a free/open source license, as |
|
| 171 |
+defined by <a href="http://www.opensource.org/licenses/">OSI</a> or <a |
|
| 172 |
+href="http://www.debian.org/social_contract#guidelines">DFSG</a>. See <a |
|
| 173 |
+href="http://wiki.noreply.org/noreply/TheOnionRouter/ContestFAQ#DefineFree">this |
|
| 174 |
+FAQ entry</a> for clarification.</li> |
|
| 175 |
+<li>Compiled binaries or bytecodes for at least one platform of choice.</li> |
|
| 176 |
+<li>A design document providing an overview of what major functions |
|
| 177 |
+to look for and what functions were implemented.</li> |
|
| 178 |
+</ul> |
|
| 179 |
+ |
|
| 180 |
+<hr /> |
|
| 181 |
+<h3>Judges</h3> |
|
| 182 |
+ |
|
| 183 |
+<p>Judging will be led by a panel of five prominent specialists in usability |
|
| 184 |
+and security (to be announced).</p> |
|
| 185 |
+ |
|
| 186 |
+<hr /> |
|
| 187 |
+<h3>Prizes</h3> |
|
| 188 |
+ |
|
| 189 |
+<p>TBA, hopefully including a <a |
|
| 190 |
+href="http://slimdevices.com/">Squeezebox</a> for top winners.</p> |
|
| 191 |
+ |
|
| 192 |
+<hr /> |
|
| 193 |
+<h3>Timeline</h3> |
|
| 194 |
+ |
|
| 195 |
+<p>The contest will be announced on or around June 1, 2005. We expect |
|
| 196 |
+the contest deadline to be on or around January 15, 2006, with judging |
|
| 197 |
+complete by March 15, 2006.</p> |
|
| 198 |
+ |
|
| 199 |
+<hr /> |
|
| 200 |
+<h3>Technical notes</h3> |
|
| 201 |
+ |
|
| 202 |
+<p>Shortly before the contest begins, Tor will release a canonical code |
|
| 203 |
+version. This is the version that will be used for judging the contest; |
|
| 204 |
+please ensure that you use this version. Bugfixes to this version will |
|
| 205 |
+be announced to the contest web site.</p> |
|
| 206 |
+ |
|
| 207 |
+<p>Tor will also release test rigs in both Java and Python that demonstrate |
|
| 208 |
+Tor's controller protocol. It is acceptable to build entrants using this |
|
| 209 |
+code as a skeleton.</p> |
|
| 210 |
+ |
|
| 211 |
+<p>The test rig will show all of the basic functionality that is necessary |
|
| 212 |
+for the minimal features of the contest.</p> |
|
| 213 |
+ |
|
| 214 |
+<hr /> |
|
| 215 |
+<h3>Questions and clarifications</h3> |
|
| 216 |
+ |
|
| 217 |
+<p>We will have a public website and wiki up shortly for FAQ entries, |
|
| 218 |
+clarifications, etc.</p> |
|
| 219 |
+ |
|
| 220 |
+ </div><!-- #main --> |
|
| 221 |
+</div> |
|
| 222 |
+ <div class="bottom" id="bottom"> |
|
| 223 |
+ <i><a href="mailto:tor-webmaster@freehaven.net" class="smalllink">Webmaster</a></i> - |
|
| 224 |
+ $Id$ |
|
| 225 |
+ </div> |
|
| 226 |
+</body> |
|
| 227 |
+</html> |
|
| 228 |
+ |
|
| 0 | 229 |