hi Sankarshan, its worth sending this out to everyone's email address directly as well, is that something you are able to do ? - KB On 10/08/15 16:45, Sankarshan Mukhopadhyay wrote: > Mentors for the CentOS Project, > > Please do pay heed to this email. Pencils down is an important part of > GSoC and it is good to have all the rough edges sanded down before > this deadline. These could include agreed upon documentation, > demo/recordings, code commits and reviews etc > > If you have a student who sailed through the mid-terms but is an iffy > prospect at the end, please do discuss this with the OrgAdmins. It is > important that the project itself gets to know about it. > > /s > > > ---------- Forwarded message ---------- > From: 'Carol Smith' via Google Summer of Code Mentors Announce List > <gsoc-mentors-announce at googlegroups.com> > Date: Mon, Aug 10, 2015 at 9:12 PM > Subject: [GSoC Mentors Announce] GSoC 2015 Mentors/Org Admins: > "Pencils Down" and Final Evaluation Dates Approaching > To: GSoC Mentors Announce <gsoc-mentors-announce at googlegroups.com> > > > Hi there, > > This is a friendly reminder that Monday, 17 August is our soft > "pencils down" date. We suggest that students have completed their > projects by this date and spend a week writing documentation and > wrapping up their projects. We require that students stop all coding > on 21 August. > > Friday, 21 August at 19:00 UTC is when final evaluations open. Please > consider this your reminder to submit your final evaluation by 28 > August at 19:00 UTC so that you don't delay your students' final > payments or possibly jeopardize your organization's attendance at the > mentor summit. > > I have updated the code submission guidelines and posted it on Melange > for your reference. Code submission begins once students have received > a passing grade on their final evaluations (after 28 August). The > deadline is 25 September. One question students ask a lot is what > portion of their code to submit if they made changes to an existing > code base or their code interacts a lot with a system they didn't > write. The answer is: use your best discretion. Have them submit the > code that makes the most sense from a user's perspective. > > I have posted the questions for the final evaluations below as well > for your reference. > > Cheers, > Carol > > ------- > > How would you rate the student’s performance on his/her project since > the midterm evaluations? > > It has improved since the midterm > > It has stayed the same since the midterm > > It has gotten worse since the midterm > > Considering your student’s original project proposal, how closely does > the project produced reflect the project proposed? > > It’s almost exactly the same - there have been very few changes to the project > > It’s similar - there have been some changes over the course of the summer > > It’s different - we changed the goals or scope of the project > > It’s different - the student diverged from the project plan > > How much time have you spent on Google Summer of Code since the mid > term evaluations (again, take into consideration both time mentoring > the student and working on the program as a whole)? > > 10-15 hours per week > > 16-20 hours per week > > 21-25 hours per week > > 26-30 hours per week > > 31-35 hours per week > > 36-40 hours per week > > more than 40 hours per week > > How does this amount of time spent on the program compare to before > the midterms? > > It’s less than before the midterms > > It’s about the same > > It’s more than before the midterms > > How would you rate your student’s performance overall? > > Excellent - amongst the best performers I’ve ever worked with > > Strong, solid performance > > Okay > > Poor > > How would you rate your experience with the program overall? > > Excellent - one of the best programs I’ve ever participated in > > Very good > > Okay > > Poor > > If you are failing your student, please answer the next two questions > (if you are passing the student continue to Question #9): > > Why did you fail the student (check all that apply) > > the student was uncommunicative with their mentor > > the student was uncommunicative with the project community > > student disappeared after midterm > > the student didn’t complete their project > > The student did not stick to their timeline or project plan > > The students’ work was of poor quality, in spite of our/my efforts to > help them improve > > other > > Please explain. > > Any other information you’d like us to know about why you failed the student? > > What one thing would you tell mentors for your organization to do in > the future to help the students’ experience with the program? > > What was the most rewarding and/or difficult part of the program for > you this year? > > Is there additional information we should tell students before > applying to future programs? > > Your previous experiences with GSoC: (check all that apply) > > I was a student in GSoC > > I was a mentor in a previous GSoC > > This is my first time as a mentor > > Are you a current or former Google employee or intern? > > Yes > > No > > Anything else you’d like to tell us? > > -- > You received this message because you are subscribed to the Google > Groups "Google Summer of Code Mentors Announce List" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to gsoc-mentors-announce+unsubscribe at googlegroups.com. > Visit this group at http://groups.google.com/group/gsoc-mentors-announce. > For more options, visit https://groups.google.com/d/optout. > > -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc