2. Who am I?
- Senior Software Engineer
- Open source contributor
- Participated GSoC 2013,2014
3. What is GSoC?
- Google Summer of Code is a global program focused on
bringing more student developers into open source software
development.
- Students work with an open source organization on a 3 month
programming project during their break from school.
5. When?
- Not announced yet for 2019
- February , announcing accepted organizations
- March, student proposals
- April, announcing accepted students
- May-August, work period
7. Advantages
- Acquire skills
- Your open source code will be your CV
- Internship Certificate signed from Google
- Opportunity to work with the organization or companies using
that project
- $$ (5500 dollars)
8. How to apply?
- Choose the organization
- Choose the project
- Choose the idea
- Make a proposal to accomplish the idea
- Prove your ability to do it
9. How to choose organization?
- Based on application domain
- Based on programming language and used technologies
- Based on Impact
- Based on competitiveness
- Plan early by checking last year accepted organizations
11. How to choose a project idea
- Choose from organization idea list:
- Choose the best fit to you
- The less competitive between applicants
- The easiest could be a bad idea
- Choose the most relevant to the organization
- Propose your idea:
- No competitiveness on the idea
- Is it relevant to the organization?
- Is it Really relevant to the organization?
- Fits well the 3 months , not less not more
- Follow the organization template
- Ask for the feedback of organization owners
12. Examples for GSoC ideas?
- My project for 2013:
- OWASP OWTF project
- Rewriting of the reporting system
- My project for 2014:
- Xapian Project
- Arabic Support and Python3 support
- You can already search for coming ideas for GSOC 2019
13. How to write a successful proposal?
- Title+Description
- Why relevant?
- Who are you?
- Why you?
- Conception
- Plan + Timeline
- Prototype
14. How to write a successful proposal?
- Don't lie about your skills,
- But don't be modest, explain your skills
- Go straight to the point
- Feedback is a key changer, ask for it from mentors
- A picture is worth thousand words
- A Patch Is Worth Ten Thousand Words
15. Contact mentors
- Do it earlier as you can!
- How to contact?
- Mailing list
- IRC channel, Slack, Gitter
- Direct emails
- Skype/Hangout
- Ask for guiding
- Ask for review
16. Submit Patches, Send Pull Requests
- Why?
- Prove your willingness
- Prove your communication and code skills
- Prove your ability to contribute
- Learn git!
- Test it well by yourself
- Ask for review first from friends
- Even if your patch/PR is not accepted at the first, fix and resend!
19. What you can do from now?
- Start!
- Build an online profile
- Contribute on Github
- Upload your well-coded apps to github, and publish them if
publishable.
- Stackoverflow could be used as profile too
- Improve your English! communication is a key.
- Focus on your objectives and plan well.