The Hue project gladly welcomes pull requests!
This document contains instructions on how to help get involved with Hue.
In any case, feel free to ask here, on the forum or @gethue.
Here is some inspiration on which areas would love to have some contributions:
- Updating a small piece of documentation.
- High level Roadmap.
- JIRA is the bug tracking system as well as Github issues.
- Generally, improving or creating connectors should be the best projects:
- SQL (Tip: read (how to write a parser)[link]
- Hive LLAP
- Parser for Apache Calcite
- Parser for PartiQl
- Parser for ZetaSql
- SqlAlchemy (any improvements to connectors for Druid, Phoenix...)
- Sql streams (Kafka SQL, Flink SQL...)
- Elastic Search, Solr
- Storage: Google Storage
- Query Optimization
- Data Catalog
- Document Sharing (Slack, email...)
- Result Sharing (Google Spreadsheet, Slack...)
Here are some example of changes:
Have a look at how to build Hue.
It is flexible on how to do code reviews and send patches:
- Github Pull request. Prefered way. Just post the pull request and reviewers will start from there. The CI will run a bsic set of tests for you.
- Review Board. For large changes. Create an account on Hue's Review Board. Post the patch against the "hue-rw" repository. Enter "hue" in the "groups" field. Example: https://review.cloudera.org/r/4019/
Blog posts about using Code Reviews and the extended process.
A general rule is to follow the on-going style of the code context.
- Python: Follow Django/PEP8, with the exception of using 2 spaces per indent level.
- JavaScript: Follow the style in this file.
See the Running the tests or opening-up a pull request will automatically run them via CircleCi.