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"

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

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

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

13) In the last two 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> and <a href="http://code.google.com/soc/2008/eff/about.html">2008</a>.
18) In total we had eleven students as full-time developers for the summers of 2007
19) and 2008.

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

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

25) and we plan to apply.

26) This page contains some information for interested students.

27) </p>
28) 

29) <!--<p>

30) The <a

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

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

34) is <b>April 20, 2009</b> at 5pm Pacific time.
35) </p>-->

36) 
37) <p>
38) You must be self-motivated and able to work independently. We have
39) a thriving community of interested developers on the IRC channel and
40) mailing lists, and we're eager to work with you, brainstorm about design,
41) and so on, but you need to be able to manage your own time, and you

42) need to already be somewhat familiar with how free software development on the

43) Internet works.
44) </p>
45) 
46) <p>

47) In addition to getting some more development work

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

137) We have picked out twelve mentors for this year — most of the

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

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