From f0e0535120a349c2136af9533ab7953e9e3749ff Mon Sep 17 00:00:00 2001 From: Cory LaViska Date: Thu, 27 Aug 2020 14:09:10 -0400 Subject: [PATCH] Update contribution guidelines --- CONTRIBUTING.md | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 1293236f..1f3345d1 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,6 +1,22 @@ # Contributing to Shoelace -Shoelace is an open source project, meaning everyone can use it and contribute to its development. Please take a moment to review these guidelines to make the contribution process as easy as possible for both you and the project's maintainers. +Shoelace is an open source project, meaning everyone can use it and contribute to its development. When you join our community, you'll find a friendly group of enthusiasts of all experience levels who are willing to chat about anything and everything related to Shoelace. + +The easiest way to get started contributing is to join the [community chat](https://discord.gg/mg8f26C). This is where we hang out, discuss new ideas, ask for feedback, and more! + +A common misconception about contributing to an open source project is that you need to know how to code. This simply isn't true. In fact, there are _many_ ways to contribute, and some of the most important contributions come from those who never write a single line of code. Here's a list of ways you can make a meaningful contribution to the project: + +- Submitting well-written bug reports +- Submitting feature requests that are within the scope of the project +- Improving the documentation +- Responding to users that need help in the [community chat](https://discord.gg/mg8f26C) +- Triaging issues on GitHub +- Being a developer advocate for the project +- Sponsoring the project financially +- Writing tests +- And, of course, contributing code! + +Please take a moment to review these guidelines to make the contribution process as easy as possible for both yourself and the project's maintainers. ## Using the Issue Tracker