Writing your application

The first and most important step to not get rejected is to remember to add the name of our sub-org (EOS) in the title of your GSoC application. Students not adding "EOS" will be rejected by Python.org. More information at http://python-gsoc.org/index.html#apply

Get in contact with the mentors of the project you chose ASAP. The time you wait to get in touch could be the difference between getting selected or going home.

Before even submitting the idea, get a feeling of EOS-icons and User Story: clone the repositories and get a better understanding of what we're doing. Again, ask as many questions as you want!

Take some hours to read the full WIKI page of EOS: https://github.com/EOS-uiux-Solutions/wiki. Yes, we have a lot of pages but they will help you get those Pull Requests merged faster if you understand our coding conventions beforehand. NOTE: all the information in this wiki applies to all of our projects. We have all of our guidelines in one repo since we apply the same rules and settings to all of our products at EOS in order to have a cohesive codebase across products.

Application template

• Contact information *

Name: E-mail address: Time zone: Other information that may be useful to contact you.

• Synopsis *

Give us the “elevator pitch“. You have 30 seconds to tell us what you are going to make, why we will like this project, and to convince us that you are qualified to do it! (You might want to write this section last).

• Which of the published tasks are you interested in? What do you plan to do? *

Detail your idea. Take into consideration the current technologies used at EOS and explain how they can be used, perhaps introducing new ones, to successfully achieve the task.

• What have you done so far with this idea? *

Research, benchmark with other tools available in the market, analyze the best options, try out EOS, and make a PR or 2 to warm up with the team. PSF guidelines are very strict and state that only those who have submitted a PR to the project in the matter will be eligible for GSoC.

• Schedule of Deliverables *

Make a plan. Being disciplined is important and it will help you have a stress-free summer coding amazing features. We won't micromanage you if you haven't stuck to the plan by the hour, it is not the point. We want you to be organized and in sync with the EOS team.

• Tell us about your previous experience *

Take the time to tell us about previous work experiences, courses you've taken, open source projects you've contributed to.

• Tell us a bit about you *

We also want to have a sense of who you are as an individual. At EOS we are young and very energetic. We have artists, musicians, gamers, and all types of people ready to have some quality time on Slack too.