Google Summer of Code Application Process

Interested in applying for Google Summer of Code with Fedora? Here is how you do that!

The following are specific guidelines for students to use to submit an application for the GSoC program through the Fedora Project. Please go through these carefully and follow them. Applications must be complete by the deadline. Late applications cannot be accepted.

Important

  • Timelines are set by Google for the entire program. Follow the timeline.

  • Applications are due in Google’s system by March 27, 2018 18:00 (CEST).

  • Applications Must be filed in the Google system. No other material can be read or accepted.

  • The final application is required to be submitted as a PDF.

Student Application Process

Learn

Before you do anything, learn about the program and Fedora. These links may be helpful:

Communicate

Begin communicating with the community. Our community members can help you understand the existing project proposals. If you’re going to try and propose your own project, this is a great way to understand the needs of the project and find a mentor.

Don’t forget to contact mentors on projects that interest you to learn more. If you’re going to propose a project you must have a mentor at the time of proposal.

Apply

The application process consists of 5 steps:

  1. Create a FAS account FAS Account Signup / Login Page

  2. Join the fedora-summer-coding mailing list Fedora Summer Coding Mailing List - This list is fairly low volume.

  3. Join the devel mailing list Devel Mailing List - this list can be higher volume you may wish to use mail filters appropriately.

  4. Sign the FPCA by following the directions here

  5. Submit the application/proposal including all requirements in the next section at the Google Summer of Code Site. We strongly encourage you to not submit your final PDF until you get feedback about the proposal from your mentor(s).

Help is available! Share your application in progress and get feedback. The mentors can help verify your understanding of the project and provide guidance on whether your plan is good.

If you are submitting an original proposal you must find a mentor. Proposals without mentors will be rejected. Sharing your proposal is key to doing this. If you don’t want to share your proposal publicly consider using something like a Google Doc and sharing a link with the mentor/reviewers. You can also share the link via a private ticket in our Pagure Repository. While we would normally not suggest a close-sourced tool such as Google Docs, in this case it is potentially easier for you because you a) must have a Google account to be able to apply to the program; and b) must generate a PDF for your application.

Google Summer of Code Application and Supplemental Material Requirements

In addition to the information Google requests, the Fedora Project requires you to submit the following information:

  • What project are you applying to? Seriously consider choosing a project for proposal from ideas list. While it is possible to propose your own project, it is often more successful for you to select one that is already proposed by a mentor.

  • Contact Information

    • List your Name, Email Address, Blog URL, and any additional contact information you think we need. We tend to email so be sure you’re reading your email.

  • About You - Consider these questions

    • Do you have any past involvement with the Fedora Project or another open-source project as a contributor? What kind of contributions have you made (code and non-code)? Please share any public contributions you have made (urls, etc.)

    • What are you studying? Why?

    • What motivates you to do your best? How do you stay focused? Briefly describe how you organize your work.

  • Why Us? - Consider these questions

    • Why do you want to work with the Fedora Project?

    • Do you plan to continue contributing to the Fedora Project after GSoC? If yes, what sub-project(s) are you interested with?

  • Why This Project? - Consider these questions

    • Which specific project interests you? If you are proposing your own project, do it here. If you are proposing the project, explain why it benefits the community.

    • Have you contacted the mentor(s) listed for the project?

    • What relevant experience do you have for this project?

    • What do you want to gain from this project?

    • Describe this project in your own words. What does it mean to you? What do you think the final deliverable is?

  • Why should we choose you over other applicants?

  • Propose a rough schedule for this project. Ideally you will have regular deliverables throughout the entire period.

  • What are you specific plans from May to September (eg: Exams in university, internships, vacations..etc). We need to know if there are periods of time where you are likely to be unavailable. We are better at accommodating these periods if we know of them in advance.

You must submit a PDF version of all of the information you prepare with your application using the Google site. The PDF should consist of the information from the supplemental application requirements section below. It should also contain any custom project you are proposing, if any.

We are not allowed to consider students who do not submit this PDF. Students will not be judged on the visual layout of their PDF, however all information must be readable.

Keep communicating

We cannot overstress the importance of communication. Keep talking, and listening, to the discussion group, to the sub-projects relevant to your proposal and to potential mentors. Be patient, as mentors and other contributors are often very busy people.

Want to help? Learn how to contribute to Fedora Docs ›