Adds details on code of conduct and contribution (#118)

.Rbuildignore

@@ -7,3 +7,5 @@
 ^\.covrignore$
 ^LICENSE\.md$
 inst/compare_lundberg\.xgb\.obj
+^\.github$
+^CODE_OF_CONDUCT\.md$

.github/CONTRIBUTING.md

@@ -0,0 +1,41 @@
+# Contributing to shapr
+
+This outlines how to propose a change to shapr.
+
+### Fixing typos
+
+Small typos or grammatical errors in documentation may be edited directly using
+the GitHub web interface, so long as the changes are made in the _source_ file.
+
+*  YES: you edit a roxygen comment in a `.R` file below `R/`.
+*  NO: you edit an `.Rd` file below `man/`.
+
+### Prerequisites
+
+Before you make a substantial pull request, you should always file an issue and
+make sure someone from the team agrees that it’s a problem. If you’ve found a
+bug, create an associated issue and illustrate the bug with a minimal 
+[reprex](https://www.tidyverse.org/help/#reprex).
+
+### Pull request process
+
+*  We recommend that you create a Git branch for each pull request (PR).  
+*  Look at the CircleCI build status before and after making changes.
+The `README` should contain badges for any continuous integration services used
+by the package.  
+*  New code should follow the tidyverse [style guide](http://style.tidyverse.org).
+You can use the [styler](https://CRAN.R-project.org/package=styler) package to
+apply these styles, but please don't restyle code that has nothing to do with 
+your PR.  
+*  We use [roxygen2](https://cran.r-project.org/package=roxygen2) for documentation.  
+*  We use [testthat](https://cran.r-project.org/package=testthat). Contributions
+with test cases included are easier to accept.  
+*  For user-facing changes, add a bullet to the top of `NEWS.md` below the
+current development version header describing the changes made followed by your
+GitHub username, and links to relevant issue(s)/PR(s).
+
+### Code of Conduct
+
+Please note that the shapr project is released with a
+[Contributor Code of Conduct](CODE_OF_CONDUCT.md). By contributing to this
+project you agree to abide by its terms.

CODE_OF_CONDUCT.md

@@ -0,0 +1,25 @@
+# Contributor Code of Conduct
+
+As contributors and maintainers of this project, we pledge to respect all people who 
+contribute through reporting issues, posting feature requests, updating documentation,
+submitting pull requests or patches, and other activities.
+
+We are committed to making participation in this project a harassment-free experience for
+everyone, regardless of level of experience, gender, gender identity and expression,
+sexual orientation, disability, personal appearance, body size, race, ethnicity, age, or religion.
+
+Examples of unacceptable behavior by participants include the use of sexual language or
+imagery, derogatory comments or personal attacks, trolling, public or private harassment,
+insults, or other unprofessional conduct.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments,
+commits, code, wiki edits, issues, and other contributions that are not aligned to this 
+Code of Conduct. Project maintainers who do not follow the Code of Conduct may be removed 
+from the project team.
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by 
+opening an issue or contacting one or more of the project maintainers.
+
+This Code of Conduct is adapted from the Contributor Covenant 
+(https://www.contributor-covenant.org), version 1.0.0, available at 
+https://contributor-covenant.org/version/1/0/0/.

README.Rmd

@@ -62,8 +62,6 @@ Future releases will include:
 Note that both the features and the prediction must be numeric. The approach is constructed for continuous features. Discrete features may also work just fine with the empirical (conditional) distribution approach.
 Unlike SHAP and TreeSHAP, we decompose probability predictions directly to ease the interpretability, i.e. not via log odds transformations.
 
-All feedback and suggestions are very welcome.
-
 ## Installation
 
 To install the current development version, use
@@ -124,6 +122,15 @@ print(explanation$dt)
 plot(explanation)
 ```
 
+## Contribution
+
+All feedback and suggestions are very welcome. Details on how to contribute can be found 
+[here](./github/CONTRIBUTING.md)
+
+Please note that the 'shapr' project is released with a
+[Contributor Code of Conduct](CODE_OF_CONDUCT.md).
+By contributing to this project, you agree to abide by its terms.
+
 ## References
 
 

README.md

@@ -83,8 +83,6 @@ approach. Unlike SHAP and TreeSHAP, we decompose probability predictions
 directly to ease the interpretability, i.e. not via log odds
 transformations.
 
-All feedback and suggestions are very welcome.
-
 ## Installation
 
 To install the current development version, use
@@ -162,6 +160,15 @@ plot(explanation)
 
 <img src="man/figures/README-basic_example-1.png" width="100%" />
 
+## Contribution
+
+All feedback and suggestions are very welcome. Details on how to
+contribute can be found [here](./github/CONTRIBUTING.md)
+
+Please note that the ‘shapr’ project is released with a [Contributor
+Code of Conduct](CODE_OF_CONDUCT.md). By contributing to this project,
+you agree to abide by its terms.
+
 ## References
 
 <div id="refs" class="references">