We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:
- Reporting a bug
- Discussing the current state of the code
- Submitting a fix
- Proposing new features
- Becoming a maintainer
We use github to host code, to track issues and feature requests, as well as accept pull requests.
We use GitHub issues to track public bugs and requests. Report a bug or a request by opening a new issue; it's that easy!
We Use Github Flow, So All Code Changes Happen Through Pull Requests
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
master. - 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!
Any contributions to a driver and/or an application you make will be under the MIT Software License
In short, when you submit code changes to drivers and apps, your submissions are understood to be under the same MIT License that covers the project. Feel free to contact the maintainers if that's a concern.
Any contributions to Luos core technology you make will be under the Luos License
In short, when you submit code changes to Luos core technology, your submissions are understood to be under the Luos License that covers the project. Feel free to contact the maintainers if that's a concern.
Great Bug Reports tend to have:
- A quick summary and/or background
- Steps to reproduce
- Be specific!
- Give sample code if you can
- What you expected would happen
- What actually happens
- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
People love thorough bug reports. I'm not even kidding.
Don't hesitate to read our documentation, or to post your questions/issues on the Luos' Forum. 📚
