1,190
edits
Difference between revisions of "Summer of Code/Application/2016"
Summer of Code/Application/2016 (view source)
Revision as of 21:48, 17 February 2016
, 21:48, 17 February 2016→How will you get your students involved in your community during GSoC?
Strangerke (talk | contribs) |
|||
| Line 77: | Line 77: | ||
=== How will you get your students involved in your community during GSoC? === | === How will you get your students involved in your community during GSoC? === | ||
Before and during GSoC, we'll consider students as special developers, but developers nonetheless. | |||
They will therefore have equivalent rights, privileges and duties. For instance, | |||
- We first ask our students to write introductory letters to our development list and their blog so everyone will have a sensible background about them, their skills and their assigned task. | |||
- We created several documentation in order to help the students to familiarize with the projects, particularly 'Developer Central' and our wiki. | |||
- They are encouraged to take part in discussions, whatever the means these discussions occur. | |||
- They will be able to get support from the team literally 24/7 on our IRC channels, as our developers are scattered all over the globe. They are voiced (+v) so that everybody knows who they are. | |||
- We noticed during our previous participations that merging the student code early make them feel more involved, so we plan to do it again this year. | |||
=== How will you keep students involved with your community after GSoC? === | === How will you keep students involved with your community after GSoC? === | ||
<span style="color:red">In our last two participations, we decided to require the GSoC student code to be merged into our Master tree much earlier in the process, if possible. Our past experience was telling us it should be very motivating for students to directly interact with our main repository and that this could potentially make some of them stay after the end of GSoC: it seems we were right as several former students kept contributing more than a year after our last participation. This is obviously for us a very positive sign and we plan to proceed in the same way this year again.</span> | <span style="color:red">In our last two participations, we decided to require the GSoC student code to be merged into our Master tree much earlier in the process, if possible. Our past experience was telling us it should be very motivating for students to directly interact with our main repository and that this could potentially make some of them stay after the end of GSoC: it seems we were right as several former students kept contributing more than a year after our last participation. This is obviously for us a very positive sign and we plan to proceed in the same way this year again.</span> | ||