Thank you for considering contributing to Drax! Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.
If you've found a bug, you're having trouble with the documentation, or you have a feature request, please open an issue with the relevant information.
If you're interested in making a non-trivial contribution, please first discuss the change you wish to make via GitHub issue, email, or any other method with the maintainers. We respect your time and energy, and we would like you to feel secure before expending significant effort.
Drax's code may appear complex, but project contributions can come in forms other than code commits! Anything that improves the quality of the library or helps its user community is a contribution. For example, enhancing the documentation, creating cool usage examples, and providing helpful input on issues are other ways to pitch in.
We understand how frustrating it can be to open an issue or pull request and not receive timely feedback. Please keep in mind that this project is maintained by volunteer effort, and we will do our best to reply promptly, according to our own capacity. For small PRs and simple issues, we'll try to reply within a few days to a week. Larger changes should be discussed in advance, as mentioned above, and they may take longer. Bug fixes and feature requests will be prioritized by gauging implementation difficulty and how widely applicable they are to the community, and they'll be addressed as availability allows.
The library does not currently have any automated tests or code review checks. We're not averse to the idea; we simply haven't had the resources to put toward it yet. This means that code changes, particularly large ones, may take additional time to review manually. If the library's automation is something you're interested in improving, the maintainers welcome that discussion.