Google Summer of Code (GSoC)

This project is for proposing projects, logging the administrative issues, mentor meetings, and credit for contributors helping to organize Google Summer of Code and related programs.

Check our issue queue and add projects if you can think of more ! Or add your name as mentor to the existing ones.

The vision of the Drupal Association is to establish the community-built Drupal software as the leading platform for the Web and how? Well, by uniting a global open source community to build, secure, and promote Drupal. It is in clear that in order to achieve this ambitious goal, we constantly need to challenge ourselves and others and grow our community with fresh bright minds. Google Summer of Code has historically been a great source of finding these talents and are an amazing example of our more internal tagline -> Come for the code, stay for the community.

We would love to have +- 10 students, focussing on the main challenges that Drupal has today in order to stay a top of class Digital Experience Platform. We would consider it a success if we find students that want to tackle these challenges with us together. These strategic initiatives can be found at core/strategic-initiatives. It would be successful if we could make progress in these initiatives with motivated students that would stay after the program and maybe also see opportunities for them to find a way to keep tackling these problems in a professional setting (eg, their own business or in a company). This both helps the students, the economy and the Drupal project mission & vision

Resources:

• Contributor Reference Guide / Documentation / Getting Started Guide
• Drupal Issues for GSoC
• History of GSoC in Drupal
• Drupal's GSoC 2026 Project Idea Page
• GSoC Official Website
• Learn how GSoC Works?
• GSoC Timeline
• How to write GSoC Proposal / Student Application
• Sample Proposal / Application Template

Drupal GSOC Standards and Requirements

Drupal has participated in Google Summer of Code from the very beginning, and each year we have a vibrant community of potential contributors - always with more good proposals than the Google team is able to fund for that cohort. Therefore, we have developed ways to help make difficult choices about which projects we nominate.

Drupal GSOC Code of Conduct

One important element is that we expect all GSOC contributors, mentors, admins, etc to adhere to the Drupal Code of Conduct for our community in general, and also a specific GSOC Drupal participant code of conduct. This code of conduct outlines some key principles:

• That we will adhere first and foremost to the requirements and standards laid out by GSOC.
• That the criteria for project selection will be transparent.
• That the specific details of a proposal's ranking will be confidential.
• That all contributors understand there is no entitlement to be selected.
• That we will handle disagreement and conflict with grace, and escalate to the proper channels (the Drupal org admins) for resolution.
• That contributors or mentors who impersonate multiple users will be disqualified for the program.
• Etc - more details to be published in the full document.

Drupal GSOC Contributor Requirements

In addition to the standard requirements of the GSOC program, we do have some requirements specific to the Drupal community:

• Proposals must be either: entirely original work, or endorsed and approved of by the project maintainer the proposal intends to support.
• Proposals should not be repeats of previous GSOC projects.
• Proposals should not be plagiarized.
• Any use of AI in the writing of the proposal must be disclosed.
• Contributors will need to submit a 1 minute video along with their proposals, in part to prevent impersonation of multiple users, but also to help hear about the contributor's passion for the project in their own words.
• Contributors should make a significant effort to join the Drupal community (including Drupal.org and Drupal slack) before the end of the proposal period, and should begin building relationships with potential mentors prior to the proposal deadline.

Drupal GSOC Proposal Selection Criteria

The organization admins and mentors will undergo a standardized selection process. There is some room for admin and mentor discretion in this process, but the universal criteria are as follows:

• Y/N - Has the proposal already been made before?
• Y/N - Has a mentor agreed to support this contributor if the proposal is selected? (Admins do not *assign* mentors - unless they ask - a mentor must have proactively selected the projects they would support)
• 1-5 - What was the Contributors level of engagement with mentors, other contributors, and community during the application period? (i.e: did they join drupal.org and drupal slack and get engaged, or only come in right at the deadline).
• 1-5 - Prior history of contribution to open source or Drupal specifically
• 1-5 - Educational/Community Building Opportunity - i.e: Does this contributor broaden our community reach to new geographies or demographics.
• 1-5 - Subjective mentor ranking of the proposal and the contributor's qualifications
• 1-5 - Subjective admin ranking of the proposals, with the big picture of the cohort in mind

Each of these criteria is fed into a weighted average (the weighting is private to the mentors/admins) - and used to make the final ranking.