Hey folks! 🙋🏻‍♂️

Hope you're doing well! 🙌🏻

As you would have read the title of the Blogpost, It's gonna be about Open-Source, and with the little knowledge I have as of now I'll cover in this Blogpost (OSS related)

So, Are you excited to experience the Open-Source Matrix? 😃

Let's Go! 🚀

What exactly is Open-Source? 💭

Although Open-Source is a much broader field, To say it in simple words and not using tech jargon, Open-Source means that an individual can make valuable changes to the project which is accessible to the public and these changes can be Documentation or Code.

And with this, comes the term - Open Source Software (OSS)

Decoding Open-Source Software 💻

Open-Source Software is just one word - "Source Code" which is publicly available and accessible and to which an individual can make changes to and improve the software for that specific part.

Okay! So enough with the definitions, let's take a look at what is happening in the real world with the Open-Source and its Source Code (to say so).

Suppose, I have been using an application called Wurph (spoiler alert) and, let me explain its concept to you in just a few lines, So whenever you receive a Woof then, you get a fax, text message, and socials messages notifications simultaneously regarding the Woof.

But, there is a bug that I found using Wurph and that was, whenever I received a Woof, I am not getting it on my particular social account.

So, I gave my time to understand Woof's codebase and found and fixed the bug. And Woof, I mean Boom! The Issue is fixed!

How do we make these changes and what are they Called?

Just one Word - Open-Source Contributions 👇🏻

Open Source Contributions 🚀

Open-Source Contributions are the changes made to the project that enhances the project's quality for that specific field/part and are called Open-Source Contributions.

How do we make Open-Source Contributions? 💭

Yep, That's a valid question and without beating around the bush, Let's jump straight into it.

I created a static webpage for this purpose (Blogpost) called Open-Source-Matrix. Here's the link

It guides a beginner and helps them make their first-ever open-source contribution.

There is a section on Issues on every GitHub repo. This Issues section will take you to all the Issues waiting to be resolved by folks.

For beginners, It's best to start with the Good-first Issues.

Do I have to make Code Contributions only? 🤔

Well, Nope!

Most of the folks start their Open-Source Journey by:

1. Fixing Typos

2. Improving the Documentation.

3. Translating the README File or such file into their Native language or any language they know for more reach of the Project.

4. Writing Documentation.

and the list goes on and on and on...

The point is that your Contribution doesn't need to always be a Code Contribution. That's the beauty of Open-Source.

Best-Practices based on my own Experience! 🌟

These are the Best-Practices that I came to know about when I explored Open-Source and are based on the Contributions I made:

• Read the Contributors file:

  This is the most critical file in the Entire Project that I would recommend a Newcomer to look for in the Project if he/she is exploring that project for the first time.

  The purpose of this File is to Inform the Contributor about Some guidelines and rules to follow before Contributing to the Project.

  Almost every Good Project has this File.

• Writing descriptive Commit messages same goes for Pull Requests:

  While writing the Commit Messages make sure that you write Descriptive Commit Messages that sets up the context when the Maintainer of the Project reads it.

  The same goes for Pull Requests, But here's a catch, You can make your Pull-Request Stand out Just by making a few changes:

  1. Add the ScreenShot of the Changes you made: Add the Image of the Final Outcome before your Change and After Your Code Change.

     Doing so, Makes your Pull Request look Different and Explainable about the Changes you made.

  2. Follow the Template (If any): Almost Every Good Project has a Template that the Contributor Sees at the time of Making the Pull Request.

     Therefore, Contributor Should answer the Questions asked in the Template Sincerely as It is both Professional and helps out the Project Maintainer to Read those answers if everything is good and all then, You'll get your Pull Request merged! (The best feeling!).

There are many Other Best-Practices for you to follow but, as of now, It's good for you to focus on these and get comfortable with them. 🔥

I would like to wrap this blog post up with a quote from an unknown person (maybe me?) about Open-Source.

"Open-Source is not a Race, It's a Marathon!"

- Unknown

If you've read this far then Thanks for the Read!

Also, Since you have read this blog post regarding Open-Source then, I think that we should also Connect on Twitter there, I share my thoughts about Open-Source, Software Development, blogging, and Random Tech stuff :)