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 2009" CHARSET="UTF-8"

6) 
7) <div class="main-column">
8) 

9) <h2>Tor: Google Summer of Code 2010</h2>

10) <hr />
11) 
12) <p>

13) In the last three years, The Tor Project in collaboration with <a

14) href="https://www.eff.org/">The Electronic Frontier Foundation</a>

15) successfully took part in
16) <a href="http://code.google.com/soc/2007/eff/about.html">Google Summer of Code

17) 2007</a>, <a href="http://code.google.com/soc/2008/eff/about.html">2008</a>,
18) and <a href="http://socghop.appspot.com/gsoc/org/home/google/gsoc2009/eff">2009</a>.
19) In total we had 17 students as full-time developers for the summers of 2007 to
20) 2009.

21) </p>
22) 
23) <p>
24) Google has announced that there will also be a <a

25) href="http://socghop.appspot.com/">Google Summer of Code 2010</a>,

26) and we plan to apply.

27) This page contains some information for interested students.

28) </p>
29) 

30) <!--<p>

31) The <a

32) href="http://socghop.appspot.com/document/show/program/google/gsoc2009/faqs#timeline">deadline</a>

33) for your <a
34) href="http://groups.google.com/group/google-summer-of-code-announce/web/guide-to-the-gsoc-web-app-for-student-applicants">application</a>

35) is <b>April 20, 2009</b> at 5pm Pacific time.
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) In addition to getting some more development work

49) done on Tor and related applications, Google and Tor are most interested

50) in getting students involved in Tor development in a way that keeps them

51) involved after the summer too. As such, we will give priority to students

52) who have demonstrated continued interest and responsiveness. We will require
53) students to write public status report updates for our community, either by
54) blogging or sending mail to our mailing list. We want to ensure that the
55) community and the student can both benefit from each other.

56) </p>
57) 
58) <p>
59) Working on Tor is rewarding because:
60) </p>
61) 
62) <ul>
63) <li>You can work your own hours in your own locations. As long as you
64) get the job done, we don't care about the process.</li>
65) <li>We only write free (open source) software. The tools you make won't
66) be locked down or rot on a shelf.</li>
67) <li>You will work with a world-class team of anonymity experts and
68) developers on what is already the largest and most active strong anonymity
69) network ever.</li>

70) <li>The work you do could contribute to academic publications &mdash;

71) Tor development raises many open questions and interesting problems
72) in the field of <a href="http://freehaven.net/anonbib/">anonymity
73) systems</a>.</li>
74) </ul>
75) 

76) <a id="Ideas"></a>
77) <h2><a class="anchor" href="#Ideas">Ideas List</a></h2>
78) 
79) <p>
80) This year, we have two ideas lists: one for projects to
81) <a href="<page volunteer>#Projects">help develop Tor</a>,
82) and one for projects to help develop

83) <a href="http://switzerland.wiki.sourceforge.net/Projects">EFF's Switzerland

84) tool</a>.
85) </p>
86) 

87) <a id="Template"></a>

88) <h2><a class="anchor" href="#Template">Application Template</a></h2>

89) 
90) <p>
91) Please use the following template for your application, to make sure you
92) provide enough information for us to evaluate you and your proposal.
93) </p>
94) 
95) <ol>
96) 

97) <li>What project would you like to work on? Use our ideas lists as starting
98) point or make up your own idea. Your proposal should include high-level

99) descriptions of what you're going to do, with more details about the
100) parts you expect to be tricky. Your proposal should also try to break
101) down the project into tasks of a fairly fine granularity, and convince
102) us you have a plan for finishing it.</li>
103) 
104) <li>Point us to a code sample: something good and clean to demonstrate
105) that you know what you're doing, ideally from an existing project.</li>
106) 

107) <li>Why do you want to work with The Tor Project / Switzerland in
108) particular?</li>

109) 
110) <li>Tell us about your experiences in free software development
111) environments. We especially want to hear examples of how you have
112) collaborated with others rather than just working on a project by
113) yourself.</li>
114) 
115) <li>Will you be working full-time on the project for the summer, or will
116) you have other commitments too (a second job, classes, etc)? If you won't
117) be available full-time, please explain, and list timing if you know them
118) for other major deadlines (e.g. exams). Having other activities isn't

119) a deal-breaker, but we don't want to be surprised.</li>

120) 
121) <li>Will your project need more work and/or maintenance after the summer
122) ends? What are the chances you will stick around and help out with that
123) and other related projects?</li>
124) 
125) <li>What is your ideal approach to keeping everybody informed of your
126) progress, problems, and questions over the course of the project? Said
127) another way, how much of a "manager" will you need your mentor to be?</li>
128) 
129) <li>What school are you attending? What year are you, and what's your
130) major/degree/focus? If you're part of a research group, which one?</li>
131) 
132) <li>Is there anything else we should know that will make us like your
133) project more?</li>
134) 
135) </ol>
136) 
137) <p>

138) We have picked out 10+ mentors for this year — most of the

139) people on the <a href="<page people>#Core">core Tor development team</a>

140) plus a few people from <a href="http://www.eff.org/about/staff">EFF's staff</a>

141) — so we should be able to accommodate a wide variety of projects,
142) ranging from work on Tor itself to work on supporting or peripheral
143) projects. We can figure out which mentor is appropriate while we're

144) discussing the project you have in mind. We plan to assign a primary