DEV Community: Ananya

🎉First PR? Get paid for it

Ananya — Wed, 01 Apr 2026 18:55:05 +0000

Introducing Dollar Deletions — a special campaign only for first-time contributors.

We know large codebases can be intimidating, so we are paying you $1 for your first accepted Pull Request where you safely delete unused or legacy code.

👉 Why are we doing this?

We are preparing for a major migration! To do this safely, we need to thoroughly clear out the existing repository. Your deletions will help us sweep away all the old files so we can seamlessly move our brand-new system into the clean repo.

🧹 Clean up real production code
🧠 Learn how large codebases work
🚀 Make your first open-source contribution
💵 Earn your first dollar online

How it works

Find dead or unnecessary code in our repository.
Submit your first-ever PR to remove it.
Pass the code review (your changes must not break existing functionality).
Get $1 via GitHub Sponsors!

📌 The Rules

This campaign is only for first-time contributors to this repo.
Your PR must include a clear explanation of what you removed and why.
The code must remain fully functional after your deletion.
Limited to one reward per contributor.

🏆 Bonus: Referral Leaderboard!

Spread the word and climb the ranks! You can refer others to this initiative. Just have the PR mentioning that you are referring a contributor as @user1 refers @user2 and link that PR to our mega issue. This will track the mention and boost @user1's rank on our referral leaderboard.

💡Not sure where to start? Look for issues labeled good-first-deletion to get your bearings.

👉Start here: OWASP-BLT/BLT

Your first PR shouldn’t be scary—it should be rewarding. We can't wait to review your code!

The Architecture of Ideas: My GSoC 2026 Proposal Journey

Ananya — Wed, 01 Apr 2026 18:29:37 +0000

The Google Summer of Code 2026 application window has officially closed, and after a month of intense drafting, reviewing, and refining, I have finally hit "submit" on my three proposals.

The last 30 days have been a blur of markdown files, system architecture diagrams, and deep dives into codebases. Moving from an active contributor to a prospective GSoC student was a significant leap. It wasn't just about proposing new features; it was about thoroughly understanding the underlying architecture of the projects, aligning my ideas with the maintainers' long-term goals, and proving that I had the technical agility to execute the vision.

From Commits to Comprehensive Plans📝

Earlier, I wrote about the "momentum of the merge"—that rewarding shift from planning to actively living within the repositories. This past month put that momentum to the test. Writing distinct proposals meant compartmentalizing different problem spaces. It required me to step back from fixing immediate bugs and start thinking about the software lifecycle over a 12-week timeline.

I had to map out weekly deliverables, anticipate potential technical roadblocks, and clearly communicate my logic. It forced me to be objective about my skills and realistic about my timelines.

The Real Win 🏆

There is a unique kind of exhaustion that comes from writing a technical proposal, but it is heavily outweighed by the clarity it brings. Regardless of the final selection results, the growth over this past month has been invaluable. The gap between having a good idea and writing a resilient project plan is where the real engineering growth happens.

A huge thank you to the mentors who patiently reviewed my drafts and the communities that welcomed my initial pull requests. Now, the waiting period begins, but the daily rhythm of open-source contribution doesn't pause here.

Let’s keep building. 🚀

Let's have a deep dive on my idea that gave our OWASP BLT community a a dashboard for navigation and detailed insight.

Ananya — Mon, 23 Mar 2026 17:27:34 +0000

Ananya

Mar 23

Visualizing the OWASP BLT Ecosystem: From Idea to the live Navigation 📊✨

#opensource #gsoc2026 #summerofcode #owaspblt

Comments

2 min read

Visualizing the OWASP BLT Ecosystem: From Idea to the live Navigation 📊✨

Ananya — Mon, 23 Mar 2026 17:25:47 +0000

In the world of open source, growth is a double-edged sword. As the OWASP BLT ecosystem expanded, we found ourselves with a beautiful but complex collection of repositories, each serving a vital purpose. However, for a seasoned contributor-finding the right repo was starting to feel like navigating a maze without a map.
This realization sparked an idea: What if we had a dashboard? A central hub designed specifically to act as the "North Star" for the OWASP BLT's Universe, guiding every developer exactly where they need to be.

How it started 🕵️

I proposed the idea to the team, the idea of having a dashboard as a central navigation to the BLT's vast expanding project network. What began as an idea quickly turned into a collaborative project. I’m incredibly grateful to our Lead Mentor, Donnie, for believing in the vision. He didn't just give the green light; he helped turn that idea into a working repository base: setting up the initial site structure, CI hooks, and a minimal content layout. With that scaffolding in place, we could focus on features rather than plumbing.

