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

13)     <hr>

14) 
15)     <br /><br />
16) 

17)     <p>

18)     The Tor Project, in collaboration with <a href="https://www.eff.org/">The
19)     Electronic Frontier Foundation</a>, have taken part in Google Summer of Code

20)     for 2007 through 2016, mentoring the total of 64 students.  Now google has

21)     announced that we'll be taking part again for <a

22)     href="https://summerofcode.withgoogle.com/">Google Summer of Code 2017</a>!

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

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

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

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

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

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

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

87)     ideas.

88)     </p>
89)     
90)     <p>

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

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

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

123)     throughout the summer is highly recommended.<br /><br />
124) 
125)     <i>Note that we might share which project ideas have strong applications in
126)     order to spread applicants out (it's bad for everyone for several strong
127)     applicants to be for the exact same project).</i><br /><br /></li>

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

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

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

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

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

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

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

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

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

189)     </p>
190)     
191)     <p>

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

195)     </p>

196)     

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

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

199)     
200)     <p>
201)     Below are examples of some GSoC applications from previous years we liked.
202)     The best applications tend to go through several iterations so you're
203)     highly encouraged to send drafts early.
204)     </p>
205)     
206)     <ul>

207)       <li><h4><a href="https://ahmia.fi/gsoc/">Ahmia.fi - Search Engine for Hidden Services</a> by Juha Nurmi</h4></li>

208)       <li><h4><a href="http://ilv.github.io/gettor_proposal.html">Revamp GetTor</a> by Israel Leiva</h4></li>

209)       <li><h4><a href="https://sites.google.com/site/sreenathadev/gsoc-2014-weather-rewrite">Weather Rewrite</a> by Sreenatha Bhatlapenumarthi</h4></li>

210)       <li><h4><a href="http://kostas.mkj.lt/gsoc2014/gsoc2014.html">BridgeDB Distributor</a> by Kostas Jakeliunas</h4></li>

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

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

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

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

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

218)       <li><h4><a href="https://www.atagar.com/misc/gsocBlog09/">Website Pootle Translation</a> by Damian Johnson</h4></li>

219)     </ul>
220)