Skip to content

Latest commit

 

History

History
75 lines (48 loc) · 3.7 KB

Application.md

File metadata and controls

75 lines (48 loc) · 3.7 KB

Please send in applications for Google Summer of Code via the GSoC website.

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/GitLab and projects you have participated in
  • Get involved as soon as possible with us and introduce yourself on our IRC channel #blackarch on Freenode
  • Start contributing with bug fixes and features or packages so we can see your code if possible
  • Write a good proposal with goals and milestones. Please define deliverables and what you expect to deliver in each step of the GSoC.

Application template

Contact Details

  • Name:
  • Email:
  • Blog:
  • GitHub/GitLab/Bitbucket ... Profile
  • 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:

  • Description:

  • Benefits for BlackArch, 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?

Time Planing

As GSoC is no longer a full time program, how are you planing to split your time over the summer. Show us project planing in your perfect application

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:

Other Hints

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

Passing/Failure of Students

Google Summer of Code has strict timelines. It is a coding program and contributors are expected to provide 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 people, who cannot fulfill the programs obligations for whatever reason, even if there are issues out of the responsibility of the contributor. Should this be the case contributors always have the chance to apply again a year later as well.

This Application document is based on Freifunks applications page, which was a great help in creating this.