Complete Gsoc 2024 Roadmap by @kirat_tw
(with some extra tips)
1. Get moderately good at a tech-stack :
(Time period: Sept-Oct-early Nov )
Four general tech stacks that Gsoc organisations uses are:
- Javascript/ Typescript
- Python
- Java
- C++
2. Start looking for organisations:
( Time period: mid-November)
Choose at least 2-3 organisations to be safe.
After choosing an organisation,
- Create a decent reputation of yourself with the maintainers.
- Start with small bugs.
- Introduce yourself in SLACK, DISCORD.
- Ask curious questions but don't ask too many questions.
- Make your presence felt early to the maintainers because there is a huge crowd in Jan-Feb.
- Get to know the maintainers before the crowd comes.
Until December, have a decent reputation with the maintainers and hopefully solve a few bugs in the organisation.
3. Be aggressive:
(Time period: Jan-Feb)
- When January comes, start contributing to bigger codebases and try to solve bigger issues without the help of maintainers.
- 2 months learning a stack and 2 months understanding the codebases so by this time you should be aware of the tech stack and the organisations' codebase to solve bigger issues
4. Have a very polished proposal:
(Time period: Feb end)
- Try 2-3 proposals in 2-3 organisations.
- You can send multiple proposals to one organisation
OR
- You can pick 2-3 organisations and send a proposal to each one of them.
80% of getting into Gsoc is contributions
10% is a decent reputation with maintainers and the rest
10% is the proposal.
15-20 days before the Gsoc result announcement, be very aggressive with the contributions.
(with some extra tips)
1. Get moderately good at a tech-stack :
(Time period: Sept-Oct-early Nov )
Four general tech stacks that Gsoc organisations uses are:
- Javascript/ Typescript
- Python
- Java
- C++
2. Start looking for organisations:
( Time period: mid-November)
Choose at least 2-3 organisations to be safe.
After choosing an organisation,
- Create a decent reputation of yourself with the maintainers.
- Start with small bugs.
- Introduce yourself in SLACK, DISCORD.
- Ask curious questions but don't ask too many questions.
- Make your presence felt early to the maintainers because there is a huge crowd in Jan-Feb.
- Get to know the maintainers before the crowd comes.
Until December, have a decent reputation with the maintainers and hopefully solve a few bugs in the organisation.
3. Be aggressive:
(Time period: Jan-Feb)
- When January comes, start contributing to bigger codebases and try to solve bigger issues without the help of maintainers.
- 2 months learning a stack and 2 months understanding the codebases so by this time you should be aware of the tech stack and the organisations' codebase to solve bigger issues
4. Have a very polished proposal:
(Time period: Feb end)
- Try 2-3 proposals in 2-3 organisations.
- You can send multiple proposals to one organisation
OR
- You can pick 2-3 organisations and send a proposal to each one of them.
80% of getting into Gsoc is contributions
10% is a decent reputation with maintainers and the rest
10% is the proposal.
15-20 days before the Gsoc result announcement, be very aggressive with the contributions.
Extra Tips:
1. While choosing tech stacks try choosing something that aligns with your long-term goals:
As mentioned earlier, there are 4 popular tech stacks used by Gsoc organisations i.e. Javascript/Typescript, Python, Java and C++.
- Javascript is beneficial if you want to get into remote jobs.
- Python is used to build backends in Django and is heavily used for AI that is upcoming future.
- Java is generally the language of choice by big techs like Amazon, and Goldman Sachs.
- C++ is used by best algorithmic developers and competitive programmers.
2. Try to be the top maintainer in terms of contribution and if someone else's contributions are better than you, you might want to change the organisation.
3. Don't have very big red flags such as
- Don't be rude.
- Don't have typos.
4. Few tones for Gsoc as well as Remote Jobs:
- Be polite
- Don't be aggressive while communicating.
- Don't ask them persistently why they haven't looked at your issue.
- Don't make them feel like you are just there for GSOC, even if you are.
- Don't ask too many questions ( applies in the case of Remote Job as well)
1. While choosing tech stacks try choosing something that aligns with your long-term goals:
As mentioned earlier, there are 4 popular tech stacks used by Gsoc organisations i.e. Javascript/Typescript, Python, Java and C++.
- Javascript is beneficial if you want to get into remote jobs.
- Python is used to build backends in Django and is heavily used for AI that is upcoming future.
- Java is generally the language of choice by big techs like Amazon, and Goldman Sachs.
- C++ is used by best algorithmic developers and competitive programmers.
2. Try to be the top maintainer in terms of contribution and if someone else's contributions are better than you, you might want to change the organisation.
3. Don't have very big red flags such as
- Don't be rude.
- Don't have typos.
4. Few tones for Gsoc as well as Remote Jobs:
- Be polite
- Don't be aggressive while communicating.
- Don't ask them persistently why they haven't looked at your issue.
- Don't make them feel like you are just there for GSOC, even if you are.
- Don't ask too many questions ( applies in the case of Remote Job as well)
Loading suggestions...