Iterative development and key features 💻

Since those early commits, we’ve been working steadily to turn OWASP BLT Organization Dashboard into a true compass for the project. We adopted an incremental approach: build a small, stable core, then add features one at a time.

Highlights include:

Project listing and metadata to surface each BLT repo with links, descriptions, and status.
Search and navigation improvements to help newcomers find what they need.
Accessibility and responsive design to make the Waypoint usable on any device.
and more to come...!

Open source is at its best when a simple suggestion is met with active mentorship. Building this project has taught me that open source is as much about the "architecture of ideas" as it is about the code itself.

This Waypoint is now live, and we’re just getting started.

Check out the progress here: https://github.com/OWASP-BLT/owasp-blt.github.io

Designing the Face of OWASP BLT: Three New Creative Challenges 🎨✨

Ananya — Fri, 20 Mar 2026 15:33:34 +0000

If you’ve been following our journey, you know that OWASP BLT is evolving. We’re streamlining our mission and modularizing our code, but a project is only as strong as its identity. We want the "front door" of our project to reflect the innovation happening behind the scenes.

We are officially inviting the creative community to help us redefine our look and community interaction through these design contests:

1. The Video Meme Contest 🎬

Who says security has to be serious all the time? We’re looking for the most creative, relatable, or just plain hilarious video memes that capture the "bug hunting" struggle or the spirit of the OWASP community.

Prize: $10
Deadline: April 15, 2026

👉 View Video Meme Contest Details

2. The Logo Design Contest 🕵️

The OWASP BLT logo is more than just an icon; it’s a symbol of security and community accountability. We’re looking for a fresh, modern take on our visual identity. Whether you’re a minimalist or a fan of bold, "hacker-y" aesthetics, we want to see your vision.

Prize: $25
Deadline: April 15, 2026

👉 View Logo Contest Details

3. The Homepage Redesign Contest 💻

We want our landing page to be as intuitive and high-performance as the tools we build. This is a challenge for the UI/UX enthusiasts—how would you structure the first experience a researcher or contributor has with BLT? Show us your layouts, your transitions, and your vision for a better user experience.

Prize: $25
Deadline: April 15, 2026

👉 View Homepage Contest Details

Why get involved?

Open source isn’t a gated club for "genius coders." It’s a space for anyone who wants to build something that matters. By participating in these contests, you’re not just submitting a file; you’re interacting with the OWASP BLT repository, getting your name on the contributor list, and helping us shape the future of the project.

Start small, design bold, and let’s see what you can create.

The Transition: From Intent to Integration

Ananya — Wed, 11 Mar 2026 18:15:45 +0000

I had defined my "why" and mapped out a vision for GSoC 2026. However, the last few weeks have shifted my focus from the abstract goal to the granular reality of open-source contribution. The momentum I gained from the past few months of contributions, has evolved into a disciplined daily rhythm.

The gap between planning and execution is where the most significant learning occurs. In my previous update, I spoke about the "Plan." Since then, I have moved past simply archiving organizations to actively living within the repositories of OWASP BLT. I will share more insights on those in the upcoming posts.

The Recent Progress

A major technical highlight of these past two weeks was my deep dive into HTMX. While my foundation in the MERN stack is solid, exploring HTMX allowed me to view web development through a different lens—focusing on simplicity and high-performance transitions without the overhead of heavy JavaScript frameworks.

I successfully implemented a project using HTMX, which served as a practical laboratory for my learning. This experience taught me that being an engineer isn't just about sticking to what you know; it’s about the agility to adopt the right tool for the specific problem at hand. Integrating this into my workflow has made my contributions more versatile and informed.

The Momentum of the Merge

The most rewarding aspect of this period has been the "merged" status on my Pull Requests. There is a specific kind of validation that comes from having code reviewed by experienced maintainers and then integrated into a real-world repository. Each merged PR represented a hurdle cleared—whether it was navigating a complex file structure, adhering to strict coding standards, or resolving merge conflicts that initially seemed daunting.

Through this process, I have begun to overcome the hesitation I previously mentioned. Being active on GitHub and participating in PR discussions has forced me to communicate my logic clearly and accept feedback professionally. I am no longer just a spectator in these communities; I am a contributor, or better say an "Active Contributor"

Revamp of the main BLT home page as BLT Pages

Being involved in the launch of the new BLT Pages home page from both a development and a strategic perspective provided a holistic view of software delivery. It taught me that a successful launch requires more than just clean code; it requires a narrative that connects the technology to the user. This experience has been pivotal in addressing my previous goal of improving proactive communication and overcoming my hesitation in professional settings.

