<?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"><channel><title><![CDATA[speakstothepoint]]></title><description><![CDATA[speakstothepoint]]></description><link>https://jagruti.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Tue, 08 Sep 2026 04:04:30 GMT</lastBuildDate><atom:link href="https://jagruti.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[5 things no one told me when I made my first open-source contribution]]></title><description><![CDATA[As a beginner, open-source projects can seem intimidating. 
Here are a few things I wished someone had told me when I started out.
1. Selecting the right project
It all starts with a purpose. Which skill you are looking to acquire, and what technolog...]]></description><link>https://jagruti.hashnode.dev/5-things-no-one-told-me-when-i-made-my-first-open-source-contribution</link><guid isPermaLink="true">https://jagruti.hashnode.dev/5-things-no-one-told-me-when-i-made-my-first-open-source-contribution</guid><category><![CDATA[Open Source]]></category><category><![CDATA[Beginner Developers]]></category><category><![CDATA[#codenewbies]]></category><dc:creator><![CDATA[Jagruti Tiwari]]></dc:creator><pubDate>Sat, 05 Mar 2022 09:40:31 GMT</pubDate><enclosure url="https://cdn.hashnode.com/res/hashnode/image/upload/v1646470967014/twZd1HOyt.jpg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>As a beginner, open-source projects can seem intimidating. </p>
<p>Here are a few things I wished someone had told me when I started out.</p>
<p><strong>1. Selecting the right project</strong></p>
<p>It all starts with a purpose. Which skill you are looking to acquire, and what technology interests you. </p>
<p>Staying motivated is difficult if you are not interested in what you do. <a target="_blank" href="https://www.freecodecamp.org/news/why-i-abandoned-online-data-courses-for-project-based-learning-17e350fd9347/">freeCodeCamp blog</a> emphasizes on the importance of choosing right projects.</p>
<p>As a beginner, look for issues with the labels <code>first-timers only</code> or <code>beginner-friendly</code>.</p>
<p>These issues have detailed instructions about the problem and solution. Great for a beginner to start with. </p>
<p>Don't lose hope if you preferred a repository that didn't have issues with these labels. You can keep coming back or ask for help in the community developer's group. </p>
<p><strong>2. I don't understand a thing</strong></p>
<p>Okay. So now you have found an issue you partially understand. Now what? </p>
<p>How to find the relevant code about the issue? What do you do when you don't understand something?</p>
<p>Ask. </p>
<p>You can comment on the issue or post it in the developer's community. </p>
<p><strong>3. I don't know Github</strong> </p>
<p>The <code>read.me</code> usually have instructions to set up projects. </p>
<p>After setting up, basic commands that you need to learn are:</p>
<ul>
<li><p>creating a new branch</p>
</li>
<li><p>committing your code</p>
</li>
<li><p>setting an upstream</p>
</li>
<li><p>making a pull request</p>
</li>
</ul>
<p>Not to mention there is always learning on the go.</p>
<p><strong>3. What should I do next? </strong></p>
<p>Congratulations on making your first pull request. It's okay if you haven't yet. You will be there soon. </p>
<p>After the first PR is merged what is next? What issues should you approach? </p>
<p><code>help-wanted</code> labels are open to everyone. Comment on those issues. </p>
<p>Make sure there are no PRs waiting to be merged on those issues, and no one else has taken it up.</p>
<p>The rule is: Don't be afraid to ask. </p>
<p><strong>4. Who do I ask?</strong></p>
<p>A developer's forum is the best place. </p>
<p>You can get the links where the developer's hangout from the <code>read.me</code>. </p>
<p>Don't overlook the <code>read.me</code>. It's there for a purpose.</p>
<p><strong>5. What else should I know</strong></p>
<p>A few things go without saying. </p>
<p>Be respectful and nice to everyone you are interacting with. Value their time and yours. . 
All your queries might not be answered all the time. Be patient.</p>
<p>One project contains multiple repositories. When running out of issues explore other repositories.</p>
<p><br /></p>
<p>Open-source is more than making your Github profile green. </p>
<p>It is an opportunity to collaborate and network. The returns are compound.</p>
]]></content:encoded></item></channel></rss>