Hello Mentor,
My name is Vanshika Maheshwari, and I am a first-year B.Tech student pursuing Mathematics and Computing. I am excited to apply for GSoC 2026 with Django and contribute to the community.
I have experience in Python and web development, and I am particularly interested in contributing to Documentation. As a beginner in open-source, I am eager to start with smaller, manageable tasks such as improving documentation, fixing minor errors, or adding examples, and gradually take on more challenging issues as I become more familiar with the Django codebase.
It would be great if you could suggest any beginner-level issues for me to start with. I’m very excited and looking forward to contributing to Django for GSoC 2026.
I am also exploring GSoC project ideas and would greatly appreciate guidance on choosing a suitable project, refining my proposal, or starting contribution tasks. My goal is to actively contribute to Django, learn from the community, and help make the framework more accessible and easier to use for developers.
Thank you for your time and support.
Welcome @Vanshikakhasat !
We recommend that everyone gets started by reading:
Feel free to ask questions here if there’s anything in those references that you don’t understand or if you get stuck.
Thank you for the welcome! I’ve gone through the recommended guides, including the Django GSoC 2026 page and the “Getting Started Contributing to Django” blog. I’m looking to start contributing and would like some guidance on choosing my first ticket. Could you suggest a beginner-friendly issue to work on?
Thanks in advance for your help!
There is no “formula” or “fixed” method to find a “beginner-friendly” issue. Even if a ticket is marked as being an easy ticket, there’s no guarantee that it will actually turn out to be easy. (There are time when a hidden “gotcha” will end up making a ticket significantly more complex than what it appears at first.)
There’s a section in that Better Simple blog post with links to other references to give you some ideas on ways to find appropriate tickets.
But there is no staff or individuals dedicated to identifying easy tickets. It takes real time and effort to read a ticket and understand it enough to be able to classify it that way. And, the easiest tickets are frequently grabbed very quickly.
Personally, no. I don’t follow the ticket system to know what’s being submitted other than reading the Fellows summaries to see what’s new.
The bottom line is that this is probably something you’re going to need to find for yourself.
Thank you for the clarification! I understand that finding a suitable ticket requires going through the issue tracker and understanding the problem myself. I’ll review the resources from the Better Simple blog and start exploring the tickets to find something I can work on. Thanks again for the guidance!
1 Like