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 2012" 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. Google has
19)     announced that the program's taking place again this year, see <a
20)     href="https://www.google-melange.com/gsoc/homepage/google/gsoc2013">their
21)     site</a> for a timeline!
22)     
23)     <!--
24)     We have been accepted as a mentoring organization for <a

25)     href="https://socghop.appspot.com/gsoc/program/home/google/gsoc2012">Google

26)     Summer of Code 2012</a>!

27)     -->

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

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

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

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

82)     the initiative to do things — will be at least as important as
83)     the actual project you'll be working on.
84)     </p>
85)     
86)     <a id="Ideas"></a>
87)     <h2><a class="anchor" href="#Ideas">Ideas List</a></h2>
88)     
89)     <p>

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

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

92)     ideas.

93)     </p>
94)     
95)     <p>

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

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

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

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

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

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

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

175)     We mostly pick mentors from the <a href="<page about/corepeople>">core Tor
176)     development team</a> and <a href="http://www.eff.org/about/staff">EFF's
177)     staff</a> so we should be able to accommodate a wide variety of projects.
178)     These can range from work on Tor itself to work on supporting or peripheral
179)     projects.
180)     </p>
181)     
182)     <p>
183)     All selected projects are assigned both a primary and assistant mentor to
184)     answer your questions and help you integrate with the broader Tor
185)     community. Though your mentors are a primary point of contact please use
186)     our public spaces (the <a href="<page about/contact>#irc">#tor-dev irc
187)     channel</a> and <a href="<page docs/documentation>#MailingLists">tor-dev@
188)     email list</a>) to discuss your project. We want you to become a part of
189)     the community by the end of the summer, not a stranger that's only known by
190)     your mentor.

191)     </p>
192)     
193)     <p>
194)     If you're interested, you can either contact the <a href="<page

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

202)     </p>
203)     
204)     <p>

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

208)     </p>

209)     

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

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

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

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

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

222)       <li><h4><a href="http://dustri.org/pub/tails_server.pdf">Tails Server</a> by Julien Voisin</h4></li>

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

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

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

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