We are committed to providing a friendly, safe and welcoming environment for all. Make sure to take a look at the Code of Conduct.
All contributions are appreciated! Typo fixes, bug fixes, feature requests, example suggestions, bug reports are all helpful for the project.
If you are looking for a good place to start, check the good first issues or reach out on the #contributing channel on our group chat.
- We want the examples website to be the centralized place to find your up-to-date, roc-expert-approved answer to common search queries like "How to X in roc".
- The code snippet of the example should concisely provide the code that the user is looking for and be easy to understand. Nuanced explanations, suggestions for further reading, and links to other examples may be provided in the text part of the example.
- For the platform and packages URLs should be used, not relative links. This makes the example easy to copy.
- If this is your first pull request on github, check out this link
- Fork the repo so that you can apply your changes first on your own copy of the roc repo. It's a good idea to open a draft pull request as you begin working on something. This way, others can give feedback sooner rather than later and duplicate effort is avoided. Click the button "ready for review" when it's ready.