Changes between Version 238 and Version 239 of doc/gsoc


Ignore:
Timestamp:
Feb 5, 2019, 11:41:40 AM (4 months ago)
Author:
pili
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/gsoc

    v238 v239  
    680680=== Why does your org want to participate in Google Summer of Code? ===
    681681
    682 Tor has many open development tasks that are well-suited to summer projects, and also many students who are excited to work on them. GSoC can help these students work on important new free software work while also paying rent. In recent years The Tor Project has continued to grow, offering interesting new opportunities for summer projects. We expect to attract smart students as we did in prior years.
     682We are excited to have the opportunity to once again participate in Google Summer of Code for 2019. We have been involved with GSoC since 2007 and have seen the benefits that participating in this program can provide, both for us as a hosting organization and the students themselves.
     683
     684Tor has many open development tasks that are well-suited to summer projects, and also many students who are excited to work on them. As a non-profit organisation we are used to engaging with volunteers for these sorts of standalone projects which then become part of the larger Tor ecosystem. GSoC can help these students work on important new free software work while also paying rent.
     685
     686In recent years, The Tor Project has continued to grow, offering interesting new opportunities for summer projects. We expect to attract as many smart students as we have done in previous years.
    683687
    684688=== How will you keep mentors engaged with their students? ===
    685689
    686 Each individual has been leading his or her own projects related to Tor, and they are the most suited for mentoring students working on those modules.
    687 
    688 Our plan is to assign two mentors per student to provide redundancy in case anything goes wrong. In general, our chosen mentors are Tor staff or have been working on Tor for multiple years now (and for many of them, it's their full or part time job), so they're unlikely to just disappear.
    689 
    690 Note that five of our mentors and two of our admins are former GSoC students.
     690Each project that we are putting forward this year has been proposed by the mentor as something that they are invested in succeeding. Each of these mentors have been leading his or her own projects related to Tor, and they are the most suited for mentoring students working on those modules. Some of our mentors are actually former GSoC students!
     691
     692We have a structure in place, from our many years of previous participation in GSoC, whereby mentors and mentees check in regularly to ensure that both parties are engaged with the project. This year we will also require mentors to check in regulary with the organisation administrator to share progress and ensure that, if there are any issues, these can be solved promptly.
     693
     694We additionally plan to assign two mentors per student to provide redundancy in case anything goes wrong. In general, our chosen mentors are Tor staff or have been working on Tor for multiple years now (and for many of them, it's their full or part time job).
    691695
    692696=== How will you help your students stay on schedule to complete their projects? ===
    693697
    694 We hope to minimize the chances of disappearing students by picking students who have already demonstrated commitment and/or interest to our community. Further, having multiple mentors per student can hopefully give us a better shot at keeping the students' interest.
    695 
    696 We want to learn about disappearing students as early as possible. Therefore, we are planning to require our students to write bi-weekly status updates to keep us informed of their progress.
     698We understand that in order for students to stay on schedule they need to be engaged and invested in their projects, we hope to capitalise on this by picking students who have already demonstrated commitment and/or interest to our community. Further, having multiple mentors per student can hopefully give us a better shot at keeping the students' on track.
     699
     700As part of the student application process, we will ask students to break down their project into manageable steps, ideally with timelines. This is a pre-requisite first step before any work is started. We will use this timeline to track progress throughout the project.
     701
     702We will ensure that students have a regular check in time with their mentors in order to check status and share any blockers. We will encourage students to be open about any issues that they may encounter so that a solution may be found.
     703
     704We will also require our students to write bi-weekly status updates with the community to keep us informed of their progress.
    697705
    698706=== How will you get your students involved in your community during GSoC? ===
    699707
    700 Tor already has an active community on IRC and the mailing lists, and there's also an active research community of scientists trying to improve security of systems like Tor. We can draw on this community---the current active Tor volunteers as well as the graduate and undergraduate students at the research institutions. Further, we require our students to introduce themselves to the community, and to make periodic status reports available in a public format.
     708We encourage GSoC students to start off by interacting with us on IRC to help us get to know them and them to get to know our community.
     709
     710Tor already has an active community on IRC and the mailing lists, and there's also an active research community of scientists trying to improve security of systems like Tor. We can draw on this community---the current active Tor volunteers as well as the graduate and undergraduate students at the research institutions to engage with our GSoC students.
     711
     712Further, we require our students to introduce themselves to the community, and to make periodic status reports available in a public format.
    701713
    702714=== How will you keep students involved with your community after GSoC? ===
    703715
    704 In past years the students that stuck around afterward were the ones most invested in their project and our development community. We plan to encourage them to actively participate in discussions and connect with the community to improve their chances of staying on after the summer has ended.
     716We have quite a good track record of past GSoC mentees staying on as volunteers and contributing code, some have even ended up becoming core contributors to Tor.
     717
     718From past experience, the students that were most invested in their project and our development community were the most likely to stick around after the GSoC program ended. Our plan is to encourage them to actively participate in discussions and connect with the community throughout the course of GSoC in order to improve their chances of staying on after the summer has ended.
    705719
    706720=== Has your org been accepted as a mentor org in Google Summer of Code before? ===
     
    710724=== Years ===
    711725
    712 2012, 2013, 2014, 2016 and 2017
     7262007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2016 and 2017
    713727
    714728=== For each year your organization has participated, provide the counts of successful and total students. (e.g. 2016: 3/4) ===