<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Riddhig on Medium]]></title>
        <description><![CDATA[Stories by Riddhig on Medium]]></description>
        <link>https://medium.com/@riddhig1110?source=rss-0860e1e8a908------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*I4zWJluT5w2FeRrU</url>
            <title>Stories by Riddhig on Medium</title>
            <link>https://medium.com/@riddhig1110?source=rss-0860e1e8a908------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 13:51:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@riddhig1110/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Community Before Code: What I Learned About Contributing to Open Source]]></title>
            <link>https://medium.com/@riddhig1110/community-before-code-what-i-learned-about-contributing-to-open-source-df62ec1e2f81?source=rss-0860e1e8a908------2</link>
            <guid isPermaLink="false">https://medium.com/p/df62ec1e2f81</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[developer-experience]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[open-source-contribution]]></category>
            <category><![CDATA[community]]></category>
            <dc:creator><![CDATA[Riddhig]]></dc:creator>
            <pubDate>Wed, 18 Nov 2026 04:36:43 GMT</pubDate>
            <atom:updated>2026-11-18T04:36:43.135Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Sometimes, a Slack message can get you an issue assigned faster than a comment on GitHub!</em></p><p>I learnt this while exploring issues in a large open source repository. An issue I was interested in had already been assigned to someone, and they had even created a pull request. During the review, they were asked to provide a screenshot or screen recording demonstrating their changes. Since it was a CSS related change, this was a reasonable request. However, instead of providing the recording, the contributor closed the pull request.</p><p>I noticed this and decided to mention it in the project’s Slack community, pointing out that the pull request had been closed without being merged. Within minutes, I was assigned the issue.</p><p>It was a small interaction, but it changed how I looked at contributing to open source. I began to realise that there was a lot happening beyond GitHub issues and pull requests. There were real people, conversations, and communities behind the code.</p><p>And that brings me to something I had heard much earlier: C<strong>ommunity Before Code.</strong></p><h3>Where I First Heard It</h3><p>During the Codess.Cafe OSS Cohort 8, Ruchi Pakhle brought up this idea in two sessions: <em>Everything about GSoC</em> (Day 3) and <em>Everything about LFX</em> (Day 8).</p><p>A few things she mentioned stayed with me:</p><p><strong>Day 3: Everything about GSoC</strong></p><ul><li>Be active in the community. Interact, collaborate, and make your presence known.</li><li>Understand the codebase. Code comes later.</li><li>Choose a project that genuinely interests you. Skills can be learnt along the way.</li></ul><p><strong>Day 8: Everything about LFX</strong></p><p>On applications:</p><ul><li>Your work speaks for itself.</li></ul><p>On open source:</p><ul><li>Collaboration: Maintainers may not always reply.</li><li>Community: Don’t spam; be patient.</li><li>Code: Learn through YouTube, blogs, documentation, and AI tools.</li></ul><p>At the time, these sounded like good pieces of advice. But I didn’t fully understand what community before code meant until I started contributing to larger projects like Meshery.</p><h3>There Are Real People Behind Those GitHub Profiles</h3><p>When you’re new to open source, it’s easy to think of the process as a sequence of steps: find an issue, get assigned, understand the code, fix it, create a pull request, and get it merged. But that’s only one part of the process.</p><p>Popular open source projects receive numerous expressions of interest from contributors. Maintainers might have several issues, pull requests, reviews, and discussions to keep track of, alongside their own work. If ten people comment that they’d like to work on the same issue, your comment can easily get lost. Sometimes, someone else simply gets there before you.</p><p>A delayed response doesn’t necessarily mean you’re being ignored, either. Maintainers are people with their own schedules and responsibilities. This is where understanding the project’s community becomes useful. You learn where discussions happen, how contributors communicate, how maintainers prefer to be approached, and how to stay updated without constantly asking for updates.</p><h3>Every Project Has Its Own Ecosystem</h3><p>Different open source projects use different communication platforms. Some have dedicated Slack workspaces. Others use Matrix, an open communication protocol that can be accessed through clients such as Element. Some projects use mailing lists, while others maintain dedicated discussion forums. GNU Octave, for example, has a community discussion forum on Discourse.</p><p>But communication platforms aren’t the only thing that differs. Not every project uses GitHub for hosting code and managing contributions. We’re so accustomed to finding repositories, issues, and pull requests on GitHub that it’s easy to assume every project follows the same workflow.</p><p>For instance, OpenStack uses Git for version control and Gerrit for code review and patch submission, while GNU Octave uses Mercurial (Hg), a distributed version control system, rather than Git. Each project has its own tools and contribution workflow, and getting familiar with them is part of getting started.</p><p>Once I started contributing, I realised that exploring these channels and tools was just as important as exploring the codebase. Now, when I look at a new project, I try to understand how its community operates before diving too deeply into an issue. I look for contributing guidelines, communication channels, existing discussions, newcomer resources, and instructions on how to submit changes.</p><p>It helps me understand how the project works, where I can ask questions, and how I can contribute without working in isolation.</p><h3>Attend Meetings, Even If You Have Nothing to Say</h3><p>If a project organises newcomer meetings or developer meetings, attend them. You don’t necessarily have to speak or ask questions from day one. Just listen.</p><p>Pay attention to what developers are discussing, what problems need attention, and whether anyone is looking for help. You might come across a discussion related to something you’ve been exploring, or discover an opportunity to contribute that hasn’t yet made its way to the issue tracker.</p><p>These meetings also give you a glimpse into how the project works. You understand how decisions are made, how maintainers approach problems, and how contributors collaborate. Over time, people also become familiar with seeing you around. You don’t need to constantly announce that you’re looking for an issue or trying to contribute. Meaningful and consistent participation goes a long way.</p><h3>Code Matters, But So Does Everything Around It</h3><p>None of this means that writing code is less important. You still need to understand the codebase, debug problems, write tests, respond to reviews, and make meaningful contributions. You might not know the framework or programming language used by a project when you first start. That’s okay. You can learn through documentation, tutorials, existing implementations, and conversations with other contributors.</p><p>But technical skills alone don’t teach you how to collaborate. Contributing to open source also means understanding why something needs to change, discussing possible solutions, being receptive to feedback, and respecting the time and effort of other contributors.</p><p>Looking back, I think that’s what Ruchi meant by C<em>ommunity Before Code</em>.</p><blockquote>Don’t treat the community as something you engage with only when you need an issue assigned or a pull request reviewed. Be part of it. Read discussions, attend meetings, ask thoughtful questions, and help other newcomers when you can.</blockquote><p>You don’t have to know everything before joining a community. In fact, that’s often where the learning begins.</p><blockquote><strong>Because open source isn’t just about the code you contribute. It’s also about the people you build it with.</strong></blockquote><p><strong>A little note:</strong> I share my open-source journey, learnings, and cohort experiences on <a href="https://x.com/notYetConverged">X</a>. Feel free to follow along!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df62ec1e2f81" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Finding My Way into Open Source]]></title>
            <link>https://medium.com/@riddhig1110/finding-my-way-into-open-source-lessons-from-codess-cafe-5d7164c41261?source=rss-0860e1e8a908------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d7164c41261</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[open-source-contribution]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Riddhig]]></dc:creator>
            <pubDate>Fri, 06 Nov 2026 08:43:39 GMT</pubDate>
            <atom:updated>2026-11-06T09:19:13.853Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Going from searching for issues nobody wanted to getting my first code PR merged, and everything I learnt along the way!</em></p><p>I didn’t really expect to get into Codess.cafe. I filled out the application, but wasn’t particularly hopeful about getting selected. Getting accepted was a pleasant surprise. Sometimes, if it’s meant to be, it’s meant to be. And that’s also why you shouldn’t self-reject.</p><p>Before getting into my experience, if you’d like to know what sessions were conducted and what resources were shared during the program, you can check out my posts on <a href="https://x.com/notYetConverged">X</a>. This blog is a little different. I want to talk about something I wish I’d understood earlier: how to navigate the open-source world when you’re a beginner, don’t know where to start, and don’t necessarily have someone to guide you.</p><blockquote>Because reading about open source and actually making your first contribution are two very different things.</blockquote><h3>The part nobody tells you about being a beginner</h3><p>When you’ve been contributing to open source for a while, picking an issue and figuring out a codebase might seem fairly routine. But when you’re starting out, even knowing which issue to pick can be a challenge. You come across an issue, read it a few times, look at the code, and still aren’t entirely sure whether you’ve understood what needs to be done. You wonder if you’re missing something obvious. And then there’s the question of whether you’re even experienced enough to attempt it.</p><p>A big thank you to Akshita Dixit for recognising this during the mentorship and patiently walking us through a few issues. These issues had already been solved, but we discussed how we would approach them and what steps we could take if we were to work on them.</p><p>Something that stuck with me was how descriptive issues could be. Sometimes, maintainers have already explained the expected behaviour and even pointed towards what needs to change. I’d been looking at issues as problems I had to figure out entirely on my own.</p><p>That made a difference. Things seemed a little less intimidating.</p><p>So, I started looking.</p><h3>My initial strategy was to find issues nobody else wanted</h3><p>I wanted to begin with documentation fixes. They seemed relatively approachable, and I assumed most contributors would prefer working on actual code. Fewer people competing for documentation issues sounded like a good deal. Except, finding those wasn’t as easy as I’d imagined. Initially, I could only find repositories with fewer than 50 stars. Yes, I was using the number of stars as my metric for deciding which repositories to explore.</p><p>Then came another idea. Why not look for Java issues? Students seemed to be gravitating towards Python, Rust and other languages, so perhaps there would be fewer people working on Java issues.</p><p>If you haven’t noticed already, my entire approach was centred around finding something that fewer people would choose.</p><h3>My first attempt didn’t go as planned</h3><p>I finally found an issue and left a comment: <em>“</em>I’d like to work on this. Could you assign it to me?” The response was along the lines of, “Yes, feel free to open a PR.” I wasn’t added to the assignee list on the right side of GitHub, but I took the response as confirmation that I could go ahead.</p><p>I worked on the fix, only to discover that someone else had already raised a PR for the same issue by the time I was done. And this happened within half a day! It was quite disappointing. I was quite excited about finally having something to work on and now the opportunity seemed to have slipped away.</p><p>I brought this up in the Codess.cafe group, where Akshita mentioned that some maintainers are okay with contributors directly raising a PR instead of waiting to be assigned.</p><p>That made sense, especially after what had happened.</p><p>I realised that commenting on an issue doesn’t necessarily reserve it for you. And while getting assigned is reassuring, it isn’t always a prerequisite for contributing. If the issue is clear, the repository allows direct contributions, and you have something useful to contribute, there’s often no reason to wait indefinitely for an assignment.</p><h3>Getting comfortable with the PR process</h3><p>Even after that experience, I wanted to make a smaller contribution first. I hadn’t really gone through the entire process of raising a PR and seeing it get merged. So I started looking at PRs raised by my fellow cohort members. I came across the GitHub Next repository and found two documentation fixes where the required changes were already described in the issues. I worked on both.</p><p>They weren’t particularly complicated contributions, but they helped me understand the process of making changes, raising a PR and following it through to a merge.</p><p><strong>More importantly, I was no longer just reading about how contributions worked. I’d actually done it.</strong></p><p>That gave me enough confidence to start exploring larger repositories.</p><h3>My first code PR, and everything that came with it</h3><p>I started searching for issues in repositories with more stars, commenting on a few and eventually got assigned an issue in the Sentient repository. This turned out to be quite a learning experience. The repository had CI/CD workflows, so I got some exposure to working with those. It was also an active project, which meant there was plenty of back and forth once I raised my PR. My branch had gone out of date, and I ended up dealing with merge conflicts. There were reviews, changes to make and discussions to follow up on. Builds and tests also took their time to run.</p><p>It wasn’t a straightforward experience where you write the fix, raise a PR and get it merged the next day.</p><p>But the PR eventually got merged!</p><p>That felt great, not just because it was my first proper code contribution, but because I had navigated parts of the process that had seemed intimidating just a few weeks earlier.</p><p>And honestly, it felt different from the documentation fixes. Not because documentation contributions are any less valuable, but because this was the first time I’d gone through a more involved code contribution, including the parts that don’t necessarily show up in a GitHub contribution graph.</p><h3>How I started finding better opportunities</h3><p>Around this time, I also began looking at contributions people were sharing on LinkedIn and X.</p><p>If someone was sharing their contribution to a repository, that was often a good indication that the project was active and had a community where contributions were happening. I started exploring those repositories. I wanted to contribute to projects that people actually knew and used.</p><p>I also changed the way I searched for issues:</p><p>One piece of advice you’ll hear frequently is to look for good first issue labels. It&#39;s a good starting point, but there&#39;s a catch: these issues are visible to everyone looking for beginner-friendly contributions. By the time you find one, there may already be several comments expressing interest.</p><p><strong>I started looking at other labels that essentially meant the same thing but weren’t explicitly called </strong><strong>good first issue</strong>. Different projects have different conventions, and exploring those labels can sometimes lead you to issues with fewer people competing for them.</p><p><strong>I also started paying more attention to how issues were written. An issue that clearly explains the problem, expected behaviour and scope of the fix can be a much better starting point than one carrying a beginner-friendly label but offering very little context</strong>.</p><p>A few things I now check before deciding to spend time on an issue:</p><ul><li><strong>Repository activity:</strong> When was the last commit? Check recent commits and merged PRs. If there’s been little activity for months, there’s a chance your issue or PR might not receive a response either.</li><li><strong>Existing interest:</strong> Has someone already picked it up? Check the assignees, comments and linked PRs. Don’t assume an issue is available just because it hasn’t been closed.</li><li><strong>Issue description:</strong> Can you understand what needs to be done? You don’t need to know the entire codebase, but you should have some idea of the problem and its boundaries.</li></ul><h3>A word about using AI</h3><p>It’s hard to ignore how much easier AI tools have made navigating unfamiliar codebases. They can help you understand files, trace function calls, interpret errors and even suggest implementations. It’s very tempting to let them do most of the work, especially when you’re new and everything in the codebase looks unfamiliar.</p><blockquote>Some repositories explicitly require contributors to disclose which AI model they used and how. Regardless of whether a repository has such a requirement, you are responsible for the code you submit.</blockquote><p>I think it’s important to pick issues where you can at least understand the problem independently. You can use AI to help you navigate the implementation, but you should still be able to explain why your changes solve the issue and test whether they actually work.</p><blockquote>There’s little value in getting a PR merged if you don’t understand what you’ve contributed.</blockquote><p>The goal is to learn how these projects work, not just to add another entry to your contribution history.</p><h3>So, was Codess.cafe worth it?</h3><p>Absolutely!! When I applied, open source felt like something I was supposed to know how to do already. I knew about GitHub, repositories, issues and PRs, but knowing what these things meant and knowing how to navigate an actual project were two different things. The mentorship helped bridge that gap.</p><p>Jyoti Bisht had said something at the beginning that I kept thinking about throughout the program:</p><blockquote><em>“Open source is daunting, but we will make it less daunting.”</em></blockquote><p>And they really did.</p><p>I’m still figuring things out, but I no longer look at open source as something that’s out of reach.</p><p>If you’re in a similar position, I’d say apply for that mentorship, explore that repository, or attempt that issue you’ve been going back and forth on.</p><p><strong>Your first contribution doesn’t have to be impressive. Mine started with two documentation fixes.</strong></p><blockquote><strong>You don’t have to know everything to begin. You just have to stop waiting until you’re ready.</strong></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d7164c41261" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>