Changes between Version 13 and Version 14 of org/TorSoP


Ignore:
Timestamp:
Apr 3, 2015, 4:59:16 PM (4 years ago)
Author:
ailanthus
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • org/TorSoP

    v13 v14  
    1616
    1717=== Payment flow ===
    18 
    1918Tor will provide a total stipend of USD $5,500 per accepted student developer.
    2019
     
    2322 * Students who receive passing final evaluations and who have submitted their final program evaluations will receive a USD $2,500 stipend shortly after the final evaluation deadline.
    2423
    25 
    26 
    2724=== TIMELINE: ===
    2825 *
    29  * Announce, outreach (April 3) 
     26 * Announce, outreach (April 3)
    3027 * Accept applications (April 2-10)
    3128 * Accept more applications; communicate with student applicants  (April 10-17)
     
    3835 * Pencils down date (Aug 25)
    3936 * End-of-term evaluation (Sep 1)
    40 
    4137
    4238== WHO ==
     
    5753In addition to getting some more development work     done on Tor and related applications, we are most interested     in getting students involved in Tor development in a way that keeps them     involved after the summer too. That means we will give priority to students     who have demonstrated continued interest and responsiveness. We will require     students to write public status report updates for our community, either by     blogging or sending mail to our mailing list. We want to ensure that the     community and the student can both benefit from each other.
    5854
    59 When it comes time for us to choose projects, our impression of how well     you'll fit into our community — and how well you are at taking     the initiative to do things — will be at least as important as    the actual project you'll be working on.
     55When it comes time for us to choose projects, our impression of how well you'll fit into our community (friendliness, good at working in teams, etc.) — and how well you are at taking the initiative to do things — will be at least as important as the actual project you'll be working on.
    6056
    61 == How ==
    6257=== Ideas ===
    63 To start with, please see Tor's '''[https://www.torproject.org/getinvolved/volunteer.html.en#Projects projects page]''' and its following     ideas.
     58To start with, please see Tor's '''[https://www.torproject.org/getinvolved/volunteer.html.en#Projects projects page]''' and its following ideas.
    6459
    65 The best kind of ideas are well defined and easily broken into subtasks.     A lot of students try to bite off open-ended development and research     topics. But if you're going to spend the first half of your summer figuring     out what exactly you should code, there's a chance that the conclusion will     be "oh, that isn't actually feasible to build after all" and your proposal    will make us very nervous.
     60The best kind of ideas are well defined and easily broken into subtasks. Students sometimes try to bite off open-ended development and research topics. But if you're going to spend the first half of your summer figuring out what exactly you should code, there's a chance that the conclusion will be "oh, that isn't actually feasible to build after all" and your proposal will make us very nervous.
    6661
    67 Try to figure out how much you can actually fit in a summer, break the work     down into manageable pieces, and most importantly, figure out how to make     sure your incremental milestones are actually useful — if you don't     finish everything in your plan, we want to know that you'll still have     produced something useful.
    68 
     62Try to figure out how much you can actually fit in a summer, break the work down into manageable pieces, and most importantly, figure out how to make sure your incremental milestones are actually useful — if you don't finish everything in your plan, we want to know that you'll still have produced something useful.
    6963
    7064=== Application Template ===
    71 Please use the following template for your application, to make sure you provide enough information for us to evaluate you and your proposal.
     65Please use the following template for your application to make sure you provide enough information for us to evaluate you and your proposal.
    7266
    7367 * 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.
     
    7771 * Point us to a code sample: something good and clean to demonstrate that you know what you're doing, ideally from an existing project.
    7872 * 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.
    79  * 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.
     73 * 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 it for other major deadlines (e.g. exams). Having other activities isn't a deal-breaker, but we don't want to be surprised.
    8074 * 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?
    8175 * 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?
    8276 * 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?
    8377 * 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.
    84  * 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?
     78 * Are you applying to other projects and, if so, what would be your preference if you're accepted to both? Having a stated preference helps with the de-duplication process and will not affect whether or not we accept your application. *Is there anything else that we should know that will make us like your project more?
    8579
    8680We 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.
    8781
    88 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.
     82All 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 who is only known by your mentor.
    8983
    9084If 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.