Browse code

Updating GSoC page for 2012 and rewriting some sections

Changing the dates and linking to the 2012 GSoC page. Some of the sections were
kinda rough or gave out of date advice so this includes quite a bit of
rewording too.

Damian Johnson authored on 25/02/2012 20:58:43
Showing 1 changed files
... ...
@@ -9,28 +9,29 @@
9 9
     <a href="<page about/gsoc>">Google Summer of Code</a>
10 10
   </div>
11 11
   <div id="maincol"> 
12
-    <h2>Tor: Google Summer of Code 2011</h2>
12
+    <h2>Tor: Google Summer of Code 2012</h2>
13 13
     <hr>
14 14
     
15 15
     <p>
16
-    In the last four years, The Tor Project in collaboration with <a
16
+    In the last five years, The Tor Project in collaboration with <a
17 17
     href="https://www.eff.org/">The Electronic Frontier Foundation</a>
18 18
     successfully took part in
19 19
     <a href="http://code.google.com/soc/2007/eff/about.html">Google Summer of Code
20 20
     2007</a>, <a href="http://code.google.com/soc/2008/eff/about.html">2008</a>,
21 21
     <a
22 22
     href="http://socghop.appspot.com/gsoc/org/home/google/gsoc2009/eff">2009</a>,
23
-    and <a href="<blog>tor-google-summer-code-2010">2010</a>.
24
-    In total we had 21 students as full-time developers for the summers of 2007 to
25
-    2010. Now we are applying to <a
26
-    href="https://socghop.appspot.com/gsoc/program/home/google/gsoc2011">Google
27
-    Summer of Code 2011</a>.
23
+    <a href="<blog>tor-google-summer-code-2010">2010</a>, and <a
24
+    href="https://socghop.appspot.com/gsoc/program/home/google/gsoc2011">2011</a>.
25
+    In total we had 27 students as full-time developers for the summers of 2007 to
26
+    2011. Now we are applying to <a
27
+    href="https://socghop.appspot.com/gsoc/program/home/google/gsoc2012">Google
28
+    Summer of Code 2012</a>.
28 29
     </p>
29 30
     
30 31
     <p>
31 32
     The <a
32
-    href="https://socghop.appspot.com/document/show/gsoc_program/google/gsoc2011/timeline">timeline</a>
33
-    for GSoC 2011 is available.
33
+    href="https://google-melange.appspot.com/gsoc/events/google/gsoc2012">timeline</a>
34
+    for GSoC 2012 is available.
34 35
     </p>
35 36
     
36 37
     <p>
... ...
@@ -64,11 +65,11 @@
64 65
     <h2><a class="anchor" href="#GettingInvolved">How To Get Involved</a></h2>
65 66
     
66 67
     <p>
67
-    The best way to get involved is to come listen on IRC (both "#tor" and
68
-    "#tor-dev"), read our docs and other webpages, try out the various tools
69
-    that are related to the projects that interest you, and ask questions
70
-    as they come to you: <a href="<page docs/documentation>#UpToSpeed">Getting
71
-    up to speed</a>.
68
+    The best way to get involved is to come <a href="<page
69
+    about/contact>#irc">listen on IRC</a> (both "#tor" and "#tor-dev"), read
70
+    our docs and other webpages, try out the various tools that are related to
71
+    the projects that interest you, and ask questions as they come to you: <a
72
+    href="<page docs/documentation>#UpToSpeed">Getting up to speed</a>.
72 73
     </p>
73 74
     
74 75
     <p>
... ...
@@ -84,7 +85,7 @@
84 85
     
85 86
     <p>
86 87
     When it comes time for us to choose projects, our impression of how well
87
-    you'll fit into our community &mdash; and how good you are at taking
88
+    you'll fit into our community &mdash; and how well you are at taking
88 89
     the initiative to do things &mdash; will be at least as important as
89 90
     the actual project you'll be working on.
90 91
     </p>
... ...
@@ -99,19 +100,20 @@
99 100
     </p>
100 101
     
101 102
     <p>
