Contributions to blazingSQL fall into the following three categories.
- To report a bug, request a new feature, or report a problem with documentation, please file an issue describing in detail the problem or new feature. The BlazingSQL team evaluates and triages issues, and schedules them for a release. If you believe the issue needs priority attention, please comment on the issue to notify the team.
- To propose and implement a new Feature, please file a new feature request issue. Describe the intended feature and discuss the design and implementation with the team and community. Once the team agrees that the plan looks good, go ahead and implement it, using the code contributions guide below.
- To implement a feature or bug-fix for an existing outstanding issue, please Follow the code contributions guide below. If you need more context on a particular issue, please ask in a comment.
- Follow the guide in our documentation for Building From Source.
- Comment on the issue stating that you are going to work on it.
- Code! Make sure to update unit tests!
- When done, create your pull request.
- Wait for other developers to review your code and update code as needed.
- Once reviewed and approved, a BlazingSQL developer will merge your pull request.
Remember, if you are unsure about anything, don't hesitate to comment on issues and ask for clarifications!
Portions adopted from https://github.com/rapidsai/cudf/CONTRIBUTING.md