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 2013" 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 2013</h2>

13)     <hr>

14)     
15)     <p>

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

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

55)     The best way to get involved is to come <a href="<page
56)     about/contact>#irc">listen on IRC</a> (both "#tor" and "#tor-dev"), read
57)     our docs and other webpages, try out the various tools that are related to
58)     the projects that interest you, and ask questions as they come to you: <a
59)     href="<page docs/documentation>#UpToSpeed">Getting up to speed</a>.

60)     </p>
61)     
62)     <p>
63)     In addition to getting some more development work
64)     done on Tor and related applications, Google and Tor are most interested
65)     in getting students involved in Tor development in a way that keeps them
66)     involved after the summer too. That means we will give priority to students
67)     who have demonstrated continued interest and responsiveness. We will require
68)     students to write public status report updates for our community, either by
69)     blogging or sending mail to our mailing list. We want to ensure that the
70)     community and the student can both benefit from each other.
71)     </p>
72)     
73)     <p>
74)     When it comes time for us to choose projects, our impression of how well

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

76)     the initiative to do things — will be at least as important as
77)     the actual project you'll be working on.
78)     </p>
79)     
80)     <a id="Ideas"></a>
81)     <h2><a class="anchor" href="#Ideas">Ideas List</a></h2>
82)     
83)     <p>

84)     To start with, please see Tor's <b><a href="<page

85)     getinvolved/volunteer>#Projects">projects page</a></b> and its following

86)     ideas.

87)     </p>
88)     
89)     <p>

90)     The best kind of ideas are well defined and easily broken into subtasks. 
91)     A lot of students try to bite off open-ended development and research
92)     topics. But if you're going to spend the first half of your summer figuring
93)     out what exactly you should code, there's a chance that the conclusion will
94)     be "oh, that isn't actually feasible to build after all" and your proposal
95)     will make us very nervous.
96)     </p>
97)     
98)     <p>
99)     Try to figure out how much you can actually fit in a summer, break the work
100)     down into manageable pieces, and most importantly, figure out how to make
101)     sure your incremental milestones are actually useful &mdash; if you don't
102)     finish everything in your plan, we want to know that you'll still have
103)     produced something useful.

104)     </p>
105)     
106)     <a id="Template"></a>
107)     <h2><a class="anchor" href="#Template">Application Template</a></h2>
108)     
109)     <p>
110)     Please use the following template for your application, to make sure you
111)     provide enough information for us to evaluate you and your proposal.
112)     </p>
113)     
114)     <ol>
115)     
116)     <li>What project would you like to work on? Use our ideas lists as a starting
117)     point or make up your own idea. Your proposal should include high-level
118)     descriptions of what you're going to do, with more details about the
119)     parts you expect to be tricky. Your proposal should also try to break
120)     down the project into tasks of a fairly fine granularity, and convince

121)     us you have a plan for finishing it. A timeline for what you will be doing

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>

127)     
128)     <li>Point us to a code sample: something good and clean to demonstrate
129)     that you know what you're doing, ideally from an existing project.</li>
130)     

131)     <li>Why do you want to work with The Tor Project in

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

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

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

168)     project more?</li>
169)     
170)     </ol>
171)     
172)     <p>

173)     We mostly pick mentors from the <a href="<page about/corepeople>">core Tor

174)     development team</a> so we should be able to accommodate a wide variety of
175)     projects. These can range from work on Tor itself to work on supporting or
176)     peripheral projects.

177)     </p>
178)     
179)     <p>
180)     All selected projects are assigned both a primary and assistant mentor to
181)     answer your questions and help you integrate with the broader Tor
182)     community. Though your mentors are a primary point of contact please use
183)     our public spaces (the <a href="<page about/contact>#irc">#tor-dev irc
184)     channel</a> and <a href="<page docs/documentation>#MailingLists">tor-dev@
185)     email list</a>) to discuss your project. We want you to become a part of
186)     the community by the end of the summer, not a stranger that's only known by
187)     your mentor.

188)     </p>
189)     
190)     <p>
191)     If you're interested, you can either contact the <a href="<page

192)     about/contact>">tor-assistants list</a> (a private list) with a brief
193)     summary of your proposal and we'll give you feedback, or just jump right in
194)     and post your ideas and goals to the <a href="<page
195)     docs/documentation>#MailingLists">tor-dev mailing list</a> (which is open).
196)     Make sure to be responsive during the application selection period; if we
197)     like your application but you never answer our mails asking for more
198)     information, that's not a good sign.

199)     </p>
200)     
201)     <p>

202)     We're always happy to have new contributors so if you haven't filled up
203)     your summer plans yet, please consider spending some time working with us
204)     to make Tor better!

205)     </p>

206)     

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

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

209)     
210)     <p>
211)     Below are examples of some GSoC applications from previous years we liked.
212)     The best applications tend to go through several iterations so you're
213)     highly encouraged to send drafts early.
214)     </p>
215)     
216)     <ul>

217)       <li><h4><a href="http://kostas.mkj.lt/gsoc2013/gsoc2013.html">Searchable Tor descriptor archive</a> by Kostas Jakeliunas</h4></li>

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>

219)       <li><h4><a href="../about/gsocProposal/gsoc12-proposal-stemImprovements.html">Stem Improvements and Arm port</a> by Ravi Padmala</h4></li>

220)       <li><h4><a href="http://feroze.in/gsoc12.html">Implementing Hidden Service Configuration and Bandwidth Scheduling Plugins</a> by Feroze Naina</h4></li>

221)       <li><h4><a href="../about/gsocProposal/gsoc10-proposal-soat.txt">SOAT Expansion</a> by John Schanck</h4></li>

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

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>
227)     </ul>
228)