Adding CONTRIBUTING.md file

CONTRIBUTING.md

@@ -0,0 +1,91 @@
+# Contributing at Distro
+
+We are beyond excited to see that you want to contribute! We would love to accept your contributions. Distro is built by the community and warmly welcomes collaboration. There are many ways in which one could contribute to Distro and every contribution is equally appreciated here. Navigate through the following to understand more about contributing here.
+
+- [Before You Get Started](#before-you-get-started)
+- [Contributing to Distro Projects](#contributing-to-distro-projects)
+- [Contributing to Distro's Blogs](#contributing-to-distros-blogs)
+- [How to Contribute](#how-to-contribute)
+  - [Prerequisites](#prerequisites)
+  - [Set up your Local Development Environment](#set-up-your-local-development-environment)
+  - [Signing-off on Commits](#signing-off-on-commits)
+
+  ⚠️ Cloning this repository ⚠️
+
+Cloning the repo with all its history results in a ~6 GB download. If you don't need the whole history you can use the depth parameter to significantly reduce download size.
+
+```bash
+git clone --depth=1 https://github.com/camicroscope/Distro.git
+```
+
+# Before You Get Started
+
+## Code of Conduct
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting community@Distro.
+Violation of the code of conduct is taken seriously,
+
+The comfort and safety of Distro community members are our priority. Please do well to adhere to the Code of Conduct to participate in the Distro community.
+
+## For Newcomers
+
+To help you get started on contributing to  projects, refer to the which aims to make contributions easier for new folks like you! See the resources and tutorials to help you get started. Along with this we have an extensive handbook on how this community works , how folks inside the community wear different hats to run it and few of its guidelines, have a look inside the 
+
+
+## Issues & Pull Requests
+
+### Creating an Issue
+
+Before **creating** an Issue i.e for `features`/`bugs`/`improvements` please follow these steps:
+
+
+1. Search existing Issues before creating a new Issue (look to see if the Issue has already been created).
+1. If it doesn't exist create a new Issue giving as much context as possible (please take note and select the correct Issue type, for example `bug`, `documentation` or `feature`.
+1. If you wish to work on the Issue once it has been triaged, please include this in your Issue description.
+
+
+### Working on an Issue
+
+Before working on an existing Issue please follow these steps:
+
+1. Comment asking for the Issue to be assigned to you.
+1. To best position yourself for Issues assignment, we recommend that you:
+    1. Confirm that you have read the CONTRIBUTING.md.
+    1. Have a functional development environment (have built and are able to run the project).
+    1. Convey your intended approach to solving the issue.
+    1. Put each of these items in writing in one or more comments.
+1. After the Issue is assigned to you, you can start working on it.
+1. In general, **only** start working on this Issue (and open a Pull Request) when it has been assigned to you. Doing so will prevent confusion, duplicate work (some of which may go unaccepted given its duplicity), incidental stepping on toes, and the headache involved for maintainers and contributors alike as Issue assignments collide and heads bump together. 
+1. Reference the Issue in your Pull Request (for example `This PR fixes #123`). so that the corresponding Issue is automatically closed upon merge of your Pull Request.
+
+> Notes:
+>
+> - Check the `Assignees` box at the top of the page to see if the Issue has been assigned to someone else before requesting this be assigned to you. If the issue has a current Assignee, but appears to be inactive, politely inquire with the current Assignee as to whether they are still working on a solution and/or if you might collaborate with them.
+> - Only request to be assigned an Issue if you know how to work on it.
+> - If an Issue is unclear, ask questions to get more clarity before asking to have the Issue assigned to you; avoid asking "what do I do next? how do I fix this?" (see the item above this line)
+> - An Issue can be assigned to multiple people, if you all agree to collaborate on the Issue (the Pull Request can contain commits from different collaborators)
+> - Any Issues that has no activity after 2 weeks will be unassigned and re-assigned to someone else.
+
+## Reviewing Pull Requests
+
+We welcome everyone to review Pull Requests. It is a great way to learn, network, and support each other.
+
+### DOs
+
+- Use inline comments to explain your suggestions
+- Use inline suggestions to propose changes
+- Exercise patience and empathy while offering critiques of the works of others.
+
+### DON'Ts
+
+- Do not repeat feedback, this creates more noise than value (check the existing conversation), use GitHub reactions if you agree/disagree with a comment
+- Do not blindly approve Pull Requests to improve your GitHub contributors graph
+
+# Contributing to Distro Projects
+
+Please follow these steps and note these guidelines to begin contributing:
+
+1. First step is to set up the local development environment.
+1. Bug fixes are always welcome. Start by reviewing the [list of bugs]().
+1. A good way to easily start contributing is to pick and work on a [good first issue](). We try to make these Issues as clear as possible and provide basic info on how the code should be changed, and if something is unclear feel free to ask for more information on the Issue.
+1. We regularly discuss new Issues to work on in our [discussion forum]() and the [#websites]() channel. Feel free to join and discuss any Issue or any idea that you may have.