This project has a code of conduct. By interacting with this repository, organization, or community you agree to abide by its terms.
Hi! 👋 We’re excited that you’re using PiRhoTechs and we’d love to help. To help us help you, please read through the following guidelines.
Please understand that people involved with this project often do so for fun, next to their course work and/or day job; you are not entitled to free customer service.
Please chat and ask questions on [Discussions][chat]! Jump in there and lurk, talk to us, and help others.
- ------- — Topics relating to [-------][-------] in general
Help us help you!
It’s easy to fall into the trap of asking something too specific when you’re close to a problem.
Spending time framing a question and adding support links or resources makes it much easier for us to help.
Then, those trying to help you out don't have to spend a lot of time asking additional questions to understand what you are hoping to achieve.
Spending the extra time up front can help save everyone time in the long run.
- Try to define what you need help with:
- Is there something in particular you want to do?
- What problem are you encountering and what steps have you taken to try and fix it?
- Is there a concept you’re not understanding?
- Learn about the rubber duck debugging method
- Avoid falling for the XY problem
- Search on GitHub to see if a similar question has been asked
- If possible, provide sample code, a CodeSandbox, or a video
- The more time you put into asking your question, the better we can help you
See contributing.md on how to contribute.