252
edits
GSoC 2013 application: Difference between revisions
Jump to navigation
Jump to search
m
Protected "GSoC 2013 application" ([edit=sysop] (indefinite) [move=sysop] (indefinite))
m (Protected "GSoC 2013 application" ([edit=sysop] (indefinite) [move=sysop] (indefinite))) |
|||
| (6 intermediate revisions by the same user not shown) | |||
| Line 82: | Line 82: | ||
=== What criteria did you use to select your mentors for this year's program? Please be as specific as possible. === | === What criteria did you use to select your mentors for this year's program? Please be as specific as possible. === | ||
Each project includes at least one core Octave developer as mentor. These | |||
are | are proven, veteran members of the project, active in its development, and familiar | ||
with the code base. | with the code base. | ||
GNU Octave is a project with applications in very diverse domains so each | |||
project also includes mentors with expertise in the related field. All of these | project also includes mentors with expertise in the related field. All of these | ||
have previously contributed with code, have commit access to either Octave or | have previously contributed with code, have commit access to either Octave or | ||
| Line 95: | Line 95: | ||
First, make all reasonable efforts to accommodate the student and make them feel | First, make all reasonable efforts to accommodate the student and make them feel | ||
welcome. | welcome. We will engage the students frequenty by email and IRC, provide prompt response to student queries, | ||
periodic status reports from mentors about the | and expect periodic status reports from mentors about the project status. We will also | ||
encourage the student to participate in the public mailing list and IRC channel, | encourage the student to participate in the public mailing list and IRC channel, | ||
with or without mentor. Their progress should be regularly applied to our source | with or without the mentor. Their progress should be regularly applied to our source | ||
tree, if necessary, in a feature branch. All of these have shown to be effective | tree, if necessary, in a feature branch. All of these have shown to be effective | ||
with all students in previous years. | with all students in previous years. | ||
| Line 112: | Line 112: | ||
=== What is your plan for dealing with disappearing mentors? === | === What is your plan for dealing with disappearing mentors? === | ||
Distribute the workload | Distribute the workload among the remaining mentors. The mailing list is | ||
active enough and questions almost never go unanswered. Reassign the student to | active enough and questions almost never go unanswered. Reassign the student to | ||
a backup mentor. In the worst case, the project admin can become a mentor for | a backup mentor. In the worst case, the project admin can become a mentor for | ||
the student until another backup mentor is found. | the student until another backup mentor is found. | ||
This should be infrequent and we hope to prevent | This situation should be infrequent and we hope to prevent it by selecting | ||
mentors with proven involvement in Octave or other free projects. We are also | mentors with proven involvement in Octave or other free software projects. We are also | ||
pairing new mentors with | pairing new mentors with more experienced ones. | ||
=== 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 | |||
progress updates of every two to three days. Longer updates, should be done on a | progress updates of every two to three days. Longer updates, should be done on a | ||
blog and aggregated at http://planet.octave.org. | blog and aggregated at http://planet.octave.org. | ||