CONTRIBUTING.md 3.1 KB

alt text

The Hue project gladly welcomes any patches or pull requests!

This document contains instructions on how to get involved with Hue, and our development process. The team also follows this logic.

In any case, feel free to ask on hue-user, here or @gethue.

Getting Started

Have a look at how to build Hue.

Example of bug, patch and review

List of Easy bugs.

Bug Tracking

Hue uses JIRA as its bug tracking system.

Submitting an improvement

Reviews

Hue blog posts about using Review Board: How to do Code Reviews.

Currently, the Hue project is very flexible on how to do code reviews:

  • Review Board Create an account on Hus's Review Board. Post the patch against the "hue-rw" repository. Enter "hue" in the "groups" field. Example: https://review.cloudera.org/r/4019/

  • Github Diff or Pull request Again, for small changes, if you have the fix in a commit in your own github fork, you can just post the pull request

  • JIRA Attachment For small changes, you can attach the patch in the JIRA.

Commit

A Hue committer will commit your patch when it is is ready after being reviewed.

Example of commit.

If it is the first time, please sign the CCLA that way we don't get sued later ;)

Coding Style

A general rule is to follow the on-going style of the code context.

  • Python: Follow PEP 8, with the exception of using 2 spaces per indent level. Line width is 100 characters.
  • JavaScript: Follow the style in this file.

Tests

Please run the tests. Se the Getting started then testing.

Patch Format

Generate the patch using @git format-patch@ with a message looking like:

HUE-NNNN [APP_NAME] The JIRA summary line

Optional details on the commit *after* a blank line.
This section can span multiple lines.

Or have multiple paragraphs.

Example of format.