tor-webwml.git

1) ## translation metadata
2) # Revision: $Revision$

3) # Translation-Priority: 4-optional

4) 

5) #include "head.wmi" TITLE="Tor: Google Summer of Code 2010" CHARSET="UTF-8"

6) 
7) <div class="main-column">
8) 

9) <h2>Tor: Google Summer of Code 2010</h2>

10) <hr />
11) 
12) <p>

13) In the last three years, The Tor Project in collaboration with <a

14) href="https://www.eff.org/">The Electronic Frontier Foundation</a>

15) successfully took part in
16) <a href="http://code.google.com/soc/2007/eff/about.html">Google Summer of Code

17) 2007</a>, <a href="http://code.google.com/soc/2008/eff/about.html">2008</a>,
18) and <a href="http://socghop.appspot.com/gsoc/org/home/google/gsoc2009/eff">2009</a>.
19) In total we had 17 students as full-time developers for the summers of 2007 to

20) 2009. Now we've been accepted to <a
21) href="https://socghop.appspot.com/gsoc/org/show/google/gsoc2010/tor">Google
22) Summer of Code 2010</a>!

23) </p>
24) 

25) <!--<p>

26) The <a

27) href="http://socghop.appspot.com/document/show/program/google/gsoc2009/faqs#timeline">deadline</a>

28) for your <a
29) href="http://groups.google.com/group/google-summer-of-code-announce/web/guide-to-the-gsoc-web-app-for-student-applicants">application</a>

30) is <b>April 20, 2009</b> at 5pm 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 somewhat familiar with how free software development on the

39) Internet works.
40) </p>
41) 
42) <p>

43) In addition to getting some more development work

44) done on Tor and related applications, Google and Tor are most interested

45) in getting students involved in Tor development in a way that keeps them

46) involved after the summer too. That means we will give priority to students

47) who have demonstrated continued interest and responsiveness. We will require
48) students to write public status report updates for our community, either by
49) blogging or sending mail to our mailing list. We want to ensure that the
50) community and the student can both benefit from each other.

51) </p>
52) 
53) <p>
54) Working on Tor is rewarding because:
55) </p>
56) 
57) <ul>
58) <li>You can work your own hours in your own locations. As long as you
59) get the job done, we don't care about the process.</li>
60) <li>We only write free (open source) software. The tools you make won't
61) be locked down or rot on a shelf.</li>
62) <li>You will work with a world-class team of anonymity experts and
63) developers on what is already the largest and most active strong anonymity
64) network ever.</li>

65) <li>The work you do could contribute to academic publications &mdash;

66) Tor development raises many open questions and interesting problems
67) in the field of <a href="http://freehaven.net/anonbib/">anonymity
68) systems</a>.</li>
69) </ul>
70) 

71) <a id="GettingInvolved"></a>
72) <h2><a class="anchor" href="#GettingInvolved">How To Get Involved</a></h2>
73) 
74) <p>
75) The best way to get involved is to come listen on IRC (both "#tor" and
76) "#tor-dev"), read our docs and other webpages, try out the various tools
77) that are related to the projects that interest you, and ask questions
78) as they come to you: <a href="<page documentation>#UpToSpeed">Getting
79) up to speed</a>.
80) </p>
81) 
82) <p>
83) When it comes time for us to choose projects, our impression of how well
84) you'll fit into our community &mdash; and how good you are at taking
85) the initiative to do things &mdash; will be at least as important as
86) the actual project you'll be working on.
87) </p>
88) 

89) <a id="Ideas"></a>
90) <h2><a class="anchor" href="#Ideas">Ideas List</a></h2>
91) 
92) <p>
93) This year, we have two ideas lists: one for projects to
94) <a href="<page volunteer>#Projects">help develop Tor</a>,

95) and one for <a href="https://www.eff.org/gsoc2010">EFF's projects</a>.

96) </p>
97) 

98) <a id="Template"></a>

99) <h2><a class="anchor" href="#Template">Application Template</a></h2>

100) 
101) <p>
102) Please use the following template for your application, to make sure you
103) provide enough information for us to evaluate you and your proposal.
104) </p>
105) 
106) <ol>
107) 

108) <li>What project would you like to work on? Use our ideas lists as starting
109) point or make up your own idea. Your proposal should include high-level

110) descriptions of what you're going to do, with more details about the
111) parts you expect to be tricky. Your proposal should also try to break
112) down the project into tasks of a fairly fine granularity, and convince
113) us you have a plan for finishing it.</li>
114) 
115) <li>Point us to a code sample: something good and clean to demonstrate
116) that you know what you're doing, ideally from an existing project.</li>
117) 

118) <li>Why do you want to work with The Tor Project / EFF in

119) particular?</li>

120) 
121) <li>Tell us about your experiences in free software development
122) environments. We especially want to hear examples of how you have
123) collaborated with others rather than just working on a project by
124) yourself.</li>
125) 
126) <li>Will you be working full-time on the project for the summer, or will
127) you have other commitments too (a second job, classes, etc)? If you won't
128) be available full-time, please explain, and list timing if you know them
129) for other major deadlines (e.g. exams). Having other activities isn't

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

131) 
132) <li>Will your project need more work and/or maintenance after the summer
133) ends? What are the chances you will stick around and help out with that
134) and other related projects?</li>
135) 
136) <li>What is your ideal approach to keeping everybody informed of your
137) progress, problems, and questions over the course of the project? Said
138) another way, how much of a "manager" will you need your mentor to be?</li>
139) 
140) <li>What school are you attending? What year are you, and what's your
141) major/degree/focus? If you're part of a research group, which one?</li>
142) 

143) <li>How can we contact you to ask you further questions? Google doesn't
144) share your contact details with us automatically, so you should include

145) that in your application.</li>

146) 

147) <li>Is there anything else we should know that will make us like your
148) project more?</li>
149) 
150) </ol>
151) 
152) <p>

153) We have picked out 10+ mentors for this year — most of the

154) people on the <a href="<page people>#Core">core Tor development team</a>

155) plus a few people from <a href="http://www.eff.org/about/staff">EFF's staff</a>

156) — so we should be able to accommodate a wide variety of projects,
157) ranging from work on Tor itself to work on supporting or peripheral
158) projects. We can figure out which mentor is appropriate while we're

159) discussing the project you have in mind. We plan to assign a primary