Google's Summer of Code 2027
Django is a mentor organization for the 2027 Google Summer of Code. Read Google's page for more information on how the program works.
Django's GSoC program is being coordinated by Bhuvnesh Sharma and Apoorv Garg.
Mentors
If you're interested in mentoring -- supervising a student in work on Django-related activities -- please let us know. Until we have a forum post, reach out to Bhuvnesh or Apoorv.
Students
Student application period runs until TBD.
If you'd like to get started on your proposal early, we'll be looking for a few things.
- You'll need to have a concrete task in mind along with a solid idea of what will constitute "success" (you tell us).
- If your proposal is a single large feature, library or site, you'll need to present a detailed design specification. This proposal should be posted to the Django Forum, where it can be refined until it is accepted by the developer community.
- We'll want to know a bit about you -- links to previous work are great, if any. If you're proposing something ambitious, you'll need to convince us that you're up to the task.
- You'll also need to provide us with a schedule, including a detailed work breakdown and major milestones so your mentor can know if and when to nag you :)
Here's an example of an accepted proposal from a previous year:
Note that none of the ideas below are good enough to be submissions in their own right (so don't copy and paste)! We'll want to know not just what you want to do but how you plan to pull it off.
Don't feel limited to the ideas below -- if you've got a cool project you want to work on, we'll probably be able to find you a mentor. We plan on approving as many projects as we possibly can.
We're accepting any GSOC proposal that fits one of the following three categories:
- Work on Django itself - such as the ORM, forms, etc. This is what we've traditionally accepted GSoC entries in.
- Work on tools to support Django - the issue tracker dashboard (https://dashboard.djangoproject.com/) is a good example of an existing tool that would have fit into this category.
- Work on libraries that supplement or add new features to Django to ease development -
django-stubsand Django Debug Toolbar are good examples of existing projects that would have fit here.
Here are the projects that were accepted last year: https://summerofcode.withgoogle.com/archive/2025/organizations/django-software-foundation-8o (2026 hasn't been published yet)
We're going to be strict with what we accept - you'll need to provide a strong use case for your idea and show that it would be useful to a majority of developers or significantly improve the development of Django itself.
We're not looking for small groups of incremental updates - like "improve Django's Trac" - nor are we looking for impossible tasks, like "replace Trac with this brand new issue tracker I'm writing". What you propose should be a single project, achievable within the time period of GSoC, and something the core developers can help mentor you on.
We're also not looking for sites or projects that are merely written in Django — this GSoC is not for you to propose your new forum hosting site or amazing Django-based blogging engine. However, community sites such as django-packages.org would be qualified.
Note that when you contribute code, you will be expected to adhere to the same contribution guidelines as any other code contributor. This means you will be expected to provide extensive tests and documentation for any feature you add, you will be expected to participate in discussion on the Django Forum when your topic of interest is raised. If you're not already familiar with Django's contribution guidelines, now would be a good time to read them - even if you're not applying to work on Django core directly, we'll still want the same level of contribution.
How can I improve my chances of being accepted?
The best thing you can do to improve your chances to be accepted as a Django GSoC student is to start being a community member now.
This can be a number of things:
- Participate on the Django Discord and Forum
- Work on a ticket, please only work on one ticket until your previous one is merged
- Submit a review for a PR, please only participate on a single PR until that previous PR is merged
- Participate in community events
Read up on Django’s contribution documentation and make yourself known to the other contributors by your contributions (ideally, related to the area of your proposal). That way, when it comes time to evaluate student applications, you’ll be a known individual and more likely to be able to get the attention you need to develop a proposal.
We're looking for candidates who can demonstrate that they can engage in work of a project scope on an independent basis. We're there to help but we can't watch you every step of the way, so we need to see that motivation from you. Being active before the submissions process is the best way to demonstrate this.
On AI/LLM usage. It is acceptable to use AI/LLM to assist you in your work. However, the goal here is for you to become a community member which means you should communicate with your own words to the best of your ability. Using AI/LLM to tweak your communication is perfectly fine. Using AI/LLM to generate your text and copying it verbatim is not.
Similarly, be aware every action you take in the community is asking something of a volunteer community member. We want you to engage with us, but avoid flooding the community with PRs, reviews, or messages. Even if it's well-intentioned it is still spamming and against our code of conduct.
Communication
All GSOC-related communication is handled via the Django Forum, in the Mentoring channel. Any proposals for GSoC should be submitted there, as well as discussion on the proposed projects and any updates that students post.
Please be careful to keep content to the forum clear and purposeful; if you have an idea, update, or criticism, please make sure you describe it in detail; it can be tedious asking people to clarify any vague statements.
Ideas
Here are the for project ideas students may propose. Remember, we'd much prefer that you posted a draft proposal and your rough timeline / success conditions to the the Django Forum, in the Mentoring channel, even if it's already on the list below; it will help you get feedback on choosing the right part of a problem, as well as helping to see if there is any interest before you start drafting a full proposal.
When developing your proposal, try to scope ideas/proposals to size of your project (175hrs or 350hrs) -- you need to be ambitious, but not too ambitious. The GSoC does not cover activities other than coding, so certain ideas ("Write a more detailed tutorial" or "Create demonstration screencasts") are not suitable for inclusion here.
On the other side, though, be sure to be concrete in your proposal. We'll want to know what your goals are, and how you plan to accomplish them.
The project ideas below will list key skill, but all assume a knowledge of Python, and familiarity with Django itself.
[PLACEHOLDER] Project name
| Difficulty | Medium or Hard |
| Size | 175hr or 350hr |
| Mentors | (need confirmation) |
| Key Skills | - |
Project description including the expected outcome of the project.