Add contribution guidelines and set up sentimentBot and welcomeBot

Author: Adam Richie-Halford

.github/config.yml

@@ -0,0 +1,37 @@
+# Configuration for sentiment-bot - https://github.com/behaviorbot/sentiment-bot
+
+# *Required* toxicity threshold between 0 and .99 with the higher numbers being the most toxic
+# Anything higher than this threshold will be marked as toxic and commented on
+sentimentBotToxicityThreshold: .7
+
+# *Required* Comment to reply with
+sentimentBotReplyComment: >
+  SentimentBot thinks that this comment is toxic. Perhaps SentimentBot got it wrong. But then again, maybe you did.
+  
+  Please reread your comment and take advantage of any opportunities to "turn down the temperature." We want the Cloudknot community to be inclusive and welcoming. Please be respectful of other users and think about ways to communicate the same message in a more delicate manner. cc/ @richford
+
+#=======================================================================
+
+# Configuration for welcome - https://github.com/behaviorbot/welcome
+
+# Configuration for new-issue-welcome - https://github.com/behaviorbot/new-issue-welcome
+
+# Comment to be posted to on first time issues
+newIssueWelcomeComment: >
+  👋 Thanks for opening your first issue here! We appreciate your help making Cloudknot better.
+
+# Configuration for new-pr-welcome - https://github.com/behaviorbot/new-pr-welcome
+
+# Comment to be posted to on PRs from first time contributors in your repository
+newPRWelcomeComment: >
+  Thanks for opening this pull request! Please check out our contributing guidelines.
+
+# Configuration for first-pr-merge - https://github.com/behaviorbot/first-pr-merge
+
+# Comment to be posted to on pull requests merged by a first time user
+firstPRMergeComment: >
+  Congrats on merging your first pull request! We're proud of you! 🎉🎉🎉
+
+# It is recommended to include as many gifs and emojis as possible!
+
+#=======================================================================

CONTRIBUTING.md

@@ -0,0 +1,53 @@
+# Contributing
+
+Contributions are welcome, and they are greatly appreciated! Every little bit
+helps, and credit will always be given.
+
+You can contribute in many ways:
+
+## Types of Contributions
+
+### Report Bugs
+
+Report bugs at https://github.com/richford/cloudknot/issues.
+
+If you are reporting a bug, please include:
+
+- Your operating system name and version.
+- Any details about your local setup that might be helpful in troubleshooting.
+- Detailed steps to reproduce the bug.
+
+### Work on "good first issues"
+
+Look through the GitHub issues for anything labelled "good first issue." These
+are issues that we think would be especially appropriate for those new to
+open-source software contribution.
+
+### Fix Bugs
+
+Look through the GitHub issues for bugs. Anything tagged with "bug" and "help
+wanted" is open to whoever wants to implement it.
+
+### Implement Features
+
+Look through the GitHub issues for features. Anything tagged with "enhancement"
+and "help wanted" is open to whoever wants to implement it.
+
+### Write Documentation
+
+Cloudknot could always use more documentation, whether as part of the
+official afq-insight docs, in docstrings, or even on the web in blog posts,
+articles, and such.
+
+### Submit Feedback
+
+The best way to send feedback is to file an issue at
+https://github.com/richford/cloudknot/issues.
+
+If you are proposing a feature:
+
+- Explain in detail how it would work.
+- Keep the scope as narrow as possible, to make it easier to implement.
+- Remember that this is a volunteer-driven project, and that contributions
+  are welcome :)
+

README.md

@@ -1,4 +1,5 @@
-## cloudknot
+# cloudknot
+
 [![Build Status](https://travis-ci.org/richford/cloudknot.svg?branch=master)](https://travis-ci.org/richford/cloudknot)
 [![DOI](https://zenodo.org/badge/102051437.svg)](https://zenodo.org/badge/latestdoi/102051437)
 
@@ -10,3 +11,48 @@ This is the cloudknot development site. You can view the source code, file new
 issues, and contribute to cloudknot's development. If you are just getting
 started, you should look at the
 [cloudknot documentation](https://richford.github.io/cloudknot/).
+
+
+## Contributing
+
+We love contributions! Cloudknot is open source, built on open source,
+and we'd love to have you hang out in our community.
+
+We have developed some [guidelines](CONTRIBUTING.md) for contributing to
+AFQ-Insight.
+
+**Imposter syndrome disclaimer**: We want your help. No, really.
+
+There may be a little voice inside your head that is telling you that
+you're not ready to be an open source contributor; that your skills
+aren't nearly good enough to contribute. What could you possibly offer a
+project like this one?
+
+We assure you - the little voice in your head is wrong. If you can
+write code at all, you can contribute code to open source. Contributing
+to open source projects is a fantastic way to advance one's coding
+skills. Writing perfect code isn't the measure of a good developer (that
+would disqualify all of us!); it's trying to create something, making
+mistakes, and learning from those mistakes. That's how we all improve,
+and we are happy to help others learn.
+
+Being an open source contributor doesn't just mean writing code, either.
+You can help out by writing documentation, tests, or even giving
+feedback about the project (and yes - that includes giving feedback
+about the contribution process). Some of these contributions may be the
+most valuable to the project as a whole, because you're coming to the
+project with fresh eyes, so you can see the errors and assumptions that
+seasoned contributors have glossed over.
+
+
+## Credits
+
+This package was created with
+[shablona](https://github.com/uwescience/shablona).
+
+The imposter syndrome disclaimer was originally written by
+[Adrienne Lowe](https://github.com/adriennefriend) for a [PyCon
+talk](https://www.youtube.com/watch?v=6Uj746j9Heo), and was
+adapted based on its use in the README file for the [MetPy
+project](https://github.com/Unidata/MetPy).
+