Browse code

Change hidden service to onion service. (See #24285)

kat authored on16/11/2017 19:08:34
Showing1 changed files
... ...
@@ -204,7 +204,7 @@
204 204
     </p>
205 205
     
206 206
     <ul>
207
-      <li><h4><a href="https://ahmia.fi/gsoc/">Ahmia.fi - Search Engine for Hidden Services</a> by Juha Nurmi</h4></li>
207
+      <li><h4><a href="https://ahmia.fi/gsoc/">Ahmia.fi - Search Engine for Onion Services</a> by Juha Nurmi</h4></li>
208 208
       <li><h4><a href="http://ilv.github.io/gettor_proposal.html">Revamp GetTor</a> by Israel Leiva</h4></li>
209 209
       <li><h4><a href="https://sites.google.com/site/sreenathadev/gsoc-2014-weather-rewrite">Weather Rewrite</a> by Sreenatha Bhatlapenumarthi</h4></li>
210 210
       <li><h4><a href="http://kostas.mkj.lt/gsoc2014/gsoc2014.html">BridgeDB Distributor</a> by Kostas Jakeliunas</h4></li>
Browse code

Update GSoC page to say we're accepted

Time to pass along the good news!

Damian Johnson authored on27/02/2017 21:00:28
Showing1 changed files
... ...
@@ -17,14 +17,9 @@
17 17
     <p>
18 18
     The Tor Project, in collaboration with <a href="https://www.eff.org/">The
19 19
     Electronic Frontier Foundation</a>, have taken part in Google Summer of Code
20
-    for 2007 through 2016, mentoring the total of 64 students. We have applied
21
-    to <a href="https://summerofcode.withgoogle.com/">GSoC 2017</a>, and we
22
-    should know at the end of February whether we are in this year.
23
-    <!--
24
-    Now google has
20
+    for 2007 through 2016, mentoring the total of 64 students.  Now google has
25 21
     announced that we'll be taking part again for <a
26 22
     href="https://summerofcode.withgoogle.com/">Google Summer of Code 2017</a>!
27
-    -->
28 23
     </p>
29 24
     
30 25
     <p>
Browse code

Update GSoC page for 2017

Few changes...

* Update year to be for 2017.

* Change back to 'applying' rather than 'accepted'.

* Dropping the paragraph that discusses tor-assistants@. List is no longer
available, and the rest of the paragraph doesn't really add much that isn't
obvious.

* Dropping proposal examples that are now 404s. Mostly this is the melange
links.

Damian Johnson authored on05/02/2017 22:42:56
Showing1 changed files
... ...
@@ -2,14 +2,14 @@
2 2
 # Revision: $Revision$
3 3
 # Translation-Priority: 4-optional
4 4
 
5
-#include "head.wmi" TITLE="Tor: Google Summer of Code 2016" CHARSET="UTF-8"
5
+#include "head.wmi" TITLE="Tor: Google Summer of Code 2017" CHARSET="UTF-8"
6 6
 <div id="content" class="clearfix">
7 7
   <div id="breadcrumbs">
8 8
     <a href="<page index>">Home &raquo; </a>
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 2016</h2>
12
+    <h2>Tor: Google Summer of Code 2017</h2>
13 13
     <hr>
14 14
 
15 15
     <br /><br />
... ...
@@ -17,9 +17,14 @@
17 17
     <p>
18 18
     The Tor Project, in collaboration with <a href="https://www.eff.org/">The
19 19
     Electronic Frontier Foundation</a>, have taken part in Google Summer of Code
20
-    for 2007 through 2014, mentoring the total of 57 students. Now google has
20
+    for 2007 through 2016, mentoring the total of 64 students. We have applied
21
+    to <a href="https://summerofcode.withgoogle.com/">GSoC 2017</a>, and we
22
+    should know at the end of February whether we are in this year.
23
+    <!--
24
+    Now google has
21 25
     announced that we'll be taking part again for <a
22
-    href="https://summerofcode.withgoogle.com/">Google Summer of Code 2016</a>!
26
+    href="https://summerofcode.withgoogle.com/">Google Summer of Code 2017</a>!
27
+    -->
23 28
     </p>
24 29
     
25 30
     <p>
... ...
@@ -188,17 +193,6 @@
188 193
     your mentor.
189 194
     </p>
190 195
     
191
-    <p>
192
-    If you're interested, you can either contact the <a href="<page
193
-    about/contact>">tor-assistants list</a> (a private list) with a brief
194
-    summary of your proposal and we'll give you feedback, or just jump right in
195
-    and post your ideas and goals to the <a href="<page
196
-    docs/documentation>#MailingLists">tor-dev mailing list</a> (which is open).
197
-    Make sure to be responsive during the application selection period; if we
198
-    like your application but you never answer our mails asking for more
199
-    information, that's not a good sign.
200
-    </p>
201
-    
202 196
     <p>
203 197
     We're always happy to have new contributors so if you haven't filled up
204 198
     your summer plans yet, please consider spending some time working with us
... ...
@@ -216,14 +210,11 @@
216 210
     
217 211
     <ul>
218 212
       <li><h4><a href="https://ahmia.fi/gsoc/">Ahmia.fi - Search Engine for Hidden Services</a> by Juha Nurmi</h4></li>
219
-      <li><h4><a href="http://www.google-melange.com/gsoc/proposal/public/google/gsoc2014/amoghbl1/5629499534213120">Orbot &amp; Orfox</a> by Amogh Pradeep</h4></li>
220 213
       <li><h4><a href="http://ilv.github.io/gettor_proposal.html">Revamp GetTor</a> by Israel Leiva</h4></li>
221 214
       <li><h4><a href="https://sites.google.com/site/sreenathadev/gsoc-2014-weather-rewrite">Weather Rewrite</a> by Sreenatha Bhatlapenumarthi</h4></li>
222 215
       <li><h4><a href="http://kostas.mkj.lt/gsoc2014/gsoc2014.html">BridgeDB Distributor</a> by Kostas Jakeliunas</h4></li>
223 216
       <li><h4><a href="http://kostas.mkj.lt/gsoc2013/gsoc2013.html">Searchable Tor descriptor archive</a> by Kostas Jakeliunas</h4></li>
224
-      <li><h4><a href="https://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/weltraumpfleger/1">Create an Internet Censorship Virtual Machine Based Simulator</a> by Johannes Fürmann</h4></li>
225 217
       <li><h4><a href="../about/gsocProposal/gsoc12-proposal-stemImprovements.html">Stem Improvements and Arm port</a> by Ravi Padmala</h4></li>
226
-      <li><h4><a href="http://feroze.in/gsoc12.html">Implementing Hidden Service Configuration and Bandwidth Scheduling Plugins</a> by Feroze Naina</h4></li>
227 218
       <li><h4><a href="../about/gsocProposal/gsoc10-proposal-soat.txt">SOAT Expansion</a> by John Schanck</h4></li>
228 219
       <li><h4><a href="http://inspirated.com/uploads/tor-gsoc-11.pdf">GTK+ Frontend and Client Mode Improvements for arm</a> by Kamran Khan</h4></li>
229 220
       <li><h4><a href="http://www.gsathya.in/gsoc11.html">Orbot + ORLib</a> by Sathya Gunasekaran</h4></li>
Browse code

Update GSoC page to say we're accepted

Well past due this page had the good news. I'm dropping the SoP note and
wrapping its count into GSoC since there's no need to confuse students with
that detail.

Damian Johnson authored on03/03/2016 17:40:24
Showing1 changed files
... ...
@@ -17,17 +17,9 @@
17 17
     <p>
18 18
     The Tor Project, in collaboration with <a href="https://www.eff.org/">The
19 19
     Electronic Frontier Foundation</a>, have taken part in Google Summer of Code
20
-    for 2007 through 2014, mentoring the total of 53 students.
21
-    In 2015, Tor <a href="https://lists.torproject.org/pipermail/tor-dev/2015-March/008358.html">was not accepted</a> into GSoC (along with many other established organizations). Instead we ran our own program that summer:
22
-<a href="https://trac.torproject.org/projects/tor/wiki/org/TorSoP">the Summer of Privacy</a>!
23
-    <!--
24
-    Now google has
20
+    for 2007 through 2014, mentoring the total of 57 students. Now google has
25 21
     announced that we'll be taking part again for <a
26
-    href="https://www.google-melange.com/gsoc/homepage/google/gsoc2015">Google
27
-    Summer of Code 2016</a>!
28
-    -->
29
-    We have applied to GSoC 2016, and we should know at the end of February
30
-    whether we are in this year.
22
+    href="https://summerofcode.withgoogle.com/">Google Summer of Code 2016</a>!
31 23
     </p>
32 24
     
33 25
     <p>
Browse code

make it clearer we're not accepted to gsoc 2016 yet

Roger Dingledine authored on20/02/2016 04:02:10
Showing1 changed files
... ...
@@ -26,6 +26,8 @@
26 26
     href="https://www.google-melange.com/gsoc/homepage/google/gsoc2015">Google
27 27
     Summer of Code 2016</a>!
28 28
     -->
29
+    We have applied to GSoC 2016, and we should know at the end of February
30
+    whether we are in this year.
29 31
     </p>
30 32
     
31 33
     <p>
Browse code

update gsoc page for 2016

Roger Dingledine authored on19/02/2016 19:08:38
Showing1 changed files
... ...
@@ -2,29 +2,29 @@
2 2
 # Revision: $Revision$
3 3
 # Translation-Priority: 4-optional
4 4
 
5
-#include "head.wmi" TITLE="Tor: Google Summer of Code 2015" CHARSET="UTF-8"
5
+#include "head.wmi" TITLE="Tor: Google Summer of Code 2016" CHARSET="UTF-8"
6 6
 <div id="content" class="clearfix">
7 7
   <div id="breadcrumbs">
8 8
     <a href="<page index>">Home &raquo; </a>
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 2015</h2>
12
+    <h2>Tor: Google Summer of Code 2016</h2>
13 13
     <hr>
14 14
 
15
-    <h3>IMPORTANT NOTE: Tor <a href="https://lists.torproject.org/pipermail/tor-dev/2015-March/008358.html">was not accepted</a> into GSoC 2015. Hopefully we'll be back next year, but in the meantime we're running our own program: <a href="https://trac.torproject.org/projects/tor/wiki/org/TorSoP">the Summer of Privacy</a>!</h3>
16
-
17 15
     <br /><br />
18 16
 
19 17
     <p>
20 18
     The Tor Project, in collaboration with <a href="https://www.eff.org/">The
21 19
     Electronic Frontier Foundation</a>, have taken part in Google Summer of Code
22 20
     for 2007 through 2014, mentoring the total of 53 students.
21
+    In 2015, Tor <a href="https://lists.torproject.org/pipermail/tor-dev/2015-March/008358.html">was not accepted</a> into GSoC (along with many other established organizations). Instead we ran our own program that summer:
22
+<a href="https://trac.torproject.org/projects/tor/wiki/org/TorSoP">the Summer of Privacy</a>!
23 23
     <!--
24 24
     Now google has
25 25
     announced that we'll be taking part again for <a
26 26
     href="https://www.google-melange.com/gsoc/homepage/google/gsoc2015">Google
27
-    Summer of Code 2015</a>!
27
+    Summer of Code 2016</a>!
28 28
     -->
29 29
     </p>
30 30
     
Browse code

Cite SoP on the GSoC page

Yay, we can replace our rejection note with something even better!

Damian Johnson authored on04/04/2015 20:59:48
Showing1 changed files
... ...
@@ -12,7 +12,7 @@
12 12
     <h2>Tor: Google Summer of Code 2015</h2>
13 13
     <hr>
14 14
 
15
-    <h3>IMPORTANT NOTE: Tor <a href="https://lists.torproject.org/pipermail/tor-dev/2015-March/008358.html">was not accepted</a> into GSoC 2015, hopefully we'll be back next year!</h3>
15
+    <h3>IMPORTANT NOTE: Tor <a href="https://lists.torproject.org/pipermail/tor-dev/2015-March/008358.html">was not accepted</a> into GSoC 2015. Hopefully we'll be back next year, but in the meantime we're running our own program: <a href="https://trac.torproject.org/projects/tor/wiki/org/TorSoP">the Summer of Privacy</a>!</h3>
16 16
 
17 17
     <br /><br />
18 18
 
Browse code

Note that we're not taking part in GSoC 2015

This page at least should mention it to avoid potential confusion.

Damian Johnson authored on11/03/2015 17:31:03
Showing1 changed files
... ...
@@ -11,7 +11,11 @@
11 11
   <div id="maincol"> 
12 12
     <h2>Tor: Google Summer of Code 2015</h2>
13 13
     <hr>
14
-    
14
+
15
+    <h3>IMPORTANT NOTE: Tor <a href="https://lists.torproject.org/pipermail/tor-dev/2015-March/008358.html">was not accepted</a> into GSoC 2015, hopefully we'll be back next year!</h3>
16
+
17
+    <br /><br />
18
+
15 19
     <p>
16 20
     The Tor Project, in collaboration with <a href="https://www.eff.org/">The
17 21
     Electronic Frontier Foundation</a>, have taken part in Google Summer of Code
Browse code

Updating GSoC page for 2015

Minor update just like last year's.

Damian Johnson authored on03/02/2015 17:31:24
Showing1 changed files
... ...
@@ -2,23 +2,26 @@
2 2
 # Revision: $Revision$
3 3
 # Translation-Priority: 4-optional
4 4
 
5
-#include "head.wmi" TITLE="Tor: Google Summer of Code 2014" CHARSET="UTF-8"
5
+#include "head.wmi" TITLE="Tor: Google Summer of Code 2015" CHARSET="UTF-8"
6 6
 <div id="content" class="clearfix">
7 7
   <div id="breadcrumbs">
8 8
     <a href="<page index>">Home &raquo; </a>
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 2014</h2>
12
+    <h2>Tor: Google Summer of Code 2015</h2>
13 13
     <hr>
14 14
     
15 15
     <p>
16 16
     The Tor Project, in collaboration with <a href="https://www.eff.org/">The
17 17
     Electronic Frontier Foundation</a>, have taken part in Google Summer of Code
18
-    for 2007 through 2013, mentoring the total of 40 students. Now google has
18
+    for 2007 through 2014, mentoring the total of 53 students.
19
+    <!--
20
+    Now google has
19 21
     announced that we'll be taking part again for <a
20
-    href="https://www.google-melange.com/gsoc/homepage/google/gsoc2014">Google
21
-    Summer of Code 2014</a>!
22
+    href="https://www.google-melange.com/gsoc/homepage/google/gsoc2015">Google
23
+    Summer of Code 2015</a>!
24
+    -->
22 25
     </p>
23 26
     
24 27
     <p>
Browse code

Fixed broken link of revamp gettor for gsoc

ileiva authored on05/01/2015 20:55:46 • Damian Johnson committed on06/01/2015 17:45:16
Showing1 changed files
... ...
@@ -216,7 +216,7 @@
216 216
     <ul>
217 217
       <li><h4><a href="https://ahmia.fi/gsoc/">Ahmia.fi - Search Engine for Hidden Services</a> by Juha Nurmi</h4></li>
218 218
       <li><h4><a href="http://www.google-melange.com/gsoc/proposal/public/google/gsoc2014/amoghbl1/5629499534213120">Orbot &amp; Orfox</a> by Amogh Pradeep</h4></li>
219
-      <li><h4><a href="http://ileiva.github.io/gettor_proposal.html">Revamp GetTor</a> by Israel Leiva</h4></li>
219
+      <li><h4><a href="http://ilv.github.io/gettor_proposal.html">Revamp GetTor</a> by Israel Leiva</h4></li>
220 220
       <li><h4><a href="https://sites.google.com/site/sreenathadev/gsoc-2014-weather-rewrite">Weather Rewrite</a> by Sreenatha Bhatlapenumarthi</h4></li>
221 221
       <li><h4><a href="http://kostas.mkj.lt/gsoc2014/gsoc2014.html">BridgeDB Distributor</a> by Kostas Jakeliunas</h4></li>
222 222
       <li><h4><a href="http://kostas.mkj.lt/gsoc2013/gsoc2013.html">Searchable Tor descriptor archive</a> by Kostas Jakeliunas</h4></li>
Browse code

Adding Sreenatha's GSoC project

Damian Johnson authored on24/04/2014 18:06:12
Showing1 changed files
... ...
@@ -217,6 +217,7 @@
217 217
       <li><h4><a href="https://ahmia.fi/gsoc/">Ahmia.fi - Search Engine for Hidden Services</a> by Juha Nurmi</h4></li>
218 218
       <li><h4><a href="http://www.google-melange.com/gsoc/proposal/public/google/gsoc2014/amoghbl1/5629499534213120">Orbot &amp; Orfox</a> by Amogh Pradeep</h4></li>
219 219
       <li><h4><a href="http://ileiva.github.io/gettor_proposal.html">Revamp GetTor</a> by Israel Leiva</h4></li>
220
+      <li><h4><a href="https://sites.google.com/site/sreenathadev/gsoc-2014-weather-rewrite">Weather Rewrite</a> by Sreenatha Bhatlapenumarthi</h4></li>
220 221
       <li><h4><a href="http://kostas.mkj.lt/gsoc2014/gsoc2014.html">BridgeDB Distributor</a> by Kostas Jakeliunas</h4></li>
221 222
       <li><h4><a href="http://kostas.mkj.lt/gsoc2013/gsoc2013.html">Searchable Tor descriptor archive</a> by Kostas Jakeliunas</h4></li>
222 223
       <li><h4><a href="https://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/weltraumpfleger/1">Create an Internet Censorship Virtual Machine Based Simulator</a> by Johannes Fürmann</h4></li>
Browse code

Adding Kostas' GSoC proposal

Damian Johnson authored on22/04/2014 18:11:08
Showing1 changed files
... ...
@@ -217,6 +217,7 @@
217 217
       <li><h4><a href="https://ahmia.fi/gsoc/">Ahmia.fi - Search Engine for Hidden Services</a> by Juha Nurmi</h4></li>
218 218
       <li><h4><a href="http://www.google-melange.com/gsoc/proposal/public/google/gsoc2014/amoghbl1/5629499534213120">Orbot &amp; Orfox</a> by Amogh Pradeep</h4></li>
219 219
       <li><h4><a href="http://ileiva.github.io/gettor_proposal.html">Revamp GetTor</a> by Israel Leiva</h4></li>
220
+      <li><h4><a href="http://kostas.mkj.lt/gsoc2014/gsoc2014.html">BridgeDB Distributor</a> by Kostas Jakeliunas</h4></li>
220 221
       <li><h4><a href="http://kostas.mkj.lt/gsoc2013/gsoc2013.html">Searchable Tor descriptor archive</a> by Kostas Jakeliunas</h4></li>
221 222
       <li><h4><a href="https://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/weltraumpfleger/1">Create an Internet Censorship Virtual Machine Based Simulator</a> by Johannes Fürmann</h4></li>
222 223
       <li><h4><a href="../about/gsocProposal/gsoc12-proposal-stemImprovements.html">Stem Improvements and Arm port</a> by Ravi Padmala</h4></li>
Browse code

Adding Juha's GSoC Proposal

... and another. :)

