Because Colossus is pre 1.0 and under very heavy development, there is lots of room for improvement and we are not afraid to make large-scale breaking changes if it makes sense. All bug fixes and feature improvements are welcome, but if you are planning on implementing a significant change, especially one that changes an API or breaks backwards compatibility, you should verify with one of the core contributors that your work won't conflict with any ongoing or planned changes.
- Fork the repo and create your branch from
- If you've added code that should be tested, add tests.
- If you've changed APIs, update the documentation.
- Ensure the test suite passes.
- If you've significantly changed low-level code, you must run benchmarks and provide numbers.
- If you haven't already, complete the Contributor License Agreement ("CLA").
Contributor License Agreement ("CLA")
In order to accept your pull request, we need you to submit a CLA.
Complete your CLA here (a more integrated web form is coming soon).
By contributing to Colossus you agree that your contributions will be licensed under its Apache 2.0 license.