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)     <b>If you're interested in participating in Google Summer of Code then
17)     please keep in mind that Google has not yet announced the participating
18)     organisations, and Tor might not be selected. See the <a
19)     href="https://www.google-melange.com/document/show/gsoc_program/google/gsoc2013/help_page#2._What_is_the_program_timeline">timeline</a>
20)     for more information.</b>
21)     </p>
22) 

23)     <p>

24)     The Tor Project, in collaboration with <a href="https://www.eff.org/">The
25)     Electronic Frontier Foundation</a>, have taken part in Google Summer of Code
26)     for 2007 through 2012, mentoring the total of 33 students. Google has
27)     announced that the program's taking place again this year, see <a
28)     href="https://www.google-melange.com/gsoc/homepage/google/gsoc2013">their
29)     site</a> for a timeline!
30)     
31)     <!--
32)     We have been accepted as a mentoring organization for <a

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

34)     Summer of Code 2012</a>!

35)     -->

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

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

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

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

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

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

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

100)     ideas.

101)     </p>
102)     
103)     <p>

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

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

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

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

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

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

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

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

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

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

210)     </p>
211)     
212)     <p>

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

216)     </p>

217)     

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

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

220)     
221)     <p>
222)     Below are examples of some GSoC applications from previous years we liked.
223)     The best applications tend to go through several iterations so you're
224)     highly encouraged to send drafts early.
225)     </p>
226)     
227)     <ul>

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

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

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

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

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

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

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