Damian Johnson authored on22/04/2014 17:31:37
Showing1 changed files
... ...
@@ -214,6 +214,7 @@
214 214
     </p>
215 215
     
216 216
     <ul>
217
+      <li><h4><a href="https://ahmia.fi/gsoc/">Ahmia.fi - Search Engine for Hidden Services</a> by Juha Nurmi</h4></li>
217 218
       <li><h4><a href="http://www.google-melange.com/gsoc/proposal/public/google/gsoc2014/amoghbl1/5629499534213120">Orbot &amp; Orfox</a> by Amogh Pradeep</h4></li>
218 219
       <li><h4><a href="http://ileiva.github.io/gettor_proposal.html">Revamp GetTor</a> by Israel Leiva</h4></li>
219 220
       <li><h4><a href="http://kostas.mkj.lt/gsoc2013/gsoc2013.html">Searchable Tor descriptor archive</a> by Kostas Jakeliunas</h4></li>
Browse code

Adding Israel's GSoC proposal

Got another ok to add one.

Damian Johnson authored on22/04/2014 17:28:55
Showing1 changed files
... ...
@@ -215,6 +215,7 @@
215 215
     
216 216
     <ul>
217 217
       <li><h4><a href="http://www.google-melange.com/gsoc/proposal/public/google/gsoc2014/amoghbl1/5629499534213120">Orbot &amp; Orfox</a> by Amogh Pradeep</h4></li>
