Index of Categories
If you are interested in contributing to Eucalyptus code, please read the following instructions and guidelines.
Significant contributions (usually those more than about 15 lines of code) require that you sign our contributor agreement before they can be accepted. This agreement is located at http://www.eucalyptus.com/participate/code/contribute/agreement
Before committing any code, please make note of the issue IDs to which your code relates. You may also want to comment in the issues to let people know that you are working on a fix. If no issue exists yet for the code you are writing, please create one. See the REPORTING-BUGS file in the source tree for more information about this process.
Be aware that if an issue is still in "Unconfirmed" or "Investigating" state, it may mean that the Eucalyptus engineering team has not yet confirmed that they can reproduce the issue, and this is required before a patch can be reviewed. Providing a test case can accelerate this process.
If you are developing your patch in git (which we highly recommend), please ensure that your commit messages include a short summary line (50 chars or less), followed by a blank line, followed by a description of what the patch does (in lines of 72 chars or less). The description should contain all issue IDs relevant to the commit. Ideally, fixes for separate issues should be in separate commits.
There are three ways to send a patch:
NOTE: If the issue for which you are submitting a patch is already in the "Confirmed" state in Jira, you can use the "Submit Patch" action to send the issue to "In Review" state. This will notify the Eucalyptus developers that the patch is ready for code review.
Once the patch is submitted (following the above guidelines), the following process occurs:
code on Github | bugs on Jira | questions on StackOverflow | discussions on Quora | videos on Vimeo | presentations on Slideshare | tweets on Twitter | friends on Facebook | contacts on LinkedIn | +1s on Google Plus
All content copyright Eucalyptus Systems, 2013. Made available under the CC-BY-3.0-US license.