Hi,
Quoting from the partecipant agreement: ------------------------------------------------------------------------ 2. MENTOR ORGANIZATION OBLIGATIONS The Mentor Organization must provide the following: (a) A pool of project ideas for students to choose from, publicly published by the Mentor Organization; (b) Someone available to review student "blue-sky" proposals should the student not find something that appeals in the organization's published ideas; (c) Someone available to review the incoming student applications targeted to the organization and to decide which applications should be accepted, meaning development begins on the accepted student proposals; (d) A person or persons to monitor the progress of the students and mentor them as the project proceeds; (e) A mentor ready to take over for the assigned mentor(s) in the event they are unable to continue providing guidance to the accepted student applicant, e.g. go on vacation, etc.; (f) An administrator to represent the Mentor Organization and perform administrative tasks such as submitting their Mentor Organization's application, creating the Mentor Organization's account on the Google Summer of Code site, and signing up mentors and publishing their pool of project ideas; and (f) A written evaluation of each student developer, including how they worked with the group, if they should be invited back should we do another Google Summer of Code, etc. -------------------------------------------------------------------------
So what we'll have to do in the coming weeks is just (b) and (c) .
Giovanni
giovanni
Soc is accepted !!!! I'm signing the agreement.
Stef
On 15 mars 07, at 09:58, Giovanni Corriga wrote:
Hi,
Quoting from the partecipant agreement:
-- 2. MENTOR ORGANIZATION OBLIGATIONS The Mentor Organization must provide the following: (a) A pool of project ideas for students to choose from, publicly published by the Mentor Organization; (b) Someone available to review student "blue-sky" proposals should the student not find something that appeals in the organization's published ideas; (c) Someone available to review the incoming student applications targeted to the organization and to decide which applications should be accepted, meaning development begins on the accepted student proposals; (d) A person or persons to monitor the progress of the students and mentor them as the project proceeds; (e) A mentor ready to take over for the assigned mentor(s) in the event they are unable to continue providing guidance to the accepted student applicant, e.g. go on vacation, etc.; (f) An administrator to represent the Mentor Organization and perform administrative tasks such as submitting their Mentor Organization's application, creating the Mentor Organization's account on the Google Summer of Code site, and signing up mentors and publishing their pool of project ideas; and (f) A written evaluation of each student developer, including how they worked with the group, if they should be invited back should we do another Google Summer of Code, etc.
So what we'll have to do in the coming weeks is just (b) and (c) .
Giovanni
Soc mailing list Soc@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/soc
Il giorno gio, 15/03/2007 alle 15.17 +0100, stephane ducasse ha scritto:
giovanni
Soc is accepted !!!! I'm signing the agreement.
Heh, you don't know how tense I was this morning, when the accepted org started appearing on the SoC page...
By the way, Stef, did you receive my message re: SummerTalk?
Giovanni
On 15 mars 07, at 15:47, Giovanni Corriga wrote:
Il giorno gio, 15/03/2007 alle 15.17 +0100, stephane ducasse ha scritto:
giovanni
Soc is accepted !!!! I'm signing the agreement.
Heh, you don't know how tense I was this morning, when the accepted org started appearing on the SoC page...
:) this is adreanline.
By the way, Stef, did you receive my message re: SummerTalk?
No Strange
Giovanni
Soc mailing list Soc@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/soc
soc@lists.squeakfoundation.org