218
+      <li><h4><a href="http://ileiva.github.io/gettor_proposal.html">Revamp GetTor</a> by Israel Leiva</h4></li>
218 219
       <li><h4><a href="http://kostas.mkj.lt/gsoc2013/gsoc2013.html">Searchable Tor descriptor archive</a> by Kostas Jakeliunas</h4></li>
219 220
       <li><h4><a href="https://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/weltraumpfleger/1">Create an Internet Censorship Virtual Machine Based Simulator</a> by Johannes Fürmann</h4></li>
220 221
       <li><h4><a href="../about/gsocProposal/gsoc12-proposal-stemImprovements.html">Stem Improvements and Arm port</a> by Ravi Padmala</h4></li>
Browse code

Adding Amogh's GSoC proposal

Got the ok from him to add it.

Damian Johnson authored on22/04/2014 17:19:01
Showing1 changed files
... ...
@@ -214,6 +214,7 @@
214 214
     </p>
215 215
     
216 216
     <ul>
217
+      <li><h4><a href="http://www.google-melange.com/gsoc/proposal/public/google/gsoc2014/amoghbl1/5629499534213120">Orbot &amp; Orfox</a> by Amogh Pradeep</h4></li>
217 218
       <li><h4><a href="http://kostas.mkj.lt/gsoc2013/gsoc2013.html">Searchable Tor descriptor archive</a> by Kostas Jakeliunas</h4></li>
218 219
       <li><h4><a href="https://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/weltraumpfleger/1">Create an Internet Censorship Virtual Machine Based Simulator</a> by Johannes Fürmann</h4></li>
219 220
       <li><h4><a href="../about/gsocProposal/gsoc12-proposal-stemImprovements.html">Stem Improvements and Arm port</a> by Ravi Padmala</h4></li>
Browse code

Include note that we're taking part in GSoC 2014

Uncommmenting the bit that says we've been accepted. Yay! \o/

Damian Johnson authored on26/02/2014 17:19:35
Showing1 changed files
... ...
@@ -15,13 +15,10 @@
15 15
     <p>
16 16
     The Tor Project, in collaboration with <a href="https://www.eff.org/">The
17 17
     Electronic Frontier Foundation</a>, have taken part in Google Summer of Code
18
-    for 2007 through 2013, mentoring the total of 40 students.
19
-    <!--
20
-    Now google has
18
+    for 2007 through 2013, mentoring the total of 40 students. Now google has
21 19
     announced that we'll be taking part again for <a
22
-    href="https://www.google-melange.com/gsoc/homepage/google/gsoc2013">Google
23
-    Summer of Code 2013</a>!
24
-    -->
20
+    href="https://www.google-melange.com/gsoc/homepage/google/gsoc2014">Google
21
+    Summer of Code 2014</a>!
25 22
     </p>
26 23
     
27 24
     <p>
Browse code

Updating GSoC page for 2014

Actually, there's really little to change. Took a read through but besides the
header it looks good.

Damian Johnson authored on10/02/2014 03:51:35
Showing1 changed files
... ...
@@ -2,23 +2,26 @@
2 2
 # Revision: $Revision$
3 3
 # Translation-Priority: 4-optional
4 4
 
5
-#include "head.wmi" TITLE="Tor: Google Summer of Code 2013" CHARSET="UTF-8"
5
+#include "head.wmi" TITLE="Tor: Google Summer of Code 2014" CHARSET="UTF-8"
6 6
 <div id="content" class="clearfix">
7 7
   <div id="breadcrumbs">
8 8
     <a href="<page index>">Home &raquo; </a>
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 2013</h2>
12
+    <h2>Tor: Google Summer of Code 2014</h2>
13 13
     <hr>
14 14
     
15 15
     <p>
16 16
     The Tor Project, in collaboration with <a href="https://www.eff.org/">The
17 17
     Electronic Frontier Foundation</a>, have taken part in Google Summer of Code
18
-    for 2007 through 2012, mentoring the total of 33 students. Now google has
18
+    for 2007 through 2013, mentoring the total of 40 students.
19
+    <!--
20
+    Now google has
19 21
     announced that we'll be taking part again for <a
20 22
     href="https://www.google-melange.com/gsoc/homepage/google/gsoc2013">Google
21 23
     Summer of Code 2013</a>!
24
+    -->
22 25
     </p>
23 26
     
24 27
     <p>
Browse code

Switching to https links for www.atagar.com

Dreamhost just added SSL support via SNI (Server Name Indication), no longer
requiring a unique IP. As such, the only fee is the cert itself so finally
adding SSL support for my site. I've added a http->https redirect, but still
good to update these links...

Damian Johnson authored on29/09/2013 01:18:11
Showing1 changed files
... ...
@@ -223,7 +223,7 @@
223 223
       <li><h4><a href="http://www.gsathya.in/gsoc11.html">Orbot + ORLib</a> by Sathya Gunasekaran</h4></li>
224 224
       <li><h4><a href="http://blanu.net/TorSummerOfCodeProposal.pdf">Blocking-resistant Transport Evaluation Framework</a> by Brandon Wiley</h4></li>
