tor-webwml.git

1) ## translation metadata
2) # Revision: $Revision$
3) 

4) #include "head.wmi" TITLE="GUI Competition"

5) 
6) <div class="main-column">
7) 
8) <!-- LEFT HAND MENU FOR GUI CONTEST PAGES -->
9) <div class="guileft">
10) <div class="guimenu">
11)   
12)   <div class="curveleft">
13)   <div class="curveright">
14)   &nbsp;
15)   </div>
16)   </div>
17) 
18) <div class="guimenuinner">
19) <h1>Tor GUI Competition</h1>
20) 
21) 
22) <a href="index.html">Overview &amp; Goals</a>
23) <a href="categories.html">What to Submit</a>
24) <a class="on" href="submit.html">How to Submit</a>
25) <a href="criteria.html">Judging &amp; Timeline</a>
26) <a href="technotes.html">Technical Notes</a>
27) <a href="legal.html">Licensing</a>
28) <h1>&nbsp;</h1>
29) <a class="wiki" href="http://wiki.noreply.org/noreply/TheOnionRouter/ContestFAQ">Wiki/FAQ</a>
30) </div>
31) 
32)   <div class="curvebottomleft">
33)   <div class="curvebottomright">
34)   &nbsp;
35)   </div>
36)   </div>
37) 
38) </div>
39) </div>
40) 
41) <h2>How to Submit an Entry</h2>
42) 
43) <p>Submissions for phase one (sketches) should come as:</p>
44) <ul>
45) <li>Images in an html page. The images must be able to be viewed on an
46) ordinary browser, e.g. Firefox. (You can submit proprietary formats too,
47) but if you do then you need to also export them to something we can
48) all read.) Must be licensed under a <a href="legal.html">free license</a>.</li>
49) <li>A design document (txt, html, pdf, or ps) as described in the
50) <a href="categories.html">Submission Categories</a> section.</li>
51) </ul>
52) 
53) <p>Submissions for phase two (code) should come as:</p>
54) 
55) <ul>
56) <li>Source code, with appropriate makefiles or documentation explaining
57) how to build it. Must be licensed under a free/open source license, as
58) defined by <a href="http://www.opensource.org/licenses/">OSI</a>. See <a
59) href="http://wiki.noreply.org/noreply/TheOnionRouter/ContestFAQ#DefineFree">this
60) FAQ entry</a> for clarification.</li>
61) <li>Compiled binaries or bytecodes for at least one platform of choice.</li>
62) <li>A design document (txt, html, pdf, or ps) providing an overview of

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