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 2010" 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 2011</h2>

13)     <hr>

14)     
15)     <p>

16)     In the last four 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)     and <a href="<blog>tor-google-summer-code-2010">2010</a>.

24)     In total we had 21 students as full-time developers for the summers of 2007 to
25)     2010. Now we are applying to <a
26)     href="https://socghop.appspot.com/gsoc/program/home/google/gsoc2011">Google
27)     Summer of Code 2011</a>.

28)     </p>
29)     
30)     <p>
31)     The <a

32)     href="https://socghop.appspot.com/document/show/gsoc_program/google/gsoc2011/timeline">timeline</a>
33)     for GSoC 2011 is available.

34)     </p>
35)     
36)     <p>
37)     You must be self-motivated and able to work independently. We have
38)     a thriving community of interested developers on the IRC channel and
39)     mailing lists, and we're eager to work with you, brainstorm about design,
40)     and so on, but you need to be able to manage your own time, and you
41)     need to already be somewhat familiar with how free software development on the
42)     Internet works.
43)     </p>
44)     
45)     <p>
46)     Working on Tor is rewarding because:
47)     </p>
48)     
49)     <ul>
50)     <li>You can work your own hours in your own locations. As long as you
51)     get the job done, we don't care about the process.</li>
52)     <li>We only write free (open source) software. The tools you make won't
53)     be locked down or rot on a shelf.</li>
54)     <li>You will work with a world-class team of anonymity experts and
55)     developers on what is already the largest and most active strong anonymity
56)     network ever.</li>
57)     <li>The work you do could contribute to academic publications &mdash;
58)     Tor development raises many open questions and interesting problems
59)     in the field of <a href="http://freehaven.net/anonbib/">anonymity
60)     systems</a>.</li>
61)     </ul>
62)     
63)     <a id="GettingInvolved"></a>
64)     <h2><a class="anchor" href="#GettingInvolved">How To Get Involved</a></h2>
65)     
66)     <p>
67)     The best way to get involved is to come listen on IRC (both "#tor" and
68)     "#tor-dev"), read our docs and other webpages, try out the various tools
69)     that are related to the projects that interest you, and ask questions
70)     as they come to you: <a href="<page docs/documentation>#UpToSpeed">Getting
71)     up to speed</a>.
72)     </p>
73)     
74)     <p>
75)     In addition to getting some more development work
76)     done on Tor and related applications, Google and Tor are most interested
77)     in getting students involved in Tor development in a way that keeps them
78)     involved after the summer too. That means we will give priority to students
79)     who have demonstrated continued interest and responsiveness. We will require
80)     students to write public status report updates for our community, either by
81)     blogging or sending mail to our mailing list. We want to ensure that the
82)     community and the student can both benefit from each other.
83)     </p>
84)     
85)     <p>
86)     When it comes time for us to choose projects, our impression of how well
87)     you'll fit into our community &mdash; and how good you are at taking
88)     the initiative to do things &mdash; will be at least as important as
89)     the actual project you'll be working on.
90)     </p>
91)     
92)     <a id="Ideas"></a>
93)     <h2><a class="anchor" href="#Ideas">Ideas List</a></h2>
94)     
95)     <p>

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

99)     </p>
100)     
101)     <p>
102)     The best kind of ideas are A) ones that we know we need done real soon
103)     now (you can get a sense of urgency from the priority on the wishlist,
104)     and from talking to the potential mentors), and B) ones where it's
105)     clear what needs to be done, at least for the first few steps. Lots of
106)     students try to bite off open-ended research topics; but if you're going
107)     to be spending the first half of your summer figuring out what exactly
108)     you should code, and there's a chance that the conclusion will be "oh,
109)     that isn't actually a good idea to build", then your proposal will make
110)     us very nervous. Try to figure out how much you can actually fit in a
111)     summer, break the work down into manageable pieces, and most importantly,
112)     figure out how to make sure your incremental milestones are actually
113)     useful &mdash; if you don't finish everything in your plan, we want to
114)     know that you'll still have produced something useful.
115)     </p>
116)     
117)     <a id="Template"></a>
118)     <h2><a class="anchor" href="#Template">Application Template</a></h2>
119)     
120)     <p>
121)     Please use the following template for your application, to make sure you
122)     provide enough information for us to evaluate you and your proposal.
123)     </p>
124)     
125)     <ol>
126)     
127)     <li>What project would you like to work on? Use our ideas lists as a starting
128)     point or make up your own idea. Your proposal should include high-level
129)     descriptions of what you're going to do, with more details about the
130)     parts you expect to be tricky. Your proposal should also try to break
131)     down the project into tasks of a fairly fine granularity, and convince
132)     us you have a plan for finishing it.</li>
133)     
134)     <li>Point us to a code sample: something good and clean to demonstrate
135)     that you know what you're doing, ideally from an existing project.</li>
136)     
137)     <li>Why do you want to work with The Tor Project / EFF in
138)     particular?</li>
139)     
140)     <li>Tell us about your experiences in free software development
141)     environments. We especially want to hear examples of how you have
142)     collaborated with others rather than just working on a project by
143)     yourself.</li>
144)     
145)     <li>Will you be working full-time on the project for the summer, or will
146)     you have other commitments too (a second job, classes, etc)? If you won't
147)     be available full-time, please explain, and list timing if you know them
148)     for other major deadlines (e.g. exams). Having other activities isn't
149)     a deal-breaker, but we don't want to be surprised.</li>
150)     
151)     <li>Will your project need more work and/or maintenance after the summer
152)     ends? What are the chances you will stick around and help out with that
153)     and other related projects?</li>
154)     
155)     <li>What is your ideal approach to keeping everybody informed of your
156)     progress, problems, and questions over the course of the project? Said
157)     another way, how much of a "manager" will you need your mentor to be?</li>
158)     
159)     <li>What school are you attending? What year are you, and what's your
160)     major/degree/focus? If you're part of a research group, which one?</li>
161)     
162)     <li>How can we contact you to ask you further questions? Google doesn't
163)     share your contact details with us automatically, so you should include
164)     that in your application. In addition, what's your IRC nickname?
165)     Interacting with us on IRC will help us get to know you, and help you
166)     get to know our community.</li>
167)     
168)     <li>Is there anything else we should know that will make us like your
169)     project more?</li>
170)     
171)     </ol>
172)     
173)     <p>

174)     We will pick out mentors for this year — most of the

175)     people on the <a href="<page about/corepeople>">core Tor development team</a>

176)     plus a few people from <a href="http://www.eff.org/about/staff">EFF's staff</a>
177)     &mdash; so we should be able to accommodate a wide variety of projects,
178)     ranging from work on Tor itself to work on supporting or peripheral
179)     projects. We can figure out which mentor is appropriate while we're
180)     discussing the project you have in mind. We plan to assign a primary
181)     mentor to each student, along with one or two assistant mentors to help
182)     answer questions and help you integrate with the broader Tor community.
183)     </p>
184)     
185)     <p>
186)     If you're interested, you can either contact the <a href="<page
187)     about/contact>">tor-assistants list</a> with a brief summary of your proposal
188)     and we'll give you feedback, or just jump right in and post your ideas

189)     and goals to the <a href="<page docs/documentation>#MailingLists">tor-talk