225 225
       <li><h4><a href="../about/gsocProposal/gsoc11-proposal-metadataToolkit.pdf">Metadata Anonymisation Toolkit</a> by Julien Voisin</h4></li>
226
-      <li><h4><a href="http://www.atagar.com/misc/gsocBlog09/">Website Pootle Translation</a> by Damian Johnson</h4></li>
226
+      <li><h4><a href="https://www.atagar.com/misc/gsocBlog09/">Website Pootle Translation</a> by Damian Johnson</h4></li>
227 227
     </ul>
228 228
     
229 229
   </div>
Browse code

Adding Kostas' GSoC application as an example

Kostas copied his application to his site and sent me his ok.

Damian Johnson authored on16/06/2013 23:31:19
Showing1 changed files
... ...
@@ -214,6 +214,7 @@
214 214
     </p>
215 215
     
216 216
     <ul>
217
+      <li><h4><a href="http://kostas.mkj.lt/gsoc2013/gsoc2013.html">Searchable Tor descriptor archive</a> by Kostas Jakeliunas</h4></li>
217 218
       <li><h4><a href="https://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/weltraumpfleger/1">Create an Internet Censorship Virtual Machine Based Simulator</a> by Johannes Fürmann</h4></li>
218 219
       <li><h4><a href="../about/gsocProposal/gsoc12-proposal-stemImprovements.html">Stem Improvements and Arm port</a> by Ravi Padmala</h4></li>
219 220
       <li><h4><a href="http://feroze.in/gsoc12.html">Implementing Hidden Service Configuration and Bandwidth Scheduling Plugins</a> by Feroze Naina</h4></li>
Browse code

Adding Johannes' GSoC application as an example

Johannes made his application public and sent me his ok.

Damian Johnson authored on16/06/2013 23:27:17
Showing1 changed files
... ...
@@ -214,6 +214,7 @@
214 214
     </p>
215 215
     
216 216
     <ul>
217
+      <li><h4><a href="https://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/weltraumpfleger/1">Create an Internet Censorship Virtual Machine Based Simulator</a> by Johannes Fürmann</h4></li>
217 218
       <li><h4><a href="../about/gsocProposal/gsoc12-proposal-stemImprovements.html">Stem Improvements and Arm port</a> by Ravi Padmala</h4></li>
218 219
       <li><h4><a href="http://feroze.in/gsoc12.html">Implementing Hidden Service Configuration and Bandwidth Scheduling Plugins</a> by Feroze Naina</h4></li>
219 220
       <li><h4><a href="../about/gsocProposal/gsoc10-proposal-soat.txt">SOAT Expansion</a> by John Schanck</h4></li>
Browse code

Disclaimer for sharing which GSoC projects have applications

Several weeks back Moritz told GSoC applicants which project ideas people had
already applied for. Personally I'm fine with this - making this public can
spread out our strong applicants. This is good for both them and us. However,
we should be upfront about this so adding a notice to our GSoC page.

Damian Johnson authored on12/05/2013 21:00:34
Showing1 changed files
... ...
@@ -119,7 +119,11 @@
119 119
     parts you expect to be tricky. Your proposal should also try to break
120 120
     down the project into tasks of a fairly fine granularity, and convince
121 121
     us you have a plan for finishing it. A timeline for what you will be doing
122
-    throughout the summer is highly recommended.</li>
122
+    throughout the summer is highly recommended.<br /><br />
123
+
124
+    <i>Note that we might share which project ideas have strong applications in
125
+    order to spread applicants out (it's bad for everyone for several strong
126
+    applicants to be for the exact same project).</i><br /><br /></li>
123 127
     
124 128
     <li>Point us to a code sample: something good and clean to demonstrate
125 129
     that you know what you're doing, ideally from an existing project.</li>
Browse code

Update year in GSoC page title

Karsten Loesing authored on09/04/2013 12:23:45
Showing1 changed files
... ...
@@ -2,7 +2,7 @@
2 2
 # Revision: $Revision$
3 3
 # Translation-Priority: 4-optional
4 4
 
5
-#include "head.wmi" TITLE="Tor: Google Summer of Code 2012" CHARSET="UTF-8"
5
+#include "head.wmi" TITLE="Tor: Google Summer of Code 2013" CHARSET="UTF-8"
6 6
 <div id="content" class="clearfix">
7 7
   <div id="breadcrumbs">
8 8
     <a href="<page index>">Home &raquo; </a>
Browse code

Updating GSoC landing page to say that we've been accepted

Damian Johnson authored on09/04/2013 05:46:16
Showing1 changed files
... ...
@@ -12,27 +12,13 @@
12 12
     <h2>Tor: Google Summer of Code 2013</h2>
13 13
     <hr>
14 14
     
15
-    <p>
16
-    <b>If you're interested in participating in Google Summer of Code then
17
-    please keep in mind that Google has not yet announced the participating
18
-    organisations, and Tor might not be selected. See the <a
19
-    href="https://www.google-melange.com/document/show/gsoc_program/google/gsoc2013/help_page#2._What_is_the_program_timeline">timeline</a>
20
-    for more information.</b>
21
-    </p>
22
-
23 15
     <p>
24 16
     The Tor Project, in collaboration with <a href="https://www.eff.org/">The
25 17
     Electronic Frontier Foundation</a>, have taken part in Google Summer of Code
26
-    for 2007 through 2012, mentoring the total of 33 students. Google has
27
-    announced that the program's taking place again this year, see <a
28
-    href="https://www.google-melange.com/gsoc/homepage/google/gsoc2013">their
29
-    site</a> for a timeline!
30
-    
31
-    <!--
32
-    We have been accepted as a mentoring organization for <a
33
-    href="https://socghop.appspot.com/gsoc/program/home/google/gsoc2012">Google
34
-    Summer of Code 2012</a>!
35
-    -->
18
+    for 2007 through 2012, mentoring the total of 33 students. Now google has
19
+    announced that we'll be taking part again for <a
20
+    href="https://www.google-melange.com/gsoc/homepage/google/gsoc2013">Google
21
+    Summer of Code 2013</a>!
36 22
     </p>
37 23
     
38 24
     <p>
Browse code

Dropping Tails Server from sample proposals

The pdf Julien provided is now a 404 so dropping it from the page.

Damian Johnson authored on24/03/2013 22:01:51
Showing1 changed files
... ...
@@ -226,7 +226,6 @@
226 226
     <ul>
227 227
       <li><h4><a href="../about/gsocProposal/gsoc12-proposal-stemImprovements.html">Stem Improvements and Arm port</a> by Ravi Padmala</h4></li>
228 228
       <li><h4><a href="http://feroze.in/gsoc12.html">Implementing Hidden Service Configuration and Bandwidth Scheduling Plugins</a> by Feroze Naina</h4></li>
229
-      <li><h4><a href="http://dustri.org/pub/tails_server.pdf">Tails Server</a> by Julien Voisin</h4></li>
230 229
       <li><h4><a href="../about/gsocProposal/gsoc10-proposal-soat.txt">SOAT Expansion</a> by John Schanck</h4></li>
231 230
       <li><h4><a href="http://inspirated.com/uploads/tor-gsoc-11.pdf">GTK+ Frontend and Client Mode Improvements for arm</a> by Kamran Khan</h4></li>
232 231
       <li><h4><a href="http://www.gsathya.in/gsoc11.html">Orbot + ORLib</a> by Sathya Gunasekaran</h4></li>
Browse code

Dropping the EFF from questions on the GSoC page

The EFF hasn't indicated that they're interested in partnering with us for GSoC
this year. My feeling from prior years is that they're not particularly
interested in taking part - if they do decide to join in later it's trivial to
revert this.

Damian Johnson authored on24/03/2013 20:35:01
Showing1 changed files
... ...
@@ -138,7 +138,7 @@
138 138
     <li>Point us to a code sample: something good and clean to demonstrate
139 139
     that you know what you're doing, ideally from an existing project.</li>
140 140
     
141
-    <li>Why do you want to work with The Tor Project / EFF in
141
+    <li>Why do you want to work with The Tor Project in
142 142
     particular?</li>
143 143
     
144 144
     <li>Tell us about your experiences in free software development
... ...
@@ -181,10 +181,9 @@
181 181
     
182 182
     <p>
183 183
     We mostly pick mentors from the <a href="<page about/corepeople>">core Tor
184
-    development team</a> and <a href="http://www.eff.org/about/staff">EFF's
185
-    staff</a> so we should be able to accommodate a wide variety of projects.
186
-    These can range from work on Tor itself to work on supporting or peripheral
187
-    projects.
184
+    development team</a> so we should be able to accommodate a wide variety of
185
+    projects. These can range from work on Tor itself to work on supporting or
186
+    peripheral projects.
188 187
     </p>
