Originally sent to all GSoC students and mentors. Forwarded to parrot-dev at dukeleto's request.
> On Tue, Jun 18, 2013 at 10:18 AM, Bruce Gray <bruce.g...@acm.org> wrote: >> ( Bcc'ed to all registered Parrot GSoC mentors ) >> >> Here are the rules for this year's Parrot GSoC students, as given to me by >> dukeleto in IRC on 2013-05-23: >> >> Rule 1: Students will submit a weekly report to #parrotsketch (Tuesday 19:30 >> UTC), pre-posting it if they will not be able to attend. >> >> Rule 2: The same report will be sent to the parrot-dev mailing list, so that >> people can make suggestions, help, give encouragement, etc... >> >> Rule 3: Students will decide which communication mediums they want to use >> with their mentor: text, chat, irc, email, skype, google hangout, etc... >> Then there will be (at least) a weekly check-in with each student to at >> least one mentor. >> >> Rule 4: Students will use their progress report to create a short blog post >> and post it on parrot.org, every week. Each blog post must contain at least >> 3 external links and at least 300 words. >> >> Rule 5: Students will not start any other paid or volunteer job without >> notifying me and/or GSoC and asking permission. GSoC should be considered a >> 20-40 hr/week job. >> >> If any rule gets broken at any time, automatic failure at the next grading >> point. Unless there is a very good reason. >> >> -- >> Hope this helps, >> Bruce Gray (Util of PerlMonks) >> Backup admin for 2013 Parrot GSoC >> _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
