A short follow up, regardless of the deadline do this ASAP. There are two reasons to do it even today if possible. One is that it's a first come first serve system for the majority of processes, and second, one day buffer for the admins is not a lot and it's reserved for exceptional cases. In the regular case this will be done with more than a few days time, even though we sent the email a bit late and that's why we extended our internal deadline a bit more.
Thanks! On Thu, 25 Apr 2019 at 09:56, Carlos Soriano <csori...@gnome.org> wrote: > Hello all, > > GNOME has been accepted in GSoC one more year! \o/ > > In order to get the students you want in the accepted slots, you need to > complete these steps before next *Tuesday 30th April *(with a day for us > as a buffer). > > Go to https://summerofcode.withgoogle.com/ 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-adm...@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. > > *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 planet.gnome.org before the end of the community > bonding phase. > > If you have any questions, please don't hesitate to send us an email to > soc-adm...@gnome.org (preferred) or contact one of us on IRC. > > Have a nice day, > GNOME GSoC Admins >
_______________________________________________ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