189 188
     
190 189
     <p>
Browse code

Clarifying that Google hasn't yet announced orgs for GSoC

Noting that Google hasn't yet selected orgs (hell, the org application phase
hasn't even *started* yet). I'm not interested in repeatedly saying this to
prospective students so hopefully these notices will be sufficient.

Damian Johnson authored on10/03/2013 20:28:25
Showing1 changed files
... ...
@@ -12,6 +12,14 @@
12 12
     <h2>Tor: Google Summer of Code 2013</h2>
13 13
     <hr>
14 14
     
15
+    <p>
16
+    <b>If you're interested in participating in Google Summer of Code then
17
+    please keep in mind that Google has not yet announced the participating
18
+    organisations, and Tor might not be selected. See the <a
19
+    href="https://www.google-melange.com/document/show/gsoc_program/google/gsoc2013/help_page#2._What_is_the_program_timeline">timeline</a>
20
+    for more information.</b>
21
+    </p>
22
+
15 23
     <p>
16 24
     The Tor Project, in collaboration with <a href="https://www.eff.org/">The
17 25
     Electronic Frontier Foundation</a>, have taken part in Google Summer of Code
Browse code

Updating our GSoC site for 2013

I'm not sure if I got everything, but updating the bits I could find for the
2013 program. I dropped the links to prior GSoC programs since most were 404s,
and the ones that weren't are long obsolete.

Damian Johnson authored on09/03/2013 08:25:53
Showing1 changed files
... ...
@@ -9,29 +9,22 @@
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 2012</h2>
12
+    <h2>Tor: Google Summer of Code 2013</h2>
13 13
     <hr>
14 14
     
15 15
     <p>
16
-    In the last five years, The Tor Project in collaboration with <a
17
-    href="https://www.eff.org/">The Electronic Frontier Foundation</a>
18
-    successfully took part in
19
-    <a href="http://code.google.com/soc/2007/eff/about.html">Google Summer of Code
20
-    2007</a>, <a href="http://code.google.com/soc/2008/eff/about.html">2008</a>,
21
-    <a
22
-    href="http://socghop.appspot.com/gsoc/org/home/google/gsoc2009/eff">2009</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. We have been accepted as a mentoring organization for <a
16
+    The Tor Project, in collaboration with <a href="https://www.eff.org/">The
17
+    Electronic Frontier Foundation</a>, have taken part in Google Summer of Code
18
+    for 2007 through 2012, mentoring the total of 33 students. Google has
19
+    announced that the program's taking place again this year, see <a
20
+    href="https://www.google-melange.com/gsoc/homepage/google/gsoc2013">their
21
+    site</a> for a timeline!
22
+    
23
+    <!--
24
+    We have been accepted as a mentoring organization for <a
27 25
     href="https://socghop.appspot.com/gsoc/program/home/google/gsoc2012">Google
28 26
     Summer of Code 2012</a>!
29
-    </p>
30
-    
31
-    <p>
32
-    The <a
33
-    href="https://google-melange.appspot.com/gsoc/events/google/gsoc2012">timeline</a>
34
-    for GSoC 2012 is available.
27
+    -->
35 28
     </p>
36 29
     
37 30
     <p>
... ...
@@ -96,9 +89,7 @@
96 89
     <p>
97 90
     To start with, please see Tor's <b><a href="<page
98 91
     getinvolved/volunteer>#Projects">projects page</a></b> and its following
99
-    ideas. There are also <b><a
100
-    href="https://trac.torproject.org/projects/tor/wiki/doc/HTTPSEverywhere/GSOC-2012">projects
101
-    available</a></b> for the EFF's HTTPS Everywhere plugin.
92
+    ideas.
102 93
     </p>
103 94
     
104 95
     <p>
Browse code

Adding Julien's GSoC application as an example

Damian Johnson authored on01/05/2012 17:49:46
Showing1 changed files
... ...
@@ -228,6 +228,7 @@
228 228
     <ul>
229 229
       <li><h4><a href="../about/gsocProposal/gsoc12-proposal-stemImprovements.html">Stem Improvements and Arm port</a> by Ravi Padmala</h4></li>
230 230
       <li><h4><a href="http://feroze.in/gsoc12.html">Implementing Hidden Service Configuration and Bandwidth Scheduling Plugins</a> by Feroze Naina</h4></li>
231
+      <li><h4><a href="http://dustri.org/pub/tails_server.pdf">Tails Server</a> by Julien Voisin</h4></li>
231 232
       <li><h4><a href="../about/gsocProposal/gsoc10-proposal-soat.txt">SOAT Expansion</a> by John Schanck</h4></li>
232 233
       <li><h4><a href="http://inspirated.com/uploads/tor-gsoc-11.pdf">GTK+ Frontend and Client Mode Improvements for arm</a> by Kamran Khan</h4></li>
233 234
       <li><h4><a href="http://www.gsathya.in/gsoc11.html">Orbot + ORLib</a> by Sathya Gunasekaran</h4></li>
Browse code

Adding feroze's gsoc app as an example

Damian Johnson authored on30/04/2012 07:55:01
Showing1 changed files
... ...
@@ -227,6 +227,7 @@
227 227
     
228 228
     <ul>
229 229
       <li><h4><a href="../about/gsocProposal/gsoc12-proposal-stemImprovements.html">Stem Improvements and Arm port</a> by Ravi Padmala</h4></li>
230
+      <li><h4><a href="http://feroze.in/gsoc12.html">Implementing Hidden Service Configuration and Bandwidth Scheduling Plugins</a> by Feroze Naina</h4></li>
230 231
       <li><h4><a href="../about/gsocProposal/gsoc10-proposal-soat.txt">SOAT Expansion</a> by John Schanck</h4></li>
231 232
       <li><h4><a href="http://inspirated.com/uploads/tor-gsoc-11.pdf">GTK+ Frontend and Client Mode Improvements for arm</a> by Kamran Khan</h4></li>
232 233
       <li><h4><a href="http://www.gsathya.in/gsoc11.html">Orbot + ORLib</a> by Sathya Gunasekaran</h4></li>
Browse code

Adding Ravi's stem proposal as an example

Got permission to use his proposal as an example on the GSoC page.

Damian Johnson authored on26/04/2012 18:18:31
Showing1 changed files
... ...
@@ -226,6 +226,7 @@
226 226
     </p>
227 227
     
228 228
     <ul>
229
+      <li><h4><a href="../about/gsocProposal/gsoc12-proposal-stemImprovements.html">Stem Improvements and Arm port</a> by Ravi Padmala</h4></li>
229 230
       <li><h4><a href="../about/gsocProposal/gsoc10-proposal-soat.txt">SOAT Expansion</a> by John Schanck</h4></li>
230 231
       <li><h4><a href="http://inspirated.com/uploads/tor-gsoc-11.pdf">GTK+ Frontend and Client Mode Improvements for arm</a> by Kamran Khan</h4></li>
231 232
       <li><h4><a href="http://www.gsathya.in/gsoc11.html">Orbot + ORLib</a> by Sathya Gunasekaran</h4></li>
Browse code

clean up some obvious dead links that are frequently hit by users.

Andrew Lewman authored on21/03/2012 04:33:49
Showing1 changed files
... ...
@@ -226,8 +226,6 @@
226 226
     </p>
227 227
     
228 228
     <ul>
229
-      <li><h4><a href="http://tor.spanning-tree.org/proposal.html">DNSEL Rewrite</a> by Harry Bock</h4></li>
230
-      <li><h4><a href="http://kjb.homeunix.com/wp-content/uploads/2010/05/KevinBerry-GSoC2010-TorProposal.html">Extending Tor Network Metrics</a> by Kevin Berry</h4></li>
231 229
       <li><h4><a href="../about/gsocProposal/gsoc10-proposal-soat.txt">SOAT Expansion</a> by John Schanck</h4></li>
232 230
       <li><h4><a href="http://inspirated.com/uploads/tor-gsoc-11.pdf">GTK+ Frontend and Client Mode Improvements for arm</a> by Kamran Khan</h4></li>
233 231
       <li><h4><a href="http://www.gsathya.in/gsoc11.html">Orbot + ORLib</a> by Sathya Gunasekaran</h4></li>
Browse code

And we know we're accepted, yay

Sebastian Hahn authored on17/03/2012 17:34:06
Showing1 changed files
... ...
@@ -23,9 +23,9 @@
23 23
     <a href="<blog>tor-google-summer-code-2010">2010</a>, and <a
24 24
     href="https://socghop.appspot.com/gsoc/program/home/google/gsoc2011">2011</a>.
25 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
26
+    2011. We have been accepted as a mentoring organization for <a
27 27
     href="https://socghop.appspot.com/gsoc/program/home/google/gsoc2012">Google
