DEV Community

Amarnath Ps
Amarnath Ps

Posted on

My First Steps into Open Source: Setting Up Wagtail for GSoC 2026

As a first-year BTech student, I always thought open source contribution was something only experienced developers did. GSoC 2026 proved me wrong.

Why GSoC?

When I first heard about Google Summer of Code, I was intimidated. But then I saw Wagtail — a Django-based CMS with a friendly community and a history of mentoring newcomers. Six years, fourteen successful projects. That felt like a sign.

Picking Wagtail

I looked at a few organizations. Some required deep math knowledge, others needed years of experience. Wagtail was different — their contributor guide was clear, their Slack was welcoming, and their project ideas made sense to me even as a beginner. The Demo Website Redesign project caught my eye immediately.

The Setup

I started with the basics — forking the repository on GitHub and cloning it locally. Sounds simple, but for someone who had only used Git for personal projects, working with an upstream remote was new territory.

The first real lesson came with virtual environments. I had heard of them before but never fully understood why they mattered. Setting up Wagtail's bakerydemo taught me the hard way — without isolating dependencies, things break fast. Now I get it.

What Surprised Me

I expected the codebase to be overwhelming. It wasn't. Wagtail's templates are readable, the structure is logical, and the issues tracker is active. I could actually understand what was going on — and that matters a lot when you're just starting out.

I also learned that open source isn't just about writing code. Reading issues, understanding discussions between maintainers, and following how decisions get made — that's a skill in itself.

What's Next

I'm working on my GSoC proposal for the Demo Website Redesign project. The goal is to make Wagtail's demo site more flexible and suitable for different verticals — not just a bakery, but any kind of content-driven site.

For any other first-year students reading this — don't wait until you feel "ready." Fork the repo, run the project locally, and start reading issues. That's all it takes to begin.

The deadline is March 31. Let's go. 🚀

Top comments (0)