We actively encourage contributing to all of our open-source projects in all of the following areas:
- Reporting a bug
- Submitting a fix for a bug
- Discussing and improving the code
- Proposing new features
We host most of our open-source and public commercial projects on GitHub although some will be on GitLab (we use GitLab mostly for our private commercial projects).
We typically use Git Feature Branch Workflow on our projects
This means that pull requests are the best way to propose changes to the codebase. We actively welcome your pull requests:
- Fork the repo and create your branch from
main
. - If you've added code that should be tested, add tests.
- If you've changed APIs, update the documentation.
- Ensure the test suite passes.
- Make sure your code lints.
- Issue that pull request!
In short, when you submit code changes, your submissions are understood to be under a Proprietary License that covers the project. Feel free to contact the maintainers if that's a concern.
We use GitHub issues to track public bugs. Report a bug by opening a new issue; we already have two templates setup so it's super easy, barely an inconvenience!
Don't forget to be thorough in your description of the bug, we love detail!
- 4 spaces (PHP & HTML) and 2 spaces (All other files) for indentation rather than tabs (we use a .editorconfig file for consistency)
- Comments should match the existing format in this repo and be written in clear english with enough detail about what it's describing.
By contributing, you agree that your contributions will be licensed under its Proprietary License.