Update docs slack->chat

Change-Id: I9edf291a7888b737bbdba218bc04bd1c2e9e2f90
Signed-off-by: Ry Jones <[email protected]>

Author: ryjones

README.md

@@ -38,7 +38,7 @@ Full details of how to contribute to this project are documented [here](http://h
 
 [Hyperledger mailing lists and archives](http://lists.hyperledger.org/)
 
-[Hyperledger Slack](http://hyperledgerproject.slack.com) - if you need an invitation, try our [Slack inviter](https://slack.hyperledger.org)
+[Hyperledger Chat](http://chat.hyperledger.org/channel/fabric)
 
 [Hyperledger Wiki](https://wiki.hyperledger.org/)
 

docs/CONTRIBUTING.md

@@ -30,20 +30,19 @@ into the window and press 'Add'.
 If you are looking for something to work on, or need some expert assistance in
 debugging a problem or working out a fix to an issue, our
 [community](https://www.hyperledger.org/community) is always eager to help. We
-hang out on [Slack](https://hyperledgerproject.slack.com/), IRC (#hyperledger on
-freenode.net) and the [mailing lists](http://lists.hyperledger.org/). Most of us
-don't bite :grin: and will be glad to help. The only silly question is the one
-you don't ask. Questions are in fact a great way to help improve the project as
-they highlight where our documentation could be clearer.
+hang out on [Chat](https://chat.hyperledger.org/channel/fabric/), IRC
+(#hyperledger on freenode.net) and the [mailing lists](http://lists.hyperledger.org/).
+Most of us don't bite :grin: and will be glad to help. The only silly question
+is the one you don't ask. Questions are in fact a great way to help improve the
+project as they highlight where our documentation could be clearer.
 
 ## Requirements and Use Cases
 
 We have a [Requirements
 WG](https://wiki.hyperledger.org/groups/requirements/requirements-wg) that is
 documenting use cases and from those use cases deriving requirements. If you are
 interested in contributing to this effort, please feel free to join the
-discussion in
-[slack](https://hyperledgerproject.slack.com/messages/requirements/).
+discussion in [chat](https://chat.hyperledger.org/channel/requirements/).
 
 ## Reporting bugs
 
@@ -53,7 +52,7 @@ sufficient information for someone else to reproduce the issue. One of the
 project's maintainers should respond to your issue within 24 hours. If not,
 please bump the issue with a comment and request that it be reviewed. You can
 also post to the `#fabric-maintainers` channel in
-[slack](https://hyperledgerproject.slack.com/messages/requirements/).
+[chat](https://chat.hyperledger.org/channel/fabric-maintainers).
 
 ## Fixing issues and working stories
 

docs/Gerrit/gerrit.md

@@ -5,7 +5,7 @@ through the Gerrit review system.
 
 Please be sure that you are subscribed to the [mailing
 list](http://lists.hyperledger.org/mailman/listinfo/hyperledger-fabric) and of
-course, you can reach out on [Slack](https://hyperledgerproject.slack.com/) if
+course, you can reach out on [chat](https://chat.hyperledger.org/) if
 you need help.
 
 Gerrit assigns the following roles to users:

docs/index.md

@@ -48,7 +48,7 @@ Project's Technical Steering Committee (TSC).
 
 ## Communication <a name="communication"></a>
 
-We use [Hyperledger Slack](https://slack.hyperledger.org/) for communication and
+We use [Hyperledger chat](https://chat.hyperledger.org/) for communication and
 Google Hangouts&trade; for screen sharing between developers. Our development
 planning and prioritization is done in [JIRA](https://jira.hyperledger.org),
 and we take longer running discussions/decisions to the
@@ -62,7 +62,7 @@ project not answered in this documentation, please use
 [StackOverflow](http://stackoverflow.com/questions/tagged/hyperledger). If you
 need help finding things, please don't hesitate to send a note to the
 [mailing list](http://lists.hyperledger.org/mailman/listinfo/hyperledger-fabric),
-or ask on [Slack]((https://slack.hyperledger.org/)).
+or ask on [chat]((https://chat.hyperledger.org/)).
 
 # Hyperledger Fabric Documentation