docs(CONTRIBUTING): update contributing doc

[Joshua-Anderson]

No description provided.

[deis-bot]

@krancour, @bacongobbler and @carmstrong are potential reviewers of this pull request based on my analysis of git blame information. Thanks @Joshua-Anderson!

[codecov-io]

Current coverage is 86.14% (diff: 100%)

Merging #1006 into master will increase coverage by 0.03%

@@             master      #1006   diff @@
==========================================
  Files            28         28          
  Lines          3175       3175          
  Methods           0          0          
  Messages          0          0          
  Branches        540        540          
==========================================
+ Hits           2734       2735     +1   
+ Misses          295        294     -1   
  Partials        146        146          

Powered by Codecov. Last update bff6d60...5d2cd10

[helgi]

The deis.com doc is missing the DCO (do we care about that anymore?) and linking to troubleshooting, among other things.

[Joshua-Anderson]

The DCO is in a filed called DCO in the project root.

Should we link to troubleshooting in contributing docs?
Is there somewhere else you would rather link?

[helgi]

The contributing guide was caking out the DCO and semi explained it - otherwise I would have never known what it was

[helgi]

Probably enough to link to the troubleshooting docs - gets it into more hands

[Joshua-Anderson]

@helgi Would you like me to add back:

By contributing to any Deis project you agree to its [Developer Certificate of Origin (DCO)][dco]. This document was created by the Linux Kernel community and is a simple statement that you, as a contributor, have the legal right to make the contribution.

to the document?

[helgi]

Figured that could be added to the website

[Joshua-Anderson]

Ok, I'll make a PR to the docs adding mentioning the DCO and adding a link to troubleshooting to the page.