Feedback

×

• Feedback
• Was this page helpful?*
  • Yes
  • No
• Do you have any additional feedback?
  • Yes
  • No
• Additional Feedback

Contribution Guidelines

VerticaPy

Documentation 1.0.x

This document will guide you through the contribution process. For code contribution, have a look at the links below:

• CI/CD
  • Black
  • Pylint
  • Unit Tests
  • Code Coverage
  • Automated Documentation using Sphinx
• Code Contribution
  • Setting-Up the Environment
  • Unit Tests
  • Useful Functions
  • Miscellenious
  • Automatic Documentation
  • Example
• ML algorithm tolerance compared with other open-source libraries
  • Regression
  • Classification
  • Others

Some other options are:

• Bug Reports

• Feature Requests

Bug Reports

If you find a bug, submit an issue with a complete and reproducible bug report. If the issue can’t be reproduced, it will be closed. If you opened an issue, but figured out the answer later on your own, comment on the issue to let people know, then close the issue.

For issues (e.g. security related issues) that are not suitable to be reported publicly on the GitHub issue system, report your issues to Vertica open source team directly or file a case with Vertica support if you have a support account.

Feature Requests

Feel free to share your ideas for how to improve VerticaPy. We’re always open to suggestions. You can open an issue with details describing what feature(s) you’d like to be added or changed.

If you would like to implement the feature yourself, open an issue to ask before working on it. Once approved, please refer to Code Contribution.