Technical and Community Growth

My commitment to upskilling remains a constant. While I work on the frontend and strategy for BLT, I continue to strengthen my backend capabilities and practice Data Structures and Algorithms in C++. My roles in GDG on Campus and the FLUX Society continue to provide a necessary balance, reminding me that while coding is often a solitary act, building great software is a communal effort.

Looking Ahead

The next few weeks will be about sustaining this velocity. The momentum from the last fourteen days has replaced the "magic" of open source with something more sustainable: the confidence that comes from consistent, meaningful work.

I will continue to deepen my involvement with the BLT core team, ensuring the momentum of the new home page launch is maintained. I am also beginning to translate these practical experiences into the initial framework of my formal GSoC proposal, using my recent contributions as a proof of concept for my potential as a long-term contributor.

See you in the next post. Let's make it happen!

A New Chapter for OWASP BLT: Our Website Revamp is Live! ✨

Ananya — Wed, 04 Mar 2026 04:33:53 +0000

We are thrilled to announce that the new OWASP BLT site at owaspblt.org is officially live. This revamp isn't just about a fresh coat of paint; it’s a complete reimagining of how we interact with our community. The new interface is designed to be intuitive, making it easier than ever for researchers and contributors to navigate bug logs and engage with our security tools.

While we look toward the future with this new UI, our roots remain deep in the open-source community. This project has been active for over a decade, including eight years of participation in Google Summer of Code (GSoC). This long history has allowed us to collaborate with brilliant students worldwide, helping us evolve from a large, complex codebase into the streamlined, mission-driven ecosystem we are today.

A core part of this evolution is our move toward absolute security in responsible disclosure. Our involvement with OWASP led us to develop BLT Zero, a pioneering Zero Trust vulnerability reporting platform. By ensuring sensitive details are never stored on a central server, we’ve created a disclosure process that is inherently resistant to compromise—a standard that is now reflected in our new digital home.

To support this growth, we are migrating key components of our architecture into independent repositories, making it simpler for new contributors to get involved. We invite you to explore the new site, Join our Slack, or submit a pull request. Together, we’re building a more secure and transparent internet for the next decade and beyond. 🚀

Happy to share my submission for the OWASP BLT Design Contest! 🚀

Ananya — Tue, 03 Mar 2026 07:45:18 +0000

As a designer, it’s a privilege to contribute to a project that makes the web safer for everyone. This was a great challenge that pushed me to think about security and usability in new ways.

This felt like the perfect opportunity to blend design with a great cause like internet security.

It’s been a fun journey refining this entry. Feel free to take a look, and if you're a fan of the design, a thumbs up (👍) on the GitHub issue would be greatly appreciated!

👉 Design Attempt

Your first Open Source contribution could be a T-shirt design

Ananya — Tue, 24 Feb 2026 00:07:58 +0000

What if your first step into open source didn’t involve debugging backend code or trying to wrap your head around a massive, complex architecture? What if it actually started with a T-shirt?
It sounds a bit wild, right?

At OWASP BLT, we’ve already seen some crazy creative work from our community, so turning that energy into merch just felt right. We’re opening up a design contest because we want to see your personality in the project. And no, this isn't one of those situations where you submit your art and disappear into a void.

We need an original design that captures the grit and the community of OWASP.

We’re talking:

Minimalist sleekness that screams "Pro Dev."
Bold graphics that pop on a dark hoodie.
Clever security references only the "in-the-know" will catch. Pure creative chaos.

The "Bounty"

Winner’s Award: $25 (and the glory of seeing your design on the community).
Hard Deadline: Submit your masterpiece by March 1, 2026.

The Workflow: Submit via GitHub

We’re keeping it open-source. No boring forms—just the tools you already know:

Craft your design (high-res, please!).
Initialize: Open a GitHub Issue using our Design Submission template.
Document: Include a preview and a brief "commit message" (description) of your concept.
Signal: Community reactions (👍, ❤️, 🚀) are the ultimate "social proof" and will help us crown the winner.

You create a design, you submit it as a GitHub issue, it appears on the showcase, and people vote on it. Just like that, you’re officially inside an open source project.
Yes. Through a T-shirt.

Design something cool. Something hacker-y. Maybe something that screams “squash those bugs.” When you submit it as an issue, you’ll see your name appear in a real repository. Honestly, that feeling is worth more than the prize itself.
Speaking of which, there is a $25 award for the winner, but that’s really just the side quest reward. The real unlock here is the confidence. Once you hit "submit," you’ve crossed a barrier most people never do. You’ve learned how issues work and stepped into a global community.

