1,190
edits
Strangerke (talk | contribs) |
Strangerke (talk | contribs) (→What steps will you take to encourage students to interact with your project's community before, during and after the program?: Add a description of the new merge process) |
||
Line 138: | Line 138: | ||
Not only the mentors, but also the entire development team, are encouraged to communicate with the students. The students are marked with a special flag on our IRC channel, so everyone knows who they are. And we require the students to write introductory letters to our development list, so everyone will have an impression about them, their skills and their assigned task (of course). | Not only the mentors, but also the entire development team, are encouraged to communicate with the students. The students are marked with a special flag on our IRC channel, so everyone knows who they are. And we require the students to write introductory letters to our development list, so everyone will have an impression about them, their skills and their assigned task (of course). | ||
<span style="color:red"> requires proofreading: <p> | |||
This year, we also decided to merge in our Master tree the GSoC student code much earlier in the process. Based on our own experience, on discussion with returning students and on discussions with other projects, it should be very motivating for students to directly interact with our main repository and could potentially make some of them stay after the end of GSoC. We'll obviously have to make an assessment afterwards of the benefits and disadvantages of that new process. | |||
</p></span> | |||
=== Are you a new organization who has a Googler or other organization to vouch for you? If so, please list their name(s) here. === | === Are you a new organization who has a Googler or other organization to vouch for you? If so, please list their name(s) here. === |