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 2011" CHARSET="UTF-8"

6) <div id="content" class="clearfix">
7)   <div id="breadcrumbs">

8)     <a href="<page index>">Home &raquo; </a>

9)     <a href="<page about/gsoc>">Google Summer of Code</a>

10)   </div>
11)   <div id="maincol"> 

12)     <h2>Tor: Google Summer of Code 2012</h2>

13)     <hr>

14)     
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. Now we are applying to <a
27)     href="https://socghop.appspot.com/gsoc/program/home/google/gsoc2012">Google
28)     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.

35)     </p>
36)     
37)     <p>
38)     You must be self-motivated and able to work independently. We have
39)     a thriving community of interested developers on the IRC channel and
40)     mailing lists, and we're eager to work with you, brainstorm about design,
41)     and so on, but you need to be able to manage your own time, and you
42)     need to already be somewhat familiar with how free software development on the
43)     Internet works.
44)     </p>
45)     
46)     <p>
47)     Working on Tor is rewarding because:
48)     </p>
49)     
50)     <ul>
51)     <li>You can work your own hours in your own locations. As long as you
52)     get the job done, we don't care about the process.</li>
53)     <li>We only write free (open source) software. The tools you make won't
54)     be locked down or rot on a shelf.</li>
55)     <li>You will work with a world-class team of anonymity experts and
56)     developers on what is already the largest and most active strong anonymity
57)     network ever.</li>
58)     <li>The work you do could contribute to academic publications &mdash;
59)     Tor development raises many open questions and interesting problems
60)     in the field of <a href="http://freehaven.net/anonbib/">anonymity
61)     systems</a>.</li>
62)     </ul>
63)     
64)     <a id="GettingInvolved"></a>
65)     <h2><a class="anchor" href="#GettingInvolved">How To Get Involved</a></h2>
66)     
67)     <p>

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>.

73)     </p>
74)     
75)     <p>
76)     In addition to getting some more development work
77)     done on Tor and related applications, Google and Tor are most interested
78)     in getting students involved in Tor development in a way that keeps them
79)     involved after the summer too. That means we will give priority to students
80)     who have demonstrated continued interest and responsiveness. We will require
81)     students to write public status report updates for our community, either by
82)     blogging or sending mail to our mailing list. We want to ensure that the
83)     community and the student can both benefit from each other.
84)     </p>
85)     
86)     <p>
87)     When it comes time for us to choose projects, our impression of how well

88)     you'll fit into our community — and how well you are at taking

89)     the initiative to do things — will be at least as important as
90)     the actual project you'll be working on.
91)     </p>
92)     
93)     <a id="Ideas"></a>
94)     <h2><a class="anchor" href="#Ideas">Ideas List</a></h2>
95)     
96)     <p>

97)     To start with, please see our <b><a href="<page
98)     getinvolved/volunteer>#Projects">projects page</a></b> and its following
99)     ideas.

100)     </p>
101)     
102)     <p>

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.

117)     </p>
118)     
119)     <a id="Template"></a>
120)     <h2><a class="anchor" href="#Template">Application Template</a></h2>
121)     
122)     <p>
123)     Please use the following template for your application, to make sure you
124)     provide enough information for us to evaluate you and your proposal.
125)     </p>
126)     
127)     <ol>
128)     
129)     <li>What project would you like to work on? Use our ideas lists as a starting
130)     point or make up your own idea. Your proposal should include high-level
131)     descriptions of what you're going to do, with more details about the
132)     parts you expect to be tricky. Your proposal should also try to break
133)     down the project into tasks of a fairly fine granularity, and convince

134)     us you have a plan for finishing it. A timeline for what you will be doing
135)     throughout the summer is highly recommended.</li>

136)     
137)     <li>Point us to a code sample: something good and clean to demonstrate
138)     that you know what you're doing, ideally from an existing project.</li>
139)     
140)     <li>Why do you want to work with The Tor Project / EFF in
141)     particular?</li>
142)     
143)     <li>Tell us about your experiences in free software development
144)     environments. We especially want to hear examples of how you have
145)     collaborated with others rather than just working on a project by
146)     yourself.</li>
147)     
148)     <li>Will you be working full-time on the project for the summer, or will
149)     you have other commitments too (a second job, classes, etc)? If you won't
150)     be available full-time, please explain, and list timing if you know them
151)     for other major deadlines (e.g. exams). Having other activities isn't
152)     a deal-breaker, but we don't want to be surprised.</li>
153)     
154)     <li>Will your project need more work and/or maintenance after the summer
155)     ends? What are the chances you will stick around and help out with that
156)     and other related projects?</li>
157)     
158)     <li>What is your ideal approach to keeping everybody informed of your
159)     progress, problems, and questions over the course of the project? Said
160)     another way, how much of a "manager" will you need your mentor to be?</li>
161)     
162)     <li>What school are you attending? What year are you, and what's your
163)     major/degree/focus? If you're part of a research group, which one?</li>
164)     
165)     <li>How can we contact you to ask you further questions? Google doesn't
166)     share your contact details with us automatically, so you should include
167)     that in your application. In addition, what's your IRC nickname?
168)     Interacting with us on IRC will help us get to know you, and help you
169)     get to know our community.</li>
170)     

171)     <li>Are you applying to other projects for GSoC and, if so, what would be
172)     your preference if you're accepted to both? Having a stated preference
173)     helps with the deduplication process and will not impact if we accept your
174)     application or not.</li>
175)     

176)     <li>Is there anything else that we should know that will make us like your

177)     project more?</li>
178)     
179)     </ol>
180)     
181)     <p>

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.

198)     </p>
199)     
200)     <p>
201)     If you're interested, you can either contact the <a href="<page

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.

209)     </p>
210)     
211)     <p>

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!

215)     </p>

216)     

217)     <a id="Example"></a>

218)     <h2><a class="anchor" href="#Example">Application Examples</a></h2>

219)     
220)     <p>
221)     Below are examples of some GSoC applications from previous years we liked.
222)     The best applications tend to go through several iterations so you're
223)     highly encouraged to send drafts early.
224)     </p>
225)     
226)     <ul>
227)       <li><h4><a href="http://tor.spanning-tree.org/proposal.html">DNSEL Rewrite</a> by Harry Bock</h4></li>
228)       <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>
229)       <li><h4><a href="../about/gsocProposal/gsoc10-proposal-soat.txt">SOAT Expansion</a> by John Schanck</h4></li>

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>
231)       <li><h4><a href="http://www.gsathya.in/gsoc11.html">Orbot + ORLib</a> by Sathya Gunasekaran</h4></li>
232)       <li><h4><a href="http://blanu.net/TorSummerOfCodeProposal.pdf">Blocking-resistant Transport Evaluation Framework</a> by Brandon Wiley</h4></li>

233)       <li><h4><a href="../about/gsocProposal/gsoc11-proposal-metadataToolkit.pdf">Metadata Anonymisation Toolkit</a> by Julien Voisin</h4></li>

234)       <li><h4><a href="http://www.atagar.com/misc/gsocBlog09/">Website Pootle Translation</a> by Damian Johnson</h4></li>
235)     </ul>
236)