28
-    Summer of Code 2012</a>.
28
+    Summer of Code 2012</a>!
29 29
     </p>
30 30
     
31 31
     <p>
Browse code

I hear this year is gsoc 2012

Sebastian Hahn authored on17/03/2012 17:32:56
Showing1 changed files
... ...
@@ -2,7 +2,7 @@
2 2
 # Revision: $Revision$
3 3
 # Translation-Priority: 4-optional
4 4
 
5
-#include "head.wmi" TITLE="Tor: Google Summer of Code 2011" CHARSET="UTF-8"
5
+#include "head.wmi" TITLE="Tor: Google Summer of Code 2012" CHARSET="UTF-8"
6 6
 <div id="content" class="clearfix">
7 7
   <div id="breadcrumbs">
8 8
     <a href="<page index>">Home &raquo; </a>
Browse code

Linking GSoC landing page to the EFF's HTTPS Everywhere ideas

Peter didn't reply about if he wants to incorporate the EFF project ideas with
our page so I'm assuming that he just wants the listing on trac. Linking it
from the landing page so students can find it.

Damian Johnson authored on03/03/2012 20:47:35
Showing1 changed files
... ...
@@ -94,9 +94,11 @@
94 94
     <h2><a class="anchor" href="#Ideas">Ideas List</a></h2>
95 95
     
96 96
     <p>
97
-    To start with, please see our <b><a href="<page
97
+    To start with, please see Tor's <b><a href="<page
98 98
     getinvolved/volunteer>#Projects">projects page</a></b> and its following
99
-    ideas.
99
+    ideas. There are also <b><a
100
+    href="https://trac.torproject.org/projects/tor/wiki/doc/HTTPSEverywhere/GSOC-2012">projects
101
+    available</a></b> for the EFF's HTTPS Everywhere plugin.
100 102
     </p>
101 103
     
102 104
     <p>
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 on25/02/2012 20:58:43
Showing1 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>
Browse code

Storing copies of past gsoc proposals

Suggested by Roger in case the originals vanish. These are pdf printoffs
with the exception of hbock's DNSEL rewrite app, which didn't translate well.
This was a simple page, so just copying it.

I'm also replacing a simple txt copy of jvoisin's metadata toolkit proposal
with a much better looking pdf of his melange app (restricted to just the
content via firebug).

Damian Johnson authored on14/05/2011 21:14:00
Showing1 changed files
... ...
@@ -220,7 +220,7 @@
220 220
       <li><h4><a href="http://inspirated.com/uploads/tor-gsoc-11.pdf">GTK+ Frontend and Client Mode Improvements for arm</a> by Kamran Khan</h4></li>
221 221
       <li><h4><a href="http://www.gsathya.in/gsoc11.html">Orbot + ORLib</a> by Sathya Gunasekaran</h4></li>
222 222
       <li><h4><a href="http://blanu.net/TorSummerOfCodeProposal.pdf">Blocking-resistant Transport Evaluation Framework</a> by Brandon Wiley</h4></li>
223
-      <li><h4><a href="../about/gsocProposal/gsoc11-proposal-metadataToolkit.txt">Metadata Anonymisation Toolkit</a> by Julien Voisin</h4></li>
223
+      <li><h4><a href="../about/gsocProposal/gsoc11-proposal-metadataToolkit.pdf">Metadata Anonymisation Toolkit</a> by Julien Voisin</h4></li>
224 224
       <li><h4><a href="http://www.atagar.com/misc/gsocBlog09/">Website Pootle Translation</a> by Damian Johnson</h4></li>
225 225
     </ul>
226 226
     
Browse code

Asking org preference on the GSoC app template to help with deduplication next year

Damian Johnson authored on13/05/2011 18:10:10
Showing1 changed files
... ...
@@ -166,6 +166,11 @@
166 166
     Interacting with us on IRC will help us get to know you, and help you
167 167
     get to know our community.</li>
168 168
     
169
+    <li>Are you applying to other projects for GSoC and, if so, what would be
170
+    your preference if you're accepted to both? Having a stated preference
171
+    helps with the deduplication process and will not impact if we accept your
172
+    application or not.</li>
173
+    
169 174
     <li>Is there anything else we should know that will make us like your
170 175
     project more?</li>
171 176
     
Browse code

Adding gsoc proposals for this year's students

Damian Johnson authored on13/05/2011 17:51:39
Showing1 changed files
... ...
@@ -212,6 +212,10 @@
212 212
       <li><h4><a href="http://tor.spanning-tree.org/proposal.html">DNSEL Rewrite</a> by Harry Bock</h4></li>
213 213
       <li><h4><a href="http://kjb.homeunix.com/wp-content/uploads/2010/05/KevinBerry-GSoC2010-TorProposal.html">Extending Tor Network Metrics</a> by Kevin Berry</h4></li>
214 214
       <li><h4><a href="../about/gsocProposal/gsoc10-proposal-soat.txt">SOAT Expansion</a> by John Schanck</h4></li>
215
+      <li><h4><a href="http://inspirated.com/uploads/tor-gsoc-11.pdf">GTK+ Frontend and Client Mode Improvements for arm</a> by Kamran Khan</h4></li>
216
+      <li><h4><a href="http://www.gsathya.in/gsoc11.html">Orbot + ORLib</a> by Sathya Gunasekaran</h4></li>
217
+      <li><h4><a href="http://blanu.net/TorSummerOfCodeProposal.pdf">Blocking-resistant Transport Evaluation Framework</a> by Brandon Wiley</h4></li>
218
+      <li><h4><a href="../about/gsocProposal/gsoc11-proposal-metadataToolkit.txt">Metadata Anonymisation Toolkit</a> by Julien Voisin</h4></li>
215 219
       <li><h4><a href="http://www.atagar.com/misc/gsocBlog09/">Website Pootle Translation</a> by Damian Johnson</h4></li>
216 220
     </ul>
217 221
     
Browse code

Noting that a timeline is highly recommended for gsoc apps (caught by asn).

Damian Johnson authored on05/04/2011 17:05:20
Showing1 changed files
... ...
@@ -129,7 +129,8 @@
129 129
     descriptions of what you're going to do, with more details about the
130 130
     parts you expect to be tricky. Your proposal should also try to break
131 131
     down the project into tasks of a fairly fine granularity, and convince
132
-    us you have a plan for finishing it.</li>
132
+    us you have a plan for finishing it. A timeline for what you will be doing
133
+    throughout the summer is highly recommended.</li>
133 134
     
134 135
     <li>Point us to a code sample: something good and clean to demonstrate
135 136
     that you know what you're doing, ideally from an existing project.</li>
Browse code

fix page title

Roger Dingledine authored on01/04/2011 19:31:50
Showing1 changed files
... ...
@@ -2,7 +2,7 @@
2 2
 # Revision: $Revision$
3 3
 # Translation-Priority: 4-optional
4 4
 
5
-#include "head.wmi" TITLE="Tor: Google Summer of Code 2010" CHARSET="UTF-8"
5
+#include "head.wmi" TITLE="Tor: Google Summer of Code 2011" CHARSET="UTF-8"
6 6
 <div id="content" class="clearfix">
7 7
   <div id="breadcrumbs">
8 8
     <a href="<page index>">Home &raquo; </a>
Browse code

