GSoC Mentors to select students proposals

Hello GSoC Mentors,

Students already have their final proposals in the Google's website and we cleaned up everything so you can search for the ones you are interested in.

In order to get the students you want in the accepted slots, go to and search for the proposals you want to mentor. Then you need to do the following:
- Make sure you have marked all proposals you'd like to accept as "want to mentor". If you have two proposals for the same project, you need to decide which one to take.
- Include a score (explanation of score below*) and any comments about your experience mentoring the applicant and how strongly you feel that they should be accepted for the program. Do this in the comments section of the proposal on the Google's website.
- In case you selected to mentor more than one student, send us an email at soc-admins gnome org confirming it. Please make sure you will have enough time for two students. It's expected to spend around 10 hours per week per student. Google started to strongly recommend to just accept a single student per mentor, so we need to be careful when accepting these exceptions.

It is important to do these steps soon - the sooner this is done, the more likely you get the students you want! In any case, do this before 14/04/2016

*Score scale, half point rankings (i.e. 4.5, 3.5) are ok:
5 = amazing applicant, could become a module maintainer on completing the program, made extensive contributions to GNOME of high quality
4 = strong applicant, will certainly do a good job, made substantial contributions to GNOME of high quality (> ~50 lines of code or equivalent)
3 = good applicant, but is somewhat inexperienced
2 = is unlikely to do a good job
1 = not a good candidate

Also remember that when mentoring in GSoC, we expect:
- Fill evaluations at least 3 days before the official Google deadline. We need some time to tie up loose ends. Your student will fail and GNOME will get penalized if the evaluation is not filled on time.
- Spend around 10h per week with the student; reviewing code, helping him/her, chatting, etc.
- Weekly goals and review of the goals in weekly meetings.
- Review code submissions of the student thoroughly and in a timely manner.
- Communicate regularly with the student.
- The student is on before the end of the community bonding phase.

If you have any questions, please don't hesitate to send us an email to soc-admins gnome org (preferred) or contact one of us on IRC.

Have a nice day,
GSoC Admins

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]