remove obsolete gui-contest file
Roger Dingledine commited on 2005-10-17 23:48:47
Zeige 1 geänderte Dateien mit 0 Einfügungen und 386 Löschungen.
- gui/gui-contest.html 4f6067b72..000000000
| ... | ... |
@@ -1,387 +0,0 @@ |
| 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 Competition</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="volunteer.html">Volunteer</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 Competition</h2> |
|
| 43 |
-<hr /> |
|
| 44 |
-<p>DRAFT IN PROGRESS</p> |
|
| 45 |
-<hr /> |
|
| 46 |
-<a id="Overview"></a> |
|
| 47 |
-<h3><a class="anchor" href="#Overview">Overview</a></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 50,000 Tor users currently, routing their traffic |
|
| 53 |
-through about 250 volunteer Tor servers on five continents. However, Tor's |
|
| 54 |
-current user interface approach --- running as a service in the background |
|
| 55 |
---- does a poor job of communicating network status and security levels |
|
| 56 |
-to the user. |
|
| 57 |
-</p> |
|
| 58 |
- |
|
| 59 |
-<p> |
|
| 60 |
-The Tor project, affiliated with the |
|
| 61 |
-<a href="http://www.eff.org/">Electronic Frontier Foundation</a>, is |
|
| 62 |
-running a UI contest to develop a vision of how Tor can |
|
| 63 |
-work in a user's everyday anonymous browsing experience. Some of the |
|
| 64 |
-challenges include how to make alerts and error conditions visible on |
|
| 65 |
-screen; how to let the user configure Tor to use or avoid certain routes |
|
| 66 |
-or nodes; how to learn about the current state of a Tor connection, |
|
| 67 |
-including which servers it uses; and how to find out whether (and which) |
|
| 68 |
-applications are using Tor safely. |
|
| 69 |
-</p> |
|
| 70 |
- |
|
| 71 |
-<hr /> |
|
| 72 |
-<a id="Goals"></a> |
|
| 73 |
-<h3><a class="anchor" href="#Goals">Goals</a></h3> |
|
| 74 |
- |
|
| 75 |
-<p>Submitters will produce a work of <a |
|
| 76 |
-href="http://www.opensource.org/">Open Source Software</a> |
|
| 77 |
-that will |
|
| 78 |
-provide a user interface to the Tor system by way of the <a |
|
| 79 |
-href="/cvs/control/doc/howto.txt">Tor Controller |
|
| 80 |
-Protocol</a>.</p> |
|
| 81 |
- |
|
| 82 |
-<p>We are looking for a vision of how Tor can work in a user's everyday |
|
| 83 |
-anonymous browsing experience.</p> |
|
| 84 |
- |
|
| 85 |
-<p>Entries will:</p> |
|
| 86 |
-<ul> |
|
| 87 |
-<li>Allow the user to fully configure Tor rather than manually searching |
|
| 88 |
-for and opening text files.</li> |
|
| 89 |
-<li>Let users learn about the current state of their Tor connection |
|
| 90 |
-(including which servers they are connected to, and how many connections |
|
| 91 |
-they have), and find out whether any of their applications are using |
|
| 92 |
-it.</li> |
|
| 93 |
-<li>Make alerts and error conditions visible to the user.</li> |
|
| 94 |
-<li>Run on at least one of Windows, Linux, and OS X, on a |
|
| 95 |
-not-unusually-configured consumer-level machine.</li> |
|
| 96 |
-</ul> |
|
| 97 |
- |
|
| 98 |
-<p>In addition, they may:</p> |
|
| 99 |
-<ul> |
|
| 100 |
-<li>Provide detailed information about which |
|
| 101 |
-applications, ports, or packets are (or are not!) passing through Tor, |
|
| 102 |
-including accounting for both Tor- and non-Tor traffic.</li> |
|
| 103 |
-<li>Provide |
|
| 104 |
-additional statistics about the Tor connection.</li> |
|
| 105 |
-<li>Give users more control over how their Tor behaves at certain times |
|
| 106 |
-of day or in other contexts (like operating as a server).</li> |
|
| 107 |
-</ul> |
|
| 108 |
- |
|
| 109 |
-<p>Some examples of useful features include:</p> |
|
| 110 |
-<ul> |
|
| 111 |
-<li>How much bandwidth is Tor using? How does this compare |
|
| 112 |
-to the overall network traffic to/from the computer?</li> |
|
| 113 |
-<li>Is there network traffic from ports or applications that the user |
|
| 114 |
-intended to be anonymized?</li> |
|
| 115 |
-<li>What Tor servers does the user know about on the network? Where are |
|
| 116 |
-they? How available are they?</li> |
|
| 117 |
-<li>An interface for displaying or controlling Tor paths: |
|
| 118 |
-"show me the network from Africa by way of Asia". Think of the global |
|
| 119 |
-satellite map from the movie <i>Sneakers</i>.</li> |
|
| 120 |
-<li>Configure other running applications to use Tor (for example, |
|
| 121 |
-by modifying or working through the network stack, and/or by altering |
|
| 122 |
-application configurations).</li> |
|
| 123 |
-<li>Provide an elegant installer for Tor, your GUI submission, and |
|
| 124 |
-other supporting applications.</li> |
|
| 125 |
-<li>Make your GUI manage the Tor process and other supporting applications |
|
| 126 |
-<li>Provide meaningful defaults for a good Tor experience.</li> |
|
| 127 |
-<li>Provide application-level anonymity -- that is, not just paying |
|
| 128 |
-attention to transport anonymity on the level of Tor, but also paying |
|
| 129 |
-attention to the anonymity of the http headers, cookies, etc.</li> |
|
| 130 |
-<li>Let the user specify different Tor config option sets depending on |
|
| 131 |
-time of day (e.g. daytime vs. nighttime).</li> |
|
| 132 |
-<li>Provide useful controller functions for Tor servers too -- |
|
| 133 |
-for example, walk the user through recommended bandwidth configurations |
|
| 134 |
-and exit policies.</li> |
|
| 135 |
-<li>Have a "minimized view" of your GUI for common use, and then a more |
|
| 136 |
-detailed view or set of windows when the user wants more detail.</li> |
|
| 137 |
-<li>Provide a button or some automatically updating interface to let |
|
| 138 |
-the user learn whether Tor is working currently, perhaps by accessing an |
|
| 139 |
-external what's-my-IP site and seeing if it thinks you're a Tor server; |
|
| 140 |
-and give useful messages and recommendations if it doesn't seem to |
|
| 141 |
-be working.</li> |
|
| 142 |
-<li>Provide a way to automatically configure local firewalls (ipchains, |
|
| 143 |
-Windows firewalls, etc) to let Tor traffic out (and in, for Tor |
|
| 144 |
-servers). As a bonus, configure it to prevent non-Tor traffic from |
|
| 145 |
-leaving (and notify when it tries).</li> |
|
| 146 |
-</ul> |
|
| 147 |
- |
|
| 148 |
-<hr /> |
|
| 149 |
-<a id="Categories"></a> |
|
| 150 |
-<h3><a class="anchor" href="#Categories">Submission Categories</a></h3> |
|
| 151 |
- |
|
| 152 |
-<p> |
|
| 153 |
-The design contest will proceed in two phases: first sketches and then |
|
| 154 |
-working code. You are invited to submit to either phase, or both phases. |
|
| 155 |
-For each phase, our panel of judges will recognize the |
|
| 156 |
-best submissions. All qualifying entries will receive an EFF Tor T-shirt |
|
| 157 |
-(subject to availability). The best sketches and working implementations |
|
| 158 |
-will be published on the Tor website. |
|
| 159 |
-</p> |
|
| 160 |
- |
|
| 161 |
-<p><b>Sketches:</b> |
|
| 162 |
-the goal of this phase is to produce a mock-up of a functioning interface. |
|
| 163 |
-This should include design documents describing how the interface should |
|
| 164 |
-function. If you want, it should also include graphical elements that |
|
| 165 |
-can be used by programmers. |
|
| 166 |
-</p> |
|
| 167 |
- |
|
| 168 |
-<p> |
|
| 169 |
-A qualifying sketch will present an informal specification for a |
|
| 170 |
-design. That is, it will present with some degree of thoroughness all |
|
| 171 |
-of the major interfaces that we might expect to encounter, all of the |
|
| 172 |
-major functionality for the interface, and a reasonable story about |
|
| 173 |
-how it would be integrated into currently-existing tools (if, indeed, |
|
| 174 |
-it would be). One example, with more detail than we would require, is |
|
| 175 |
-<a href="http://ui.netbeans.org/docs/ui/junits/promo_f.html">the NetBeans |
|
| 176 |
-UI for JUnit</a>. Note that it walks through multiple interfaces, |
|
| 177 |
-highlighting the features and functions of the various buttons. |
|
| 178 |
-</p> |
|
| 179 |
- |
|
| 180 |
-<ul> |
|
| 181 |
-<li><b>Most featureful interface</b> will be awarded to the graphic design |
|
| 182 |
-that would provide usable, clear access to the most aspects of the Tor |
|
| 183 |
-system, covering many or most of the categories on the "useful features" |
|
| 184 |
-list.</li> |
|
| 185 |
-<li><b>Most usable experience</b> will be awarded to the graphic |
|
| 186 |
-design that would provide the most unobtrusive Tor experience while still |
|
| 187 |
-covering all criteria (working, perhaps, on the "no news is good news" |
|
| 188 |
-theory).</li> |
|
| 189 |
-<li><b>Clearest implementation guidance</b> will be awarded to the |
|
| 190 |
-graphic design that provides the cleanest package of graphic elements |
|
| 191 |
-and design documentation to aid would-be implementers.</li> |
|
| 192 |
-</ul> |
|
| 193 |
- |
|
| 194 |
-<p><b>Code:</b> the goal of this phase is to produce a working |
|
| 195 |
-implementation. You may use any of the sketches, graphics, or ideas from |
|
| 196 |
-the first phase (with appropriate credit to |
|
| 197 |
-their authors), or you can make your own. See the <a |
|
| 198 |
-href="http://wiki.noreply.org/noreply/TheOnionRouter/ContestSamples">Contest |
|
| 199 |
-Samples</a> wiki page for some other images you can reuse. |
|
| 200 |
-</p> |
|
| 201 |
- |
|
| 202 |
-<p> |
|
| 203 |
-An acceptable entry will be a package of free software that builds and |
|
| 204 |
-runs. It can be a stand-alone application, or it can act as an extension |
|
| 205 |
-or plugin to other broadly-available free software. The entry will |
|
| 206 |
-demonstrate the points in the Goals section: that is, it will be able |
|
| 207 |
-to control, display, and maintain awareness as discussed above. |
|
| 208 |
-</p> |
|
| 209 |
- |
|
| 210 |
-<ul> |
|
| 211 |
-<li><b>Most featureful interface</b> will be awarded to the application |
|
| 212 |
-that provides usable, clear access to the most aspects of the Tor system, |
|
| 213 |
-covering many or most of the categories on the "additional" list.</li> |
|
| 214 |
-<li><b>Most usable experience</b> will be awarded to the |
|
| 215 |
-application that provides the most unobtrusive Tor experience while |
|
| 216 |
-still covering all criteria (working, perhaps, on the "no news is good |
|
| 217 |
-news" theory).</li> |
|
| 218 |
-<li><b>Most flexible</b> will be awarded to the best system that runs |
|
| 219 |
-smoothly on all three of Windows, Linux, and OS X; extra points will be |
|
| 220 |
-awarded for additional systems.</li> |
|
| 221 |
-</ul> |
|
| 222 |
- |
|
| 223 |
-<p>We reserve the right to award other awards as the entries deserve.</p> |
|
| 224 |
- |
|
| 225 |
-<hr /> |
|
| 226 |
-<a id="Submit"></a> |
|
| 227 |
-<h3><a class="anchor" href="#Submit">How to Submit</a></h3> |
|
| 228 |
- |
|
| 229 |
-<p>Submissions for phase one (sketches) should come as:</p> |
|
| 230 |
-<ul> |
|
| 231 |
-<li>Images in an html page. The images must be able to be viewed on an |
|
| 232 |
-ordinary browser (e.g. Firefox). You can submit proprietary formats too, |
|
| 233 |
-but if you do then you need to also export them to something we can |
|
| 234 |
-all read.</li> |
|
| 235 |
-<li>A design document (txt, html, pdf, or ps) as described in the |
|
| 236 |
-<a href="#Categories">Contest Categories</a> section above.</li> |
|
| 237 |
-</ul> |
|
| 238 |
- |
|
| 239 |
-<p>Submissions for phase two (code) should come as:</p> |
|
| 240 |
- |
|
| 241 |
-<ul> |
|
| 242 |
-<li>Source code, with appropriate makefiles or documentation explaining |
|
| 243 |
-how to build it. Must be licensed under a free/open source license, as |
|
| 244 |
-defined by <a href="http://www.opensource.org/licenses/">OSI</a>. See <a |
|
| 245 |
-href="http://wiki.noreply.org/noreply/TheOnionRouter/ContestFAQ#DefineFree">this |
|
| 246 |
-FAQ entry</a> for clarification.</li> |
|
| 247 |
-<li>Compiled binaries or bytecodes for at least one platform of choice.</li> |
|
| 248 |
-<li>A design document (txt, html, pdf, or ps) providing an overview of |
|
| 249 |
-what major functions to look for and what functions were implemented.</li> |
|
| 250 |
-</ul> |
|
| 251 |
- |
|
| 252 |
-<p>To submit your entry, make a web page with |
|
| 253 |
-all your materials on it, then add a line to <a |
|
| 254 |
-href="http://wiki.noreply.org/noreply/TheOnionRouter/ContestEntries">The |
|
| 255 |
-GUI Contest Entries Wiki</a>. (If you don't have a web page of |
|
| 256 |
-your own to put your entry on, find a friend who does, or mail <a |
|
| 257 |
-href="mailto:tor-gui@freehaven.net">tor-gui@freehaven.net</a> and we'll |
|
| 258 |
-put it up on a temporary page.</p> |
|
| 259 |
- |
|
| 260 |
-<p>If you put it up on your own site, you can continue to update and |
|
| 261 |
-modify it. Remember that submitting early means you can get feedback |
|
| 262 |
-from Tor users and make it into a better submission!</p> |
|
| 263 |
- |
|
| 264 |
-<hr /> |
|
| 265 |
-<a id="Criteria"></a> |
|
| 266 |
-<h3><a class="anchor" href="#Criteria">Criteria</a></h3> |
|
| 267 |
- |
|
| 268 |
-<p>Awards will be granted on the basis of (in rough preference order):</p> |
|
| 269 |
- |
|
| 270 |
-<ul> |
|
| 271 |
-<li>Usability (<a |
|
| 272 |
-href="http://wiki.noreply.org/noreply/TheOnionRouter/ContestFAQ#DefineUsable">what |
|
| 273 |
-does this mean?</a>)</li> |
|
| 274 |
-<li>Informativeness: can the user learn what they need to know, both in terms |
|
| 275 |
-of using the network and also in terms of security decisions?</li> |
|
| 276 |
-<li>Total user experience</li> |
|
| 277 |
-<li>Aesthetics</li> |
|
| 278 |
-<li>Responsiveness</li> |
|
| 279 |
-<li>Stability and robustness</li> |
|
| 280 |
-<li>Internationalization (multiple language support)</li> |
|
| 281 |
-<li>Installation experience</li> |
|
| 282 |
-</ul> |
|
| 283 |
- |
|
| 284 |
-<hr /> |
|
| 285 |
-<a id="Judges"></a> |
|
| 286 |
-<h3><a class="anchor" href="#Judges">Judges</a></h3> |
|
| 287 |
- |
|
| 288 |
-<p>Judging will be led by a panel of N prominent specialists in usability |
|
| 289 |
-and security (to be announced).</p> |
|
| 290 |
- |
|
| 291 |
-<hr /> |
|
| 292 |
-<a id="Timeline"></a> |
|
| 293 |
-<h3><a class="anchor" href="#Timeline">Timeline</a></h3> |
|
| 294 |
- |
|
| 295 |
-<ul> |
|
| 296 |
-<li>Phase 1 deadline (sketches): October 31.</li> |
|
| 297 |
-<li>Phase 1 judging: November 31.</li> |
|
| 298 |
-<li>Phase 2 deadline (code): January 31, 2006.</li> |
|
| 299 |
-</ul> |
|
| 300 |
- |
|
| 301 |
-<p>Winners will be announced on the webpage and also at the SOUPS 2006 |
|
| 302 |
-conference. (Here's a suggestion on one approach to <a |
|
| 303 |
-href="http://wiki.noreply.org/noreply/TheOnionRouter/ContestFAQ#AcademicResearch">academic |
|
| 304 |
-usability research on Tor</a>.)</p> |
|
| 305 |
- |
|
| 306 |
-<hr /> |
|
| 307 |
-<a id="Clarifications"></a> |
|
| 308 |
-<h3><a class="anchor" href="#Clarifications">Questions and Clarifications</a></h3> |
|
| 309 |
- |
|
| 310 |
-<p>Check back <a |
|
| 311 |
-href="http://tor.eff.org/gui-contest.html#Clarifications">here</a> |
|
| 312 |
-periodically, and look at the <a |
|
| 313 |
-href="http://wiki.noreply.org/noreply/TheOnionRouter/ContestFAQ">Contest |
|
| 314 |
-FAQ wiki</a>, for FAQ entries, clarifications, etc.</p> |
|
| 315 |
- |
|
| 316 |
-<!-- |
|
| 317 |
-<hr /> |
|
| 318 |
-<h3>Testing criteria</h3> |
|
| 319 |
- |
|
| 320 |
-<p>To check for basic acceptability, the contest will be judged |
|
| 321 |
-with several major tests. For example, the system designer should expect:</p> |
|
| 322 |
- |
|
| 323 |
-<ul> |
|
| 324 |
-<li>A minimal test: does it work?</li> |
|
| 325 |
-<li>Several parameters, both obscure and obvious, will be configured. Is |
|
| 326 |
-it possible and easy to do so?</li> |
|
| 327 |
-<li>A network will be connected once the system is running. Can the |
|
| 328 |
-user tell that the network is now live?</li> |
|
| 329 |
-<li>The network will be disconnected or interrupted. Can the user tell |
|
| 330 |
-that the network has an error?</li> |
|
| 331 |
-</ul> |
|
| 332 |
---> |
|
| 333 |
- |
|
| 334 |
-<hr /> |
|
| 335 |
-<a id="Technical"></a> |
|
| 336 |
-<h3><a class="anchor" href="#Technical">Technical Notes</a></h3> |
|
| 337 |
- |
|
| 338 |
-<p>Shortly before phase two begins, the Tor developers will release |
|
| 339 |
-a canonical version of Tor. This is the version that will be used for |
|
| 340 |
-judging the contest; please ensure that you use this version. Bugfixes |
|
| 341 |
-to this version of Tor will be announced to the contest web site.</p> |
|
| 342 |
- |
|
| 343 |
-<p>The Tor developers will also release test rigs (libraries) in both Java |
|
| 344 |
-and Python that demonstrate Tor's controller protocol. Code submissions |
|
| 345 |
-may be able to save a lot of time by using this code as a skeleton. You |
|
| 346 |
-can check out the <a href="http://tor.eff.org/cvs/control/">development |
|
| 347 |
-versions of these libraries</a> now. |
|
| 348 |
-</p> |
|
| 349 |
- |
|
| 350 |
-<hr /> |
|
| 351 |
-<a id="Legal"></a> |
|
| 352 |
-<h3><a class="anchor" href="#Legal">Legal Notes</a></h3> |
|
| 353 |
- |
|
| 354 |
-<p>By submitting your entry to be considered in the Tor GUI contest, you |
|
| 355 |
-hereby:</p> |
|
| 356 |
- |
|
| 357 |
-<ul> |
|
| 358 |
-<li>(A) represent and warrant that (1) the entry was created by you and |
|
| 359 |
-that you own all rights to the entry or have the authorized rights to |
|
| 360 |
-submit such entry and grant the licenses below; and (2) that the |
|
| 361 |
-entry does not infringe on any third party copyright or other |
|
| 362 |
-intellectual property rights; AND</li> |
|
| 363 |
-<li>(B) EITHER (1) grant us a worldwide, royalty-free, non-exclusive, |
|
| 364 |
-perpetual license to reproduce, edit, perform, display, publish, make |
|
| 365 |
-derivative works, and otherwise use the entry as we see fit, |
|
| 366 |
-including without limitation, incorporating (in whole or in part) |
|
| 367 |
-into the Tor software, and to sublicense such rights; OR, (2) |
|
| 368 |
-provide the entry pursuant to a license that complies with the |
|
| 369 |
-<a href="http://www.opensource.org/docs/definition.php">Open |
|
| 370 |
-Source Definition</a>, such as the 3-clause BSD, MIT, or |
|
| 371 |
-GPL licenses, or (where applicable) provide the entry licensed under |
|
| 372 |
-the <a href="http://creativecommons.org/licenses/by/2.5/">Creative |
|
| 373 |
-Commons Attribution</a> license. If you provide the entry pursuant to |
|
| 374 |
-such a license, you must include the applicable information in your |
|
| 375 |
-submission.</li> |
|
| 376 |
-</ul> |
|
| 377 |
- |
|
| 378 |
- </div><!-- #main --> |
|
| 379 |
-</div> |
|
| 380 |
- <div class="bottom" id="bottom"> |
|
| 381 |
- <i><a href="mailto:tor-webmaster@freehaven.net" class="smalllink">Webmaster</a></i> - |
|
| 382 |
- $Id$ |
|
| 383 |
- </div> |
|
| 384 |
-</body> |
|
| 385 |
-</html> |
|
| 386 |
- |
|
| 387 | 0 |