Contributions to velox-testing fall into the following categories:
- To report a bug, request a new feature, or report a problem with documentation, please file an issue describing the problem or new feature in detail. The RAPIDS 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 issue, please follow the code contributions guide below. If you need more context on a particular issue, please ask in a comment.
As contributors and maintainers to this project, you are expected to abide by velox-testing's code of conduct. More information can be found at: Contributor Code of Conduct.
- Find an issue to work on. The best way is to look for the good first issue or help wanted labels.
- Comment on the issue stating that you are going to work on it.
- Create a fork of the velox-testing repository and check out a branch with a name that describes your planned work. For example, ix-documentation
- Write code to address the issue or implement the feature.
- Add unit tests and unit benchmarks.
- Create your pull request. To run continuous integration (CI) tests without requesting review, open a draft pull request.
- Verify that CI passes all status checks. Fix if needed. TODO: link to appropriate CI once it has stabilized.
- Wait for other developers to review your code and update code as needed.
- Once reviewed and approved, a RAPIDS developer will merge your pull request.
If you are unsure about anything, don't hesitate to comment on issues and ask for clarification!