\
Open source has always been an amazing place to learn, collaborate, contribute and build. Having been a part of many open source communities, events, and organizations, I have realized that people slowly and steadily understand the potential of open source as the future of technology. 

\
However, they often get confused regarding the workflow in open source projects and communities and end up making mistakes that lead to not-so-good contributions. Thus, they often get stuck in a loop of code reviews and changes before they ever make a meaningful or effective contribution to a project.

\

:::info
**Note:** This article can only be helpful if you are familiar with the basic git terminology and have an understanding of the initial workflow of using Git and GitHub.

:::

\
Here are some of the best practices that you can take up for your next contribution!

## Culture and Communication

Open source communities are a big pool of people from different social and ethnic backgrounds, races, religions, and languages. Thus, the best way to walk along with everyone would be to practice empathy.

\
* Always ensure that your tone stays friendly and respectful during a discussion.
* Try to adapt your language to non-native English speakers as they might find the environment challenging or intimidating at times.
* Stay humble and modest. None of us know everything. We are all learning. Some developers might need help with something that is very basic, be kind and extend a helping hand whenever you can.

[ \n  ![Remote Work Culture](https://cdn.hackernoon.com//images/MUo6MihNAVUIcUvRBbcToKZ7MKh1-2022-04-14T17:52:38.759Z-cl1zaue7b000g0as6ajat4rnv)](https://res.cloudinary.com/practicaldev/image/fetch/s--L3sVuHmE--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://cdn.hashnode.com/res/hashnode/image/upload/v1620929342550/vBKmgHn93.jpeg)

* Try to learn as much as possible, devote time to explore the codebase, and attempt to understand things before you ask a question on a public channel or open an issue. Regardless, if you seem to be stuck with anything, do not hesitate to ask questions to fellow developers. Likewise, do respect the space and the questions put up by others.
* Be nice and welcoming. Appreciate your fellow developers and contributors, for they did a good job. Extend a **" please "** or **" thank you "** in a discussion to express politeness and generosity.

[ \n  ![GitHub Discussions](https://cdn.hackernoon.com//images/MUo6MihNAVUIcUvRBbcToKZ7MKh1-2022-04-14T17:52:39.689Z-cl1zauex5001e0as6dx5m267i)](https://res.cloudinary.com/practicaldev/image/fetch/s--Gg9Xxe4f--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_66%2Cw_880/https://github.blog/wp-content/uploads/2016/03/d55b8b7e-e6ba-11e5-9b31-59a8db92e456.gif%3Ffit%3D917%252C359)

## Communication Channels

Most open-source communities have their own private or public communication channels like Slack, Discord, Gitter, etc, as chatting is a great way to connect with other contributors and maintainers.

[    ![GitHub Discussions](https://cdn.hackernoon.com//images/MUo6MihNAVUIcUvRBbcToKZ7MKh1-2022-04-14T17:52:39.689Z-cl1zauex5001d0as63of934x0)](https://res.cloudinary.com/practicaldev/image/fetch/s--R5F7HFQv--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_66%2Cw_880/https://cdn.hashnode.com/res/hashnode/image/upload/v1620929791597/WxvGy_4Ys.gif)

To use these channels effectively, contributors should try to follow the below points:

* Do not switch to private communication with a maintainer or fellow contributor until and unless necessary. This shuts out other contributors who might be facing the same issues and can get help straight away by reading the earlier conversation.
* Do not discuss feature requests or bug reports over chat, as they are best handled over GitHub or Issue Tracker.

## Feature Requests and Bug Reports

Feature Requests and bug reports are best handled over GitHub, but one must follow certain steps to use them constructively:

[ \n  ![Creating Issues on GitHub](https://cdn.hackernoon.com//images/MUo6MihNAVUIcUvRBbcToKZ7MKh1-2022-04-14T17:52:39.497Z-cl1zauert001c0as6eng99chp)](https://res.cloudinary.com/practicaldev/image/fetch/s--vrq1x2xh--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://cdn.hashnode.com/res/hashnode/image/upload/v1620928822105/PNfx55FDh.png)

* For any bug or feature, no matter how small or big, open an issue with all the necessary details, and don't forget to indicate if you're interested in working on it.
* Try to include all relevant information when you submit an issue so as to help others understand it easily. Include links, information about the code that has to be changed, and screenshots wherever necessary.
* Break down big feature requests into smaller issues so that more than one contributor can simultaneously work on them.
* Always remember to add steps to reproduce the bug that you are reporting while submitting a bug report.

  \

> Most open source projects use [Issue templates](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates) for Feature Requests and Bug Reports. This can be used as a reference for the details that should be mentioned while submitting an issue.

\
[ \n  ![Issue Templates for various Issue Types](https://cdn.hackernoon.com//images/MUo6MihNAVUIcUvRBbcToKZ7MKh1-2022-04-14T17:52:39.491Z-cl1zauern001b0as6cv366lq3)](https://res.cloudinary.com/practicaldev/image/fetch/s--GHR-oj8E--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://user-images.githubusercontent.com/877585/64684565-3c595a00-d47d-11e9-8ea4-589cffa16375.png)[ \n  ![Template for a Bug Report](https://cdn.hackernoon.com//images/MUo6MihNAVUIcUvRBbcToKZ7MKh1-2022-04-14T17:52:39.490Z-cl1zauerm001a0as653pz4jnw)](https://res.cloudinary.com/practicaldev/image/fetch/s--E9C0ymWn--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://vgpena.github.io/images/github-templates/good-issue.png)

## Development

Once you have decided on the open-source project that you want to contribute to, the first step, to begin with, would be to set up the project on your local machine and run it. The steps are usually defined in the `README.md` file. The next step would be to go through the branch policies and [contributing guidelines](https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/accessing-a-projects-community-profile) of that project. These can be easily found inside the `CONTRIBUTING.md` file. Once you are done, you can begin with the changes in the project.

[ \n  ![Setup Instructions in the Readme](https://cdn.hackernoon.com//images/MUo6MihNAVUIcUvRBbcToKZ7MKh1-2022-04-14T17:52:39.485Z-cl1zauerh00190as662w6ddre)](https://res.cloudinary.com/practicaldev/image/fetch/s--j-uW6ZRO--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://cdn.hashnode.com/res/hashnode/image/upload/v1620930564126/Jfng7D8_I.png)

Meanwhile, during development, if you have any doubts or come across any challenges, feel free to ask questions from the maintainers or fellow contributors. (You can either use the communication channel or keep the conversation going over GitHub.)

## Commits and Pull Requests

Most first-time contributors are hesitant or fearful of making a PR, although there's no need to be afraid. Just keep a few things in mind while making your PR to get a quick code review and feedback:

* Write meaningful commit messages that convey what changes have been made. For example:[ \n  ![Commit Message Format](https://cdn.hackernoon.com//images/MUo6MihNAVUIcUvRBbcToKZ7MKh1-2022-04-14T17:52:39.013Z-cl1zaueed00180as6cb3u46xz)](https://res.cloudinary.com/practicaldev/image/fetch/s--ukyZexQE--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://neighbourhood.ie/assets/blog-images/semrel-1.png)
* Ensure that you use the minimum number of commits for a change. If you have a lot of commits for a small fix, [squash](https://levelup.gitconnected.com/how-to-squash-git-commits-9a095c1bc1fc) them before making a PR.

[ \n  ![Squashing Commits while merging a PR on GitHub](https://cdn.hackernoon.com//images/MUo6MihNAVUIcUvRBbcToKZ7MKh1-2022-04-14T17:52:39.012Z-cl1zaueec00170as6e8b2bpha)](https://res.cloudinary.com/practicaldev/image/fetch/s--6Mn16xs7--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_66%2Cw_880/https://user-images.githubusercontent.com/2996465/57393418-a8068000-7188-11e9-9167-2471a634a47c.gif)

* Make only the changes in the PR that were mentioned in the issue. Do not change anything else that is not relevant to that particular issue.
* Always link your PR to the issue that it fixes. Learn how to do it [here](https://docs.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#:\~:text=On%20GitHub%2C%20navigate%20to%20the,to%20link%20to%20an%20issue.).

[ \n  ![Linking a PR to a related Issue](https://cdn.hackernoon.com//images/MUo6MihNAVUIcUvRBbcToKZ7MKh1-2022-04-14T17:52:39.012Z-cl1zaueec00160as6bes04y89)](https://res.cloudinary.com/practicaldev/image/fetch/s--zZUovQpq--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://cdn.hashnode.com/res/hashnode/image/upload/v1620930949750/78DUGiXhd.png)

* Make PRs from your own forks (even if you have the rights to the repo, do not create new branches, develop on your own branches).
* State the actual enhancements or changes done in the PR rather than just mentioning `Fixes #1`. Refer to the PR template for details to be mentioned if the project has one.
* Remember to add a screenshot or video if you have made any UI changes. This boosts the review process exponentially.

[ \n  ![Adding Screenshots for UI changes in GitHub Issue or PR](https://cdn.hackernoon.com//images/MUo6MihNAVUIcUvRBbcToKZ7MKh1-2022-04-14T17:52:39.011Z-cl1zaueeb00150as68ixkhbdy)](https://res.cloudinary.com/practicaldev/image/fetch/s--9GZ_4RgE--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_66%2Cw_880/http://www.kianyang.co/wp-content/uploads/2018/01/blog_git_commit_v2.gif)

* Help reviewers solve merge conflicts if any. Read more about merging conflicts [here](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts).

[    ![Resolving Merge Conflicts on GitHub](https://cdn.hackernoon.com//images/MUo6MihNAVUIcUvRBbcToKZ7MKh1-2022-04-14T17:52:38.904Z-cl1zauebc00140as6evvw5c38)](https://res.cloudinary.com/practicaldev/image/fetch/s--GeUHsCGN--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_66%2Cw_880/https://github.blog/wp-content/uploads/2016/12/fd64b010-c06b-11e6-9dd3-a827e299c5bf.gif%3Ffit%3D1360%252C426)

## Documentation

Everything in open-source space happens through an exchange of words. Thus, documentation stands as a crucial step to provide information about your contribution.

\
> Documentation is a continuous effort at every step of software development.

\
* Add information on the new technologies, frameworks, libraries, and the code via comments and into documentation files, e.g., into the `README.md` or `/docs` folder.
* Always keep documentation up to date and make it easy for new contributors to join the project.

  \

Last but not least, open-source is a collaboration between many different people with many different priorities, and sometimes, you got to wait until the right time. Other people working on a project likely have very different lives than you, and their priorities may not match yours. Work projects, vacations, and family are some of the most common things that can push back a response to your needs, and patience is the best way to deal with it. Since great things are worth the wait, never mind the delay.

\
This is all that I learned along my journey in open-source. I hope that the practices mentioned above take you closer to your next **(effective)** open-source contribution and help you fulfill your chance to give back to the community, one commit at a time!

\
If you find this insightful, do let me know your views in the comments. Also, any kind of feedback is welcome. In case you want to connect with me, follow the links below:

\
[LinkedIn](https://www.linkedin.com/in/pragativerma18/) | [GitHub](https://github.com/PragatiVerma18/) | [Twitter](https://twitter.com/pragati_verma18) | [StackOverflow](https://stackoverflow.com/users/10364459/pragati-verma)

\
Also published [here](https://dev.to/pragativerma18/open-source-best-practices-902).

Fetch

Slack

Twitter

Read My Stories

Portfolio

Software Developer

Too Long; Didn't Read

Cassandra Forward a free Cassandra-focused community event

Understanding the Open Source Culture: Best Practices to Contribute Effectively

Too Long; Didn't Read

Companies Mentioned

@pragativerma

RELATED STORIES