|
Helping the student plan realistic achievable milestones that provide for regular deliverables and feedback.
|
|
|
Regular communication with your student. This means you must be regularly available for the entire project. If you take a holiday you need to know early and help your student be ready for your brief absence.
|
|
|
Attending a brief mentors call, as scheduled.
|
|
|
Be the final, accountable person for deciding if the student is successful or not. This is responsibility akin to being a professor or boss.
|
|
|
Communication
|
|
|
*Mailing List (GSoC-related):* link:https://lists.fedoraproject.org/admin/lists/summer-coding@lists.fedoraproject.org/[summer-coding@lists.fedoraproject.org]
|
|
|
*Mailing List (Technical):* link:https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org/[devel@lists.fedoraproject.org]
|
|
|
*IRC:* link:https://webchat.freenode.net/?channels=#fedora-summer-coding[#fedora-summer-coding] or link:https://webchat.freenode.net/?channels=#fedora-devel[#fedora-devel] on Freenode
|
|
|
Timeline
|
|
|
Always refer to the link:https://summerofcode.withgoogle.com/how-it-works/#timeline[Official Google Summer of Code Timeline] for details.
|
|
|
Administration
|
|
|
In order to get questions answered or obtain more information related to this year's GSoC with Fedora, please contact the administrators directly (please consider CCing the summer-coding list where ever possible).
|
|
|
link:https://fedoraproject.org/wiki/User:Bex[Brian (bex) Exelbierd] (Primary)
|
|
|
link:https://fedoraproject.org/wiki/User:Mbriza[Martin Bříza] (Secondary)
|
|
