address comments from paul. (alas, rms loses again.)
Roger Dingledine

Roger Dingledine commited on 2005-07-21 01:37:46
Zeige 1 geänderte Dateien mit 11 Einfügungen und 11 Löschungen.

... ...
@@ -73,7 +73,7 @@ applications are using Tor safely.
73 73
 <h3><a class="anchor" href="#Goals">Goals</a></h3>
74 74
 
75 75
 <p>Contestants will produce a work of <a
76
-href="http://www.fsf.org/licensing/essays/free-sw.html">Free Software</a>
76
+href="http://www.opensource.org/">Open Source Software</a>
77 77
 that will
78 78
 provide a user interface to the Tor system by way of the <a
79 79
 href="/cvs/control/doc/howto.txt">Tor Controller
... ...
@@ -151,15 +151,16 @@ leaving (and notify when it tries).</li>
151 151
 <h3><a class="anchor" href="#Categories">Contest Categories</a></h3>
152 152
 
153 153
 <p>
154
-The design contest will proceed in two stages: first sketches and then
155
-working code. For each stage, our panel of judges will recognize the
154
+The design contest will proceed in two phases: first sketches and then
155
+working code. You are invited to submit to either phase, or both phases.
156
+For each phase, our panel of judges will recognize the
156 157
 best submissions. All qualifying entries will receive an EFF Tor T-shirt
157 158
 (subject to availability). The best sketches and working implementations
158 159
 will be published on the Tor website.
159 160
 </p>
160 161
 
161 162
 <p><b>Sketches:</b>
162
-the goal of this stage is to produce a mock-up of a functioning interface.
163
+the goal of this phase is to produce a mock-up of a functioning interface.
163 164
 This should include design documents describing how the interface should
164 165
 function. If you want, it should also include graphical elements that
165 166
 can be used by programmers.
... ...
@@ -191,9 +192,9 @@ graphic design that provides the cleanest package of graphic elements
191 192
 and design documentation to aid would-be implementers.</li>
192 193
 </ul>
193 194
 
194
-<p><b>Code:</b> the goal of this stage is to produce a working
195
+<p><b>Code:</b> the goal of this phase is to produce a working
195 196
 implementation. You may use any of the sketches, graphics, or ideas from
196
-the first stage (with appropriate credit to
197
+the first phase (with appropriate credit to
197 198
 their authors), or you can make your own. See the <a
198 199
 href="http://wiki.noreply.org/noreply/TheOnionRouter/ContestSamples">Contest
199 200
 Samples</a> wiki page for some other images you can reuse.
... ...
@@ -236,8 +237,7 @@ awarded for additional systems.</li>
236 237
 <ul>
237 238
 <li>Source code, with appropriate makefiles or documentation explaining
238 239
 how to build it. Must be licensed under a free/open source license, as
239
-defined by <a href="http://www.opensource.org/licenses/">OSI</a> or <a
240
-href="http://www.debian.org/social_contract#guidelines">DFSG</a>.  See <a
240
+defined by <a href="http://www.opensource.org/licenses/">OSI</a>. See <a
241 241
 href="http://wiki.noreply.org/noreply/TheOnionRouter/ContestFAQ#DefineFree">this
242 242
 FAQ entry</a> for clarification.</li>
243 243
 <li>Compiled binaries or bytecodes for at least one platform of choice.</li>
... ...
@@ -289,9 +289,9 @@ and security (to be announced).</p>
289 289
 <h3><a class="anchor" href="#Timeline">Timeline</a></h3>
290 290
 
291 291
 <ul>
292
-<li>Stage 1 deadline (sketches): October 31.</li>
293
-<li>Stage 1 judging: November 31.</li>
294
-<li>Stage 2 deadline (code): January 31, 2006.</li>
292
+<li>Phase 1 deadline (sketches): October 31.</li>
293
+<li>Phase 1 judging: November 31.</li>
294
+<li>Phase 2 deadline (code): January 31, 2006.</li>
295 295
 </ul>
296 296
 
297 297
 <p>Winners will be announced on the webpage and also at the SOUPS 2006
298 298