Google Summer of Code Application and Project Mentorship

To apply for Google Summer of Code, students submit a proposal outlining their project idea, which should align with one of the participating open-source projects.

The application deadline is typically in March, and students have about a month to submit their proposals.

Students can browse through the list of participating open-source projects and find one that interests them, and then submit a proposal outlining their project idea.

Google Summer of Code provides a stipend to students, which is paid out in three installments over the course of the summer.

For your interest: Android Application Open Source Code

The application process for Google Summer of Code is a 5-step journey that starts with creating a FAS account. You'll need to sign up and log in to the Fedora Summer Coding Mailing List, which is a low-volume list where you can connect with other developers.

The next step is to join the devel mailing list, which can be a higher volume list, so be prepared to use mail filters to stay organized. You'll also need to sign the FPCA, which you can do by following the directions on the Fedora website.

After that, it's time to submit your application and proposal, including all the requirements, on the Google Summer of Code Site. Be sure to get feedback from your mentor(s) before submitting your final PDF.

If you're submitting an original proposal, you'll need to find a mentor, as proposals without mentors will be rejected. Sharing your proposal is key to finding a mentor, and you can do this by sharing a link to a Google Doc or a private ticket in the Pagure Repository.

Here are the 5 steps to apply:

Remember, the application process is a journey, not a destination, and it's okay to ask for help along the way. Don't be afraid to share your proposal and get feedback from your mentor(s) before submitting your final application.

Before you apply, make sure you're aware of the application timeline. Applications are due in Google's system by March 31st, 2020 18:00 (UTC), so don't leave it all to the last minute. Submit your proposal early, ideally before the final rush, to get more attention from developers.

To get started, create a FAS account and join the fedora-summer-coding mailing list, as well as the devel mailing list. You'll also need to sign the FPCA and submit your application proposal, which should include all requirements. If you're submitting an original proposal, you'll need to find a mentor, as proposals without mentors will be rejected.

Here are some key deadlines to keep in mind:

Before you apply to the Google Summer of Code, it's essential to learn about the program and Fedora.

Start by visiting the GSoC official site to get a comprehensive understanding of the program.

You can also check out Fedora's Participation in GSoC for specific information about Fedora's involvement in the program.

Here are some additional resources to help you get started:

Remember, learning about the program will give you a solid foundation to build upon as you prepare your application.

Before you start applying to the Google Summer of Code, make sure you're familiar with the program and Fedora. Check out the GSoC official site and Fedora's Participation in GSoC for more information.

It's essential to submit your proposal early, as early submissions get more attention from developers. Aim to submit your application and proof of enrollment before the final rush, and avoid submitting very late, as this will give your proposal the least attention from mentors.

To increase your chances of getting selected, submit more than one proposal, but make sure to tell the organizers which one you would choose if both were selected. Former students recommend focusing on one or two high-quality proposals rather than trying to submit three.

Reach out to organizations early and review the GSoC Contributor/Student Guide, which has valuable tips on having a successful GSoC. You can also look at the orgs that participated previously and review their Projects Ideas list to find a project that matches your interests and skills.

Before submitting your proposal, communicate with the org and get feedback on your idea. This will give you a chance to refine your proposal and increase your chances of getting selected.

Fedora's application process consists of five steps: creating a FAS account, joining the fedora-summer-coding mailing list, joining the devel mailing list, signing the FPCA, and submitting the application/proposal.

Make sure to follow the timeline set by Google, as applications are due by March 31st, 2020, 18:00 UTC. Your final application must be submitted as a PDF, and you must file it in the Google system.

As a potential contributor, you'll need to produce code for KDE during the coding period. You'll work with mentors who will dedicate time to mentoring you, so it's essential to be committed to helping KDE long-term and be proactive in communicating with your mentor(s).

Worth a look: Generative Ai Coding Tools

To participate in Google Summer of Code, you need to be a student and at least 18 years old before the results are announced.

There's no requirement for a specific department or year of study, but you can't participate in Google Summer of Code for more than two times, a rule that's been in place since the 2017 edition.

To be eligible, you must be 18 years or older on the date you register for the program.

You also can't be a resident of a country subject to a United States embargo and must be eligible to work in the country where you reside for the duration of the program.

New contributors to open source software development are preferred.

To apply, you need to register as a GSoC contributor on the program site between March 18 and April 2.

You can apply to up to three organizations, which are announced on February 21st.

Your written proposal must be submitted through the program site between March 18 and April 2.

As a Google Summer of Code (GSoC) participant, finding the right project and mentor is crucial for a successful application. Any KDE developer can be a mentor if they meet the GSoC eligibility requirements.

You'll need to subscribe to the KDE-Soc-Mentor mailing list to discuss ideas and vote on proposals. Daily communication is required with your student during the Community Bonding period, and multiple times per week during the coding period.

The KDE project has a list of formal project suggestions, but feel free to come up with your own unique ideas. Here's a sample list of suggested project ideas:

If you're new to contributing to Inkscape, it's a good idea to start with a formal project suggestion. These projects have been vetted by experienced developers and mentors, and can provide a great way to learn and get involved.

Some of the formal project suggestions include estimating the difficulty of a project, which can help you determine how much time and effort to commit. For example, one project is estimated to be difficult and long, requiring around 350 hours of work.

Another project is estimated to be hard and short, requiring just 175 hours of work. This one might be a good choice if you're looking for a shorter project to get started with.

To get started with any of these projects, you'll need to have some programming skills, specifically in C++ and CMake. You'll also need to have a good understanding of build systems, which can be a bit tricky if you're new to them.

Here are some of the formal project suggestions with their estimated difficulty and required skills:

Each project also has a potential mentor assigned to it, who can help guide you through the process and provide feedback on your work. For example, one project has Marc Jeanmougin as a potential mentor, while another has Jabier Arraiza.

Mentoring is a crucial part of the KDE development process. Any KDE developer can be a mentor if they meet the GSoC eligibility requirements.

To become a mentor, you'll need to subscribe to the KDE-Soc-Mentor mailing list. This is where you'll discuss ideas, read proposals, and vote on them according to guidelines.

As a mentor, you'll be assigned a student who may need help with a large project. Make sure you're up for the task, as mentoring takes time and lots of communication. Daily communication is required with your student during the Community Bonding period, and multiple times per week during the coding period.

You'll never be assigned a project you don't want to work on, and you'll have a backup mentor in case something unforeseen happens.

To sign up as a mentor, follow these steps:

It's also a good idea to read the mentoring guide and Federico Mena-Quintero's helpful information based on his experiences in previous years.

Refactoring Gcodetools is an easy task, but it can take anywhere from 175 to 350 hours depending on the scope. This project is a great opportunity to learn and improve your Python programming skills.

Jonathan is a potential mentor for this project, and having a Maker background or familiarity with the Maker community is a prerequisite.

To get started, you'll need to query Maker spaces on their needs regarding Gcodetools. This will help you understand what needs to be improved and implemented.

The tasks involved in this project include implementing the needs of Maker spaces, writing unit tests, improving test coverage, and writing proper documentation for Gcodetools.

Here's a breakdown of the tasks: