GSoC 2026 Contributor Introduction - Aniket

Mentorship Google Season of Code
1

Hi everyone,

I’m Aniket Gupta, a first year Computer Science student from India. I’m writing this to introduce myself as a potential candidate for Google Summer of Code 2026.

Background:

  • Built practical web applications using Django
  • Experience with Databases and production deployment
  • Solid background in fullstack development

Because of this, I am highly interested in the “Experimental feature flags and processes” project. The idea of formalizing a sandbox environment within Django core—allowing the community to test and iterate on new APIs without compromising strict backwards compatibility—is a fascinating architectural challenge.

I have been reviewing the discussions around DEP 2 and the concepts of using a django.experimental namespace versus a settings-based EXPERIMENTAL_FEATURES dictionary.

Before I finalize my proposal draft, I wanted to ask:

  1. Are there specific existing tickets or PRs where the friction of introducing new features was particularly high, which I could study as a case study for why this project is needed?

  2. Is the current consensus leaning more toward module-level decorators or a centralized settings registry for checking these flags?

I am currently setting up my local environment and looking for a small “easy pickings” ticket to get familiar with the review workflow. Thank you for your time and for maintaining such an incredible framework!

I’ll be looking forward to contribute!

1 Like
2

I would first read the brief summary here: SummerOfCode2026 – Django
This summary is short but every sentence meaningful so I would advise you digging into each thing mentioned here.
Then there is studying the new-features repo and the process the current Steering Council has put in place as well as reading what you can find about the old/current DEP process.

To answer 1. The recent release of the tasks framework, while a great success, did cause a fair amount of confusion about what was and wasn’t required for it to be usable. If we had an experimental API in place then more could have been proposed and included as experimental which would have lessened the confusion.

  1. There is no consensus yet. The first part of the project will be defining what the various terms mean and documenting them having achieved consensus. Then it will be defining and documenting new policies and modifying existing processes/policies. Then we get to the code changes. Do propose ideas on what you think could work, but having a solid set of processes & policies in place it the starting point.
1 Like