tor-webwml.git

1) ## translation metadata
2) # Revision: $Revision$
3) 
4) #include "head.wmi" TITLE="Tor: Google Summer of Code 2008"
5) 
6) <div class="main-column">
7) 
8) <h2>Tor: Google Summer of Code 2008</h2>
9) <hr />
10) 
11) <p>
12) Last year in 2007, The Tor Project in collaboration with <a
13) href="https://www.eff.org/">The Electronic Frontier Foundation</a>
14) successfully took part in <a href="http://code.google.com/soc/">Google
15) Summer of Code 2007</a>. In total we had four students as full-time
16) developers for the summer of 2007.
17) </p>
18) 
19) <p>
20) Google has announced that there will also be a <a

21) href="http://code.google.com/soc/">Google Summer of Code 2008</a>...
22) and we have been accepted! A <a href="http://code.google.com/soc/2008/">list 
23) of accepted mentoring
24) organizations</a> was published by Google on March 17.
25) This page contains some information for interested students.

26) </p>
27) 
28) <p>
29) The deadline for your application is <b>March 31, 2008</b> at 5pm
30) Pacific time.
31) </p>
32) 
33) <p>
34) You must be self-motivated and able to work independently. We have
35) a thriving community of interested developers on the IRC channel and
36) mailing lists, and we're eager to work with you, brainstorm about design,
37) and so on, but you need to be able to manage your own time, and you
38) need to already be familiar with how free software development on the

39) Internet works.
40) </p>
41) 
42) <p>
43) In addition to hoping to get some more development work

44) done on Tor and related applications, Google and Tor are most interested
45) in getting students involved in the project in a way that keeps them
46) involved after the summer too. As such, we will give priority to students
47) who have demonstrated continued interest and responsiveness.

48) </p>
49) 
50) <p>
51) Working on Tor is rewarding because:
52) </p>
53) 
54) <ul>
55) <li>You can work your own hours in your own locations. As long as you
56) get the job done, we don't care about the process.</li>
57) <li>We only write free (open source) software. The tools you make won't
58) be locked down or rot on a shelf.</li>
59) <li>You will work with a world-class team of anonymity experts and
60) developers on what is already the largest and most active strong anonymity
61) network ever.</li>
62) <li>The work you do could contribute to academic publications --
63) Tor development raises many open questions and interesting problems
64) in the field of <a href="http://freehaven.net/anonbib/">anonymity
65) systems</a>.</li>
66) </ul>
67) 
68) <a id="Template"></a>
69) 
70) <p>
71) Please use the following template for your application, to make sure you
72) provide enough information for us to evaluate you and your proposal.
73) </p>
74) 
75) <ol>
76) 
77) <li>What project would you like to work on? Use
78) <a href="<page volunteer>#Projects">this list</a>
79) for ideas or make up your own. Your proposal should include high-level
80) descriptions of what you're going to do, with more details about the
81) parts you expect to be tricky. Your proposal should also try to break
82) down the project into tasks of a fairly fine granularity, and convince
83) us you have a plan for finishing it.</li>
84) 
85) <li>Point us to a code sample: something good and clean to demonstrate
86) that you know what you're doing, ideally from an existing project.</li>
87) 
88) <li>Why do you want to work with The Tor Project in particular?</li>
89) 
90) <li>Tell us about your experiences in free software development
91) environments. We especially want to hear examples of how you have
92) collaborated with others rather than just working on a project by
93) yourself.</li>
94) 
95) <li>Will you be working full-time on the project for the summer, or will
96) you have other commitments too (a second job, classes, etc)? If you won't
97) be available full-time, please explain, and list timing if you know them
98) for other major deadlines (e.g. exams). Having other activities isn't

99) a deal-breaker, but we don't want to be surprised.</li>