1 files changed, 47 insertions, 0 deletions

diff --git a/users/ryan/modules/simple-bar/simple-bar-source/CONTRIBUTING.md b/users/ryan/modules/simple-bar/simple-bar-source/CONTRIBUTING.md
new file mode 100755
index 0000000..13ec1f9
--- /dev/null
+++ b/users/ryan/modules/simple-bar/simple-bar-source/CONTRIBUTING.md
@@ -0,0 +1,47 @@
+# Contributor guidelines
+
+## What do I need to know to help?
+
+If you are looking to help to with a code contribution our project uses **React** in a mac os application names **Übersicht**. It is build on top of **yabai**. If you don't feel ready to make a code contribution yet, no problem! You can also check out the [documentation issues](https://github.com/Jean-Tinland/simple-bar/issues).
+
+If you are interested in making a code contribution and would like to learn more about the technologies that we use, check out the list below.
+
+- [React documentation](https://react.dev/learn)
+- [Übersicht documentation](https://github.com/felixhageloh/uebersicht#%C3%BCbersicht)
+- [yabai documentation](https://github.com/koekeishiya/yabai)
+
+## Coding style conventions
+
+Your PR should:
+
+- Be formatted with prettier
+- Pass the linter (run `yarn lint` to check)
+
+## How do I make a contribution?
+
+Never made an open source contribution before? Wondering how contributions work in the in our project? Here's a quick rundown!
+
+1. Find an issue that you are interested in addressing or a feature that you would like to add.
+2. Fork the repository associated with the issue to your local GitHub organization. This means that you will have a copy of the repository under `your-GitHub-username/simple-bar`.
+3. Clone the repository to your local machine using `git clone https://github.com/Jean-Tinland/simple-bar.git`.
+4. Create a new branch for your fix using `git checkout -b branch-name-here`.
+5. Make the appropriate changes for the issue you are trying to address or the feature that you want to add.
+6. Use `git add insert-paths-of-changed-files-here` to add the file contents of the changed files to the "snapshot" git uses to manage the state of the project, also known as the index.
+7. Use `git commit -m "Insert a short message of the changes made here"` to store the contents of the index with a descriptive message.
+8. Push the changes to the remote repository using `git push origin branch-name-here`.
+9. Submit a pull request to the upstream repository.
+10. Title the pull request with a short description of the changes made and the issue or bug number associated with your change. For example, you can title an issue like so "Added more log outputting to resolve #4352".
+11. In the description of the pull request, explain the changes that you made, any issues you think exist with the pull request you made, and any questions you have for the maintainer. It's OK if your pull request is not perfect (no pull request is), the reviewer will be able to help you fix any problems and improve it!
+12. Wait for the pull request to be reviewed by a maintainer.
+13. Make changes to the pull request if the reviewing maintainer recommends them.
+14. Celebrate your success after your pull request is merged!
+
+## Where can I go for help?
+
+If you need help, you can ask questions on simple-bar's issue section on GitHub or with the contact form on [my website](https://www.jeantinland.com/en/contact/).
+
+## What does the Code of Conduct mean for me?
+
+Our Code of Conduct means that you are responsible for treating everyone on the project with respect and courtesy regardless of their identity. If you are the victim of any inappropriate behavior or comments as described in our Code of Conduct, we are here for you and will do the best to ensure that the abuser is reprimanded appropriately, per our code.
+
+> This contributor guide is adapted from the [opensource.com guide available here](https://opensource.com/life/16/3/contributor-guidelines-template-and-tips).