---
# System prepended metadata

title: Google Summer of Code

---

# Google Summer of Code

### Timeline

#### Dec - Jan
- Start early!
- Go to GSoC archives, look for projects and organizations that interest you.
- Introduce yourself.

#### Feb [week 1]
- Clone project repository
- Run the code locally, set up the dev environment.
- Try to debug, look at the test cases. 
- Read the documentation.

#### Feb - March
- Attend community calls.
- Be active in the community.
- Look for 'good-first-issues'.
- To solve an issue.
    - Inform the maintainer, you want to work on that issue.
    - Fork the repository or sync the fork.
    - Create a branch, checkout to it.
    - Clone your fork.
    - Make changes and verify you have solved the issue.
    - Push the changes.
    - Create a PR from the new branch to the main branch of upstream.
    - Follow PR guidelines.
    - Resolve all the reviews.
- Keep contributing.
- Discuss your GSoC project with your mentors.

#### March-May
- Draft a proposal, which should include the following things.
    - Follow the provided format.
    - List of deliverables / specific goals.
    - Timeline
    - How would you complete the project?
    - Your previous contribution to open-source.
- Get the proposal reviewed.
- Submit it, and complete the application.
- Fee receipt would work as proof of enrollment.

Start your GSoC journey!

#### Additionally
- Setup your blog.
- Follow your mentors on Twitter.

<hr>

### Do's 
- Be authentic and humble.
- Try your best to debug or solve an issue before reaching out to the mentors.

### Don't
- Don't ping the mentors too often.
