GSoC 2016 application: Difference between revisions

Jump to navigation Jump to search
Line 21: Line 21:


=== 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 by the student will be a condition for acceptance. In this way, we hope to select students who are familiar with the Octave codebase and able to start with their project quickly.
Once a student is selected, the mentor will work with them to come up with a detailed summer timeline, including clear expectations for progress by the midterm and final evaluation periods.
Students will be urged to participate on our IRC channel and mailing list. We will set clear expectations on the minimum frequency of email progress updates, typically every two to three days. Students will also set up a blog for longer, weekly, updates which is aggregated at http://planet.octave.org
Everything should be completely open. Almost all interactions with the student should be public, e.g. contacting the mentor should happen in the public IRC channel or copy the maintainers mailing list.
Our annual conference, OctConf, is usually held in the summer. Students will be invited to attend and present on their work. Previous OctConfs had several such student presenters.
=== How will you get your students involved in your community during GSoC? ===
=== How will you get your students involved in your community during GSoC? ===
=== How will you keep students involved with your community after GSoC? ===
=== How will you keep students involved with your community after GSoC? ===
281

edits

Navigation menu