281
edits
Line 135: | Line 135: | ||
=== What steps will you take to encourage students to interact with your project's community before and during the program? === | === What steps will you take to encourage students to interact with your project's community before and during the program? === | ||
We will encourage them to join us on our IRC channel and mailing list. We will set clear expectations on the minimum frequency of email | We will encourage them to join us on our IRC channel and mailing list. We will set clear expectations on the minimum frequency of email progress updates of every two to three days. Longer updates should be done on a blog and aggregated at http://planet.octave.org | ||
progress updates of every two to three days. Longer updates should be done on a | |||
blog and aggregated at http://planet.octave.org | |||
Everything should be completely open. Almost all interactions with the student should | 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. | ||
be public, e.g. contacting the mentor should happen in the public IRC | |||
channel or | |||
Our annual conference, OctConf, will be held in the summer. Students will be invited to attend and present on their work. | Our annual conference, OctConf, will be held in the summer. Students will be invited to attend and present on their work. Previous OctConfs had several such student presenters. | ||
For some projects, there may be way to bridge | For some projects, there may be way to bridge directly with industry interests. We hope that we can increase student participation this way. | ||
=== What will you do to encourage that your accepted students stick with the project after Google Summer of Code concludes? === | === What will you do to encourage that your accepted students stick with the project after Google Summer of Code concludes? === |
edits