Little more failure with anchor (this time stopped trying to race with phobos' push).

Damian Johnson authored on25/03/2011 16:57:24
Showing1 changed files
... ...
@@ -198,6 +198,7 @@
198 198
     consider spending some time working with us to make Tor better!
199 199
     </p>
200 200
     
201
+    <a id="Example"></a>
201 202
     <h2><a class="anchor" href="#Example">Application Examples</a></h2>
202 203
     
203 204
     <p>
Browse code

Minor bug with anchor tag.

Damian Johnson authored on25/03/2011 16:55:26
Showing1 changed files
... ...
@@ -198,7 +198,7 @@
198 198
     consider spending some time working with us to make Tor better!
199 199
     </p>
200 200
     
201
-    <h2><a class="anchor" href="#Template">Application Examples</a></h2>
201
+    <h2><a class="anchor" href="#Example">Application Examples</a></h2>
202 202
     
203 203
     <p>
204 204
     Below are examples of some GSoC applications from previous years we liked.
Browse code

Adding example proposals for GSoC.

Damian Johnson authored on25/03/2011 16:53:52
Showing1 changed files
... ...
@@ -197,6 +197,22 @@
197 197
     students. So if you haven't filled up your summer plans yet, please
198 198
     consider spending some time working with us to make Tor better!
199 199
     </p>
200
+    
201
+    <h2><a class="anchor" href="#Template">Application Examples</a></h2>
202
+    
203
+    <p>
204
+    Below are examples of some GSoC applications from previous years we liked.
205
+    The best applications tend to go through several iterations so you're
206
+    highly encouraged to send drafts early.
207
+    </p>
208
+    
209
+    <ul>
210
+      <li><h4><a href="http://tor.spanning-tree.org/proposal.html">DNSEL Rewrite</a> by Harry Bock</h4></li>
211
+      <li><h4><a href="http://kjb.homeunix.com/wp-content/uploads/2010/05/KevinBerry-GSoC2010-TorProposal.html">Extending Tor Network Metrics</a> by Kevin Berry</h4></li>
212
+      <li><h4><a href="../about/gsocProposal/gsoc10-proposal-soat.txt">SOAT Expansion</a> by John Schanck</h4></li>
213
+      <li><h4><a href="http://www.atagar.com/misc/gsocBlog09/">Website Pootle Translation</a> by Damian Johnson</h4></li>
214
+    </ul>
215
+    
200 216
   </div>
201 217
   <!-- END MAINCOL -->
202 218
   <div id = "sidecol">
Browse code

minor fix

Roger Dingledine authored on11/03/2011 02:12:39
Showing1 changed files
... ...
@@ -186,7 +186,7 @@
186 186
     If you're interested, you can either contact the <a href="<page
187 187
     about/contact>">tor-assistants list</a> with a brief summary of your proposal
188 188
     and we'll give you feedback, or just jump right in and post your ideas
189
-    and goals to the <a href="<page docs/documentation>#MailingLists">or-talk
189
+    and goals to the <a href="<page docs/documentation>#MailingLists">tor-talk
190 190
     mailing list</a>. Make sure to be responsive during the application
191 191
     selection period; if we like your application but you never answer our
192 192
     mails asking for more information, that's not a good sign.
Browse code

get rid of a stray /

Roger Dingledine authored on10/03/2011 20:58:49
Showing1 changed files
... ...
@@ -20,7 +20,7 @@
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>.
23
+    and <a href="<blog>tor-google-summer-code-2010">2010</a>.
24 24
     In total we had 21 students as full-time developers for the summers of 2007 to
25 25
     2010. Now we are applying to <a
26 26
     href="https://socghop.appspot.com/gsoc/program/home/google/gsoc2011">Google
Browse code

Making the link from the gsoc -> projects page more prominent (for students this will be the most important link on the page since it has the ideas, so we want it to stand out).

Damian Johnson authored on04/03/2011 17:30:18
Showing1 changed files
... ...
@@ -93,8 +93,9 @@
93 93
     <h2><a class="anchor" href="#Ideas">Ideas List</a></h2>
94 94
     
95 95
     <p>
96
-    This year, we started an ideas list about projects to
97
-    <a href="<page getinvolved/volunteer>#Projects">help develop Tor</a>.
96
+    To start with, please see our <b><a href="<page
97
+    getinvolved/volunteer>#Projects">projects page</a></b> and its following
98
+    ideas.
98 99
     </p>
99 100
     
100 101
     <p>
Browse code

more gsoc cleanup.

Andrew Lewman authored on02/02/2011 16:48:41
Showing1 changed files
... ...
@@ -18,7 +18,9 @@
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
-    and <a href="http://socghop.appspot.com/gsoc/org/home/google/gsoc2009/eff">2009</a>.
21
+    <a
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>.
22 24
     In total we had 21 students as full-time developers for the summers of 2007 to
23 25
     2010. Now we are applying to <a
24 26
     href="https://socghop.appspot.com/gsoc/program/home/google/gsoc2011">Google
... ...
@@ -91,9 +93,8 @@
91 93
     <h2><a class="anchor" href="#Ideas">Ideas List</a></h2>
92 94
     
93 95
     <p>
94
-    This year, we have two ideas lists: one for projects to
95
-    <a href="<page getinvolved/volunteer>#Projects">help develop Tor</a>,
96
-    and one for <a href="https://www.eff.org/gsoc2010">EFF's projects</a>.
96
+    This year, we started an ideas list about projects to
97
+    <a href="<page getinvolved/volunteer>#Projects">help develop Tor</a>.
97 98
     </p>
98 99
     
99 100
     <p>
Browse code

clean up the gsoc page for 2011.

Andrew Lewman authored on02/02/2011 16:41:21
Showing1 changed files
... ...
@@ -6,31 +6,29 @@
6 6
 <div id="content" class="clearfix">
7 7
   <div id="breadcrumbs">
8 8
     <a href="<page index>">Home &raquo; </a>
9
-    <a href="<page about/gsoc>">Google Summer of Code 2010</a>
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 2010</h2>
12
+    <h2>Tor: Google Summer of Code 2011</h2>
13 13
     <hr>
14 14
     
15 15
     <p>
16
-    In the last three years, The Tor Project in collaboration with <a
16
+    In the last four 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
     and <a href="http://socghop.appspot.com/gsoc/org/home/google/gsoc2009/eff">2009</a>.
22
-    In total we had 17 students as full-time developers for the summers of 2007 to
23
-    2009. Now we've been accepted to <a
24
-    href="https://socghop.appspot.com/gsoc/org/show/google/gsoc2010/tor">Google
25
-    Summer of Code 2010</a>!
22
+    In total we had 21 students as full-time developers for the summers of 2007 to
23
+    2010. Now we are applying to <a
24
+    href="https://socghop.appspot.com/gsoc/program/home/google/gsoc2011">Google
25
+    Summer of Code 2011</a>.
26 26
     </p>
27 27
     
28 28
     <p>
29 29
     The <a
30
-    href="http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/timeline">deadline</a>
31
-    for your <a
32
-    href="http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#student_apply">application</a>
33
-    is <b>April 9, 2010</b> at 19:00 UTC.
30
+    href="https://socghop.appspot.com/document/show/gsoc_program/google/gsoc2011/timeline">timeline</a>
31
+    for GSoC 2011 is available.
34 32
     </p>
35 33
     
36 34
     <p>
... ...
@@ -171,7 +169,7 @@
171 169
     </ol>
172 170
     
173 171
     <p>
174
-    We have picked out 10+ mentors for this year &mdash; most of the
172
+    We will pick out mentors for this year &mdash; most of the
175 173
     people on the <a href="<page about/corepeople>">core Tor development team</a>
176 174
     plus a few people from <a href="http://www.eff.org/about/staff">EFF's staff</a>
177 175
     &mdash; so we should be able to accommodate a wide variety of projects,
Browse code

looks like we never set the keywords either

Roger Dingledine authored on27/10/2010 12:31:57
Showing1 changed files
... ...
@@ -1,5 +1,5 @@
1 1
 ## translation metadata
2
-# Revision: $Revision: 22179 $
2
+# Revision: $Revision$
3 3
 # Translation-Priority: 4-optional
4 4
 
5 5
 #include "head.wmi" TITLE="Tor: Google Summer of Code 2010" CHARSET="UTF-8"
Browse code

We decided to go with HTML in favor of XHTML.

Sebastian Hahn authored on10/10/2010 03:34:47
Showing1 changed files
... ...
@@ -10,7 +10,7 @@
10 10
   </div>
11 11
   <div id="maincol"> 
12 12
     <h2>Tor: Google Summer of Code 2010</h2>
13
-    <hr />
13
+    <hr>
14 14
     
15 15
     <p>
16 16
     In the last three years, The Tor Project in collaboration with <a
Browse code

remove more dead links.

Andrew Lewman authored on07/10/2010 22:18:13
Showing1 changed files
... ...
@@ -172,7 +172,7 @@
172 172
     
173 173
     <p>
174 174
     We have picked out 10+ mentors for this year &mdash; most of the
175
-    people on the <a href="<page about/people>#Core">core Tor development team</a>
175
+    people on the <a href="<page about/corepeople>">core Tor development team</a>
176 176
     plus a few people from <a href="http://www.eff.org/about/staff">EFF's staff</a>
177 177
     &mdash; so we should be able to accommodate a wide variety of projects,
178 178
     ranging from work on Tor itself to work on supporting or peripheral
Browse code

change all of the breadcrumbs from page home to page index.

Andrew Lewman authored on12/08/2010 17:17:47
Showing1 changed files
... ...
@@ -5,7 +5,7 @@
5 5
 #include "head.wmi" TITLE="Tor: Google Summer of Code 2010" CHARSET="UTF-8"
6 6
 <div id="content" class="clearfix">
7 7
   <div id="breadcrumbs">
8
-    <a href="<page home>">Home &raquo; </a>
8
+    <a href="<page index>">Home &raquo; </a>
9 9
     <a href="<page about/gsoc>">Google Summer of Code 2010</a>
10 10
   </div>
11 11
   <div id="maincol"> 
Browse code

first cut of the new, shiny tor website as wml.

Andrew Lewman authored on09/07/2010 03:55:22
Showing1 changed files
1 1
new file mode 100644
... ...
@@ -0,0 +1,210 @@
1
+## translation metadata
2
+# Revision: $Revision: 22179 $
3
+# Translation-Priority: 4-optional
4
+
5
+#include "head.wmi" TITLE="Tor: Google Summer of Code 2010" CHARSET="UTF-8"
6
+<div id="content" class="clearfix">
7
+  <div id="breadcrumbs">
8
+    <a href="<page home>">Home &raquo; </a>
9
+    <a href="<page about/gsoc>">Google Summer of Code 2010</a>
10
+  </div>
11
+  <div id="maincol"> 
12
+    <h2>Tor: Google Summer of Code 2010</h2>
13
+    <hr />
14
+    
15
+    <p>
16
+    In the last three years, The Tor Project in collaboration with <a
17
+    href="https://www.eff.org/">The Electronic Frontier Foundation</a>
18
+    successfully took part in
19
+    <a href="http://code.google.com/soc/2007/eff/about.html">Google Summer of Code
20
+    2007</a>, <a href="http://code.google.com/soc/2008/eff/about.html">2008</a>,
21
+    and <a href="http://socghop.appspot.com/gsoc/org/home/google/gsoc2009/eff">2009</a>.
22
+    In total we had 17 students as full-time developers for the summers of 2007 to
23
+    2009. Now we've been accepted to <a
24
+    href="https://socghop.appspot.com/gsoc/org/show/google/gsoc2010/tor">Google
25
+    Summer of Code 2010</a>!
26
+    </p>
27
+    
28
+    <p>
29
+    The <a
30
+    href="http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/timeline">deadline</a>
31
+    for your <a
32
+    href="http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#student_apply">application</a>
33
+    is <b>April 9, 2010</b> at 19:00 UTC.
34
+    </p>
35
+    
36
+    <p>
37
+    You must be self-motivated and able to work independently. We have
38
+    a thriving community of interested developers on the IRC channel and
39
+    mailing lists, and we're eager to work with you, brainstorm about design,
40
+    and so on, but you need to be able to manage your own time, and you
41
+    need to already be somewhat familiar with how free software development on the
42
+    Internet works.
43
+    </p>
44
+    
45
+    <p>
46
+    Working on Tor is rewarding because:
47
+    </p>
48
+    
49
+    <ul>
50
+    <li>You can work your own hours in your own locations. As long as you
51
+    get the job done, we don't care about the process.</li>
52
+    <li>We only write free (open source) software. The tools you make won't
53
+    be locked down or rot on a shelf.</li>
54
+    <li>You will work with a world-class team of anonymity experts and
55
+    developers on what is already the largest and most active strong anonymity
56
+    network ever.</li>
57
+    <li>The work you do could contribute to academic publications &mdash;
58
+    Tor development raises many open questions and interesting problems
59
+    in the field of <a href="http://freehaven.net/anonbib/">anonymity
60
+    systems</a>.</li>
61
+    </ul>
62
+    
63
+    <a id="GettingInvolved"></a>
64
+    <h2><a class="anchor" href="#GettingInvolved">How To Get Involved</a></h2>
65
+    
66
+    <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>.
72
+    </p>
73
+    
74
+    <p>
75
+    In addition to getting some more development work
76
+    done on Tor and related applications, Google and Tor are most interested
77
+    in getting students involved in Tor development in a way that keeps them
78
+    involved after the summer too. That means we will give priority to students
79
+    who have demonstrated continued interest and responsiveness. We will require
80
+    students to write public status report updates for our community, either by
81
+    blogging or sending mail to our mailing list. We want to ensure that the
82
+    community and the student can both benefit from each other.
83
+    </p>
84
+    
85
+    <p>
86
+    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
+    the initiative to do things &mdash; will be at least as important as
89
+    the actual project you'll be working on.
90
+    </p>
91
+    
92
+    <a id="Ideas"></a>
93
+    <h2><a class="anchor" href="#Ideas">Ideas List</a></h2>
94
+    
95
+    <p>
96
+    This year, we have two ideas lists: one for projects to
97
+    <a href="<page getinvolved/volunteer>#Projects">help develop Tor</a>,
98
+    and one for <a href="https://www.eff.org/gsoc2010">EFF's projects</a>.
99
+    </p>
100
+    
101
+    <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.
115
+    </p>
116
+    
117
+    <a id="Template"></a>
118
+    <h2><a class="anchor" href="#Template">Application Template</a></h2>
119
+    
120
+    <p>
121
+    Please use the following template for your application, to make sure you
122
+    provide enough information for us to evaluate you and your proposal.
123
+    </p>
124
+    
125
+    <ol>
126
+    
127
+    <li>What project would you like to work on? Use our ideas lists as a starting
128
+    point or make up your own idea. Your proposal should include high-level
129
+    descriptions of what you're going to do, with more details about the
130
+    parts you expect to be tricky. Your proposal should also try to break
131
+    down the project into tasks of a fairly fine granularity, and convince
132
+    us you have a plan for finishing it.</li>
133
+    
134
+    <li>Point us to a code sample: something good and clean to demonstrate
135
+    that you know what you're doing, ideally from an existing project.</li>
136
+    
137
+    <li>Why do you want to work with The Tor Project / EFF in
138
+    particular?</li>
139
+    
140
+    <li>Tell us about your experiences in free software development
141
+    environments. We especially want to hear examples of how you have
142
+    collaborated with others rather than just working on a project by
143
+    yourself.</li>
144
+    
145
+    <li>Will you be working full-time on the project for the summer, or will
146
+    you have other commitments too (a second job, classes, etc)? If you won't
147
+    be available full-time, please explain, and list timing if you know them
148
+    for other major deadlines (e.g. exams). Having other activities isn't
149
+    a deal-breaker, but we don't want to be surprised.</li>
150
+    
151
+    <li>Will your project need more work and/or maintenance after the summer
152
+    ends? What are the chances you will stick around and help out with that
153
+    and other related projects?</li>
154
+    
155
+    <li>What is your ideal approach to keeping everybody informed of your
156
+    progress, problems, and questions over the course of the project? Said
157
+    another way, how much of a "manager" will you need your mentor to be?</li>
158
+    
159
+    <li>What school are you attending? What year are you, and what's your
160
+    major/degree/focus? If you're part of a research group, which one?</li>
161
+    
162
+    <li>How can we contact you to ask you further questions? Google doesn't
163
+    share your contact details with us automatically, so you should include
164
+    that in your application. In addition, what's your IRC nickname?
165
+    Interacting with us on IRC will help us get to know you, and help you
166
+    get to know our community.</li>
167
+    
168
+    <li>Is there anything else we should know that will make us like your
169
+    project more?</li>
170
+    
171
+    </ol>
172
+    
173
+    <p>
174
+    We have picked out 10+ mentors for this year &mdash; most of the
175
+    people on the <a href="<page about/people>#Core">core Tor development team</a>
176
+    plus a few people from <a href="http://www.eff.org/about/staff">EFF's staff</a>
177
+    &mdash; so we should be able to accommodate a wide variety of projects,
178
+    ranging from work on Tor itself to work on supporting or peripheral
179
+    projects. We can figure out which mentor is appropriate while we're
180
+    discussing the project you have in mind. We plan to assign a primary
181
+    mentor to each student, along with one or two assistant mentors to help
182
+    answer questions and help you integrate with the broader Tor community.
183
+    </p>
184
+    
185
+    <p>
186
+    If you're interested, you can either contact the <a href="<page
187
+    about/contact>">tor-assistants list</a> with a brief summary of your proposal
188
+    and we'll give you feedback, or just jump right in and post your ideas
189
+    and goals to the <a href="<page docs/documentation>#MailingLists">or-talk
190
+    mailing list</a>. Make sure to be responsive during the application
191
+    selection period; if we like your application but you never answer our
192
+    mails asking for more information, that's not a good sign.
193
+    </p>
194
+    
195
+    <p>
196
+    The more applications we get, the more likely Google is to give us good
197
+    students. So if you haven't filled up your summer plans yet, please
198
+    consider spending some time working with us to make Tor better!
199
+    </p>
200
+  </div>
201
+  <!-- END MAINCOL -->
202
+  <div id = "sidecol">
203
+#include "side.wmi"
204
+#include "info.wmi"
205
+  </div>
206
+  <!-- END SIDECOL -->
207
+</div>
208
+<!-- END CONTENT -->
209
+#include <foot.wmi>
210
+