We're always looking for help implementing features, finding bugs, writing test cases, and improving documentation. If you find any issues, please don't hesitate to discuss with us, any ideas are helpful for us.
There're some related guides for you to check before contributing to our project:
Make sure you already take a deep look at our High-level Architecture. We, as an on-going project, welcome anyone help us improve our code, ideas or design.
It would be great to hear new ideas, features contribute to Aloxide, if you have any, don't hesitate to let us know about that.
Any contributions are precious to us, if you have any troubles or just have some ideas to improve Aloxide, please don't hesitate to send us your concerns at our groups https://groups.google.com/g/aloxide, we're happy and willing to help checking at anytime when we're available.
Bugs in old versions of Aloxide may have already been fixed. In order to avoid reporting known issues, make sure you are always testing against the latest build.
Please also do a quick search in the issues page to see if a similar issue has been raised by others.
When experiencing a problem, reduce your code to the bare minimum required to reproduce the issue. This makes it much easier to isolate and fix the offending code.