tor-webwml.git

make it clearer to avoid open-ended research topics; and make it clearer that incremental results are very important
Parent 9a27e83af
Roger Dingledine

Roger Dingledine commited on 2010-04-02 00:40:26
Zeige 1 geänderte Dateien mit 28 Einfügungen und 12 Löschungen.

en/gsoc.wml
Zeige Datei @ d6bfce1c5
... ... 
@@ -38,17 +38,6 @@ need to already be somewhat familiar with how free software development on the
38 38 
 Internet works.
39 39 
 </p>
40 40
41 
-<p>
42 
-In addition to getting some more development work
43 
-done on Tor and related applications, Google and Tor are most interested
44 
-in getting students involved in Tor development in a way that keeps them
45 
-involved after the summer too. That means we will give priority to students
46 
-who have demonstrated continued interest and responsiveness. We will require
47 
-students to write public status report updates for our community, either by
48 
-blogging or sending mail to our mailing list. We want to ensure that the
49 
-community and the student can both benefit from each other.
50 
-</p>
51 
-
52 41 
 <p>
53 42 
 Working on Tor is rewarding because:
54 43 
 </p>
... ... 
@@ -78,6 +67,17 @@ as they come to you: <a href="<page documentation>#UpToSpeed">Getting
78 67 
 up to speed</a>.
79 68 
 </p>
80 69
70 
+<p>
71 
+In addition to getting some more development work
72 
+done on Tor and related applications, Google and Tor are most interested
73 
+in getting students involved in Tor development in a way that keeps them
74 
+involved after the summer too. That means we will give priority to students
75 
+who have demonstrated continued interest and responsiveness. We will require
76 
+students to write public status report updates for our community, either by
77 
+blogging or sending mail to our mailing list. We want to ensure that the
78 
+community and the student can both benefit from each other.
79 
+</p>
80 
+
81 81 
 <p>
82 82 
 When it comes time for us to choose projects, our impression of how well
83 83 
 you'll fit into our community &mdash; and how good you are at taking
... ... 
@@ -94,6 +94,22 @@ This year, we have two ideas lists: one for projects to
94 94 
 and one for <a href="https://www.eff.org/gsoc2010">EFF's projects</a>.
95 95 
 </p>
96 96
97 
+<p>
98 
+The best kind of ideas are A) ones that we know we need done real soon
99 
+now (you can get a sense of urgency from the priority on the wishlist,
100 
+and from talking to the potential mentors), and B) ones where it's
101 
+clear what needs to be done, at least for the first few steps. Lots of
102 
+students try to bite off open-ended research topics; but if you're going
103 
+to be spending the first half of your summer figuring out what exactly
104 
+you should code, and there's a chance that the conclusion will be "oh,
105 
+that isn't actually a good idea to build", then your proposal will make
106 
+us very nervous. Try to figure out how much you can actually fit in a
107 
+summer, break the work down into manageable pieces, and most importantly,
108 
+figure out how to make sure your incremental milestones are actually
109 
+useful &mdash; if you don't finish everything in your plan, we want to
110 
+know that you'll still have produced something useful.
111 
+</p>
112 
+
97 113 
 <a id="Template"></a>
98 114 
 <h2><a class="anchor" href="#Template">Application Template</a></h2>
99 115
... ... 
@@ -104,7 +120,7 @@ provide enough information for us to evaluate you and your proposal.
104 120
105 121 
 <ol>
106 122
107 
-<li>What project would you like to work on? Use our ideas lists as starting
123 
+<li>What project would you like to work on? Use our ideas lists as a starting
108 124 
 point or make up your own idea. Your proposal should include high-level
109 125 
 descriptions of what you're going to do, with more details about the
110 126 
 parts you expect to be tricky. Your proposal should also try to break
111 127