![alt text](https://raw.githubusercontent.com/cloudera/hue/master/docs/images/hue_logo.png "Hue Logo") The Hue project gladly welcomes [improvements](https://github.com/cloudera/hue/pulls)! This document contains instructions on how to get involved. In any case, feel free to ask [questions](https://github.com/cloudera/hue/discussions). # What to improve Here is some inspiration: 1. Updating a small piece of [documentation](https://docs.gethue.com). Pick a page and click on "Edit The Page". 2. High level [Roadmap](/docs/ROADMAP.md) 3. Check [Github issues](https://github.com/cloudera/hue/issues), especially [Good First Issues](https://github.com/cloudera/hue/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22). 4. Core areas: improving [SQL Components](https://docs.gethue.com/developer/components/) like Scratchpad and Parsers, [APIs](https://docs.gethue.com/developer/api/), Kubernetes service or [SQL connectors](https://docs.gethue.com/administrator/configuration/connectors/) # Submitting an improvement Here is a good example of [Pull request](https://github.com/cloudera/hue/pull/2470) with code and unit test with mocks. ## Building Have a look at [how to quick build](https://docs.gethue.com/developer/development/#build-start). ## Reviews It is flexible but Github Pull request are handy. Just post the [pull request](https://github.com/cloudera/hue/pulls) and reviewers will start from there. The CI will run a basic set of tests for you. ## Coding Style A general rule is to follow the on-going style of the code context. * Python: Follow [Django/PEP8](https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/coding-style/), with the exception of using 2 spaces per indent level * JavaScript: Check the [EsLint](https://github.com/cloudera/hue/blob/master/.eslintrc.js) style ## CI & Tests See how to automatically [run the tests](https://docs.gethue.com/developer/development/#testing) via [CircleCi](https://circleci.com/gh/cloudera/hue) by pushing to a branch or opening-up a pull request.