You'd like to contribute to Attendize? Amazing! Thank you so much! Feel free to fork and contribute. If you are unsure about adding a feature, please create a Github issue to ask for feedback.
If you encounter a bug in Attendize, please first search the list of current open Issues on the GitHub repository. You may add additional feedback on an existing bug report. If the issue you're having has not yet been reported, please open a new issue. There is a template available for new issues. Please fill out all information requested in the template so we can help you more easily.
Please note: support is not offered from the project maintainers through GitHub. Paid support is available by purchasing a license. You may submit support requests in a GitHub issue to see if someone in the community is able to offer help or advice. Support issues will be automatically closed after 7 days to keep the size of the issues list down.
If you'd like to contribute code with a bug fix, new feature or enhancement, please do so via a pull request. Adding details in the PR description about what your changes are and why you implemented will help us to review and merge it sooner. Please ensure you add or update the tests along with your changes, as well as documentation if it's applicable.
Contributions of tests and documentation are always welcome too!
If you're able to provide comments, feedback or reviews on the issues or pull requests from other users, that is greatly appreciated too! The more feedback and input the change receives, the better it will be, so this helps us a lot and helps the community too!
Any code, tests or documention you decide to contribute will become part of the Attendize code base and will be subject to the standard license.
Being part of the Attendize community and contributing to that community includes abiding by our Code of Conduct