Contributing

First of all, thank you so much for taking a deeper look at the project. It does mean a lot.

PRs and issues of all sorts are welcome, here are some guides to help you out.

PRs

Refer to HACKING.md for information on the inner-workings of the project. If you're still unsure about anything open an Issue.
If you're unure you to help, check out backlogs.md which contains plenty of new features and tasks that need to be imlemented.
If you would like to gain approval or discuss how you'll tackle a new feature in a logical sense, open an issue.
For commit message, please do your best to use the project's commit labelling techniques to ensure uniformity
Name the pull request with the same labelling as commits 👍
Include what you changed, but also why. It'll help give context and help your contributions make more sense.
If once opening the pull request the lint workflow build fails, that's ok, take a look at the build and see what went wrong. If you can fix it please do, if not feel free to ask for help.

You can throw anything you like (within context) as an issues. However, to help we have three templates for the basic feature requests:

Also if you want to improve or add to these templates go ahead