Students may also wish to start working on the Fedora specific parts of the application (see the application section)
Student Responsibilities
Student Application
*Status :* Open for Ideas +
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.
Reference: https://developers.google.com/open-source/gsoc/timeline[Full Timeline]
Please read and follow the xref:application_process.adoc[student application process].
Our project is large and diverse. We are very experienced at working with new contributors and helping them be successful.
One way is to provide an idea for students to work on. This idea might be very well planned out, in which case you may need a high-level of contact with the student to get it implemented correctly. Other ideas may be more general and require more planning during onboarding.
Mentors are listed on the xref:ideas.adoc[Main Idea Page and Supporting Mentor List]
Mentor responsibilities
Many of our contributors are long-time contributors. They remain because they want to keep growing the project and to lend their expertise, advice and mentoring to you! People who stay around the community and do good work are noticed. They get hired for jobs from it, including being hired by Red Hat. Past Google Summer of Code students were hired by Red Hat, as well as interns in various positions. This is just an example, as experience and reputation in the Fedora Project communities is influential in your career in many ways.
Make friends and contacts around the globe.
*Mailing List (Technical) :* link:https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org/[devel@lists.fedoraproject.org]
*Mailing List (GSoC-related) :* link:https://lists.fedoraproject.org/admin/lists/summer-coding@lists.fedoraproject.org/[summer-coding@lists.fedoraproject.org]
List of Mentors
*Link :* xref:ideas.adoc[Summer coding ideas for 2017]