Google Summer Of Code

Spend your summer doing something exciting and valuable for the open-source community, and join Google Summer of Code. Read more about how the program works on this page.

OpenVINO Toolkit has been a mentoring organization since 2022!

Announcements

Please subscribe this discussion and check it regularly for important announcements.

Prerequisite task

To better understand your coding skills, familiarity with Git and GitHub, and overall coding style, we ask each prospective GSoC contributor to complete a preliminary coding task. You may either request a prerequisite task directly from a mentor or follow the approach outlined below.

If you choose to follow the specified approach:

1. Visit the OpenVINO Good First Issues board.
2. Select one of the unassigned tickets ("Contributors Needed" column) and ask for the assignment.
3. Discuss the solution with the OpenVINO developers.
4. Implement it according to the OpenVINO contribution guide.
5. If you encounter any issues talk to our developers directly in the ticket or via discussions.
6. Create a new pull request with your work.
7. Wait for the review and eventual merge.

Please note that completing a prerequisite task is mandatory for consideration. However, we reserve the right to review and merge only selected pull requests. Anyway, please don't open more PRs than 2 at the same time! Whether your PRs are merged or closed will not affect your chances of being accepted for GSoC. As we expect a large number of submissions, reviews may take some time. Thank you for your patience.

If you're unfamiliar with git and GitHub, check out this blog. The blog is about contributing to OpenVINO core project, but the workflow is the same for all projects.

Application Template

Purely AI-generated applications are not allowed and will result in disqualification. Applicants must author their submissions themselves and be able to fully explain all content. AI tools may only be used to check grammar, punctuation, or slightly improve language style; they must not generate ideas, write sections of the application, or replace the applicant’s own reasoning. Submissions that appear to be primarily AI-generated will be rejected. The guiding principle is that AI may assist in polishing your application, but it cannot replace your thinking, creativity, or voice.

Your application should consist of the following parts:

1. About you
   1. Your full name
   2. Your university/current enrollment
   3. The timezone you live/work in
   4. Short bio
   5. Your experience in programming (especially C++ and Python)
   6. Your experience in technologies required for the project
2. About the project
   1. What is your choice?
   2. Why did you choose this specific idea?
   3. How much time do you plan to invest in the project?
   4. Provide an abstract of the solution
   5. Provide a detailed timeline of how you want to implement the project (include the main points you want to cover and dates)
3. General questions
   1. How do you know OpenVINO?
   2. What do you know about OpenVINO?
   3. Have you already contributed to the OpenVINO project? (please include links)
   4. How could you apply it to your professional development?
   5. Describe any other career development plan you have for the summer in addition to GSoC.
   6. Why should we pick you?
4. Prerequisites
   1. Link to your pull request (for the prerequisite task – the top part of this document), even if it is already merged or closed

Proposal examples can be found here and here. Please get in touch with us early to discuss your application with the mentor.

The proposal must be uploaded to the GSoC website during the GSoC contributor application period (according to the dates in timeline) and have the same name as the project name (that will prevent your submission from being missed).

Project ideas for 2026

All project ideas for 2026 can be found here.

Projects already implemented (2022-2025)

Projects implemented in the past can be found here.

Contribution guidelines

Contribution guidelines can be found here.

AI Usage Policy for Google Summer of Code Contributions

This policy defines acceptable use of AI tools in GSoC contributions to ensure code quality, accountability, and learning outcomes. Core Rules

1. Ownership and understanding

   • Contributors must fully understand and be able to explain all submitted changes.

2. No raw AI output

   • All AI-assisted content must be reviewed, modified, and owned by the contributor.
   • Non-conforming, unnecessary, or low-quality code must be rewritten or removed.

3. Build and test requirements

   • All changes must compile.
   • Appropriate tests must be added and must pass.
   • Untested or unbuilt code is not acceptable.

4. AI is an assistant, not an author

   • AI may be used only for research, learning, understanding, and test exploration.
   • AI must not be the primary problem-solving or code-generating mechanism.

Please note the final decision of accepting code written with the help of AI is up to the project mentor.

Contact us

1. Open OpenVINO discussions tab
2. Start a new discussion by pushing the green button (if you cannot see the button, it means you're not logged in)
3. Select a "Google Summer of Code" category and add the "gsoc" label
4. Ask your question (please be aware everything you post there is publicly available)
5. Tag the mentor to whom you address your question (the mentors are specified for all project ideas)

Please get in touch with us early to discuss your application with the mentor. Mentors will do their best to reply to all contributors, but due to a large contributor interest this year, they may not be able to respond to all inquiries