From 28adbbbef3ff93af27bc1d5abb0238adcf2e2f04 Mon Sep 17 00:00:00 2001 From: Sebastian Garcia Date: Tue, 27 Feb 2024 11:37:06 +0100 Subject: [PATCH] Update contributor_guide.md --- contributor_guide.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/contributor_guide.md b/contributor_guide.md index 2338242..5a13781 100644 --- a/contributor_guide.md +++ b/contributor_guide.md @@ -21,8 +21,8 @@ These are our guidelines for how the application process works: 1. If this is your first time applying for Google Summer of Code, we recommend you read through the official [Student Contribution Guide](https://google.github.io/gsocguides/student/) from Google, which is filled with very useful advice. 2. Check the project repositories and learn more about what their aim is. Browse through the codebase to familiarize yourself a bit with the structure and technologies involved in the code. 3. Read through the list of [[List of Ideas](list_of_ideas.md)] to see if anything listed matches your interests as a potential application. -4. Discuss the ideas with the mentor(s) on Discord (see Communication section). If the idea is not listed, discuss it and see if it can be acceptable to your mentors. We welcome innovative proposals that require three months of dedicated implementation. Should you have such a concept, we are eager to consider its potential. -5. Before being selected, all applicants **must** contribute to the selected project by working on open issues and opening a Pull Request (PR) with your contributions. These contributions are outside GSoC, but they give us an important chance to get to know you and for you to get to know us. We also want to show you that your code contributions won't be ignored, and they will be part of the codebase of our projects. Contributing to these open issues is an excellent way for us to show you our commitment. +4. **Discuss** the ideas with the mentor(s) on Discord (see Communication section). If the idea is not listed, discuss it and see if it can be acceptable to your mentors. We welcome innovative proposals that require three months of dedicated implementation. Should you have such a concept, we are eager to consider its potential. +5. Before being selected, all applicants **must** contribute to the selected project by working on open issues and **opening a Pull Request** (PR) with your contributions. These contributions are outside GSoC, but they give us an important chance to get to know you and for you to get to know us. We also want to show you that your code contributions won't be ignored, and they will be part of the codebase of our projects. Contributing to these open issues is an excellent way for us to show you our commitment. Some projects have a list of 'beginner' issues to solve, check them in Github Issues. 6. We ask all applicants to send an application to us (see Application Template section) before submitting it officially so we can give you feedback and suggestions, increasing your chances of getting accepted later. This is also an excellent way to have a small interaction with us and a getting to know each other a little before going through with the applications. 7. Before applying officially, check with yourself that: 1. You are committing to working with us for the duration of the project (12 weeks or 22 weeks, depending on the size of the project).