English
*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 (Abbreviated)
Reference: https://developers.google.com/open-source/gsoc/timeline[Full Timeline]
*10 October, 2016*: Program announced.
*19 January, 2017: 16:00 UTC* Mentoring organizations can begin
submitting applications to Google.
*09 February: 16:00 UTC* Mentoring organization application deadline.
*10 - 26 February*: Google program administrators review organization
applications.
*27 February 16:00 UTC* List of accepted mentoring organizations
published on the Google Summer of Code site.
Interim Period: Would-be students discuss project ideas with potential mentoring organizations.
*20 March: 16:00 UTC* Student application period opens.
*03 April: 16:00 UTC* Student application deadline.
Interim Period: Slot allocation trades happen among organizations. Mentoring organizations review and rank student proposals; where necessary, mentoring organizations may request further proposal detail from the student applicant.
*04 May: 16:00 UTC* Accepted student proposals announced.
http://googlesummerofcode.blogspot.cz/2007/04/so-what-is-this-community-bonding-all.html[Community Bonding Period] - Students get to know mentors, read documentation, get up to speed to begin working on their projects.
*30 May*: Students begin coding for their Google Summer of Code
projects; Google begins issuing initial student payments provided tax
forms are on file and students are in good standing with their
communities.
Work Period: Mentors give students a helping hand and guidance on their projects.
*26 June: 16:00 UTC* Mentors and students can begin submitting Phase 1
evaluations.
*30 June: 16:00 UTC* Phase 1 evaluations deadline; Google begins
issuing mid-term student payments provided passing student survey is on
file.
*28 July: 16:00 UTC* Phase 2 evaluations deadline.
*21 to 29 August: 16:00 UTC*: Final week: Students tidy code, write
tests, improve documentation and submit their code sample. Students also
submit their final mentor evaluation.