And if you’re looking at the bigger picture, OWASP BLT is participating in Google Summer of Code (GSoC) 2026. This contest is one of the easiest entry gates you’ll ever find to get to know the maintainers and the project's energy before the GSoC season really kicks off.

So, start small. Stay curious. See where a simple design can take you.

Ready to leave your mark on the repo? 👉 Click here for full details & submission info

The GSOC Trojectory: From first line of code to the final commit

Ananya — Mon, 23 Feb 2026 18:20:27 +0000

The Decision

For me, Google Summer of Code is not just another task on a to-do list—it is a dream I have held since I first stepped into college. GSoC was actually the first programming program I ever heard about, and I was immediately fascinated by the concept. The idea that a student could contribute to massive, real-world codebases without actually being hired by the company felt like magic. It was a feeling of pure excitement.

My journey began with curiosity. During my first year, I started exploring the world of open source and GSoC. While my initial understanding was limited, it sparked a genuine desire to learn. I spent that year mastering the fundamentals of programming, leaning C, and practicing python, feeling a sense of accomplishment with every new concept I grasped. I was genuinely happy to simply be coding, and as time passed, my excitement for software development only grew.

However, the path was not without its failures. In my second year, I attempted to engage with several organizations, but I faced a harsh reality: I could not understand the codebases. As a beginner in web development, the complexity of real-world software was overwhelming. Despite my efforts, I was unable to secure a spot in GSoC 2025.

Rather than letting this setback define me, I used it as a catalyst for growth. I dedicated the following months to rigorous upskilling. I focused on mastering the core technologies of modern web development, including React, Node.js, Tailwind CSS, and Bootstrap. Crucially, I also became proficient in version control using Git and GitHub, which is the backbone of collaborative development.

The turning point arrived in September 2025, during my third year. I officially entered the open-source ecosystem participating and successfully completing in GirlScript Summer of Code (GSSoC) 2025. This experience was pivotal; it was the bridge that took me from merely learning concepts to actively contributing to a community. That momentum has brought me here, ready to tackle GSoC 2026.

Who Am I?

I am currently a pre-final year student pursuing a BTech.

My technical foundation is rooted in Web Development, specifically with the MERN stack, and modern CSS frameworks like Tailwind and Bootstrap both. I have wore Currently, I am expanding my problem-solving capabilities by mastering Data Structures and Algorithms (DSA) in C++. I also possess strong proficiency in Version Control Systems (Git & GitHub), which allows me to manage code and collaborate effectively within development teams.

Beyond coding, I am deeply committed to community building. I serve as the Co-Lead of GDG on Campus MMMUT and as an Executive Member of the FLUX Society. These roles have taught me the value of teamwork and leadership—qualities I believe are essential for open-source collaboration.

My Goals

My primary objective extends beyond simply securing a spot in GSoC; I aim to evolve into a more capable engineer. From a technical perspective, I am focused on bridging the gap between personal projects and professional software. This means developing the ability to navigate and understand large, complex codebases and significantly strengthening my backend development skills. I want my contributions to be substantial and meaningful, ensuring they add real value to the project rather than just scratching the surface.

Equally important is my personal growth regarding communication. I often struggle with hesitation when it comes to public channels, fearing that my questions might appear trivial or simple. I intend to overcome this barrier and learn to communicate proactively with mentors, asking the necessary questions early in the process rather than struggling in silence.

Ultimately, I view GSoC not as a final destination but as a starting point. Despite the limited time I have remaining in my college journey, I am committed to becoming a long-term open-source contributor. I want to experience the true essence of collaborative development and leave a lasting impact on the open-source community before I graduate.

The Plan

While I could quantify my commitment—aiming for at least two hours on weekdays and four on weekends—those are simply numbers. The reality is that I intend to dedicate all my available free time to this pursuit. I am driven by a desire not just to crack the program, but to immerse myself in a learning environment where I can grow. Regardless of where I started, I want to prove to myself that with enough dedication, I can master these skills and excel in the open-source ecosystem.

My immediate roadmap is clear. I will begin by navigating the official Google Summer of Code archives and using community tools to filter and shortlist organizations that align with my current skill set. Once I identify one or two target organizations, my focus will shift to reading their documentation and understanding their codebase. The first major technical milestone will be successfully setting up the development environment on my local machine, followed by identifying and solving "Good First Issues."

To maintain accountability, I believe in documenting the process. This blog is my commitment to that journey.

See you in the next post. Let's make it happen!