Adding welcome bot + fix links to slack (#567)

* Adding configuration for the welcome bot.
* Update link to the ISC slack instance.
* Stop checking link to chatham house rule (as it always gets reported as broken, even though it is not).

Author: spier

.github/ISSUE_TEMPLATE/config.yml

@@ -1,7 +1,7 @@
 blank_issues_enabled: true
 contact_links:
   - name: Slack
-    url: https://innersourcecommons-inviter.herokuapp.com
+    url: https://innersourcecommons.org/slack
     about: Join our Community on Slack for help and a casual chat.
   - name: Patterns Book
     url: https://patterns.innersourcecommons.org

.github/config.yml

@@ -0,0 +1,44 @@
+# 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: >
+  [![Welcome Banner](https://zenodo.org/api/iiif/v2/0c0188d3-d03c-4830-a6e3-00405f5c22fa:8ff47a85-7250-4d86-8e48-2f346b48b2c1:BannerWelcome.jpg/full/750,/0/default.jpg)](https://zenodo.org/record/3695300)
+
+  :tada: Welcome to _The InnerSource Commons_ community, and in particular to our patterns! :tada:
+  We're really excited to have your input into the project! :sparkling_heart:
+
+  <br>If you haven't done so already, please check out our [Contributing Guidelines](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/CONTRIBUTING.md).
+  If you need to connect more synchronously with members of _The InnerSource Commons_ community, come chat with us in our [Slack workspace](https://innersourcecommons.org/slack).
+
+# 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: >
+  [![Thank You Banner](https://zenodo.org/api/iiif/v2/0c0188d3-d03c-4830-a6e3-00405f5c22fa:7fbd97cf-283b-480c-b8e1-11866e26245c:BannerThanks.jpg/full/750,/0/default.jpg)](https://zenodo.org/record/3695300)
+
+  :sparkling_heart: Thanks for opening this pull request! :sparkling_heart:
+  _The InnerSource Commons_ community really appreciates your time and effort to contribute to the project.
+  Please make sure you have read our [Contributing Guidelines](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/CONTRIBUTING.md).
+
+  If you are submitting a new pattern, the following things will help get your pull request across the finish line! :checkered_flag:
+
+  - Check you have used our [pattern template](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/meta/pattern-template.md) and removed any placeholder text and sections that your pattern did not need.
+
+  - We will run a number of automated checks on your PR. Please review the output of those checks on the PR itself, and see if any issues got flagged that you can fix yourself.
+
+  - Make sure you have added your new pattern to the list of patterns in the main [README.md](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/README.md). If you are unsure where to add your pattern, no worries. Just let us know on the PR and we will help you.
+
+  <br>This project has a small number of maintainers, volunteering their time to this project. So please be patient and we will get back to you as soon as we can.
+  If we don't acknowledge this pull request after 7 days, feel free to chat to us about it in our [Slack workspace](https://innersourcecommons.org/slack).
+
+# 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: >
+  [![Congratulations Banner](https://zenodo.org/api/iiif/v2/0c0188d3-d03c-4830-a6e3-00405f5c22fa:32fbdb89-ae1b-434e-830c-88ade86724cc:BannerCongratulations.jpg/full/750,/0/default.jpg)](https://zenodo.org/record/3695300)
+
+  Congrats on merging your first pull request! :tada:
+  We here at _The InnerSource Commons_ are proud of you! :sparkling_heart:
+  Thank you so much for your contribution :gift:

.lycheeignore

@@ -4,8 +4,9 @@ https://example.com/link/to/your/trusted/committer/documentation.md
 https://github.com/rcs/rcs-viewer/pull/81
 http://creativecommons.org/licenses
 https://isc-inviter.herokuapp.com
+https://innersourcecommons-inviter.herokuapp.com
 fearlesschangepatterns.com
 https://ulir.ul.ie/bitstream/handle/10344/4443/Stol_2014_inner.pdf
 .*@andrew.clegg.*
 https://m.dotdev.co/how-to-write-a-readme-that-rocks-bc29f279611a
-https://innersourcecommons-inviter.herokuapp.com
+https://www.chathamhouse.org/about-us/chatham-house-rule

CONTRIBUTING.md

@@ -29,7 +29,7 @@ We are happy to support you in contributing to the InnerSource patterns or to ju
 
 You can best reach out to us **via Slack**:
 
-Join the InnerSource Commons [Slack instance](https://isc-inviter.herokuapp.com/) and enter the `#innersource-patterns` channel there.
+Join the InnerSource Commons [Slack instance](https://innersourcecommons.org/slack) and enter the `#innersource-patterns` channel there.
 
 ## License of Contributions
 

meta/FAQ.md

@@ -17,5 +17,5 @@ This is a list of frequently asked questions about InnerSource Patterns.
 
 ## I'd like to consult with the InnerSource Patterns community; do I need to have participating members sign NDAs?
 
-* The vast majority of InnerSource Patterns meetings and all conversations in the InnerSource Commons [Slack](https://isc-inviter.herokuapp.com/) are held under the [Chatham House Rule](https://www.chathamhouse.org/chatham-house-rule) that should provide sufficient protection to enable a productive discussion.
+* The vast majority of InnerSource Patterns meetings and all conversations in the InnerSource Commons [Slack](https://innersourcecommons.org/slack) are held under the [Chatham House Rule](https://www.chathamhouse.org/about-us/chatham-house-rule) that should provide sufficient protection to enable a productive discussion.
 * To answer the question directly: No, you don't have to get NDAs signed :)