Version 2 (modified by isabela, 4 years ago) (diff)


Tor Summer of Privacy


The Tor Project, in collaboration with The Electronic Frontier Foundation, have taken part in Google Summer of Code for 2007 through 2014, mentoring the total of 53 students. But this year we were not accepted on GSoC 2015, the program was trimmed back and room was needed for new organizations and we think that is important too.

But we decided to not drop the idea of supporting students who wants to help support Open and Free software that

This page is still under construction. You can refer to the following pad for brainstorming and meeting notes where the content of this page has been discussed:


[Explain what we are doing, why we are doing it]

[Area of focus - what type of help we are looking for? Damian started a list]


TIMELINE (Tentative!):

  • Reach preliminary decisions, go over project list. (April 1)
  • Announce, outreach (April 2?) (
  • Accept applications (April 2-10)
  • Accept more applications; communicate with student applicants (April 10-17)
  • Final interviews (April 17-19)
  • Reach decisions about which student (April 20)
  • Community bonding period begins (April 21)
  • [End of spring term] (Mid May)
  • Students begin officially working on projects (May 25)
  • Midterm evaluation (3 July)
  • Pencils down date (Aug 25)
  • End-of-term evaluation (Sep 1)

Application Template

Please use the following template for your application, to make sure you provide enough information for us to evaluate you and your proposal.

  • What project would you like to work on? Use our ideas lists as a starting point or make up your own idea. Your proposal should include high-level descriptions of what you're going to do, with more details about the parts you expect to be tricky. Your proposal should also try to break down the project into tasks of a fairly fine granularity, and convince us you have a plan for finishing it. A timeline for what you will be doing throughout the summer is highly recommended.

Note that we might share which project ideas have strong applications in order to spread applicants out (it's bad for everyone for several strong applicants to be for the exact same project).

  • Point us to a code sample: something good and clean to demonstrate that you know what you're doing, ideally from an existing project.
  • Why do you want to work with The Tor Project in particular? Tell us about your experiences in free software development environments. We especially want to hear examples of how you have collaborated with others rather than just working on a project by yourself.
  • Will you be working full-time on the project for the summer, or will you have other commitments too (a second job, classes, etc)? If you won't be available full-time, please explain, and list timing if you know them for other major deadlines (e.g. exams). Having other activities isn't a deal-breaker, but we don't want to be surprised.
  • Will your project need more work and/or maintenance after the summer ends? What are the chances you will stick around and help out with that and other related projects?
  • What is your ideal approach to keeping everybody informed of your progress, problems, and questions over the course of the project? Said another way, how much of a "manager" will you need your mentor to be?
  • What school are you attending? What year are you, and what's your major/degree/focus? If you're part of a research group, which one?
  • How can we contact you to ask you further questions? Google doesn't share your contact details with us automatically, so you should include that in your application. In addition, what's your IRC nickname? Interacting with us on IRC will help us get to know you, and help you get to know our community.
  • Are you applying to other projects for GSoC and, if so, what would be your preference if you're accepted to both? Having a stated preference helps with the deduplication process and will not impact if we accept your application or not. *Is there anything else that we should know that will make us like your project more?

We mostly pick mentors from the core Tor development team so we should be able to accommodate a wide variety of projects. These can range from work on Tor itself to work on supporting or peripheral projects.

All selected projects are assigned both a primary and assistant mentor to answer your questions and help you integrate with the broader Tor community. Though your mentors are a primary point of contact please use our public spaces (the #tor-dev irc channel and tor-dev@ email list) to discuss your project. We want you to become a part of the community by the end of the summer, not a stranger that's only known by your mentor.

If you're interested, you can either contact the tor-assistants list (a private list) with a brief summary of your proposal and we'll give you feedback, or just jump right in and post your ideas and goals to the tor-dev mailing list (which is open). Make sure to be responsive during the application selection period; if we like your application but you never answer our mails asking for more information, that's not a good sign.

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

If you want to look at examples of applications, you can check our old GSoC page.


Must be a student enrolled in a university or college; must be old enough (18yrs up) we can give them money (need to get this list); must not be in some country that we can't legally send them any money in; Rewards How much each student will get Rewards == How much each student will get