...
This checklist tells you how to create accounts and obtain permissions needed by Hive contributors. See the Hive website for additional information.
- Create Request an Apache Software Foundation JIRA account, if you do not already have one: Sign Up for JIRA.
- To review patches you could do that on Github
- All Hive patches posted for review are listed here.
- Individual JIRA tickets provide a link to the issue on the review board when a review request has been made.
- To contribute to the Hive wiki, follow the instructions in About This Wiki.
- To edit the Hive website, follow the instructions in How to edit the website.
- Join the Hive mailing lists to receive email about issues and discussions.
Making Changes
If you're a newcomer, feel free to contribute by working on a newbie task.
Before you start, send a message to the Hive developer mailing list, or file a bug report in JIRA. Describe your proposed changes and check that they fit in with what others are doing and have planned for the project. Be patient, it may take folks a while to understand your requirements.
...
Committers: for non-trivial changes, it is best to get another committer to review your patches before commit. Use the Submit Patch link like other contributors, and then wait for a "+1" from another committer before committing. Please also try to frequently review things in the patch queue.
JIRA
...
Hive uses JIRA for issues/case management. You must If you don't already have a JIRA account , sign Up for JIRA.in order to log cases and issues.
Requests for the creation of new accounts can be submitted via the following form: https://selfserve.apache.org/jira-account.html
Guidelines
Please comment on issues in JIRA, Please comment on issues in JIRA, making your concerns known. Please also vote for issues that are a high priority for you.
...
Consider using bi-directional links when referring to other tickets. It is very common and convenient to refer to other tickets by adding the HIVE-XXXXX pattern in summary, description, and comments. The pattern allows someone to navigate quickly to an older JIRA from the current one but not the other way around. Ideally, along with the mention (HIVE-XXXXX) pattern, it helps to add an explicit link (relates to, causes, depends upon, etc.) so that the relationship between tickets is visible from both ends.
Add the "backward-incompatible" label to tickets changing the behavior of some component or introduce modifications to public APIs. There are various other labels available for similar purposes but this is the most widely used across projects so it is better to stick to it to keep things uniform.
When in doubt about how to fill in the Create Issue form, take a look at what was done for other issues. Here Here are several Hive JIRA issues that you can use as examples:
...
Contributors should join the Hive mailing lists. In particular the dev list (to join discussions of changes) and the user list (to help others).
...