GSoC Midterm Evaluations
Just wanted to give a heads up to anyone that doesn't receive these announcements, and for those that interested in the program but aren't directly involved.
Gail
LH wrote:
Hello everyone,
All participants in GSoC should take a moment to peruse the newly published midterm survey documentation. The document covers information for students, mentors with assigned students, mentors without assigned students and organization administrators. There are detailed instructions for submitting the surveys, as well as a granular survey timeline. If you have any questions after reading the documentation, just let us know.
Cheers, LH
http://groups.google.com/group/google-summer-of-code-announce/web/midterm-su...
Gail, thanks for sending out this reminder!
Yes, mid-term evaluations are coming up quick. Last year, we placed an expectation that for a positive review, students should have a first cut of their work integrated into Inkscape SVN by the time Google opens the mentor review forms. Also, students who have not been active will be dropped at this point in the program.
Bryce
On Thu, Jul 05, 2007 at 01:48:48PM -0400, Gail Banaszkiewicz wrote:
Just wanted to give a heads up to anyone that doesn't receive these announcements, and for those that interested in the program but aren't directly involved.
Gail
LH wrote:
Hello everyone,
All participants in GSoC should take a moment to peruse the newly published midterm survey documentation. The document covers information for students, mentors with assigned students, mentors without assigned students and organization administrators. There are detailed instructions for submitting the surveys, as well as a granular survey timeline. If you have any questions after reading the documentation, just let us know.
Cheers, LH
http://groups.google.com/group/google-summer-of-code-announce/web/midterm-su...
Bryce Harrington wrote:
Yes, mid-term evaluations are coming up quick. Last year, we placed an expectation that for a positive review, students should have a first cut of their work integrated into Inkscape SVN by the time Google opens the mentor review forms.
I'd like to keep the LivePathEffect stuff in my own branch for a little longer. This way I can check whether lpe code causes a bug or that the bug is also present in trunk (know that I merge trunk into this branch pretty often). Also, this way I have an easy 'diff' of all LPE code. When LPE code is ready for serious testing, probably I'll merge it into trunk, giving up the advantages of the branch.
Cheers, Johan
participants (3)
-
unknown@example.com
-
Bryce Harrington
-
Gail Banaszkiewicz