doc(*): Replace references to IRC/Freenode with Slack

Author: krancour

CONTRIBUTING.md

@@ -27,7 +27,7 @@ Our official support channels are:
   - registry: https://github.com/deis/registry/issues
   - router: https://github.com/deis/router/issues
   - All other public [Deis repositories][repos]
-- IRC: #[deis](irc://irc.freenode.org:6667/#deis) IRC channel on freenode.org
+- The [Deis #community Slack channel](https://slack.deis.io)
 
 ## Getting Started
 

src/contributing/maintainers.md

@@ -43,7 +43,7 @@ The duties of a core maintainer include:
 * Classify and respond to GitHub issues and review pull requests
 * Help to shape the Deis roadmap and lead efforts to accomplish roadmap milestones
 * Participate actively in feature development and bug fixing
-* Answer questions and help users in IRC
+* Answer questions and help users in the [Deis #community Slack channel](https://slack.deis.io)
 
 The current core maintainers of Deis:
 * Chris Armstrong - <carmstrong@engineyard.com> ([@carmstrong](https://github.com/carmstrong))
@@ -81,7 +81,7 @@ core maintainers in guiding the future of Deis.
 Generally, potential contributing maintainers are selected by the Deis core maintainers based in
 part on the following criteria:
 * Sustained contributions to the project over a period of time (usually months)
-* A willingness to help Deis users on GitHub and in IRC
+* A willingness to help Deis users on GitHub and in the [Deis #community Slack channel](https://slack.deis.io)
 * A friendly attitude :)
 
 The Deis core maintainers must unanimously agree before inviting a community member to join as a

src/contributing/overview.md

@@ -12,7 +12,7 @@ We are always looking to improve and expand our documentation. Most docs reside
 
 ## Contribute Code
 
-We are always looking for help improving the core platform, other workloads, tooling, and test coverage. Interested in contributing code? Let’s chat in IRC. Make sure to check out issues tagged [easy-fix][].
+We are always looking for help improving the core platform, other workloads, tooling, and test coverage. Interested in contributing code? Let’s chat in the [Deis #community Slack channel](https://slack.deis.io). Make sure to check out issues tagged [easy-fix][].
 
 When you're ready to begin writing code, review [Design Documents][dd] and get your [Development Environment][dev-environment] set up.
 
@@ -22,7 +22,7 @@ If you don't have time to code, consider helping with triage. The community will
 
 ## Share your Experience
 
-Interact with the community on our user mailing list or live in our IRC channel, \#deis on Freenode, where you can chat with other Deis users any time of day.
+Interact with the community on our user mailing list or live in our [Deis #community Slack channel](https://slack.deis.io), where you can chat with other Deis Workflow users any time of day.
 
 [workflow]: https://github.com/deis/workflow
 [dd]: design-documents.md

src/roadmap/planning-process.md

@@ -22,7 +22,7 @@ The Roadmap gets delivered progressively via the [Release Schedule][].  Releases
 
 Major decisions affecting the Roadmap are discussed during Release Planning Meetings on the first Thursday of each month, aligned with the [Release Schedule][].
 
-Release Planning Meetings are open to the public with access coordinated via the #deis IRC channel on Freenode.
+Release Planning Meetings are open to the public with access coordinated via the [Deis #community Slack channel](https://slack.deis.io).
 Notes from past meetings are below, along with links to a recording of the entire meeting on YouTube.
 
 ## Credits