281
edits
(copy from last year) |
|||
Line 23: | Line 23: | ||
=== How will you help your students stay on schedule to complete their projects? === | === How will you help your students stay on schedule to complete their projects? === | ||
Previous contributions to Octave | Previous contributions to Octave are a condition for acceptance. In this way, we hope to select students who are familiar with the codebase and able to start their project quickly. | ||
A tentative project timeline is required as part of the application, and is checked by mentors for realism as part of the applicant evaluation process. Once a student is selected, the mentor will work with them to come up with a more detailed summer timeline, including clear expectations for progress by the midterm and final evaluation periods. | A tentative project timeline is required as part of the application, and is checked by mentors for realism as part of the applicant evaluation process. Once a student is selected, the mentor will work with them to come up with a more detailed summer timeline, including clear expectations for progress by the midterm and final evaluation periods. | ||
During the summer, mentors will check | During the summer, mentors will check with students at least weekly to make sure they are staying on schedule and help with any obstacles that might arise. Students are also expected to regularly update their mentors and the Octave maintainers community on their progress via e-mails and blog posts. | ||
Overall, | Overall, the vast majority of previous SoC students have finished successfully, making substantive contributions to Octave that have been integrated into our codebase. | ||
=== How will you get your students involved in your community during GSoC? === | === How will you get your students involved in your community during GSoC? === |
edits