Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jclouds Wiki" for change notification.
The "How to contribute" page has been changed by EverettToews: https://wiki.apache.org/jclouds/How%20to%20contribute?action=diff&rev1=8&rev2=9 Comment: Emphasize steps in contributing. Notes about backporting. Link to Rebase. We use [[https://github.com/jclouds|GitHub]] and [[https://issues.apache.org/jira/browse/JCLOUDS|JIRA]] on the jclouds project. - Your first step is to create or find an issue in [[https://issues.apache.org/jira/browse/JCLOUDS|JIRA]] for your feature request or fix. If it's a simple cleanup, this isn't necessary, but it's good to see if you're change fixes an existing issue anyway. If it's a formatting issue alone, consider creating an issue for us to fix our checkstyle configuration to catch it in the future. + === 1. Create an issue in JIRA === - Next, you'll want to create a pull request in Github for the change you're interested in making. Some good references for working with Github are below. We ask that you keep your change rebased to master as much as possible, and we will ask you to rebase again if master has moved before accepting your patch. + Your first step is to create or find an issue in [[https://issues.apache.org/jira/browse/JCLOUDS|JIRA]] for your feature request or fix. If it's a simple cleanup, this isn't necessary, but it's good to see if your change fixes an existing issue anyway. If it's a formatting issue alone, consider creating an issue for us to fix our checkstyle configuration to catch it in the future. + + === 2. Create a pull request in GitHub === + + Next, you'll want to create a pull request (PR) in !GitHub for the change you're interested in making. The comment section of the PR must contain a link to the JIRA issue (if it has one). If you need the commit backported to one of the release branches (e.g. 1.6.x), make a note about that in the comment too. + + Some good references for working with !GitHub are below. We ask that you keep your change rebased to master as much as possible, and we will ask you to rebase again if master has moved before accepting your patch. * [[https://help.github.com/articles/set-up-git|Setting Up Git with GitHub]] * [[https://help.github.com/articles/fork-a-repo|Forking a Repository]] * [[https://help.github.com/articles/using-pull-requests|Submitting Pull Requests]] + * [[https://help.github.com/articles/interactive-rebase|Rebase]] + + === 3. Comment the issue in JIRA === Finally, add a comment in the JIRA issue with a link to the pull request so we know the code is ready to be reviewed. + + If you need the commit backported to one of the release branches (e.g. 1.6.x), make a note about that in the comment too. == The review process ==
