How to get started in jclouds: the straw-man

jclouds-getting started

1. send an email to subscribe to all lists out of the following: 
  - jclouds-user-subscribe@apache.org
  - jclouds-dev-subscribe@apache.org
  - jclouds-issues-subscribe@apache.org
  - jclouds-commits-subscribe@apache.org

2. fork the jclouds org repos of interest (these are mirrors of https://git-wip-us.apache.org/repos/asf/incubator-REPO)
  - https://github.com/jclouds/jclouds
  - https://github.com/jclouds/jclouds-chef
  - https://github.com/jclouds/jclouds-karaf
  - https://github.com/jclouds/jclouds-cli
  - https://github.com/jclouds/jclouds-labs
  - https://github.com/jclouds/jclouds-labs-aws
  - https://github.com/jclouds/jclouds-labs-google
  - https://github.com/jclouds/jclouds-labs-openstack

3. note that issues are logged in jiras and referenced in your pull requests against ^^
  - https://issues.apache.org/jira/browse/JCLOUDS
  - if you need to be assigned to an issue, ask dev@jclouds.incubator.apache.org to be added as a contributor
    - https://issues.apache.org/jira/plugins/servlet/project-config/JCLOUDS/roles
  - prefix commits with the issue id.  ex. JCLOUDS-111. fix signature test for s3
  - pull requests are checked by buildhive
    - access is granted to collaborators in the org https://github.com/jclouds
    - jobs are setup to execute maven goals: clean verify -e
    - jobs notify dev@jclouds.incubator.apache.org
    - repositories are noted here: https://buildhive.cloudbees.com/view/My%20Repositories/job/jclouds/
  - When a pull request has finished review, a committer can merge it by the following process.
    1. note the commit ids you want from https://github.com/jclouds/jclouds/pull/XXX/commits
    2. git clone https://git-wip-us.apache.org/repos/asf/incubator-jclouds.git
    3. cd incubator-jclouds
    4. git fetch https://github.com/USERNAME/jclouds.git BRANCH_FROM_PR
    5. git cherry-pick COMMIT1 COMMIT2
    6. mvn clean install
    7. git push origin master
    - if it needs to go into a feature branch like 1.6.x
       1. git checkout -t -b 1.6.x origin/1.6.x
       2. git cherry-pick COMMIT1 COMMIT2
       3. git push origin 1.6.x 

4. snapshots are published to https://repository.apache.org/content/groups/snapshots/ by cloudbees: https://jclouds.ci.cloudbees.com
  - cloudbees access can be granted by sending an email to dev@jclouds.incubator.apache.org
  - branches 1.5.x 1.6.x and 1.7.x are deployed, including source and javadoc jars
  - maven configuration is typically: -U clean deploy -e -Pdoc -Psrc
  - failures notify dev@jclouds.incubator.apache.org
  - if the build breaks due to rat, add an Execute Shell post-step of: cat target/rat.txt