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/gsoc_program/google/gsoc2010/timeline">deadline</a>

28) for your <a

29) href="http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#student_apply">application</a>
30) is <b>April 9, 2010</b> at 19:00 UTC.
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) Working on Tor is rewarding because:
44) </p>
45) 
46) <ul>
47) <li>You can work your own hours in your own locations. As long as you
48) get the job done, we don't care about the process.</li>
49) <li>We only write free (open source) software. The tools you make won't
50) be locked down or rot on a shelf.</li>
51) <li>You will work with a world-class team of anonymity experts and
52) developers on what is already the largest and most active strong anonymity
53) network ever.</li>

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

55) Tor development raises many open questions and interesting problems
56) in the field of <a href="http://freehaven.net/anonbib/">anonymity
57) systems</a>.</li>
58) </ul>
59) 

60) <a id="GettingInvolved"></a>
61) <h2><a class="anchor" href="#GettingInvolved">How To Get Involved</a></h2>
62) 
63) <p>
64) The best way to get involved is to come listen on IRC (both "#tor" and
65) "#tor-dev"), read our docs and other webpages, try out the various tools
66) that are related to the projects that interest you, and ask questions
67) as they come to you: <a href="<page documentation>#UpToSpeed">Getting
68) up to speed</a>.
69) </p>
70) 

71) <p>
72) In addition to getting some more development work
73) done on Tor and related applications, Google and Tor are most interested
74) in getting students involved in Tor development in a way that keeps them
75) involved after the summer too. That means we will give priority to students
76) who have demonstrated continued interest and responsiveness. We will require
77) students to write public status report updates for our community, either by
78) blogging or sending mail to our mailing list. We want to ensure that the
79) community and the student can both benefit from each other.
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) <p>
99) The best kind of ideas are A) ones that we know we need done real soon
100) now (you can get a sense of urgency from the priority on the wishlist,
101) and from talking to the potential mentors), and B) ones where it's
102) clear what needs to be done, at least for the first few steps. Lots of
103) students try to bite off open-ended research topics; but if you're going
104) to be spending the first half of your summer figuring out what exactly
105) you should code, and there's a chance that the conclusion will be "oh,
106) that isn't actually a good idea to build", then your proposal will make
107) us very nervous. Try to figure out how much you can actually fit in a
108) summer, break the work down into manageable pieces, and most importantly,
109) figure out how to make sure your incremental milestones are actually
110) useful &mdash; if you don't finish everything in your plan, we want to
111) know that you'll still have produced something useful.
112) </p>
113) 

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

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

116) 
117) <p>
118) Please use the following template for your application, to make sure you
119) provide enough information for us to evaluate you and your proposal.
120) </p>
121) 
122) <ol>
123) 

124) <li>What project would you like to work on? Use our ideas lists as a starting

125) point or make up your own idea. Your proposal should include high-level

126) descriptions of what you're going to do, with more details about the
127) parts you expect to be tricky. Your proposal should also try to break
128) down the project into tasks of a fairly fine granularity, and convince
129) us you have a plan for finishing it.</li>
130) 
131) <li>Point us to a code sample: something good and clean to demonstrate
132) that you know what you're doing, ideally from an existing project.</li>
133) 

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

135) particular?</li>

136) 
137) <li>Tell us about your experiences in free software development
138) environments. We especially want to hear examples of how you have
139) collaborated with others rather than just working on a project by
140) yourself.</li>
141) 
142) <li>Will you be working full-time on the project for the summer, or will
143) you have other commitments too (a second job, classes, etc)? If you won't
144) be available full-time, please explain, and list timing if you know them
145) for other major deadlines (e.g. exams). Having other activities isn't

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

147) 
148) <li>Will your project need more work and/or maintenance after the summer
149) ends? What are the chances you will stick around and help out with that
150) and other related projects?</li>
151) 
152) <li>What is your ideal approach to keeping everybody informed of your
153) progress, problems, and questions over the course of the project? Said
154) another way, how much of a "manager" will you need your mentor to be?</li>
155) 
156) <li>What school are you attending? What year are you, and what's your
157) major/degree/focus? If you're part of a research group, which one?</li>
158) 

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

161) that in your application. In addition, what's your IRC nickname?
162) Interacting with us on IRC will help us get to know you, and help you
163) get to know our community.</li>

164) 

165) <li>Is there anything else we should know that will make us like your
166) project more?</li>
167) 
168) </ol>
169) 
170) <p>

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

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

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

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

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