Student Check List

Zur Navigation springenZur Suche springen

Please send in applications for Google Summer of Code via the GSoC website. More infos about the process in the blog at Good luck with your application! Please take a look on our ideas page and select the idea you like. If you miss any information like documentation or repositories, please ask the mentors connected to the ideas. We invite you to subscribe to our mailing lists to introduce yourself and clarify your questions.

GSoC Application Check List

If you want to participate in GSoC as a student, you should do your best to persuade us that you are the best candidate.

  • Show us code you've written in the past with links to GitHub and projects you have participated in
  • Get involved as soon as possible with the freifunk project and introduce yourself on the mailing list at
  • Submit patches for bugs or new features to projects, so that we can see your code before starting big GSoC project.
  • Write a good proposal with goals, milestones and mockups (Choose descriptive name, clearly define deliverables and what you expect to deliver in mid-term and as a final results.)

Application Template

Contact Details

  • Name:
  • Email:
  • Blog:
  • Github/Bitbucket/Assembla etc. profile:
  • IRC Nick and Network:
  • Phone:
  • Country/Region:

About You

Who are you? What’s the focus of your studies? What makes you the best person to work on this project? What is your experience in the tech community?

What free and/or open source projects have you participated in? Please describe your contributions, provide us links to your features and commits.

Your GSoC Project

  • Project Title:
  • Possible Mentor:
  • Description:
Benefits to community networks, who would gain from your project?
Deliverables - It is very important to list quantifiable results here e.g. “Improve X modules in ways Y and Z.” “Write 3 new man pages for the new interfaces.” “Improve test coverage by writing X more unit/regression tests.” “Improve performance in FOO by X%.”
  • Project Details - more detailed description.
  • Project Schedule - Please provide a rough timetable with milestones every 2 weeks.
  • Availability - How many hours per week can you spend working on this? What other obligations do you have this summer?

After GSoC

  • How will you continue with your project within the community after GSoC?

Full time program

Google clearly states that Google Summer of Code is a full time program. We expect students to not have other obligations - internships, summer jobs etc. - during the summer and fully dedicate to their GSoC project.

Expectations during GSoC

We expect full dedication of students from the beginning of the program and will fail any student that does not fulfill these expectations right in the first term. As an accepted student, please:

1. Set up your blog at and post the details of your project here immediately. We expect at least four extended blog posts with detailed info about your work during the program. Please ensure to include the following in each post:

  • details on the functionality of your project and the technology
  • links to the repository and project resources
  • pictures, screenshots, mockups
  • information about the features of your project
  • a screencast/video of the project, set up or features

Please contact your project admin about access to the blog. Posts should appear at least

a) before the program starts during the community bonding period,
b) before the first evaluations
c) before second evalutations
d) before the final evaluations.

2. Sign up to the mailing list WLANware, if you have not done so yet.

3. Update your project plan. Provide a detailed list of features and issues you work on and milestones for your project until May 20 and publish your plan on the freifunk blog and provide a link to your repository and issue tracker. You could host your project on the [ GitHub account of freifunk]for example.

3. Provide weekly status reports on the mailing list. Once a week, on the same day! They are obligatory. Please send them to your mentor and to the mailing list. If you fail to provide them, you will not be passing the evaluation and fail.

4. Upload your code to the repository daily. Even if you have not finished a feature we would like to see your progress every day.

5. Keep in touch with the community and ask any questions that come up on the mailing list unless you have a good reason to ask directly your mentor.

6. Document your project in the code, the read me and other resources.

7. Join us at the Wireless Community Weekend from the 25th-28th May 2017 in Berlin. (You can apply for a 500 USD travel grant to Google as a former student).

8. Support future freifunkers in the Google Code-In program for kids 13-17 years old in December 2016/January 2017.

Other Hints

  1. Be active, don't expect to be kicked.
    • Write weekly reports on time.
    • Submit your code early.
    • If you fail to communicate, it can lead your project being marked as failed and you won't receive any money from Google.
  2. Provide code and documentation in continuously and in good quality.
    • GSoC has deadlines, but we want to see your code continuously.
    • Having documentation for users is a must, you need to include it in our existing documentation.

Passing/Failure of Students

Google Summer of Code has strict timelines. It is a coding program and students are expected to contribute code to projects within the timeframe of the program. We understand that around the world there are obligations in university and everyone has a life and that things can happens in ones personal life. In this online coding program, however, we have only limited possibilities to divert from the timeline and we will have to fail students, who cannot fulfill the programs obligations for whatever reason, even if there are issues out of the responsibility of students. Should this be the case students always have the chance to apply again a year later as well. Experience shows that students who start slowly and do not fulfill the expectations during the first term, do not improve afterwards and the resources of our volunteer mentors to bring students up to standard in this short time are limited. We will fail students who are not meeting the expectations immediately in the first term without exceptions.

See also