Merge pull request hyperledger-indy#706 from michaeldboyd/feature/contributor-resources

Added a Contributor Resources page and a how to for signing commits.

Author: jovfer

doc/contributor-resources.md

@@ -0,0 +1,43 @@
+# Contributing to Indy SDK
+
+
+Before contributing to Indy SDK, there are a couple steps that will help your process go much more smoothly.
+
+First, please take a look at our contributing guidelines: [how to contribute to Hyperledger Indy](http://bit.ly/2ugd0bq).
+
+If you are looking for how to sign current or previous commits, go here: [signing your commits](signing-commits.md)
+
+## Connect with the Community
+
+Hyperledger Indy has a vibrant and active community of developers willing to help you answer questions, learn more about self-sovereign identity, and get involved.
+
+You will find the best and most update resources on chat board here: [Hyperledger Rocket Chat](https://chat.hyperledger.org/home)
+
+\#indy-sdk, \#indy-node, and \#indy are the some of the best channels to get started. Please introduce yourself and let us know what you want to accomplish!
+
+## How to Start Working with the Code
+
+1. Fork the indy-sdk repository on Github to your personal account.
+
+1. Add the hyperledger/indy-sdk as the remote upstream:  
+   `git remote add upstream https://github.com/hyperledger/indy-sdk.git`
+
+1. Set up Developer Certificate of Origin and learn how to [sign your commits](signing-commits.md)  
+
+1. Take a look at our [release workflow](release-workflow.md)
+
+## How to send a PR
+
+- Do not create big PRs; send a PR for one feature or bug fix only.
+ If a feature is too big, consider splitting a big PR to a number of small ones.
+- Consider sending a design doc into `design` folder (as markdown or PlantUML diagram) for a new feature  before implementing it
+- Make sure that a new feature or fix is covered by tests (try following TDD)
+- Make sure that documentation is updated according to your changes
+- Provide a full description of changes in the PR including Jira ticket number if any  
+- Make sure that all your commits have a DCO sign-off from the author. (add the `-s` flag to all commits)
+- Put the link to the PR into `#indy-pr-review` channel in Rocket.Chat
+- A reviewer needs to start your tests first (add `test this please` comment to the PR)
+- You need to make sure that all the tests pass
+- A reviewer needs to review the code and approve the PR. If there are review comments, they will be put into the PR itself.
+- You must process them (feel free to reply in the PR threads, or have a discussion in Rocket.Chat if needed)
+- A reviewer or maintainer will merge the PR

doc/getting-started/getting-started.dockerfile

@@ -30,4 +30,4 @@ RUN apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 68DB5E88 \
 
 USER indy
 
-EXPOSE 8888
+EXPOSE 8888

doc/signing-commits.md

@@ -0,0 +1,25 @@
+# Signing commits
+
+If you are here because you forgot to sign your commits, fear not. Check out [how to sign previous commits](#how-to-sign-previous-commits)
+
+We use developer certificate of origin (DCO) in all hyperledger repositories, so to get your pull requests accepted, you must certify your commits by signing off on each commit.
+
+## Signing your current commit
+  - `$ git commit -s -m "your commit message"`
+  - To see if your commits have been signed off, run `$ git log --show-signature`
+  - If you need to re-sign the most current commit, use `$ git commit --amend --no-edit -s`.
+
+The `-s` flag signs the commit message with your name and email.
+
+## How to Sign Previous Commits
+   1. Use `git log --show-signature` to see which commits need to be signed.
+   1. Go into interactive rebase mode using `$ git rebase -i HEAD~X` where X is the number of commits up to the most current commit you would like to see.
+   1. You will see a list of the commits in a text file. **On the line after each commit you need to sign**, add `exec git commit --amend --no-edit -s` with the lowercase `-s` adding a text signature in the commit body. Example that signs both commits:
+      ```
+      pick 12345 commit message
+      exec git commit --amend --no-edit -s
+      pick 67890 commit message
+      exec git commit --amend --no-edit -s
+      ```
+    1. If you need to re-sign a bunch of previous commits at once, find the earliest unsigned commit using `git log --show-signature` and use that the HASH of the commit before it in this command: `git rebase --exec 'git commit --amend --no-edit -n -s' -i HASH`. This will sign every commit from most recent to right before the HASH.
+    1. You will probably need to do a force push `git push -f` if you had previously pushed unsigned commits to remote.