102
-    The best kind of ideas are A) ones that we know we need done real soon
103
-    now (you can get a sense of urgency from the priority on the wishlist,
104
-    and from talking to the potential mentors), and B) ones where it's
105
-    clear what needs to be done, at least for the first few steps. Lots of
106
-    students try to bite off open-ended research topics; but if you're going
107
-    to be spending the first half of your summer figuring out what exactly
108
-    you should code, and there's a chance that the conclusion will be "oh,
109
-    that isn't actually a good idea to build", then your proposal will make
110
-    us very nervous. Try to figure out how much you can actually fit in a
111
-    summer, break the work down into manageable pieces, and most importantly,
112
-    figure out how to make sure your incremental milestones are actually
113
-    useful &mdash; if you don't finish everything in your plan, we want to
114
-    know that you'll still have produced something useful.
103
+    The best kind of ideas are well defined and easily broken into subtasks. 
104
+    A lot of students try to bite off open-ended development and research
105
+    topics. But if you're going to spend the first half of your summer figuring
106
+    out what exactly you should code, there's a chance that the conclusion will
107
+    be "oh, that isn't actually feasible to build after all" and your proposal
108
+    will make us very nervous.
109
+    </p>
110
+    
111
+    <p>
112
+    Try to figure out how much you can actually fit in a summer, break the work
113
+    down into manageable pieces, and most importantly, figure out how to make
114
+    sure your incremental milestones are actually useful &mdash; if you don't
115
+    finish everything in your plan, we want to know that you'll still have
116
+    produced something useful.
115 117
     </p>
116 118
     
117 119
     <a id="Template"></a>
... ...
@@ -171,37 +173,45 @@
171 173
     helps with the deduplication process and will not impact if we accept your
172 174
     application or not.</li>
173 175
     
174
-    <li>Is there anything else we should know that will make us like your
176
+    <li>Is there anything else that we should know that will make us like your
175 177
     project more?</li>
176 178
     
177 179
     </ol>
178 180
     
179 181
     <p>
180
-    We will pick out mentors for this year &mdash; most of the
181
-    people on the <a href="<page about/corepeople>">core Tor development team</a>
182
-    plus a few people from <a href="http://www.eff.org/about/staff">EFF's staff</a>
183
-    &mdash; so we should be able to accommodate a wide variety of projects,
184
-    ranging from work on Tor itself to work on supporting or peripheral
185
-    projects. We can figure out which mentor is appropriate while we're
186
-    discussing the project you have in mind. We plan to assign a primary
187
-    mentor to each student, along with one or two assistant mentors to help
188
-    answer questions and help you integrate with the broader Tor community.
182
+    We mostly pick mentors from the <a href="<page about/corepeople>">core Tor
183
+    development team</a> and <a href="http://www.eff.org/about/staff">EFF's
184
+    staff</a> so we should be able to accommodate a wide variety of projects.
185
+    These can range from work on Tor itself to work on supporting or peripheral
186
+    projects.
187
+    </p>
188
+    
189
+    <p>
190
+    All selected projects are assigned both a primary and assistant mentor to
191
+    answer your questions and help you integrate with the broader Tor
192
+    community. Though your mentors are a primary point of contact please use
193
+    our public spaces (the <a href="<page about/contact>#irc">#tor-dev irc
194
+    channel</a> and <a href="<page docs/documentation>#MailingLists">tor-dev@
195
+    email list</a>) to discuss your project. We want you to become a part of
196
+    the community by the end of the summer, not a stranger that's only known by
197
+    your mentor.
189 198
     </p>
190 199
     
191 200
     <p>
192 201
     If you're interested, you can either contact the <a href="<page
193
-    about/contact>">tor-assistants list</a> with a brief summary of your proposal
194
-    and we'll give you feedback, or just jump right in and post your ideas
195
-    and goals to the <a href="<page docs/documentation>#MailingLists">tor-talk
196
-    mailing list</a>. Make sure to be responsive during the application
197
-    selection period; if we like your application but you never answer our
198
-    mails asking for more information, that's not a good sign.
202
+    about/contact>">tor-assistants list</a> (a private list) with a brief
203
+    summary of your proposal and we'll give you feedback, or just jump right in
204
+    and post your ideas and goals to the <a href="<page
205
+    docs/documentation>#MailingLists">tor-dev mailing list</a> (which is open).
206
+    Make sure to be responsive during the application selection period; if we
207
+    like your application but you never answer our mails asking for more
208
+    information, that's not a good sign.
199 209
     </p>
200 210
     
201 211
     <p>
202
-    The more applications we get, the more likely Google is to give us good
203
-    students. So if you haven't filled up your summer plans yet, please
204
-    consider spending some time working with us to make Tor better!
212
+    We're always happy to have new contributors so if you haven't filled up
213
+    your summer plans yet, please consider spending some time working with us
214
+    to make Tor better!
205 215
     </p>
206 216
     
207 217
     <a id="Example"></a>