Every volunteer project obtains its strength from the people involved in it. We invite you to participate as much or as little as you choose.
Get help using Livy or contribute to the project on our mailing lists:
Found bug? Enter an issue in the Issue Tracker.
Before submitting an issue, please:
Enhancement requests for new features are also welcome. The more concrete and rationale the request is, the greater the chance it will incorporated into future releases.
Once you find an issue that you would like to work on, if no-one is working on it, assign it to yourself (only if you intend to work on it shortly though). Except for the very smallest items, it’s a very good idea to discuss your intended approach either on the issue’s JIRA or on the dev mailing list. You are more likely to have your patch reviewed and committed if you’ve already got buy-in from the livy community before you start.
As you are writing your patch, please keep the following things in mind:
Include tests with your patch. If your patch does not include tests, it will not be accepted. If you are unsure how to write tests for a particular component, please ask on the dev mailing list for guidance.
Keep your patch narrowly targeted to the problem described by the JIRA. It is important to we maintain discipline about the scope of each patch. In general, if you find a bug while working on a specific feature, file a JIRA for the bug, check if you can assign it to yourself and fix it independently of the feature. This helps us to differentiate between bug fixes and features and allows us to build stable maintenance releases.
Write a clear commit message, with a short, descriptive title and a message that is exactly long enough to explain what the problem was, and how it was fixed.